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

MOSC Banner

JMS destination not reachable exit

edited Feb 25, 2020 4:08AM in Siebel Open UI, Tools, Scripting and EAI (MOSC) 3 commentsAnswered

We have JMS in out siebel enterprise and middleware is SOA , there are situations sometimes SOA server is rebooted or queues are bounced.

The JMS tasks exit because of error like below

(javabsvc.cpp (336)) SBL-EAI-05000: Business Service call returned error code JNDI_ERROR and message: Exception: javax.naming.CommunicationException: t3://vdclassoadev03.xxxxxxxx.corp:8007: [RJVM:000575]Destination 10.250.1.183, 8007 unreachable.; n

We tried changing receiver timeout to 1800000 ms that is 30 min still after 5-8 mins SOA server is not reachable tasks exit. Is there any parameter in JMS subsystem or JAVA subsystem which can hold the JMS tasks not to exit for upto 30 mins

Tagged:

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