TIBCO BusinessEvents (BE)Engine throws the error "java.lang.RuntimeException: Storage is not configured exception".
Article ID: KB0086115
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
==========
With Cache object management and when cache-aside is not used, the "Storage Not Configured" errors can be seen while starting up the inference engines, even when the cluster is configured properly and the cache server or servers are up and running.
This is due to a feature called “Service Guardian” introduced in Coherence 3.5.2. The issue is seen when the Coherence nodes give delayed responses due to external reasons, such as slow network speed and database latency.
Environment:
===========
TIBCO BusinessEvents 3.0.2 HF1 and above.
All OS
Workaround
==========
You can safely disable the feature. To do so set the following property in the tra file at the cluster level (so that it applies to all nodes):
tangosol.coherence.guard.timeout=0
Description:
==========
With Cache object management and when cache-aside is not used, the "Storage Not Configured" errors can be seen while starting up the inference engines, even when the cluster is configured properly and the cache server or servers are up and running.
This is due to a feature called “Service Guardian” introduced in Coherence 3.5.2. The issue is seen when the Coherence nodes give delayed responses due to external reasons, such as slow network speed and database latency.
Environment:
===========
TIBCO BusinessEvents 3.0.2 HF1 and above.
All OS
Workaround
==========
You can safely disable the feature. To do so set the following property in the tra file at the cluster level (so that it applies to all nodes):
tangosol.coherence.guard.timeout=0
Issue/Introduction
TIBCO BusinessEvents (BE)Engine throws the error "java.lang.RuntimeException: Storage is not configured exception".
Feedback
Yes
No
Powered by
