Jira server startup fails with protocol violation error
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
Starting up JIRA fails.
Attempting to generate an XML backup fails.
DVCS synchronisation failed on some GitHub repositories.
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
F2014-07-22 17:07:47,821 localhost-startStop-1 ERROR [jira.bc.dataimport.DefaultExportService] Error during XML backup.
org.ofbiz.core.entity.GenericTransactionException: Error occurred while rolling back transaction. (Protocol violation)
at org.ofbiz.core.entity.TransactionUtil.rollbackLocalTransaction(TransactionUtil.java:390)
at com.atlassian.core.ofbiz.util.CoreTransactionUtil.rollback(CoreTransactionUtil.java:54)
at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.cleanUpAfterEntity(DefaultSaxEntitiesExporter.java:196)
at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntity(DefaultSaxEntitiesExporter.java:163)
at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntities(DefaultSaxEntitiesExporter.java:108)
at com.atlassian.jira.bc.dataimport.DefaultExportService.exportJIRA(DefaultExportService.java:202)
at com.atlassian.jira.bc.dataimport.DefaultExportService.export(DefaultExportService.java:88)
at com.atlassian.jira.bc.dataimport.DefaultExportService.export(DefaultExportService.java:70)
at com.atlassian.jira.bean.export.AutoExportImpl.exportData(AutoExportImpl.java:95)
at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:387)
at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:346)
at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:106)
at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:54)
at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:42)
at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:133)
...
java.sql.SQLException: Protocol violation
at oracle.jdbc.driver.T4CTTIfun.readRXH(T4CTTIfun.java:541)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:328)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
at oracle.jdbc.driver.T4C7Ocommoncall.doOROLLBACK(T4C7Ocommoncall.java:68)
at oracle.jdbc.driver.T4CConnection.doRollback(T4CConnection.java:649)
at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:3893)
at org.apache.commons.dbcp.DelegatingConnection.rollback(DelegatingConnection.java:368)
at org.apache.commons.dbcp.DelegatingConnection.rollback(DelegatingConnection.java:368)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.rollback(PoolingDataSource.java:323)
at org.ofbiz.core.entity.jdbc.interceptors.connection.DelegatingConnection.rollback(DelegatingConnection.java:75)
at org.ofbiz.core.entity.TransactionUtil.rollbackLocalTransaction(TransactionUtil.java:385)
at com.atlassian.core.ofbiz.util.CoreTransactionUtil.rollback(CoreTransactionUtil.java:54)
Diagnosis
An Oracle database is being used.
Cause
This appears to be caused by a number of problems:
Improper permissions assigned to the database user.
Improperly configured
dbconfig.xml.Problems with the JDBC driver.
The oracle password is close to expiry.
There is a configuration issue with a 64-bit JVM (http://javatoj2ee.wordpress.com/2013/06/29/java-sql-sqlexception-protocol-violation/).
Solution
Resolution
Check the permissions are configured exactly as per Connecting JIRA to Oracle. If more permissions are provided than should be this is known to cause problems.
Ensure the
dbconfig.xmlis configured as per Connecting JIRA to Oracle.Verify the password is not going to expire soon.
Stop JIRA. Remove the Oracle JDBC file from <JIRA-INSTALL-DIR>/lib, download the latest ojdbc.jar (such as 12.1.0.2.0) from http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html and copy it to <JIRA-INSTALL-DIR>/lib. Start JIRA after that.
Was this helpful?