[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
This probably a JBM issue. I tested JBM1.4.2.GA (AS4 build) vs JBoss 4.2.3.GA and JBM1.4.2.GA (AS5 build) vs JBoss 5.0.0.GA, both failed. Here is the scenario: I have two machines Machine-1 and Machine-2. 1) Machine-1 starts a normal messaging node (with test queues deployed). Machine-2 starts with a remote JMSProvider deployed in jms-ds.xml, as RemoteJMSProvider org.jboss.jms.jndi.JNDIProviderAdapter java:/XAConnectionFactory java:/XAConnectionFactory java:/XAConnectionFactory java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=jnp://10.66.65.13:1099 //point to machine 1 2) change bridge service in bridge example to point the target queue to remote provider (Machine-1). Also the example code is changed to receive messages from the remote target queue. 3) run bridge example on machine-2 so the bridge service is deployed at Machine-2. The bridge can find local source queue and remote target queue (on Machine-1) and I can see the messages are received by bridge and then bridge sends them to the remote target queue. 4) the result is that messages are all sent to the local target queue (/queue/B on machine-2, rather than /queue/B on machine-1). So the example will never receive a message from the remote target queue. 4) In Bridge sendMessages() method, if I create the producer every time it sends a message, ( from lookup the factory to create the producer), the bridge can work. Haven't traced out the true reason but I think I'm close. Has someone encountered this before? Also I'll see if 1.4.1.GA has that problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4208128#4208128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4208128 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Hi, I assume you are using bridge example with some modification. I'll try myself. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4208060#4208060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4208060 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
How should I supply the test program and configuration? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207996#4207996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207996 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207983#4207983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207983 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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.jmsactivations...@1195c94(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@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=6 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 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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): | | | | | | | | | | | DefaultJMSProvider | org.jboss.jms.jndi.JNDIProviderAdapter | java:/XAConnectionFactory | java:/XAConnectionFactory | java:/XAConnectionFactory | | | | RemoteJMSProvider | | org.jboss.jms.jndi.JNDIProviderAdapter | | /XAConnectionFactory | /XAConnectionFactory | /XAConnectionFactory | | 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 | | | | | | JmsXA | | jms-ra.rar | org.jboss.resource.adapter.jms.JmsConnectionFactory | javax.jms.Topic | java:/DefaultJMSProvider | 20 | JmsXARealm | jboss.messaging:service=ServerPeer | | | | 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207965#4207965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207965 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Probably your RemoteJMSproviderLoader is pointing at the local instance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207876#4207876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207876 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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_N326865078927536.invokeTarget(ConnectionAdvised$sendTransaction_N326865078927536.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_N326865078927536.invokeTarget(ClientConnectionDelegate$sendTransaction_N326865078927536.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.
[jboss-user] [JBoss Messaging] - 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: | | | jboss.messaging:service=JMSProviderLoader,name=JMSProvider | jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider | | /queue/speQueue | /queue/speQueueB | 2 | 1 | -1 | 5000 | -1 | false | | Why would the bridge deliver locally? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207862#4207862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207862 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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.transpo
[jboss-user] [JBoss Messaging] - 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207570#4207570 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207570 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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! :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207545#4207545 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207545 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Oops, replace output/jboss-messaging.sar with output/lib/jboss-messaging.sar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207543#4207543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207543 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
"clebert.suco...@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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207542#4207542 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207542 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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*. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207511#4207511 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207511 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207508#4207508 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207508 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - 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? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207502#4207502 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207502 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
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. Looking at the diff.patch result it appears that many of the xxx-persistence.xml files were changed, but not the one for hsql. Which explains why I wasn't seeing any differences. So besides the JAR file udpates, if you are using a database other than hsqldb, you also have to update the persistence-service.xml file. Apparently updated AS 5.0.0.GA to the latest Messaging is not for the faint of heart. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207499#4207499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207499 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA (Repost)
anonymous wrote : compared the generate jboss-messaging.sar between 1.4.1 and 1.4.2 It can't be the same. I just did a diff between 1.4.1, and 1.4.2 and I can see the changes: svn diff http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_1_GA/ http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_2_GA/ > tmp/diff.patch | Mainly on where you said you need a fix: https://jira.jboss.org/jira/browse/JBMESSAGING-999?page=com.atlassian.jira.ext.fisheye%3Afisheye-issuepanel Those fixes ^ ^ are not available at 1.4.1.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207464#4207464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207464 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
anonymous wrote : compared the generate jboss-messaging.sar between 1.4.1 and 1.4.2 It can't be the same. I just did a diff between 1.4.1, and 1.4.2 and I can see the changes: svn diff http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_1_GA/ http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging Mainly on where you said you need a fix: https://jira.jboss.org/jira/browse/JBMESSAGING-999?page=com.atlassian.jira.ext.fisheye%3Afisheye-issuepanel Those fixes ^ ^ are not available at 1.4.1.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207464#4207464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207464 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Taking another tact, I got and built 1.4.1.GA source and compared the generate jboss-messaging.sar between 1.4.1 and 1.4.2 - they are the same. So the steps to update AS 5.0.0.GA to Messaging 1.4.2 should be copying jboss-messaging-client.jar to the client directory and jboss-messaging.jar to the common/lib directory. I did that and my messaging clients are working. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207455#4207455 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207455 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA (Repost)
anonymous wrote : What is the correct procedure for upgrading messaging on AS5? You first need to get a correct release, compiled for JBoss5. This is because of AOP dependencies as the byte weaving is different on both versions. JBossMessaging 1.4.2 was compiled for JBoss 4.2, if you want to install JbossMessaging 1.4.2 on Jboss5 you need to follow these steps: - svn co http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_2_GA/ jbm14 - cd jbm14 - change build.properties to AS5 - ant release-bundle You will have the release under ./jbm14/release and a zip-file under ./output - Replace any jboss-messaging.jar or jboss-messaging-client.jar on jboss5 tree by the ones under ./release - Make sure you also use the configs from ./example/config (That will include YOURDB-persistence-service.xml and remoting-bisocket-service.xml) A warning though: When we released JBM 1.4.2, we validated the configs for JBoss 4.2 as part of our release process. I don't think you would have an issue, but you should be aware and do some basic tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207449#4207449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207449 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
anonymous wrote : What is the correct procedure for upgrading messaging on AS5? You first need to get a correct release, compiled for JBoss5. This is because of AOP dependencies as the byte weaving is different on both versions. JBossMessaging 1.4.2 was compiled for JBoss 4.2, if you want to install JbossMessaging 1.4.2 on Jboss5 you need to follow these procedures: - svn co http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_2_GA/ jbm14 - cd jbm14 - change build.properties to AS5 - ant release-bundle You will have the release under ./jbm14/release and a zip-file under ./output - Replace any jboss-messaging.jar or jboss-messaging-client.jar on jboss5 tree by the ones under ./release - Make sure you also use the configs from ./example/config (That will include YOURDB-persistence-service.xml and remoting-bisocket-service.xml) A warning though: When we released JBM 1.4.2, we validated the configs for JBoss 4.2 as part of our release process. I don't think you would have an issue, but you should be aware and do some basic tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207449#4207449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207449 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
I had working version of jboss messaging but need to upgrade for fixes to the following issues. https://jira.jboss.org/jira/browse/JBMESSAGING-999 I have tried just replacing the jars and the xml files from the download on the site. If these jars are not compiled for AS5 and they need to be that might explain why the bridge fails to work correctly. As I pointed out messaging works correctly within a local instance of JBoss. The problems begin once I try to use a bridge. How do you normally upgrade messaging in AS5? There must be some procedure for doing so, how else would you test it normally with AS5? Building the jars myself is not a problem, but if they cannot be built for AS5 I'm unsure as to how to continue... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207446#4207446 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207446 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
ant release-bundle only works on JBoss 4.2, as we needed to do a lot of stuff to replace jboss-mq. Replacing jboss-messaging on JBoss5 should be just replacing a JAR, because it already contains JBossMessaging 1.4 there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207443#4207443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207443 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
ant release-bundle should work fine. If not, Howard or Clebert - can you please advise why not? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207442#4207442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207442 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Close, but no cigar. * "ant distro" does not work because there is no distro target in build.xml. * The util/release-admin.xml file in the resulting zip file is still 4.2.x specific - it doesn't copy "deployers", it fails when it cannot find the old 'jms' directory, the contents of messaging.sar do not match the contents of the server/default/deploy/messaging directory, it copies the messaging.jar to server/messaging/lib instead of common/lib. Which brings up another interesting point - for the release-admin.xml file to be fully 5.0.0.GA-compliant, it has to upgrade every configuration because once common/lib/messaging.jar has been replaced all configurations are now running Messaging 4.2.2. I was sure that I built it wrong so I did it twice, double-checking that I set the property correctly. Same result. Conclusion: upgrading JBoss AS 5.0.0.GA to use JBoss Messaging 4.2.2.GA is not easy, I still don't have it working. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207433#4207433 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207433 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
should be ant release-bundle then go to output/lib find the zip View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207416#4207416 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207416 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
sounds familiar, so, in total, that would be: svn co https://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_2_GA edit build properties ant distro ?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207409#4207409 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207409 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
hi, you can change the build.properties file, set integration.base=AS5 then kick off the build. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207408#4207408 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207408 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Hmmm, looking at that build script a little more, it might work only for AS 4.2.x. If it works for you for 5.0.0, let me know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207405#4207405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207405 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
Actually not quite. The JBM 1.4.2 available on the download site is built against the jars for JBoss AS 4.3, *not* jboss 5 so won't work with JBoss 5. If you want to run 1.4.2 against JBoss 5 you'll need to build it from source with a switch, can't remember it off the top of my head, but Clebert or Howard will know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207404#4207404 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207404 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Upgrading AS5 to use messaging 1.4.2.GA
First, you do realize that JBoss AS 5.0.0.GA comes with JBoss Messaging 4.2.1.GA? If you stil want to upgrade to 4.2.2.GA, then go to jbosss-messaging-1.4.2.GA/util and run: ant -f release-admin.xml -Djboss.home= You will get a new configuration named 'messaging' which is a copy of 'default' with Messaging 4.2.2 installed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207402#4207402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207402 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
