JMS Receiver JNDI_ERROR NoInitialContextException ClassNotFoundException Or javax.naming.NameNotFoundException
(Doc ID 541499.1)
Last updated on FEBRUARY 01, 2022
Applies to:
Siebel System Software - Version 7.7.2.1 SIA [18353] and laterSiebel CRM - Version 7.7.2 SIA [18325] and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2.1 [18353] Fin Svcs
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 5.8
This document was previously published as Siebel SR 38-1980355081.
Symptoms
While setting up JMS Receiver server component to receive the messages from WebSphere MQ JMS server, three subsystems were created of following types as enterprise profile:
1. EAITransportDataHandlingSubsys
2. JMSSubsys
3. JVMSubSys
The jndi.properties and all required jar files were included in the JAVA (subsystem type - JVMSubSys ) JVM Classpath (alias CLASSPATH).
Then, the JMS Receiver component’s parameters were set accordingly.
The following error, however, were reported when starting up the JMS Receiver server component:
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |