How to initiate BE re-connectivity to a database.
Article ID: KB0087137
Updated On:
| Products | Versions |
|---|---|
| TIBCO Fulfillment Order Management | - |
| Not Applicable | - |
Description
Description:
Orchestrator was not able to reconnect when a database connection was lost. Expected behavior of BusinessEvents is to reconnect to a database after a disconnect.
Orchestrator was not able to reconnect when a database connection was lost. Expected behavior of BusinessEvents is to reconnect to a database after a disconnect.
Issue/Introduction
How to initiate BE re-connectivity to a database.
Resolution
Add properties in cdd file in the cluster section:
<property name="be.backingstore.recreateOnRecovery" value="true"/>
<property name="be.backingstore.test.connections.interval" value="30"/>
Add in the tra file (SOL1-D8QBXH / KB:36218):
TRA-property: java.extended.properties (add parameter below):
-Djava.security.egd=file:///dev/urandom
From the FOM 2.0.1 TIB_af_2.0.1_installation.pdf:
Configuring TRA File for the Database Connectivity
The Oracle JDBC driver has a documented limitation when running on linux 64 bit system. The issue might happen during the login phase, it fails on some systems due to the way the random number generator works. The default random generator can be blocking in some circumstances and prevent JDBC to connect to the database. The workaround is to use the urandom generator that is not blocking.
Set the JVM-level property in the BE 5.1.1 TRA file.
• Go to the $BE_HOME/bin/be-engine.tra location.
• Append the property -Djava.security.egd=file:///dev/./urandom to the java.extended code of the relevant 64 bit jvm property. For example:
java.extended.properties=-server -d64 -Xms2048m -Xmx2048m -javaagent:$BE_HOME/lib/cep-base.jar -XX:MaxPermSize=256m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.security.egd=file:///dev/./urandom.
<property name="be.backingstore.recreateOnRecovery" value="true"/>
<property name="be.backingstore.test.connections.interval" value="30"/>
Add in the tra file (SOL1-D8QBXH / KB:36218):
TRA-property: java.extended.properties (add parameter below):
-Djava.security.egd=file:///dev/urandom
From the FOM 2.0.1 TIB_af_2.0.1_installation.pdf:
Configuring TRA File for the Database Connectivity
The Oracle JDBC driver has a documented limitation when running on linux 64 bit system. The issue might happen during the login phase, it fails on some systems due to the way the random number generator works. The default random generator can be blocking in some circumstances and prevent JDBC to connect to the database. The workaround is to use the urandom generator that is not blocking.
Set the JVM-level property in the BE 5.1.1 TRA file.
• Go to the $BE_HOME/bin/be-engine.tra location.
• Append the property -Djava.security.egd=file:///dev/./urandom to the java.extended code of the relevant 64 bit jvm property. For example:
java.extended.properties=-server -d64 -Xms2048m -Xmx2048m -javaagent:$BE_HOME/lib/cep-base.jar -XX:MaxPermSize=256m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.security.egd=file:///dev/./urandom.
Additional Information
TIB_af_2.0.1_installation.pdf
Attachments
Feedback
Yes
No
Powered by
