-
1. Re: Messaging works in stand-alone client but not in Enterpr
alfred.rsa Feb 6, 2007 12:19 AM (in response to alfred.rsa)Hi all
I found the bug. It is related to a bug in Messaging 1.0.1SP2, JBMESSAGING-682:
The cause is version of jboss-remoting.jar in server/messaging/lib and server/messaging/deploy are different.
The ant script that comes with JBoss Messaging does not overwrite jboss-remoting.jar in server/messaging/lib.
After manually replacing the file, everything worked.
Regards
Alfred -
2. Re: Messaging works in stand-alone client but not in Enterpr
timfox Feb 6, 2007 5:39 AM (in response to alfred.rsa)Sure, the versions are different, this is why you have to do a scoped deployment.
Substituting the versions may work, but is not recommended. -
3. Re: Messaging works in stand-alone client but not in Enterpr
timfox Feb 6, 2007 5:48 AM (in response to alfred.rsa)See
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
Also http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingUser_Enabling_access_to_remote_JBoss_Messaging_instance
may be useful depending on your deployment scenario.
You don't need jboss-messaging-client.jar if everything is on the same machine.
Just make sure your application ear is scoped and references the same classloading domain as JBM.
Don't copy, add or overwrite any jars in the lib, server/messaging/lib or server/messaging/deploy directories.
If you do, then you may break other apps or the app server which require there own versions of the lib.
The installation script should do this all for you, apart from scoping your own EAR which you must do yourself. -
4. Re: Messaging works in stand-alone client but not in Enterpr
alfred.rsa Feb 6, 2007 1:27 PM (in response to alfred.rsa)Hi Tim
Thanks for the advice. I actually did try http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingUser_Enabling_access_to_remote_JBoss_Messaging_instance but I couldn't get it to work.
Just one thing though, if replacing the jars is not recommended why is it listed as the work-around for JBMESSAGING-682?
Am I right in thinking that JBoss 4.2 will not have the same issues with this?
Regards
Alfred -
5. Re: Messaging works in stand-alone client but not in Enterpr
timfox Feb 6, 2007 1:39 PM (in response to alfred.rsa)"alfred.rsa" wrote:
Just one thing though, if replacing the jars is not recommended why is it listed as the work-around for JBMESSAGING-682?
JBMESSAGING-682 is just a bug report submitted by another user.
It doesn't mean we agree it's a bug.
In fact, Ovidiu has closed it with a comment to that effect. I.e. the user was mistaken.
It's not valid to copy jars there. Messaging needs to be in a scoped deployment.
If you use the script this should be automatic.
Am I right in thinking that JBoss 4.2 will not have the same issues with this?
4.2 will not require a scoped deployment. -
6. Re: Messaging works in stand-alone client but not in Enterpr
alfred.rsa Feb 6, 2007 2:05 PM (in response to alfred.rsa)Tim
Thanks for your help. I will have a look at scoping the ear again now I have more info.
Regards
Alfred -
7. Re: Messaging works in stand-alone client but not in Enterpr
timfox Feb 6, 2007 2:09 PM (in response to alfred.rsa)If you follow the instructions in the distro to create an installation based on a clean JBoss 4.0.x installation, all you should need to do then is specify the classloading domain in your EAR and it should work.
Tell me if you have any problems.