It's all about the answers!

Ask a question

Cannot save artifacts in CLM applications and database connection is repeatedly closed when using Oracle RAC environment behind firewall


Sudarsha Wijenayake (1111) | asked Jun 26 '12, 11:45 a.m.
JAZZ DEVELOPER
Ability to save artifacts in CLM applications (JTS, RTC, RQM and RRC) is lost and the jazz logs are filled with many instances of the following error when utilizing an Oracle11g RAC environment behind a firewall: CRJAZ1411E Database connection has been closed. The particular Oracle RAC environment and the CLM applications are located in the same premises and therefore, no remote communication is attempted. However, the Oracle RAC environment is in a different network zone (than the CLM applications) and is hosted behind a firewall with just the port 1521 open.

Setting the "Enable JDBC Connection Keep Alive Service" property to "true" on the advanced properties page of JTS, RQM, and RRC from 60 minutes (default) to a lower value such as 5 minutes as suggested in the following work item on jazz.net did NOT resolve the issue: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=172854.

One answer



permanent link
Sudarsha Wijenayake (1111) | answered Jun 26 '12, 11:47 a.m.
JAZZ DEVELOPER
The above mentioned issue was resolved in the following manner by allowing the use of Oracle RAC environment behind the firewall for CLM applications. The jazz application connection pool size was set to a value (128) less than its corresponding value set on the database side (unlimited). In addition, the jazz application connection timeout was also set to a value (6000 millisecond) less than what had been set for the database firewall connection timeout (1 hour). Furthermore, the following parameter was included into the JDBC connection string: ENABLE=BROKEN. Finally, the KeepAliveTime property on the application server host was changed from the default (2 hrs) to a value less than the firewall connection timeout (30 minutes). The CLM applications had started to communicate properly with the Oracle RAC environment behind the firewall and the particular issue had disappeared after completing the above steps.

The following Oracle documentation provides suggestions for utilizing JDBC on an Oracle server hosted behind a firewall: http://docs.oracle.com/cd/E11882_01/java.112/e16548/apxtblsh.htm#CHDBBDDA

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.