Error in JMS

Hi
I tried the following code to connect to a JMS server which is running on a remote machine..
String strConnectionFactory="java:comp/env/jms/sample";
               String strTopic="java:comp/env/jms/Computer";
               Hashtable env = new Hashtable();
               env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.fscontext.RefFSContextFactory");
               env.put (Context.PROVIDER_URL,"localhost");
               Context ctx = new InitialContext(env);
               //get the connection Factory
               connectionFactory=(TopicConnectionFactory)ctx.lookup(strConnectionFactory);
I am getting the following exception
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.
scontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundExceptio
: com.sun.jndi.fscontext.RefFSContextFactory]
Can anybody help me..
thanks in advance
hashin

u said its remote m/c then wats the location of the provider
looks like u dont have the fscontext.jar in your class path

Similar Messages

Error in JMS Communication Channel not raising alert

Processing Errors in JMS Communication Channel are not raising alerts.
The settings on the communication channel retires are set at 3 and 5min interval.
In RWB the JMS communication channel shows processing errors but an alert is not raised.
The alert are configured in our system and we even have a catch all alert rule with * (wildcard). Errors in PI message processing are raising alerts but errors in Comm Channel are not raising alerts.
The message in SXI_MONITOR shows as processed successfully but when we check the RWB and Comm. Channel Monitoring we see processing errors "Channel error occured; detailed error description: JMS error: Connection to the server has been terminated; Linked error: Connection reset, Error Code:null"
Are we missing any configuration? How do we get alerts/notifications if there are errors in Comm. Channel without having to login into RWB and watch it periodically?
Any help is greatly appreciated.
RM

Hi,
What is the staus of Communication channel in RWB when it fails, RED ??if yes then it should genarate alert.
create one more alert for specific to JMS interface and check it out.
Regards,
Raj

Error in JMS adapter MQ to PI

Hi,
We are connecting to Websphere MQ using the JMS adapter.
The message coming from MQ is a flat structure. So we have configured the Message Transform Bean to do the conversion from plain to xml structure according to
http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter
But when we test a message we end up with this error:
TransportException: No MIME header found at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
I'm not sure if this is related to the content conversion or general settings in the JMS adapter.
Any inputs are highly appreciated.
Thanks
Shakthi

Hi Shakthi,
Actually, it is the error that tells you where the error took place:
com.sap.aii._adapter.jms_.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
You might also want to refer to this thread: Error in JMS Sender Adpater for a few ideas to solve your problem. In general, it is connected to your adapter configuration. Please review it once again ang you should have the problem fixed.
Hope this helps,
Greg

Error in JMS Input channels

Dear all,
We have observed a peculiar issue.
Some of the JMS Input channels are throwing this error:-
"Error establishing JMS connection; error message: MQJMS2005: failed to create MQQueueManager for <IP>:<QM Manager>> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009; error code: MQJMS2005"
Other JMS channels with the same configurations are working fine. But some JMS channels have this error.
If any one has faced a similar issue, kindly share the steps to resolve the same.
Thanks in advance,
Younus

Please ask the MQ Team to restart the MQ queue.I mean to stop and start again.
We faced similar kind of issues and we even tried to restarting the JMS communication channel and MQ Queue.This solved our problem.
As only one JMS channel is not working,there might be connectivity issues with JMS Queues..
Try to restart the JMS Queue and JMS communication channel and see.

Oracle Queue Error creating JMS-120: Dequeue failed

Hi Guys,
We are facing serious problems with Oracle queue when dequeuing messages from the queue.
Our configuration is the following:
- SOA Suit 10.g (10.1.3.5.0)
- Dehydration storage - Oracle Database 11gR2 in Exadata Cloud
We use standard JMS Adabpter from AS10g to dequeue messages from the Oracle queue.
Suddenly dequeue stop working pooling the flowing errors into the log.xml log file in $ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_SOA_GROUP_1/oc4j directory.
<MSG_TEXT>Failed to process deferred message</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[oracle.tip.esb.server.dispatch.QueueHandlerException: Error creating "JMS-120: Dequeue failed"
     at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:197)
     at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:178)
     at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:135)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:825)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.jms.AQjmsException: JMS-120: Dequeue failed
     at oracle.jms.AQjmsError.throwEx(AQjmsError.java:308)
     at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:2094)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:922)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:835)
     at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:776)
     at oracle.j2ee.ra.jms.generic.CommonConsumerWrapper.receive(CommonConsumerWrapper.java:203)
     at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:175)
     ... 7 more
then:
<COMPONENT_ID>j2ee</COMPONENT_ID>
    <MSG_ID>J2EE JTA-00107</MSG_ID>
