wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes When would would JMS fail Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "When would would JMS fail " Watch "When would would JMS fail " New topic
Author

When would would JMS fail

meka toka
Ranch Hand

Joined: Dec 11, 2002
Posts: 75
Hi,
I am working on a project that involves messaging Q's and Topics. We have the application fully tested and working. But when we tried to run the same application on one of our client's network the asynchronous messages wouldnt go through.
What could be the possible scenarios where JMS could fail ? How to overcome them ?
Between, I use JBoss 3.0.6, EJB 2.0, CMP 2.0

Regards
Meka Toka


Thanks<br />MekaToka<br />SCJP 1.4
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Every vendor's JMS implementation is different. You might have more luck asking this in the JBoss forum.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Nitzan Levi
Greenhorn

Joined: Feb 19, 2003
Posts: 22
hi,
you need to supply more information about the failure, and what was the changes in the server/client configuration that you'v made !


nitzan levi :-)
meka toka
Ranch Hand

Joined: Dec 11, 2002
Posts: 75
Hi,
Everything i have is very standard.
Have a Topic T running on a server A, and 'n' number of clients are subscribed to the topic T.
The messages on the topic from A are not reaching the clients.
However, this happens only at my client site, when we tested the application in our development lab everything works fine. We also found out the 'CULPRITS' are their systems.
Now my question is what are the things(settings or configuaration on those systems) that might be responsible for this kind of abnormal behaviour.
These systems run Win 2K Professional or Xp professional.
By the way, all the synchronous calls, like the clients calling the methods on the beans on the server etc etc .. all of them work fine.
Regards
Meka Toka
[ March 16, 2003: Message edited by: meka toka ]
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
Is there a firewall between the Server and the Clients?
If so, then that is most likely the cause.
JBoss has four type of JMS Connections, the one used by most is the OIL (Optimized Invocation Layer) Connection. This opens two communication channels, one from the server to the client and one from the client to the server. In most firewall situations this will not be allowed. You will need to use a different type of Connection Factory that handle bi-directional communication in a single connection.
If there is no firewall involved then ignore my post...
meka toka
Ranch Hand

Joined: Dec 11, 2002
Posts: 75
Hi,
We were at the client side and we were testing on an isolated network. A couple of computers connected to a Hub (isolated).
The only difference is the ip's we tested were class C and the ip's on client side are class A.
Then we happen to bring a few laptops, and test them within our network. We noticed that the asynchronous messaging(JMS) was failing.
So definetly there is something on the systems. Are there any links out there that can let me learn more about the communication channels.
Regards
Meka Toka
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
If your organization is serious about using JBoss than I suggest you get them to spring for the documentation here.
Nitzan Levi
Greenhorn

Joined: Feb 19, 2003
Posts: 22
hi,
let me understand currectly , the subscribing part is successfull and the publication also , and the clients don't get the messages ??
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: When would would JMS fail
 
Similar Threads
Difference between JMS Queue and MQ queue
Seeking ideas for the design of a JTA/XA transaction test
JMS AND EJB
JMS or JCA or Webservice ?
JMS : QueueConnection.close()