My JIRA server 7 is not working. Sometimes it shutdown itself. Here is my catalina log file says.
15-May-2018 00:13:41.685 WARNING [https-jsse-nio-443-exec-112] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.abccompany.com/rest/issueNav/1/issueTable/stable, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
>>>>>> The above error I see from the start of the day
After that I see this error
15-May-2018 00:13:53.279 INFO [Thread-568821] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-80"]
18-May-2018 00:13:53.326 WARNING [https-jsse-nio-443-exec-44] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.abccompany.com/rest/issueNav/latest/preferredSearchLayout, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
15-May-2018 00:13:53.342 INFO [Thread-568821] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["https-jsse-nio-443"]
15-May-2018 00:13:53.404 INFO [Thread-568821] org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina
15-May-2018 00:18:26.358 WARNING [main] org.apache.tomcat.util.net.SSLHostConfig.setProtocols The protocol [TLSv1.1] was added to the list of protocols on the SSLHostConfig named [_default_]. Check if a +/- prefix is missing.
15-May-2018 00:18:26.358 WARNING [main] org.apache.tomcat.util.net.SSLHostConfig.setProtocols The protocol [TLSv1.2] was added to the list of protocols on the SSLHostConfig named [_default_]. Check if a +/- prefix is missing.
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.6
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Oct 6 2016 20:15:31 UTC
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.6.0
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2012
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 6.2
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: D:\Atlassian\JIRA\jre
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_102-b14
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: D:\Atlassian\JIRA
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: D:\Atlassian\JIRA
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=D:\Atlassian\JIRA
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=D:\Atlassian\JIRA
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=D:\Atlassian\JIRA\temp
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=D:\Atlassian\JIRA\conf\logging.properties
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxPermSize=7172m
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.debug=true
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms256m
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx7172m
15-May-2018 00:18:26.373 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\Atlassian\JIRA\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Perl64\site\bin;C:\Perl64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\System Center Operations Manager 2007\;C:\Program Files\NetApp\Windows Host Utilities\;D:\Perforce;C:\Perl64\bin;C:\Program Files\NetApp\MPIO\;;.
15-May-2018 00:18:26.639 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]
15-May-2018 00:18:27.483 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
15-May-2018 00:18:27.483 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-jsse-nio-443"]
15-May-2018 00:18:28.217 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
15-May-2018 00:18:28.217 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2498 ms
15-May-2018 00:18:28.233 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
15-May-2018 00:18:28.233 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.6
15-May-2018 00:23:13.260 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [http-nio-80]
15-May-2018 00:23:13.276 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [https-jsse-nio-443]
15-May-2018 00:23:13.276 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 285070 ms
Your logs are showing no errors, just a warning about a servlet that isn't a significant problem.
Could you read the application log to see what it is doing? Atlassian-jira.log in the logs directory in jira-home
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.