<MSG_TEXT>Error in resource driver during rollback: oracle.jdbc.xa.OracleXAException, errorCode : -7</MSG_TEXT>
and this message comes out every second:
    <MSG_TEXT>Attempt to use an invalid handle : 'oracle_jdbc_driver_LogicalConnection_Proxy@10af88e3'.</MSG_TEXT>
Any help, suggestions, hints would be much appreciated.
cheers!!
eMarcel

Hi there
I have got the same problem i.e
oracle.jms.AQjmsException: JMS-120: Dequeue failed
     at oracle.jms.AQjmsError.throwEx(AQjmsError.java:283)
     at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:2178)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1013)
     at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:950)
     at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:897)
     at com.cramer.cdd.mytest.QueueReceive2.init(QueueReceive2.java:122)
     at com.cramer.cdd.mytest.QueueReceive2.main(QueueReceive2.java:152)
Exception in thread "main
Please help me in debugging this.
I have a standalone java application to listen to the aqJMS queue.
Regards
Paul

Error starting JMS-Server

I get an exception in starting OC4J (oc4j_extended_1013_dp4.zip file, version 10.1.3)
java -jar oc4j.jar
(SEVERE) Failed to set the internal configuration of the OC4J JMS Server with:
XMLJMSServerConfig[file:/C:/oc4j_1013/j2ee/home/config/jms.xml]
Error starting JMS-Server...
On my computer I succeeded to start the same OC4J ok, but on other 2 computers I get the same exception.
What can be the problem?
Thanks.

The OC4J instance that is having the problem may have .lock file issues. Some quotes from the JMS chapter of the services guide:
If OC4J terminates normally, then the lock files are cleaned up automatically. However, if OC4J terminates abnormally, for example, a kill -9 command, then the lock files remain in the file system. OC4J can usually recognize leftover lock files. If not, you must manually remove lock files before restarting OC4J after abnormal termination.
JMS persistence lock files are tagged with (contain) server and persistence directory location info. If the lock file exists when the JMS server starts, and the lock file was created by the same server (having the same ip address) and using the same persistence directory location, then the JMS server will assume control of the lock file and start up successfully.
If, for some reason, the jms.state file itself is corrupted, then the only recourse is to delete it, with the attendant loss of all pending transactions - that is, transactions that have been committed, but the commits not yet performed by all individual destination objects participating in the transactions.
Note that the use of an IP address can cause issues if you have abnormal terminations and are using DHCP (so next time you start OC4J you also have a new IP address). There was also an issue in the dev preview versions if you are running on MS-Windows where the .lock files would not be automatically deleted on normal shut down - even if you have since moved to the release version, the old .lock files may still be there.

ACCESS.ERROR#service.jms.default.authorization Errors

Hi,
With standart installation, following errors are filling defaulttrace contiuosly, any idea?
#1.#0050568817F2005E000003B00000706600044473E94477A8#1201164532348#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleReference#Guest#240####86dd8e50ca5511dcc5540050568817f2#Thread[Thread-60,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#com.sap.engine.services.security.roles.SecurityRoleReference#Java###: Authorization check for caller assignment to J2EE security role [ : ] referencing J2EE security role [ : ].#5#ACCESS.ERROR#service.jms.default.authorization#administrators#SAP-J2EE-Engine#administrators#

Hi Huseyin
Implement the latest patches available in market place.
For eg: CAF 13.1
SAP-JEE 13.1
SAP-JEECOR 13.3
SAP_JTECHF 13.1
SAP_JTECJS 13.1
UMEADMIN 13.2
or give eu_role to the user
Hope this helps
Satish Kumar.

Error in JMS adapter 11g

Hi
I have configured a JMS Adapter in Jdev 11.1.1.3.0 to consume message from a queue(JNDI Name as eis/wljms/WLQueue) on a weblogic server(10.3.1) in a different domain and deployed my BPM process to the soa server 11g.
I created a new outbound connection pool (eis/wljms/WLQueue) in Deployments->JMSAdapter->Configuration->Outbound Connection Pools with Connection Pool Interface: oracle.tip.adapter.jms.IJmsConnectionFactory
Also updated the factory properties field for eis/wljms/WLQueue with :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.75.85.151:9021;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic
And finally updated the deployment plan for JMSAdapter.
However I am getting the following error :
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample JMSMessageConsumer_init: Retrying connection; attempt #1>
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample
BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the
connection factory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:207)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnec
tionFactory(JMSConnectionFactoryFactory.java:86)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:173)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.Sec
urityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialCo
ntextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
67)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.ja
va:183)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:131)
... 26 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticat
ed.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServi
ceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.jav
a:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173
Anyone has come across this issue? if yes, how do I resolve this?
Thanks

Have you tried cross-domain security or domain trust?

Error in JMS Adapter Configuration.

Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.

you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info

Error in JMS Adapter:

Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21     Error     MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21     Error     Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22     Success     The message status set to WAIT.
2010-09-09 11:45:22     Success     The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciated

XI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
    SAP XI JMS Adapter/ConvertJMSMessageToBinary
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService

Error with jms receiver communication channel

I am new to jms adapter
I am getting ERROR:"Error connection due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Please ensure that all needed resources are present in the JMS provider library: com.sap.aii.adapter.lib.sda".
How to resolve this issue?
Please help to me
Thanks
Swathi

Hi,
Check all the jar files in aii_af_jmsproviderlib.sda
See the list of files from below link
http://help.sap.com/saphelp_nw70/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
or install the drives again i suppose som of jar files are missing on PI box or not deployed correctly.
chirag

Error in JMS receiver adapter

Hi all,
I am getting an error in message monitoring.
ERROR:
Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Can anyone suggest me regarding this.
Thanks,
Kalyan

Hi Kanwaljit,
I didn't find the node localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
plz give me some suggestions regarding this.
what can i do if i didn't find node that you mentioned.
Regards,
kalyan

Error in JMS receiver adapter: "Error creating initial context with environment"

Hello,
I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
The message in adapter monitoring is:
A channel error occurred. Detailed error (if any) :
com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
(JndiConnectorImpl.java:152)<br> ....
Message processing failed. Cause:
com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
Might there be a problem with the JMS drivers?
Regards,
Marcus

Hi Marcus,
Have a look at below thread
Connecting to PI 7.11 JMS Queue from other PI 7.11 Server

Error in JMS Sender Adpater

Hi
I am doing Weblogic-PI-File scenario
when i try to pick the XML file from Weblogic JMS queues its giving the follwing error
Error occurred while processing message: 552eec87-b6c3-4035-2675-cc3cd57b5487. Detailed error (if any): com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_File_Sender xmlns:ns0="urn:XXXXXXXX.com:JMSReciever"><SalesOrderDetails><MRNNumber>1234</MRNNumber><FirstName>ABC</FirstName><LastName>CDE</LastName><SocialSecurity>1234567890</SocialSecurity></SalesOrderDetails></ns0:MT_File_Sender> to XI message for message: 552eec87-b6c3-4035-2675-cc3cd57b5487: TransportException: No MIME header found
Edited by: S V on Jan 27, 2009 1:08 AM

Hi I am using Weblogic JMS Queues ..
and the connection parameters i am using :
JNDI LOOKUP NAME FOR QUEUE CONNECTION FACTORY:
mm.jms.VendorConnectionFactory
JNDI LOOKUP NAME OF JMS QUEUE: mm.jms.PIOutboundTestQueue
NAME OF JNDI INITIAL CONTEXT: weblogic.jndi.WLInitialContextFactory
JNDI SERVER ADDRESS : t3://vendor.xxx.xxxxxxx.com:6107
JNDI LOGON USER : xxxxxx
JNDI LOGON PWD : XXXXXX
did i miss anything ... or do i have configure anything on JMS sender adpater so that it will convert the text message into Binary

Sender JMS Adapter error: The JMS provider gave the error message as Not permitted, and the error code is null

I am trying to connect tibcoems with PI using a Sender jms adapter.After successfully installing the drivers , the sender adapter goes into error.
"The JMS Provider gave the error message as Not permitted, and the error code is null"
The Transport protocol is 'Access JMS Provider with JNDI' and i have been given the required parameters from the tibco guys.
Your input are highly appreciated.
Shyam

Hi AQmit,
Thanks for the reply.
Please find the screenshots of what i am trying to do.
Also, Can u direct me how to check the right logs?

Error in JMS channel

Hi ALL,
I am getting the below error in Communication channel monitoring short log of JMS channel.
"Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing; ensure that JMS provider library 'aii_af_jmsproviderlib.sda' contains all required resources"
This error looks like the deployed .sda file dint contain the class specified.Can u let me know where i can find the aii_af_jmsproviderlib.sda file with all required classes in it .
We are on SAP XI 7.0 SP 14 and the MQ version is 7.0.
Kindly let me know if any one had faced the same error.
Regards,
Rajesh

Hi, check this links.
XI to IBM Websphere Default JMS Provider with JNDI
JMS receiver adapter configuration error
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Edited by: Marco Salazar on Dec 9, 2009 5:24 PM

Error in JMS

Similar Messages

Maybe you are looking for