This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Darcy DeClute's Scrum Master Certification Guide: The Definitive Resource for Passing the CSM and PSM Exams and have Darcy DeClute on-line! See this thread for details.
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
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