Batch notifications are not working when using Oracle database
This article only applies to Atlassian's server products. Learn more about the differences between cloud and server.
After upgrading or installing Jira 8.++, and turning on Batch Notifications, notifications are never sent at all.
The following exception appears in
atlassian-jira.log thrown by the
JIRA-INFORM-Thread which is used by the Batch Notifications plugin.
2020-01-09 09:54:45,901+0100 JIRA-INFORM-Thread-1 WARN anonymous 455x660x1 1iwbmex x.x.x.x /secure/QuickCreateIssue.jspa [o.a.commons.dbcp2.BasicDataSource] An internal object pool swallowed an Exception. java.sql.SQLException: Protocol violation: [ 0, ] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:669) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249) at oracle.jdbc.driver.T4C7Ocommoncall.doOROLLBACK(T4C7Ocommoncall.java:66) at oracle.jdbc.driver.T4CConnection.doRollback(T4CConnection.java:906) at oracle.jdbc.driver.PhysicalConnection.rollback(
Using Jira 8.+ and Oracle database.
Checking from the database, the batch notification event table
AO_733371_EVENT does not return any row. Which means the batch notification events are never generated.
SQL> select * from AO_733371_EVENT; no rows selected
SQLException: Protocol violation itself is normally caused by the Oracle driver. Therefore, first please ensure that you've used the correct Database JDBC Driver in your Jira instance.
As stated on our Supported platforms we require Oracle JDBC 19.3 driver to be used with Oracle database.
- Download the correct Oracle driver JDBC 19.3 (ojdbc8.jar)
- Update your JDBC driver by copying the driver JAR file to the
$JIRA_INSTALL/libfolder in your Jira installation. Make sure the old driver is moved out of this folder.
- Restart Jira.