Posted: Wed Sep 29, 2004 1:47 am Post subject: InvalidDestinationException?
Newbie
Joined: 27 Jul 2004 Posts: 4
Hi all,
I am trying to make WL8.1 work with MQSeries using a very simple MDB that picks a msg from a queue and then prints the message content.
I have configured a foreign JMS server, connection factory and destination in WL and created a XAQCF and Q with JMSAdmin. I paste the error displayed in the WL console below. BANKTEST and mdbQ are the queuemanager name and queue name as defined in MQSeries (not JMS). Any idea what's wrong?
<Warning> <EJB> <BEA-010061> <The Message-Driven EJB: QueueListener is unable to connect to the JMS destination: wl_myMDBQueue. The
Error was:
weblogic.jms.common.InvalidDestinationException: Foreign destination, queue://BANKTEST/mdbQ?persistence=2
weblogic.jms.common.InvalidDestinationException: Foreign destination, queue://BANKTEST/mdbQ?persistence=2
at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1626)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2012)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:978)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.contact admin(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Posted: Wed Sep 29, 2004 4:12 am Post subject: Problem solved!
Newbie
Joined: 27 Jul 2004 Posts: 4
Hiya,
Solved the problem meanwhile. Configuring a foreign JMS server etc. within weblogic was not necessary, but adding the following info in the message driven descriptor in weblogic-ejb-jar.xml was:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum