The various cause of this issue are:
1. Cluster setup issue -
a. Slide Repository not configured to use the Database as the Repository
b. JNDIs for the Topic and Topic Connection Factory not created for esb-dt and esb-rt.
If any or both of the above configuration is missing then you have to do it on all the nodes and for both esb-dt and esb-rt(oc4j_soa) containers.
2. On ESB Console, cluster name is not set to esb-rt cluster_name. Verify on all nodes that the cluster_name @ $ORACLE_HOME/j2ee/
3. The ESB Service is missing on the other nodes.
Run Opmnctl status -app|grep esb-rt
if for esb-rt, routable=false then update ohs-routing="false" to "true" at $ORACLE_HOME/j2ee/OC4J_SOA/config/default-web-site.xml where web-app application="esb-rt" name="provider-war" load-on-startup="true".
Hope this help ...
In my case ... It was subscribers in ESB_CONTROL queue that hit the maximum number caused this error to came.
ReplyDeletecheck for aq$esb_control_s and if the count is =1024, you have the same situation as me. GO and recreate ESB_CONTROL Queue.