Hi All,
our jira was down frequently...
is any one know where / which log i need to look to get the reason..
after restart it worknig fine.
could you share the major reasons for jira down
Thanks advance,
Rajesh
As Nic says. In addition you can set a "validation-query", as per https://confluence.atlassian.com/display/JIRA/Surviving+Connection+Closures, which will allow it to get past little glitches.
However better to deal with the underlying problem.
I'd start with the catalina.out log followed by the jira logs.
Location of the first depends on your os and how you configured your JIRA to work (stand alone or server). The second is in {JIRA_HOME}/log
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i found following 3 error in the log files, is it familiar to you...
could you confirm which one is the reason:
WARNING: processCallbacks status 2
Feb 19, 2014 9:44:42 AM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Feb 19, 2014 9:44:48 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 19, 2014 9:44:48 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 19, 2014 9:44:48 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Feb 19, 2014 9:45:14 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/ci/jira/bin/jre/lib/amd64/server:/opt/ci/jira/bin/jre/lib/amd64:/opt/ci/jira/bin/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Feb 19, 2014 9:45:14 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Caused by: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That usually means a problem with your database connection - check the networking - routes, downtime, slowness etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.