We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

OC webservice 3.9.1 can't work!!

dear group:
I deploying OC is fine, but OC webservice 3.9.1 can't work. And tomcat's log file appear:

Feb 24, 2016 3:18:05 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat/webapps/OpenClinica-ws.war
Feb 24, 2016 3:18:10 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://code.google.com/p/jmesa is already defined
Feb 24, 2016 3:18:51 AM liquibase.database.template.JdbcTemplate comment
INFO: Lock Database
Feb 24, 2016 3:18:51 AM liquibase.lock.LockHandler acquireLock
INFO: Successfully acquired change log lock
Feb 24, 2016 3:18:57 AM liquibase.database.AbstractDatabase getRanChangeSetList
INFO: Reading from databasechangelog
Feb 24, 2016 3:18:59 AM liquibase.database.template.JdbcTemplate comment
INFO: Release Database Lock
Feb 24, 2016 3:18:59 AM liquibase.lock.LockHandler releaseLock
INFO: Successfully released change log lock
Feb 24, 2016 3:19:00 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
Feb 24, 2016 3:19:00 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/OpenClinica-ws] startup failed due to previous errors
Feb 24, 2016 3:19:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/OpenClinica-ws] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Feb 24, 2016 3:19:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/OpenClinica-ws] appears to have started a thread named [[email protected]] but has failed to stop it. This is very likely to create a memory leak.
Feb 24, 2016 3:19:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/OpenClinica-ws] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
Feb 24, 2016 3:19:00 AM org.apache.catalina.startup.HostConfig deployDirectory


I added JAVA_OPTS='-server -d64 -Xms2g -Xmx20g -XX:PermSize=1g -XX:MaxPermSize=4g -XX:-UseGCOverheadLimit' to /etc/tomcat/tomcat.conf file.
and modified /var/lib/tomcat/webapps/OpenClinica-ws/WEB-INF/classe
s/datainfo.properties db values and threadCount values, like that:
dbType=postgres
dbUser=clinica
dbPass=clinica
db=openclinica
dbPort=5432
dbHost=localhost
org.quartz.jobStore.misfireThreshold=18000000
# threadCount should be set to zero on web services modules
org.quartz.threadPool.threadCount=0
org.quartz.threadPool.threadPriority=5
who can tell me what's problem with it! thanks in advance!

Comments

  • RCHENURCHENU Posts: 204
    Have you tried modifying the tomcat/openclinica-ws.config/datainfo.properties file ?
  • To RCHENU:
    yes,the tomcat/openclinica-ws.config/datainfo.properties and webapps/OpenClinica-ws/WEB-INF/classes/datainfo.properties is same.




  • tkhajatkhaja Posts: 61 ✭✭
    via Email
    Hi,

    What do you mean by 3.9.1 web services does not work? Are you getting a
    blank white page or a 404 page? Please provide more information on the URL
    you are trying to use for web and web services. I assume you have the
    correct sysURL.

    Regards,
    Thasbiha

    On Wed, Feb 24, 2016 at 9:43 PM, noteasyforyou <
    [email protected]> wrote:

    > OpenClinica https://forums.openclinica.com/
    >
    >
    >
    > noteasyforyou commented on OC webservice 3.9.1 can't work!!
    >
    >
    >
    > To RCHENU:
    >
    > yes,the tomcat/openclinica-ws.config/datainfo.properties and
    > webapps/OpenClinica-ws/WEB-INF/classes/datainfo.properties is same.
    >
    >
    >
    > --
    >
    > To manage your email notifications, please visit:
    > https://www.openclinica.com/forums#/profile/preferences
    >
    >
    >
    > Reply to this email directly or follow the link below to check it out:
    >
    > https://forums.openclinica.com/discussion/comment/17934#Comment_17934
    >
    >
    >
    > Check it out:
    > https://forums.openclinica.com/discussion/comment/17934#Comment_17934
    >
    >
  • TO tkhaja:
    It appear 404 page

    1.png 21.1K
  • tkhajatkhaja Posts: 61 ✭✭
    edited February 2016
    Sounds like a database connection problem. Is the db connection details the same for web and ws meaning do they match in the following files:
    tomcat/openclinica.config/datainfo.properties and
    tomcat/openclinica-ws.config/datainfo.properties?

    dbType=postgres
    dbUser=clinica
    dbPass=clinica
    db=openclinica
    dbPort=5432
    dbHost=localhost

    Please make sure there are no trailing white spaces at the end.

    Regards,
    Thasbiha
  • TO tkhaja
    I checked two files, there are not white spaces at the end of line.
    I attached my datainfo.properties and tomcat log.
  • I think webservice database have been connected.

    Feb 24, 2016 4:01:29 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive /var/lib/tomcat/webapps/OpenClinica-ws.war
    Feb 24, 2016 4:01:34 AM org.apache.catalina.startup.TaglibUriRule body
    INFO: TLD skipped. URI: http://code.google.com/p/jmesa is already defined
    Feb 24, 2016 4:02:03 AM liquibase.database.template.JdbcTemplate comment
    INFO: Lock Database
    Feb 24, 2016 4:02:03 AM liquibase.lock.LockHandler acquireLock
    INFO: Successfully acquired change log lock
    Feb 24, 2016 4:02:09 AM liquibase.database.AbstractDatabase getRanChangeSetList
    INFO: Reading from databasechangelog
    Feb 24, 2016 4:02:11 AM liquibase.database.template.JdbcTemplate comment
    INFO: Release Database Lock
    Feb 24, 2016 4:02:11 AM liquibase.lock.LockHandler releaseLock
    INFO: Successfully released change log lock
    Feb 24, 2016 4:02:12 AM org.apache.catalina.core.StandardContext startInternal
    SEVERE: Error listenerStart
Sign In or Register to comment.