JBoss Messaging and JBoss ESB

[jendruch]

Hi,
I?ve looked at "Admin Guide" and posts on developers forum where it?s written how to use JbossESB and JBoss Messaging ? it?s very clear ? but I can?t make it working (it must be my stupid mistake:-). I?ve created my own CBR application and it works fine on JbossMQ. To start working it with JBoss Messaging I:
1) unzip jboss-4.0.5.GA
2) install jboss-messaging-1.0.1.SP2
3) copy jboss-messaging-client.jar to jboss-4.0.5.GA\client
4) install jbossesb-4.0GA

But after all, when I run my CBR application I?ve got error (on JBossAS console):

java.io.IOException: Can not read data for version 6. Supported versions: 1,2
at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:426)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:478)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:631)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:293)

so I add to classpath (in my build.xml file) jboss-remoting.jar from jboss-messaging.sar but It?s the same error on JBossAS console.

What have I done wrong?

Best regards
jendruch

[kurtstam]

Hi Jendruch,

Can you try sending a JMS message using a small standalone client directly to JBossAS (the one with JBossMessaging). And for now leave the ESB out if it? For a little client you may use the code of the JMS bank in the trailblazer example. That should give you an easier problem to solve.

I actually have not had the time yet to use JBossMessaging with the ESB myself, but Jeff deLong did. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=94539&start=30

I hope this gets you on your way.

--Kurt

[jendruch]

thanks,

well - I did it - with no success - I've got problem with:
- "5) put jboss-messaging-client.jar in server/../lib" - after this server (4.0.5.GA) failed at start - but I think putting this jar in server/client is enough.
- Putting jboss-remoting.jar from jboss-messsaging.sar - that was another problem which is "root cause of error".

So I had to left JBoss Messaging in peace and start configure ESB Gateway on WebSphere MQ 6.0 on zLinux. This seems to work:-)

[jendruch]

...but of course I'll come back to ESB with JBossMessaging - now still waiting for any idea what to do.

Thanks for any suggestions.

[kurtstam]

I'm happy you found a 'workaround' :). I'll take a look at it. I should have time lateron this week. Wouldn't want you to use this 'infererior' solution for too long ;). --Kurt

[kurtstam]

Just a quick check; which version of jboss messaging are you trying to use?

[jendruch]

jboss-messaging-1.0.1.SP2 (but I've tried jboss-messaging-1.2.0.Beta2 too)

[kurtstam]

Well it looks like 1.2.0.Beta2 has a mashalling issue that just got fixed. So for now I will go try to set it up using 1.0.1SP4 and then revalidate when 1.2.0.CR1 is released.

[kurtstam]

Hi Jendruch,

I just successfully tried jboss-messaging-1.0.1SP4.
The solution is pretty easy. As explained in this thread on the messaging forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=100719
We (JBossESB) needs to be in the same classloading domain. So replace the content of the jbossesb.sar/META-INF/service.xml with:

<?xml version="1.0" encoding="UTF-8"?>

<server>
 <!-- Starts the listener controler -->
 <mbean code="org.jboss.soa.esb.listeners.config.ConfigurationControllerService"
 name="jboss.org:service=ConfigurationController"
 description="Configuration controller which generated the config files for the listener and gateway controllers">
 <attribute name="ConfigurationFile">jbossesb.xml</attribute>
 <depends>jboss.org:service=JBossESBDependencies</depends>
 <depends>jboss.org:service=JuddiRMI</depends>
 <depends>jboss.jca:service=DataSourceBinding,name=JBossESBDS</depends>
 </mbean>
 <loader-repository>
 jboss.messaging:loader=ScopedLoaderRepository
 </loader-repository>
</server>

There is no need to add the jboss-messaging-client.jar anywhere.

With that change all worked fine for me.

I hope this helps :)

--Kurt

[kurtstam]

Oh I forgot to mention that the entries in the esb-quickstart-service.xml now need to look similar to:

<?xml version="1.0" encoding="UTF-8"?>
<server>
 <loader-repository>jboss.messaging:loader=ScopedLoaderRepository
 <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
 </loader-repository>
 <mbean code="org.jboss.jms.server.destination.Queue"
 name="jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request"
 xmbean-dd="xmdesc/Queue-xmbean.xml">
 <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
 </mbean>
</server>

to bring up your queues.

--Kurt

[jendruch]

Kurt - THANKS!!!!!!!

[jjarkko]

I'm not that familiar with the differences of JBossMQ and JBoss Messaging, so I'd like to ask a humble question. Why use JBoss Messaging instead JBossMQ?

[kurtstam]

You should probably ask the Messaging guys. But is going to replace JBossMQ as the default JMS provider (I think as soon as JBossAS 4.2). It already supports full clustering and other messaging formats. You can take a look at

http://labs.jboss.com/file-access/default/members/jbosslabs/freezone/podcasts/Messaging.m4v

I've now also prepared a how-to get it installed with JBossESB:
http://wiki.jboss.org/wiki/attach?page=JBossESBDocumentation%2FJBESB-JBM.pdf

--Kurt

[kurtstam]

Oh and perhaps the coolest feature of JBM is that you can run it standalone, so we can package it up with the JBESB.