Oracle documentation:This can be set for work and master repository separately (there are 2 data sources). So, if I set 7 seconds there, it will be equivalent for ODI_CONNECTION_RETRY_DELAY=7000 and ODI_CONNECTION_RETRY_COUNT infinite (because weblogic will attempt to connect until it succedes, without any max attempt count). Am I right?
The number of seconds between attempts to establish connections to the database.
If you do not set this value, data source creation fails if the database is unavailable. If set and if the database is unavailable when the data source is created, WebLogic Server will attempt to create connections in the pool again after the number of seconds you specify, and will >continue to attempt to create the connections until it succeeds.
When set to 0, connection retry is disabled.
MBean Attribute (Does not apply to application modules) :
Minimum value: 0
Maximum value: 2147483647
WebLogic Server will attempt to create connections in the pool again after the number of seconds you specify, and will continue to attempt to create the connections until it succeeds.So it will keep trying in every 5 sec till a successful connection. The only thing I am missing here is to how to restrict this from infinitive to a limited try.
_Phil wrote:What exactly do you mean? I have a lot of session waiting for events (wait for data, wait for file etc). By default, agent will not monitor repository connection in this case (and entire session is lost if repository goes down- it waits independently and it won't detect any events anymore), but - for standalone agent, solution is changing this 2 options. So I'm asking for their equivalnets for java ee agent.
For active sessions, I handle connection problems at the Package level, by setting the "Processing After Failure" advanced options on each step.