Unhealthy WLStore at regular intervals
Could a concurrent access to the default file store of ejb timers info cause race conditions and eventually its corruption ?
My enterprise application has a set of timers, say T1, T2 and T3. Their periods are:
T1: 15'
T2: 30'
T3: 30'
For internal reasons they are programmed to fire at the very same minute and second.
When all of them are running, we always get the following error message in the server log:
Resource WLStore_lucy2_domain__WLS_AdminServer2 declared unhealthy.
(lucy2_domain is the WLS domain name).
This normally happens at the first occurrence of a triple timeout, i.e. at 8:30 if the server was started at 8:00. However, to make things worse this is very frequent but not deterministic, we saw it happen at the second or even N-th timeout.
My enterprise application has a set of timers, say T1, T2 and T3. Their periods are:
T1: 15'
T2: 30'
T3: 30'
For internal reasons they are programmed to fire at the very same minute and second.
When all of them are running, we always get the following error message in the server log:
Resource WLStore_lucy2_domain__WLS_AdminServer2 declared unhealthy.
(lucy2_domain is the WLS domain name).
This normally happens at the first occurrence of a triple timeout, i.e. at 8:30 if the server was started at 8:00. However, to make things worse this is very frequent but not deterministic, we saw it happen at the second or even N-th timeout.
0