JBossESB Quickstart Sample not working on JBossAS-4.2.2.GA c

[brad.o]

Hello JBossESB Community!

One of our current goals is to use JBossESB-4.2.1.GA deployed to JBossAS-4.2.2.GA using JBoss Messaging instead of JBoss MQ. Since JBossAS 4.2.x uses JBossMQ by default, I have installed the latest version of JBoss Messaging 1.4.0.SP3 into JBossAS per instructions on

http://labs.jboss.com/jbossmessaging/docs/userguide-1.4.0.GA/html/installation.html

After installation, I can run the JBoss Messaging tests successfully with my JBossAS. However, when I then try to deploy JBossESB to this new JBossAS configuration (configured for JBoss Messaging) I am able to deploy a JBossESB quickstart sample such as helloworld (using ant deploy), and verify that the jboss.esb.quickstart.destination queues are properly bound, but when I try to run the helloworld test (using ant runtest), the test simply hangs. The last output I see on the client console is "[java] Connection Started".

I am now attempting to debug the sample and see exactly where it is hanging. If anyone has any input into this problem, please let me know.

Thanks,

Brad

[beve]

Hi Brad,

JBoss Messaging 1.4.0.SP3 requires JBoss Remoting 2.2.2.SP4.

Can you check that you have the correct version of jboss-remoting:

#java -jar jboss-remoting.jar
JBossRemoting Version 2.2.2.SP4 (Bluto)

This version should be in ${org.jboss.esb.server.home}/server/default/lib directory.

Regards,

Daniel

[brad.o]

Hi Daniel,

Thanks for the quick response!

It appears I have version 2.2.2.SP1 instead. Let me find and grab the latest version.

#java -jar jboss-remoting.jar
JBossRemoting Version 2.2.2.SP1 (Bluto)

[brad.o]

I fetched the latest version of jboss-remoting.jar (version 2.2.2.SP4) from http://repository.jboss.com/jboss/remoting/2.2.2.SP4-brew/lib/ and placed it into my $JBOSS_HOME/server/[config]/deploy directory, overwriting the existing version. I then undeployed the helloworld sample, restarted my JBossAS, and then rebuilt the helloworld sample from scratch and redeployed. I am still seeing the

ant runtest

hang from the client side after outputting "[java] Connection Started". No output is printed from the server console.

As of now, I am still unable to run JBossESB-4.2.1.GA deployed to JBossAS-4.2.2.GA using JBoss Messaging-1.4.0.SP3 (with jboss-remoting 2.2.2.SP4).

I would appreciate any further insight into this issue.

Thanks!

[beve]

I fetched the latest version of jboss-remoting.jar (version 2.2.2.SP4) from http://repository.jboss.com/jboss/remoting/2.2.2.SP4-brew/lib/ and placed it into my $JBOSS_HOME/server/[config]/deploy directory, overwriting the existing version.

Was that a typo, the jar should go inte server/[config]/lib/.
Can you just make sure that the remoting jar is in the right dir.

I've got this running on my machine so I'm sure we can sort this out.

/Daniel

[beve]

Just to be sure that we have the same set up... Here are the versions I've got.

jbossesb-server/client/jboss-messaging-client.jar -> 1.4.0.SP3
jbossesb-server/server/default/lib/jboss-messaging.jar -> 1.4.0.SP3
jbossesb-server/server/default/lib/jboss-remoting.jar -> 2.2.2.SP4 (Bluto)

To get the version of the messaging jars you can run the following:

jar xvf jboss-messaging-client.jar VERSION
cat VERSION

Regards,

Daniel

[brad.o]

Yes, that was a typo. I placed the jar into $JBOSS_HOME/server/[config]/lib earlier.

Thanks!

[brad.o]

Hi Daniel,

Are you running the standalone jbossesb-server-4.2.1.GA ? I'm just wondering since I am using the other binary distribution jbossesb-4.2.1.GA, which is meant to be deployed into an application server (since we are running JBossAS-4.2.2.GA). I'm wondering if therefore I am seeing different behavior from your setup.

It seems like our directory structures differ somewhat. For example, I only have a jboss-messaging-client.jar under $JBOSS_ESB_HOME/lib/ext .

I can get the versions of those other jars.

Thanks!

[beve]

Hi Brad,

We have a JBoss AS 4.2.0.GA cluster infront of our standalone jbossesb-servers (latest build). Both are using JBoss Messaging 1.4.0.SP3.

We had the same problem you are describing when we upgraded to JBM 1.4.0.SP3. Client simple hung on when/after connecting to the server.

The solution to this was to have the correct jboss-messaging-client.jar, and jboss-remoting.jar on the client side (aswell as the correct version of messaging and remoting on the servers).

If you have updated your JBossAS server and jbossesb-server and have the correct versions on the client and still getting this problem, then it might be that JBossAS-4.2.2.GA is a different case :(

I'm sort of out of ideas at the moment. But I'll post back if I come up with anything.

/Daniel

[brad.o]

Thanks Daniel!

You showed me the problem. I did not have the correct version of jboss-messaging-client.jar on my classpath during the runtest. By default, JBossESB-4.2.1.GA comes with jboss-messaging-client.jar version 1.4.0.GA, and I simply needed to use the newer version 1.4.0.SP3 that came with JBoss Messaging 1.4.0.SP3.

I can now deploy and run the JBossESB helloworld sample.

By the way the versions I had were the following:

in [JBossAS]/server/[config]/lib:

jboss-remoting.jar -> 2.2.2.SP4
jboss-messsaging.jar -> 1.4.0.SP3

in [JBossESB]/lib/ext:

jboss-messaging-client.jar -> now using 1.4.0.SP3 that was bundled with JBoss Messaging 1.4.0.SP3 instead of version 1.4.0.GA which came with JBossESB-4.2.1.GA