Forums

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

Jira is not coming up after 7.12.0 upgrade

Rahul Singhal December 6, 2018

Hi team,

 i need your help, we were upgrading our jira server from 7.0.0 to 7.12.0 with Ansible scripts and now jira service is not coming up. Below is the catalina.out logs

 

2018-12-06 15:54:45,816 localhost-startStop-1 INFO [c.a.j.c.cache.ehcache.ReplicatorFactory] [Cache-replication] Cache replication using default cache replicator: LocalQCacheReplicator
2018-12-06 15:54:45,921 localhost-startStop-1 INFO [c.a.jira.startup.DatabaseLauncher] Database transactions enabled: true
2018-12-06 15:54:45,921 localhost-startStop-1 INFO [c.a.jira.startup.DatabaseLauncher] Using JIRA's default for database transaction isolation level: 2
2018-12-06 15:54:45,924 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger]

Database configuration OK

___ Database Configuration _________________

Loading entityengine.xml from : file:/Applications/jira/atlassian-jira-software-7.12.0-standalone/atlassian-jira/WEB-INF/classes/entityengine.xml
Entity model field type name : oracle10g
Entity model schema name :
Database Version : Oracle - Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics, Real Application Testing and Unified Auditing options
Database Driver : Oracle JDBC driver - 12.2.0.1.0
Database URL : jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST= vsoraalt-12c-scan.mid.aib.pri)(PORT=9010))(ADDRESS=(PROTOCOL=TCP)(HOST= vsoraomt-12c-scan.mid.aib.pri)(PORT=9010))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ETHSYSJIRA)))
Database JDBC config : oracle10g jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST= vsoraalt-12c-scan.mid.aib.pri)(PORT=9010))(ADDRESS=(PROTOCOL=TCP)(HOST= vsoraomt-12c-scan.mid.aib.pri)(PORT=9010))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ETHSYSJIRA)))

2018-12-06 15:54:45,950 localhost-startStop-1 ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.NullPointerException
at com.atlassian.jira.cluster.zdu.DefaultNodeBuildInfoFactory.create(DefaultNodeBuildInfoFactory.java:31)
at com.atlassian.jira.startup.ClusterNodeVersionCheckLauncher.lambda$verifyVersionOfNodeJoiningStableCluster$0(ClusterNodeVersionCheckLauncher.java:110)
at com.atlassian.jira.startup.ClusterNodeVersionCheckLauncher$$Lambda$307/970474951.test(Unknown Source)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at com.atlassian.jira.startup.ClusterNodeVersionCheckLauncher.verifyVersionOfNodeJoiningStableCluster(ClusterNodeVersionCheckLauncher.java:111)
at com.atlassian.jira.startup.ClusterNodeVersionCheckLauncher.start(ClusterNodeVersionCheckLauncher.java:59)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:142)
at com.atlassian.jira.startup.DefaultJiraLauncher$$Lambda$100/698338287.run(Unknown Source)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:304)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:199)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:135)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:102)
at com.atlassian.jira.startup.DefaultJiraLauncher$$Lambda$24/781585390.run(Unknown Source)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:100)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuffInBackground(LauncherContextListener.java:139)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:101)
... 5 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
2018-12-06 15:54:45,953 localhost-startStop-1 INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 346 MiB. Committed: 1318 MiB. Max: 1973 MiB
Non-heap memory : Used: 90 MiB. Committed: 93 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 437 MiB. Committed: 1410 MiB. Max: 3237 MiB
---------------------------------------------------------------------------------
06-Dec-2018 15:54:46.116 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-10080"]
06-Dec-2018 15:54:46.130 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-jsse-nio-10443"]
06-Dec-2018 15:54:46.140 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 31863 ms
2018-12-06 15:54:46,299 https-jsse-nio-10443-exec-4 ERROR anonymous 954x1x1 - 10.28.181.163 /secure/errors.jsp [c.atlassian.instrumentation.Instrument] Unable to snapshot thread local operations (implementation of OpTimerFactory is not a ThreadLocalOpTimerFactory): null
2018-12-06 15:54:46,327 https-jsse-nio-10443-exec-4 WARN anonymous 954x1x1 - 10.28.181.163 /secure/errors.jsp [c.a.jira.security.JiraSecurityFilter] Rejecting security-sensitive request that bypassed Johnson filter: /secure/errors.jsp
2018-12-06 16:20:05,030 https-jsse-nio-10443-exec-1 WARN anonymous 980x55x1 - 10.255.90.53 /secure/errors.jsp [c.a.jira.security.JiraSecurityFilter] Rejecting security-sensitive request that bypassed Johnson filter: /secure/errors.jsp
2018-12-06 16:24:19,843 commons-pool-EvictionTimer WARN [o.a.commons.dbcp2.BasicDataSource] An internal object pool swallowed an Exception.
java.lang.NegativeArraySizeException
at oracle.net.ano.CryptoNIONSDataChannel.readDataFromSocketChannel(Unknown Source)
at oracle.jdbc.driver.T4CMAREngineNIO.prepareForReading(T4CMAREngineNIO.java:98)
at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalUB1(T4CMAREngineNIO.java:534)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:485)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
at oracle.jdbc.driver.T4C7Ocommoncall.doOLOGOFF(T4C7Ocommoncall.java:62)
at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:908)
at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:2005)
at org.apache.commons.dbcp2.DelegatingConnection.closeInternal(DelegatingConnection.java:235)
at org.apache.commons.dbcp2.PoolableConnection.reallyClose(PoolableConnection.java:243)
at org.apache.commons.dbcp2.PoolableConnectionFactory.destroyObject(PoolableConnectionFactory.java:334)

1 answer

0 votes
Casey Daniell
Contributor
December 6, 2018

Read through these release notes about the Oracle JDBC driver no longer coming with JIRA, https://confluence.atlassian.com/jiracore/jira-core-7-7-x-upgrade-notes-941610917.html, 

 

On a side note the Upgrade notes, https://confluence.atlassian.com/jiracore/jira-core-release-notes-781386726.html, have other random changes sprinkeled through them that maybe affecting you too, since your jumping form 7.0.0 to 7.12.x you should read through them for other gotchas. 

Rahul Singhal December 6, 2018

Hi Casey,

Thanks or your reply.

I wen through all the upgrade notes and downloaded JDBC driver version 12.2.0.1. from Oracle site and done the required changes in Ansible script.

After done all the changes when I try to start jira it is not coming up

Rahul Singhal December 7, 2018

Hi Casey,

 

Can you help me further.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events