The jira http://issues.apache.org/jira/browse/AMQ-3401 issue has been
created.
Thank you all for your help.
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-ActiveMQ-to-Weblogic-route-tp4578300p4590649.html
Sent from the Camel - Users mailing list archive at Nab
It makes sense to fix it up such that it can work in your case and I
guess to future proof it a bit.
The solution may be to make it configurable or plugable, adding a
fallback transformer implementation that can be delegated to in this
case.
I imagine a new public static
ActiveMQDestination.setFal
Yes this class is part of activemq-core-5.5.0.jar.
I did a modification that works correctly reflecting the Destination
parameter to check if in the case of weblogic.jms.common.DestinationImpl is
has the isQueue and isTopic methods that could help to determine between
Queue and Topic.
As the prob
On Wed, Jul 13, 2011 at 2:26 PM, pwanner wrote:
> Thank you for your answer Ashwin.
>
> Actualy I found from where the error comes :
>
> The JNDI lookup to Weblogic return a weblogic.jms.common.DestinationImpl
> instance that is the Weblogic generic implementation for Queue and Topic.
>
> In the o
Thank you for your answer Ashwin.
Actualy I found from where the error comes :
The JNDI lookup to Weblogic return a weblogic.jms.common.DestinationImpl
instance that is the Weblogic generic implementation for Queue and Topic.
In the org.apache.activemq.command.ActiveMQDestination class the trans
Hi,
Looking at the stack trace, the error seems to be in the JMSProducer
attempting to send a message to a weblogic destination called toActiveMQ.
I am no weblogic expert, but I sense that the problem is in the
connectionFactory configuration and the associated connection. The
connectionFactory u
