• 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 ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Strange behaviour in Exception delivery for JMS connection

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
I am connecting to Websphere application server version 6.0, I am using an ExceptionListener to make use from API notification when the connection between my application and application server is broken to recover my connection:



I used this technique before in other MQ providers like Sun Message Queue and IBM MQSeries, I was notified only one when the connection is broken.

But when I am connected to Websphere, I will be notified three times. do any body knows why this behavious happens? how I am going to make it called only once. Below is my sample test and the output for it:

FYI: What I am doing to test this case is shutting down application server using stopServer.sh command



output is:

 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic