Re: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-09-13 Thread MalviyaSaurabh
was enabled, grid came in running with the adapter also in running state. Thanks Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/Atrium-Orchestrator-Issue-JMSActorAdapter-Naming-look-up-did-not-return-a-static-destination-tp111303p112116.html

Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-14 Thread John Baker
Carl There's nothing wrong with the WL JMS driver. It works just fine and I've used it many times before. I'm wondering if the error is due to JMS versions (1.0.2 vs 1.1). Which version of the JMS spec does AO utilise? John

Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-13 Thread John Baker
Carl Maybe I'm missing something but the error isn't being thrown by the WL jars, it's being thrown by the VM which has been asked (by AO) to cast one object as an interface that the object doesn't implement. The WL JMS drivers are required to connect to WL. John

Re: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-13 Thread Carl Wilson
(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of John Baker Sent: 13 August 2013 20:21 To: arslist@ARSLIST.ORG Subject: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!! Carl Maybe I'm missing something but the error isn't being thrown by the WL

Re: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-13 Thread Chuck
-look-up-did-not-return-a-static-destination-tp111232.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where

Re: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-12 Thread MalviyaSaurabh
API lookup failed: weblogic.jms.common.DestinationImpl cannot be cast to javax.jms.Destination Please help. Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/Atrium-Orchestrator-Issue-JMSActorAdapter-Naming-look-up-did-not-return-a-static

Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-12 Thread John Baker
This error: JMSAdapter, JNDI API lookup failed: weblogic.jms.common.DestinationImpl cannot be cast to javax.jms.Destination Suggests the WL driver is written around JMS 1.0.2 and not JMS 1.1. There were some subtle changes in the spec that made integrating with JMS 1.1 easier, and Destination

Re: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-12 Thread Carl Wilson
/ -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of MalviyaSaurabh Sent: 12 August 2013 12:34 To: arslist@ARSLIST.ORG Subject: Re: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!! Hi John

Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-11 Thread John Baker
Hello, The following: 31 Jul 2013 15:06:02,965 ERROR JMSActorAdapter : Naming look up did not return a static destination!! does not appear to be an error from the core Java libraries. I'd suggest you need to find the error from the Weblogic JMS driver, as this may tell you what's wrong, as

Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!!

2013-08-08 Thread MalviyaSaurabh
-system.1.n7.nabble.com/Atrium-Orchestrator-Issue-JMSActorAdapter-Naming-look-up-did-not-return-a-static-destination-tp111232.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE