Last updated on NOVEMBER 02, 2016
Applies to:Oracle ESB - Version 10.1.3.3.1 to 10.1.3.5
Information in this document applies to any platform.
***Checked for relevance on 08-Mar-2012***
Using SOA 10.1.3.4 MLR 9.
When bulk data load happens, you receive SOAP errors in ESB for a few RS instances which are NOT retryable. This action is inconsistent and mostly does not occur for smaller loads. When you re-load the same data in smaller chunks, everything loads successfully without any errors. Also configuration is proper and ESB is correctly migrated to Database topics as per following document:
Oracle Application Server Enterprise Deployment Guide 10g Release 3 (10.1.3.5.0)
3.22 Configuring JNDIs for the Topic and Topic Connection Factory
3.23 Updating the Oracle Enterprise Service Bus Metadata
3.24 Configuring the Slide Repository to use the Database as the Repository
The following error message in seen when data load happens:
Failed to enqueue deferred event "oracle.tip.esb.server.dispatch.QueueHandlerException:
Context lookup failed "[CONFIGURATION ERROR] Invalid Destination "Topics/ESB_JAVA_DEFERRED" :
javax.jms.InvalidDestinationException: Looking up java:comp/resource/esbRP/Topics/ESB_JAVA_DEFERRED:
javax.naming.NameNotFoundException: No resource named 'esbRP/Topics/ESB_JAVA_DEFERRED'found.
Please verify configuration of adminobject or the lookup string."
Make sure the topic is mapped to a jndi tree"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms