| Author |
Message
|
| kommaraju |
 Posted: Tue Jul 25, 2006 1:19 am Post subject: MQ JMS Error : Request your assistance |
 |
|
Newbie
Joined: 28 Jan 2006
Posts: 6
Location: Warsaw
|
| We have a JMS application which continuously checks on the queues for new messages. Today we are getting an error MQJMS1034E followed by MQJMS1022E. Can you please guide me how to rectify the problem? IS there any parameters to be set to avoid this kind of problems? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 25, 2006 2:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your first step is to gather a lot more information.
What's changed? When?
What is the linked exception with these JMS exceptions?
What does a search here for these JMS Exceptions tell you?
What is the code trying to do that throws the exception?
What other errors are listed in the application's log? What other errors are listed in the system log?
Is WebSphere MQ your JMS provider? Or something else?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kommaraju |
| Posted: Tue Jul 25, 2006 6:21 am Post subject: |
|
|
Newbie
Joined: 28 Jan 2006
Posts: 6
Location: Warsaw
|
| Thank You so much for the response. I will get back to you with these details as soon as possible. |
|
| Back to top |
|
|
| urbank |
| Posted: Wed Feb 14, 2007 3:26 am Post subject: MQJMS1034E and MQJMS1022E |
|
|
Novice
Joined: 14 Feb 2007
Posts: 16
Location: St. Gallen / Switzerland
|
[b]kommaraju:[/b] did you get a solution for this problem. We are facing the same problem:
Errormessage:
2007.02.14 11:32:36 MQJMS1034E MessageListener threw: java.lang.OutOfMemoryError: Java heap space
2007.02.14 11:32:36 MQJMS1022E failed to redirect message
Environment:
winXP
jdk1.5.0 11 (we just upgraded in the last days from 1.4; we had the described error already then.
resin 2.x
Websphere MQ 6.x JMS/Publish-Subscribe
Errordescription:
The error occurs on the subscriber-machine.
The publisher sended a message 7 seconds before the error on the consumer occured.
To the questsions posted by jefflowrey:
It's hard to say, what really happens, if you have OutOfMemory Exceptions. The only thing, that we saw in the logfiles is what we wrote in the Errordesciption above.
We would appreciate any help. It could help, if someone could post us a tip, what class to bring in log-debug mode.
Thanks.
Urban |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 14, 2007 3:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
easiest fix for an out of heap error is to increase the heap, using X args to the jvm.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| urbank |
| Posted: Mon Feb 19, 2007 2:05 am Post subject: |
|
|
Novice
Joined: 14 Feb 2007
Posts: 16
Location: St. Gallen / Switzerland
|
jefflowrey: Thanks for your answer. We have encreased the JVM memory and it works fine.
Regards Urban |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Feb 19, 2007 2:15 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| I would suggest that you do not continously look for messages. Instead issue the JMS version of MQGET with a WAIT interval. This allows MQ to pass you a message as soon as one becomes available and reduces the overhead of repeated MQI calls. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 19, 2007 5:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
| I would suggest that you do not continously look for messages. Instead issue the JMS version of MQGET with a WAIT interval. This allows MQ to pass you a message as soon as one becomes available and reduces the overhead of repeated MQI calls. |
A JMS MessageListener will do that for you.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
