Siebel Open UI, Tools, Scripting and EAI (MOSC)

MOSC Banner

Why workflow process manager does not reconnect to LDAP server via JNDI if it encounters an issue du

edited Dec 16, 2016 12:28AM in Siebel Open UI, Tools, Scripting and EAI (MOSC) 1 commentAnswered
Our Siebel Application connects to LDAP via JNDI to get the JMS Server Names using the parameters given below in the jndi.properties file.
java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
java.naming.provider.url= ldap://some-ldap-server/OU=jmsObjects,OU=jms,OU=Apps,O=cco.cisco.com

Even though the connection works fine for few hours, it starts failing and we get the following error message.

<-- Error Message Begin -->

ObjMgrBusServiceLog Error 1 0 2011-11-13 19:19:04 (javabsvc.cpp (164)) SBL-EAI-05000: Business Service call returned error code JNDI_ERROR and message: Exception: javax.naming.CommunicationException: connection closed [Root exception is java.io.IOException: connection closed]; remaining name 'CN=stage,OU=smcc,OU=ConnectionFactory,OU=zzsmccin.queue.CheckContact.SMCC.Contact.RequestResponse'; Message: connection closed

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

SBL Configuration-EAI Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center