-
15. Re: Upgrading AS5 to use messaging 1.4.2.GA
Are YOURDB-persistence-service.xml and remoting-bisocket-service.xml the only config files I need to worry about?
Previously I used the updated connections, destinations and messaging-service xml files from the release I downloaded. Should I revert to the copies of those files from the original AS5 download and only update the persistence and remoting-bisocket files? -
16. Re: Upgrading AS5 to use messaging 1.4.2.GA
"PeterJ" wrote:
I got both the 1_4_1_GA and 1_4_2_GA tags sout of svn, built each with integration.base=AS5, ran the release-bundle target and then compared the resulting jboss-messaging.sar file contents. The only difference was in the manifest file.
I bet you did something wrong on the operation :-) They can't be the same.
If you run SVN diff as I told you, you will see the differences. -
17. Re: Upgrading AS5 to use messaging 1.4.2.GA
"rnicholson10" wrote:
Are YOURDB-persistence-service.xml and remoting-bisocket-service.xml the only config files I need to worry about?
Previously I used the updated connections, destinations and messaging-service xml files from the release I downloaded. Should I revert to the copies of those files from the original AS5 download and only update the persistence and remoting-bisocket files?
On my previous post, I was referring to the ./release *directory* on the build output, not to *the release*. :-) -
18. Re: Upgrading AS5 to use messaging 1.4.2.GA
"clebert.suconic@jboss.com" wrote:
I bet you did something wrong on the operation :-) They can't be the same.
I don't doubt it, misteaks is my middle name. ;-)
But look at the contents of the packaged output/jboss-messaging.sar file - none of the configuration files included in that SAR file are listed in the patch file generated by the svn diff.
And to answer rnicholson10, you do not have to update remoting-bisocket-service.xml - according to the svn diff, that file was not changed. Also, none on the destinations-service.xml files were changed, so your existing file should work. -
19. Re: Upgrading AS5 to use messaging 1.4.2.GA
Oops, replace output/jboss-messaging.sar with output/lib/jboss-messaging.sar
-
20. Re: Upgrading AS5 to use messaging 1.4.2.GA
"PeterJ" wrote:
Oops, replace output/jboss-messaging.sar with output/lib/jboss-messaging.sar
ahhh... *SAR*
Sorry.. I screwed up. I read JAR at the first time.
I thought you said the JARS from 1.4.1 and 1.4.2 were the same.
You're safe then! :-) -
21. Re: Upgrading AS5 to use messaging 1.4.2.GA
Have a look at the JIRA release page for 1.4.2, those bug fixes (if any) are the difference from 1.4.1. For detail you can use svn log -v and then search the corresponsing jira number.
AS5 has integrated jboss-messaging already, you just need to replace jboss-messaging.jar jboss-messaging-client.jar whereever they occur in AS5.
However, whether it works or not you should try out yourself. We have tested 1.4.2 against AS4.x and not AS5. -
22. Re: Upgrading AS5 to use messaging 1.4.2.GA
I've built the libraries for AS5, once more everything works locally and so does the bridge but only locally. If the bridge is connecting to a remote server then we once more have problems.
If I kill the remote jboss instance that the bridge points too it behaves as you expect:2009-02-06 20:50:38,957 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-18) null Failed to set up connections javax.naming.CommunicationException: Could not obtain connection to any of these urls: 172.16.8.52:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server 172.16.8.52:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 172.16.8.52:1099 [Root exception is java.net.ConnectException: Connection refused]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1727) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:680) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673) at javax.naming.InitialContext.lookup(Unknown Source) at org.jboss.jms.server.bridge.JNDIFactorySupport.createObject(JNDIFactorySupport.java:66) at org.jboss.jms.server.bridge.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:45) at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:939) at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1206) at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:68) at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1552) at java.lang.Thread.run(Unknown Source) Caused by: javax.naming.CommunicationException: Failed to connect to server 172.16.8.52:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 172.16.8.52:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:311) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1698) ... 10 more Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 172.16.8.52:1099 [Root exception is java.net.ConnectException: Connection refused] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:281) ... 11 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:277) ... 11 more 2009-02-06 20:50:38,958 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-18) null Failed to set up connections, will retry after a pause of 5000 ms
But once this instance is available then neither of the queue's appear to be bound as far as the bridge is concerned (speQueue is local, speQueueB is remote):2009-02-06 20:49:03,329 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-33) null Failed to set up connections 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 sun.reflect.GeneratedMethodAccessor266.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source) at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) 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.jms.server.bridge.JNDIFactorySupport.createObject(JNDIFactorySupport.java:66) at org.jboss.jms.server.bridge.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:45) at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:939) at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1206) at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:68) at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1552) at java.lang.Thread.run(Unknown Source) 2009-02-06 20:49:03,329 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-33) null Failed to set up connections, will retry after a pause of 5000 ms 2009-02-06 20:49:05,448 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-18) null Failed to set up connections javax.naming.NameNotFoundException: speQueue 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 sun.reflect.GeneratedMethodAccessor266.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source) at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) 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.jms.server.bridge.JNDIFactorySupport.createObject(JNDIFactorySupport.java:66) at org.jboss.jms.server.bridge.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:45) at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:939) at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1206) at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:68) at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1552) at java.lang.Thread.run(Unknown Source) 2009-02-06 20:49:05,448 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-18) null Failed to set up connections, will retry after a pause of 5000 ms
And we still have null references in the logs even when the bridge is running locally.
Any ideas what to try next? -
23. Re: Upgrading AS5 to use messaging 1.4.2.GA
Hmm, this is strange. If I create a queue call "speQueueB" on the instance running the bridge, then the bridge will forward the messages to this queue instead of attempting to move it to the remote queue?
Here's the bridge config:<mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=TestBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml"> <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends> <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends> <attribute name="SourceDestinationLookup">/queue/speQueue</attribute> <attribute name="TargetDestinationLookup">/queue/speQueueB</attribute> <attribute name="QualityOfServiceMode">2</attribute> <attribute name="MaxBatchSize">1</attribute> <attribute name="MaxBatchTime">-1</attribute> <attribute name="FailureRetryInterval">5000</attribute> <attribute name="MaxRetries">-1</attribute> <attribute name="AddMessageIDInHeader">false</attribute> </mbean>
Why would the bridge deliver locally? -
24. Re: Upgrading AS5 to use messaging 1.4.2.GA
If I now delete "speQueueB" on the local bridge instance it will now attempt to deliver the message:
2009-02-06 21:38:02,087 ERROR [org.jboss.messaging.util.ExceptionUtil] (Thread-47) ConnectionEndpoint[3g-zukpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] sendTransaction [ig-bvkpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] javax.jms.JMSException: Failed to route Reference[20217139725713415]:RELIABLE to speQueueB at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:757) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:815) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:489) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeTarget(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.remoting.Client.invoke(Client.java:600) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221) at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeTarget(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java) at org.jboss.jms.tx.ResourceManager.sendTransactionXA(ResourceManager.java:662) at org.jboss.jms.tx.ResourceManager.commit(ResourceManager.java:367) at org.jboss.jms.tx.MessagingXAResource.commit(MessagingXAResource.java:254) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:800) at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2639) at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1784) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88) at com.arjuna.ats.arjuna.AtomicAction.end(AtomicAction.java:216) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:240) at org.jboss.jms.server.bridge.Bridge.sendBatchXA(Bridge.java:1294) at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1354) at org.jboss.jms.server.bridge.Bridge.access$1900(Bridge.java:68) at org.jboss.jms.server.bridge.Bridge$SourceListener.onMessage(Bridge.java:1677) at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:229) at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:1043) at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120) 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) 2009-02-06 21:38:02,087 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-47) null Failed to send + acknowledge batch, closing JMS objects javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could not commit transaction. at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:255) at org.jboss.jms.server.bridge.Bridge.sendBatchXA(Bridge.java:1294) at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1354) at org.jboss.jms.server.bridge.Bridge.access$1900(Bridge.java:68) at org.jboss.jms.server.bridge.Bridge$SourceListener.onMessage(Bridge.java:1677) at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:229) at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:1043) at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120) 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) 2009-02-06 21:38:02,089 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] (Thread-50) unregistered connection ConnectionEndpoint[3g-zukpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] with remoting session ID ...-fqvdpkus-fx 2009-02-06 21:38:02,089 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (Thread-50) removing callback handler ServerInvokerCallbackHandler[4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkus-fx+4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkuz-g0] 2009-02-06 21:38:02,089 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) removed org.jboss.remoting.transport.local.LocalClientInvoker@102f380 from registry 2009-02-06 21:38:02,089 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-50) ServerInvoker (SocketServerInvoker[172.16.66.230:1603445283]) removing client callback handler with session id of 4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkus-fx+4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkuz-g0. 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] (Thread-50) unrecognized listener ID: 4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkuz-g0 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) removed org.jboss.remoting.transport.local.LocalClientInvoker@c0958a from registry 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1603445283] stopped threads in clientpool 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1603445283] stopped threads in threadpool 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1603445283] exiting 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1603445283] stopped 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) decremented org.jboss.remoting.transport.local.LocalClientInvoker@193e3d0's count, current count 3 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) decremented org.jboss.remoting.transport.local.LocalClientInvoker@51a0c9's count, current count 3 2009-02-06 21:38:02,090 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] (Thread-50) unregistered connection ConnectionEndpoint[ag-7vkpdvqf-1-qkp2dvqf-f20a68-e6u1gs4] with remoting session ID ...-fqvdpkv0-g4 2009-02-06 21:38:02,090 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (Thread-50) removing callback handler ServerInvokerCallbackHandler[4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkv0-g4+4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkv6-g7] 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) removed org.jboss.remoting.transport.local.LocalClientInvoker@187650e from registry 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-50) ServerInvoker (SocketServerInvoker[172.16.66.230:1604517796]) removing client callback handler with session id of 4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkv0-g4+4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkv6-g7. 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] (Thread-50) unrecognized listener ID: 4sg1u6e-86a02f-fqvd2pkq-1-fqvdpkv6-g7 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) removed org.jboss.remoting.transport.local.LocalClientInvoker@1fb9ed2 from registry 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1604517796] stopped threads in clientpool 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1604517796] stopped threads in threadpool 2009-02-06 21:38:02,090 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1604517796] exiting 2009-02-06 21:38:02,091 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-50) SocketServerInvoker[172.16.66.230:1604517796] stopped 2009-02-06 21:38:02,091 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) decremented org.jboss.remoting.transport.local.LocalClientInvoker@193e3d0's count, current count 2 2009-02-06 21:38:02,091 DEBUG [org.jboss.remoting.InvokerRegistry] (Thread-50) decremented org.jboss.remoting.transport.local.LocalClientInvoker@51a0c9's count, current count 2 2009-02-06 21:38:02,091 ERROR [org.jboss.jms.client.container.ClosedInterceptor] (Thread-50) ClosedInterceptor.ClientSessionDelegate[bg-7vkpdvqf-1-qkp2dvqf-f20a68-e6u1gs4]: method getXAResource() did not go through, the interceptor is CLOSED 2009-02-06 21:38:02,091 WARN [org.jboss.jms.server.bridge.Bridge] (Thread-50) null Will retry after a pause of 5000 ms
-
25. Re: Upgrading AS5 to use messaging 1.4.2.GA
Probably your RemoteJMSproviderLoader is pointing at the local instance.
-
26. Re: Upgrading AS5 to use messaging 1.4.2.GA
Nope, that's what I checked first.
The point I'm at now, if I shutdown AS5 and replace the two libraries with the originals, the bridge will work (sending messages to a machine on a different subnet). If I then change to the libraries I built I get a host of errors which you can see in my previous posts.
Here'e my JMS-ds.xml (The IP Address of the machine this is deployed on is 172.16.66.230):<?xml version="1.0" encoding="UTF-8"?> <connection-factories> <!-- ==================================================================== --> <!-- JMS Stuff --> <!-- ==================================================================== --> <!-- The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available. See http://jira.jboss.org/jira/browse/JBMESSAGING-843. --> <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider"> <attribute name="ProviderName">DefaultJMSProvider</attribute> <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> <attribute name="FactoryRef">java:/XAConnectionFactory</attribute> <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute> <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute> </mbean> <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider"> <attribute name="ProviderName">RemoteJMSProvider</attribute> <attribute name="ProviderAdapterClass"> org.jboss.jms.jndi.JNDIProviderAdapter </attribute> <attribute name="FactoryRef">/XAConnectionFactory</attribute> <attribute name="QueueFactoryRef">/XAConnectionFactory</attribute> <attribute name="TopicFactoryRef">/XAConnectionFactory</attribute> <attribute name="Properties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=jnp://172.16.8.52:1099 </attribute> </mbean> <!-- JMS XA Resource adapter, use this to get transacted JMS in beans --> <tx-connection-factory> <jndi-name>JmsXA</jndi-name> <xa-transaction/> <rar-name>jms-ra.rar</rar-name> <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property> <max-pool-size>20</max-pool-size> <security-domain-and-application>JmsXARealm</security-domain-and-application> <depends>jboss.messaging:service=ServerPeer</depends> </tx-connection-factory> </connection-factories>
The only thing I can be sure of at the moment is that the new libraries I built do not work. Although I should point out that I have left the remote instance using the new libraries. It would be fairer to say that the new libraries do not work with bridges to remote locations.
Another question if I might, why is jboss-messaging not tested against AS5?
I will investigate this further tomorrow and supply anything further I find out. -
27. Re: Upgrading AS5 to use messaging 1.4.2.GA
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@1195c94(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@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. -
28. Re: Upgrading AS5 to use messaging 1.4.2.GA
"rnicholson10" wrote:
Another question if I might, why is jboss-messaging not tested against AS5?
Because 1.4.2.GA is not a release targeted for JBoss 5, it's for JBoss 4.x.
That's why you had to build it yourself against JBoss 5 libraries.
Latest version of JBoss 5 comes with 1.4.1.GA. Which is thoroughly tested. Next version of JBoss 5 will come with a different version of JBM, and yes that's test too.
If you decide to replace the version of any component in a shipped version of AS you do so at your own peril.
Howard - can you investigate this, to see if there is a real issue here, or it's just a misconfiguration?
rnicholson10 - please provide us with a small test program and configuration which replicates this issue, so Howard can investigate... -
29. Re: Upgrading AS5 to use messaging 1.4.2.GA
How should I supply the test program and configuration?