[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
rnicholson10
do-not-reply at jboss.com
Sat Feb 7 19:39:27 EST 2009
If I startup AS5 with the new libraries the error is as follows:
| 2009-02-08 00:25:26,836 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at 1195c94(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 4eaead destination=queue/speQueueB destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
| javax.naming.NameNotFoundException: speQueueB not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
| at javax.naming.InitialContext.lookup(Unknown Source)
| at org.jboss.util.naming.Util.lookup(Util.java:222)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
| at java.lang.Thread.run(Unknown Source)
|
As you can see from the error it is attempting to connect to the speQueueB using the DefaultJMSProvider, where it should be using the RemoteJMSProvider.
If I then redeploy the bridge I don't get an error. But once I try to send a message I get the error from post above:
| 2009-02-06 21:38:02,087 ERROR [org.jboss.messaging.util.ExceptionUtil] (Thread-47) ConnectionEndpoin
| t[3g-zukpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] sendTransaction [ig-bvkpdvqf-1-qkp2dvqf-f20a68-e6u1gs4]
| javax.jms.JMSException: Failed to route Reference[20217139725713415]:RELIABLE to speQueueB
|
So there is a startup bug where the wrong provider is used for the remote queue. And another where once redeployed message delivery fails. I can see that once the bridge is redeployed that a connection is made to the remote instance. There are still null references in the log as you can see from the post above.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207966#4207966
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207966
More information about the jboss-user
mailing list