JMS Adapter 61 starup errors in Webmethods 601

Hello,
Below are the following message I see in the server console. I am using 2 jars from Sonic MQ broker (mfcontext.jar, sonic_Client.jar) for using the ContextFactory class specific to Sonic to make a JMS Queue connection to it.

Any ideas anyone?

2004-08-13 11:04:04 EDT [ISS.0028.0012C] WmJMSAdapter: Startup service (wm.adapter.wmjms.admin:startUp)
2004-08-13 11:04:05 EDT [ART.0114.1100D] Adapter Runtime: Facility 680 - JMSAdapter registered with bundle com.wm.adapter.wmjms.JMSAdapterResourceBundle.
2004-08-13 11:04:05 EDT [ART.0114.1101W] Adapter Runtime: Duplicate facility 680 - JMSAdapter registered with bundle com.wm.adapter.wmjms.JMSAdapterResourceBundle.
2004-08-13 11:04:05 EDT [ART.0114.1100D] Adapter Runtime: Facility 680 - JMSAdapter registered with bundle com.wm.adapter.wmjms.JMSAdapterResourceBundle.
2004-08-13 11:04:08 EDT [ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”.
[ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter.
2004-08-13 11:04:08 EDT [ISS.0028.0013E] Startup service exited with the following error: com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”.
[ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter.

Bharath, what does the error log say? can you print out the error log extract too which will throw more light on the exact issue?

This is the error log from the server admin web console,

2004-08-13 11:04:08 EDT com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … d5d92d4f844b91cbfe71203c8b NULL d5d92d4f844b91cbfe71203c8b
2004-08-13 11:04:08 EDT wm.adapter.wmjms.admin:startUp com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:08 EDT wm.art.adapter.deployment:registerAdapterType com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:08 EDT wm.art.adapter.deployment:registerAdapterType [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:08 EDT wm.art.adapter.deployment:registerAdapterType [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:08 EDT wm.art.adapter.deployment:registerAdapterType [ART.118.5057] Adapter Runtime (Connection): Adapter Runtime was unable to initialize 1 connection resources for the adapter “JMSAdapter”. Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:07 EDT Armstrong:sonicQConn [ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager. progress/message/jclient/xa/XAConnectionFactory Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:07 EDT wm.art.adapter.deployment:registerAdapterType progress/message/jclient/xa/XAConnectionFactory Stack trace data … 77469fc869be2c5ffe71202e2c NULL 77469fc869be2c5ffe71202e2c
2004-08-13 11:04:03 EDT wm.tomcat.admin:deployPackages java.lang.NoSuchMethodError Stack trace data … e569bae93831e2b4fe71205174 NULL e569bae93831e2b4fe71205174
2004-08-13 10:41:20 EDT com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … 41b669724d9a73a3fe71151283 NULL 41b669724d9a73a3fe71151283
2004-08-13 10:41:20 EDT wm.adapter.wmjms.admin:startUp com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … fc3c65ad092938d0fe71150a34 NULL fc3c65ad092938d0fe71150a34
2004-08-13 10:41:20 EDT wm.art.adapter.deployment:registerAdapterType com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occured while Adapter Runtime was loading adapter type “JMSAdapter”. [ART.114.9] Adapter Runtime: Error(s) while registering adapter type JMSAdapter. Stack trace data … fc3c65ad092938d0fe71150a34 NU

The problem is not very clearly evident, as we see, from the error log. At this point I would try to test with a “stand alone java client for SonicMQ” from machine running webmethods IS. This is just to isolate any configuration and other issues with SonicMQ. This test will isolate the issue to a great extent.

If you are still having problems – Do you have jms.jar in the class path… if not then try adding it to the classpath and restart the IS to see if it is able to load the WmJMSAdapter.

I have the jms.jar in my lib/jars dir of wmIS. the problem is not with my startup of the JMS Adapter package, but to invoke the QueueConnectionFactory class of Sonic MQ which has all the jms provider jars in the lib/jars dir too.

Bharath,

Did you placed the jars in the packages/WmJMSAdapter/code/jars/static folder and after this change reload the JMS package or restart the IS.

This might resolve the problem for accessing the QueueConnectionFactory class.

Regards,

I want to access the QueueConnectionfactory class for the Sonic JMS provider and not the generic one in the jms.jar lib. Should I place the Sonic related jars in the static folder as you had mentioned. And once I do that, how does the IS know to pick it up from the static folder. Where is this location pointed to in the starup of the wm IS?

Thanks,
Bharath

bharu78@yahoo.com

Bharat,

yes place the sonic related jars in the Static folder,and reload the Package or restart IS this sets the classpath,and so internally IS will access that class.

HTH,
RMG

Hello,
I did what you asked me to, but still get the same error. Dont know what I am doing wrong here. But I have attached the entire package that I am testing with. Any ideas?

-Bharath


JMSAdapterTest_FullRel.zip (8.2 k)