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.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Jeanne Boyarsky
  • Tim Cooke
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Mikalai Zaikin
  • Carey Brown

WAS 5.0 ND and JMS

Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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??
Posts: 3892
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
Alas, poor Yorick, he knew this tiny ad:
a bit of art, as a gift, that will fit in a stocking
    Bookmark Topic Watch Topic
  • New Topic