on 02-16-2006 2:38 AM
I am trying to subscribe to a weblogic JMS queue using Transport Prototcal: "Access JMS Provide with JNDI" in my Communication Channel. I have deployed weblogic.jar and wljmsclient.jar in aii_af_jmsproviderlib.sda.
For some reason when XI is trying to create and instance of QueueConnectionFactory I get an error. See below. Any ideas on why I am getting this error? Has anyone else access a weblogic JMS queue from XI?
#1.5#000E7FED310600A00000011700005F2B00040CE03C859719#1140057134414#com.sap.aii.af.service.jms.WorkerJMSReceiver##com.sap.aii.af.service.jms.WorkerJMSReceiver.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0####70b576e09e9411da9aee000e7fed3106#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#<null># #1.5#000E7FED310600A00000011800005F2B00040CE03C85A0AF#1140057134417#com.sap.aii.af.service.jms.WorkerJMSReceiver##com.sap.aii.af.service.jms.WorkerJMSReceiver.start()#J2EE_GUEST#0####70b576e09e9411da9aee000e7fed3106#SAPEngine_Application_Thread[impl:3]_18##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' null') before. Reconfigure it or restart the JMS service!#1#JMSSender#
Thanks
Sebastian,
I have found the jar file the class WorkerJMSReceiver is in.
There is a jar file called aii_adapter_jms_svc.jar which is contained in aii_adapter_jms_svc.sda.
/usr/sap/XID/DVEBMGS53/SDM/root/origin/sap.com/com.sap.aii.adapter.jms.svc/SAP AG/7.0005.20051006184841.0000/aii_adapter_jms_svc.sda
Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Warren!
I got it! Took me some hours!
The problem was, i deployed a jms.jar with my vendorrelated client jars inside the sda file. (or respectivly any jar containing javax.jms.* packages). This is not allowed!
I even found the lines in the class files WorkerJMSReceiver + WorkerJMSSender, so the problem is the initialization of the QueueConnectionFactory, if you have the javax.jms packages inside your classpath the default QueueConnectionFactory seems to be the QueueConnectionFactory interface of these packages which couldn't get initialized as it is an interface and not a class with a constructor, this result in a return of null.
As i removed the jms.jar form the sda, everything worked fine.
Greetz
Sebastian
Hi Warren,
See the information on this factory at the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/90/57849e5e3e45d784afc4e3bfa8136f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cd/4d4941abbb4c0de10000000a1550b0/frameset.htm
Also, refer to note SAP note 856346
Rgds,
Sam Raju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello!
I have the same Problem as Warren with an ActiveMQ Provider, refering to your links Sam, its the help for registering an external provider with the web as (like for usage of jms in an web application on the SAP Web AS or something like that), as far as i understand the xi -jms adapter documentation, you don't need to do this if you want to connect to a jms provider through a xi channel configuration, as you define this properties (Initial ConnectionFactory, url, queueName, etc ...) already in the channel configuration right?
i also tried the same thing with openjms, i am very shure all my connection parameters are right as i can connect to the provider in regular java code. Also the jars are deployed properly and the classes get found otherwise i would have other exceptions in the trace.
Anybody had the same problem?
Does someone know what is exactly happening at
com.sap.aii.af.service.jms.WorkerJMSReceiver.init() in Line 282 or where to find the jar where this class is in?
Greetz
Sebastian
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.