• 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

Problem in receiving message from MQ queue

 
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have applcation that using MQ Series java for sending and receiving meassage from MQ queues.I have to convert that code into spring jms.I able to conncet with MQ series and sending message successfully.
The application send message to mainframe thorugh queue and receive message from queue.
But while recieving from queue through sping jms code getting problem to receive message.

Please help in this issue.

Thanks in advance.
 
Ranch Hand
Posts: 4864
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm afraid the phrase "getting problem to receive message" doesn't give us enough information about what may be going wrong. No one can help unless you give us more information. Please read this link to give you an idea of the type of information we will need to help you solve the problem.
 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi

My application also having the same issue as described below.

Main frame application sends messages to the MQ and MDB bean invokes when the message isput in the queue and invokes another session ejb to get the response from databse. For some reason (maybe settings) MQ manager fails to get the messages for the first or after ceratin time of inactivity...but after that works just fine. I tried changing the default setting with IBM suggested setting for this error reason.Nothing worked...can any body aslo having the same issue and did find any solutions pls..post it here.

Here is the error log


 
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi !

You have several ways to detect errors.
The logfile systemout.log is probably the most common for the WAS
(WebSphere Application Server)

Look for MQJMS**** exceptions

Normally You will start to have connection problems: wrong Quemanger, Quename
etc. MQ reasen code like: 2005 2058 2008

Try the MQ / jms problem determination redbooks
 
Venkata
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

If queuemanager or other is wrong i will get this error everytime i send the messge...that is not the case with my app. only after certain time of inactivity or for the first attempt in a day(may be because of long inactivity again)will cause this...but rest of the works just fine....


Thanks
Ven
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We are having the same problem here. Our problem was ultimately resolved by changing the tcp_keepidle value to something below 2 hours (we used 10 minutes). I have a document that I have almost finished explaining how the different settings caused us to encounter this error. I can send it to you if you like.

Ryan
 
Ryan Maurer
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sorry, I should have been a little more specific in my post. We have a UNIX server that is sending the message to MQ. I'm not sure if there is something equivalent to tcp_keepidle on the mainframe. The problem is that the connection that is being held by the MDBListener is getting severed by the server that has MQ. I believe the default for this is 2 hours. Anyway, we found two solutions to this. We wrote a dummy program to drop a message on the queue every half-hour. This keeps the connection from going two hours without any activity and getting closed. The other option was to change the value of the tcp_keepidle setting. In essence, this does the same thing as the first option without having another program to maintain and the errors that the bean would generate.

Hope this helps.

Ryan
 
Ryan Maurer
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm sorry, the information I posted earlier was not 100% accurate. It appears our issue was related to firewall. We had them bump up the timeout for the firewall rule on port 1414 and I think that is going to resolve our problem. I will know for sure in a couple days and I will post the full results.


Ryan
 
Ranch Hand
Posts: 3389
Mac MySQL Database Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That's great Ryan Maurer

It would help other people in future
 
Ryan Maurer
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Okay, here is the full description of the changes we made. It was the firewall that was severing the connections after 2 hours. This gave us 2 problems. The first was that having Minimum conections set at 1 in the ConnectionFactory kept a connection in the connection pool. After 2 hours of inactivity, the connection is severed, and the customer gets an 'Unexpected System Error'. By changing the Minimum connections to 0, the connection is cleaned up by the Pool Management Thread before 2 hours expires.

The second problem is that the MDBListener keeps the connection it is given, so when that connection gets severed after 2 hours of inactivity, we see the ListenerService have to stop and restart because of the bad connection. This is not acceptable to our customers. We are getting around this by bumping the firewall timeout to 24 hours and we are running a program to drop a message on the queue. This keeps the connection alive and prevents it from being severed.

I hope this makes sense.
 
Venkata
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

We also had the same problem as described above.What we did was...we increased the firewall time upt o 72hrs....considerign that if there is no activity during holidays....and if for some reason listener ports have beean stopped...we are using 2 custom properties to retry to establish the connection with Qmanager for about 25 attempts each 15 minutes apart...all these resolved our issue completely...

Thanks
Ven
 
Ranch Hand
Posts: 137
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ryan,

Thanks for your response.Can you send me the document across to my email ID

trysatk2001@yahoo.com


I have similar problem. It will be very much helpful to me.

Thanks,
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic