• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

WAS 5.0 ND and JMS

 
Ruben Melcon
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic