aspose file tools*
The moose likes Websphere and the fly likes WAS 5.0 ND and JMS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS 5.0 ND and JMS" Watch "WAS 5.0 ND and JMS" New topic
Author

WAS 5.0 ND and JMS

Ruben Melcon
Greenhorn

Joined: Dec 02, 2003
Posts: 14
I'm working with WAS 5.0.2 Network Deployment and i have to use the internal JMS provider for my application. I have a lot of problems with the internal provider because it is undocumented and it not works appropriately.
The first thing that i noticed is that it not operates in a cluster environment. Aparently, there is a master node that when is stopped causes the failure of the application.
Other times the problem resides in that MQ receives unknown messages that it can't process.
I have never to be able to obtain a JMS resource from an external application. I always had to make an EJB to get the resources.
And finally i am getting the following error: "MQJE003: IO error transmitting message buffer".
Is there anybody that achieve that JMS worked appropriately??
Thanks
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
That's why this is called the INTERNAL messaging provider. It is meant only for use between WebSphere applications. It does not work with external applications, is not clusterable, and does not provide failover. If you need those attributes, you should buy WebSphere MQ.
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.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: WAS 5.0 ND and JMS