EAI JMS Transport JNDI_ERROR when it re-connects to JMS Queue (OC4J JMS AQ or WebLogic JMS) when MiddleWare is restarted.
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 8.1 SIA  to 184.108.40.206 SIA  [Release V8]
Information in this document applies to any platform.
A JMS receiver is setup at Siebel to interface with AIA - Application Integration Architecture.
AIA JMS server runs on FusionMiddleware / Weblogic.
When AIA JMS Server is restarted, siebel looses connectivity to the queues and the JMS component needs to be manually restarted once the JMS Server is fully up and running.
When Siebel Object Manager (such as Siebel Thin eCommunications Client or Workflow Process Manager) makes a "Send" call to "EAI JMS Transport" after the middleware has been restarted (e.g. after some outage), it is also unable to reconnect unless the Siebel Component is restarted.
Sample Siebel Object Manager and JMS API logs (Outbound Web Service):
It would be desirable to have appropriate parameters to set in the JMS receiver so it retries for a period of time long enough to allow the JMS Server to be fully up again, without any manual intervention.
It would also be desirable to have outbound calls to reconnect automatically.
The issue can be reproduced at will with the following steps:
1. Startup siebel and the JMS server(weblogic)
2. start a JMS receiver in Siebel
3. bound JMS Server (Weblogic)
4. Even if Siebel JMS receiver is configured for automatic restart as indicated in Component Automatic Restart & Component Database Error Recoverability (Doc ID 476027.1)
there is a good chance siebel will attempt reconnects too fast and reach the maximum number of attempts to restart the JMS Receiver component before the weblogic JMS server is fully up and running again.
Make a successful call to EAI JMS Transport from eCommunications or WfProcMgr.
Restart the AIA middleware.
Make another call from eCommunications or WfProcMgr. It will always fail until the component is restarted.
The issue has the following business impact:
Due to this issue, users have to manually restart the siebel components after a middlware restart
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