Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Software 7.9 upgrade error: java.lang.ClassNotFoundException error

Madhava Bharadwaj
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 18, 2018

Hi,

We just finished JIRA Software 7.9 upgrade, and replaced below files latest version with old version before restart. When restarting JIRA application is not coming up. Please help.

Error in catalina.log

18-Apr-2018 11:02:59.358 WARNING [main] org.apache.tomcat.util.IntrospectionUtils.setProperty IntrospectionUtils: InvocationTargetException for class org.apache.catalina.connector.Connector address=172.28.127.103)
java.lang.reflect.InvocationTargetException

Regards,

Madhava

1 answer

0 votes
Tzu Hau Chai
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 18, 2018

Is the process running and did Tomcat actually manage to bind to the port successfully? Try going through this KB: https://confluence.atlassian.com/jirakb/how-to-check-the-jira-application-is-running-794499415.html

Madhava Bharadwaj
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 19, 2018

Hi Tzu Hau Chai,

Thank you for the reply.

We merged the 7.2 server.xml with 7.9 server.xml and it is working only if we use protocol="HTTP/1.1" but not with protocol="org.apache.coyote.http11.Http11NioProtocol". May be this will create unsecure connections. Please suggest.

 

<Connector address="xx.xx.xx.xx" port="8443" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
SSLEnabled="true" clientAuth="false" sslProtocol="TLS"
keyAlias="xxx" keystoreFile="/www/atlassian/jira/conf/jira.jks" keystorePass="xxx" keystoreType="JKS"
proxyName="xxxx" proxyPort="443"/>

Tzu Hau Chai
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 19, 2018

The protocol="HTTP/1.1" parameter enables auto switching between BIO/NIO/APR protocol, I don't think it affects whether it accepts secure/unsecure connections. As long as you set the scheme = "https" parameter the connector should only accept secure connections.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events