| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ Exception Completion Code 2, Reason 2195+2009 |
« View previous topic :: View next topic » |
| Author |
Message
|
| System9 |
 Posted: Thu Oct 11, 2007 12:56 am Post subject: MQ Exception Completion Code 2, Reason 2195+2009 |
 |
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Hi All,
I am using Jboss application server for my application and placing XML messages on MQ queue.It is working fine ,But If I keep the application idle for more than 2:30 hours ,channel is getting closed .(MQ queue and MQ manager are not null)and it is throwing
com.ibm.mq.MQException: MQJE001: Completion Code 2,Reason 2195,followed by Completion Code 2,Reason 2009 errors for each message.If I restart the application it is working fine.I have observed the exception every time when i kept the app idle for more time.
I tried to check any setting in jboss causing this time out.But not able to trace it out. Here is the exception stack trace..
INFO <STDOUT> MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data
INFO <STDOUT> Error occured during API call - reason code0
MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
INFO <STDOUT> MQJE001: Completion Code 2, Reason 2009
INFO <STDOUT> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
INFO <STDOUT> MQJE001: Completion Code 2, Reason 2009
INFO <STDOUT> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
INFO <STDOUT> MQJE001: Completion Code 2, Reason 2009
INFO <STDOUT> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
INFO <STDOUT> MQJE001: Completion Code 2, Reason 2009
INFO <STDOUT> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
INFO <STDOUT> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
INFO <STDOUT> MQJE001: Completion Code 2, Reason 2009
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.put(MQQueue.java:1518)
and ...
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
INFO <STDOUT> at com.ibm.mq.MQQueue.put(MQQueue.java:1518)
Thanks
Sri |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Oct 11, 2007 1:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Check out the ProbeId in the FDC file associated with the 2195. The 2009 errors are probably side effects of the original 2195.
Also post what level of software you're using on what platform, if the FDC doesn't reveal an obvious cause.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Oct 11, 2007 1:14 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
2009 0x000007d9 MQRC_CONNECTION_BROKEN
means your client to server channels are broken or down.
This could be due to server qmgr not available or populated with lot of client/server channels.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 11, 2007 1:22 am Post subject: Re: MQ Exception Completion Code 2, Reason 2195+2009 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| System9 wrote: |
,channel is getting closed .(MQ queue and MQ manager are not null)and it is throwing
|
| Gaya3 wrote: |
| means your client to server channels are broken or down |
I think that's already been determined. The question is why are they down, which I suspect is associated with the queue manager throwing a 2195. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Oct 11, 2007 1:26 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Yes Vitor...
some un-expected behaviour happened on the queue manager side.
as you said is correct.
I think he has to check if any orphan processes are there in the system which crossed the user limit too. as he is using client / server
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| System9 |
| Posted: Thu Oct 11, 2007 1:29 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Hi all,
Thanks for your replies.
I am using 6.0.2.1 com.ibm.mq.jar ,on linux box.I could see Qmanager,queue values.As you said channel could be broken.
I am wondering ..If it is because lots of connectons why it is not coming at the begining and once after I restart..
Can I have any settings that can keep channel alive ,till I explicitly close it..
Thanks
Srikanth |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 11, 2007 1:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| System9 wrote: |
I am wondering ..If it is because lots of connectons why it is not coming at the begining and once after I restart..
|
If you'd looked in the FDC file as I suggested you wouldn't have to wonder.
And if the channel had decided to close because a timeout value had expired, I wouldn't expect a 2195!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| System9 |
| Posted: Thu Oct 11, 2007 1:43 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Sorry to say that at the moment I do not have access to FDC files. I am trying to get the file.
In case If lots of connections opened ,is this exception expected..?
Thanks,
Srikanth |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 11, 2007 1:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| System9 wrote: |
In case If lots of connections opened ,is this exception expected..?
|
As I'm sure you've discovered from your research:
| Code: |
| 2195 0x00000893 MQRC_UNEXPECTED_ERROR |
So by definition it's unexpected.
It's possible a 2009 could result if the server was loaded, and short of resource for new connections. My reasoning here is that a queue manager error has occured and as a result the connections have broken.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| System9 |
| Posted: Thu Oct 11, 2007 4:33 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
I tried to check FDC dumps.But after this failure there are no FDC dumps been created.
Could someone can explain more on this please.
Thanks
Srikanth |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 11, 2007 4:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| System9 wrote: |
I tried to check FDC dumps.But after this failure there are no FDC dumps been created.
|
Each 2195 code is supposed to be accompanied with an FDC file; that's sort of the point. Sounds like you need to raise a PMR with IBM.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| System9 |
| Posted: Sat Oct 20, 2007 3:23 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Hi,
I was able to get the java mq trace for this exception.If I keep the application idle for than 2 hours , connection is getting rest and channel is getting closed.
Could you look into this and suggest me on this please.
[1192817282382] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 <== send() exit
[1192817282382] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> receive() entry
[1192817282382] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> receiveBytesFaster() entry
[1192817282382] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 Waiting for data on input stream.
[1192817282382] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> timedReadInt() entry
[1192817282383] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 <== timedReadInt() exit
[1192817282383] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 java.net.SocketException: Connection reset
[1192817282651] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data ==> MQException constructor(cc, rc, source, msgid)() entry
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data @(#) javabase/com/ibm/mq/MQException.java, java, j600, j600-201-061220 1.83.1.5 06/11/24 14:29:39
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data cc = 2
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data rc = 2195
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data source = null
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data msgId = 48
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data Explanation is 'MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data'
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data <== MQException constructor() exit
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data ==> MQInternalException constructor (cc, rc, msgId)() entry
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data @(#) javabase/com/ibm/mqservices/MQInternalException.java, java, j600, j600-201-061220 1.15.1.2 05/07/05 13:44:51
[1192817282652] Thread: Thread-16, Object: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE007: IO error reading message data <== MQInternalException constructor() exit
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 <== receive() exit
[1192817282653] Thread: Thread-16 Class: MQSESSIONClient Releasing lock on MQInternalCommunications object
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQSESSIONClient@1c6600 <== lowLevelComms() exit
[1192817282653] Thread: Thread-16 ==> MQSESSIONClient::analyseError() entry
[1192817282653] Thread: Thread-16 Class: MQSESSIONClient segment type = 134
[1192817282653] Thread: Thread-16 Class: MQSESSIONClient Err reason code = 0
[1192817282653] Thread: Thread-16 <== MQSESSIONClient::analyseError() exit
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> close() entry
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> sendStatus() entry
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 status = 8
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 errCode = 0
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> send() entry
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 TSH type = 5
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 Sending data, 0 bytes of msg data remain
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 Last segment of message
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 ==> writeTSH() entry
[1192817282653] Thread: Thread-16, Object: com.ibm.mq.MQv6InternalCommunications@1245e75 <== writeTSH() exit |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Oct 20, 2007 7:00 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| System9 wrote: |
Hi,
I was able to get the java mq trace for this exception.If I keep the application idle for than 2 hours , connection is getting rest and channel is getting closed. |
Hmmm. The first thing I though of when I read that is that the defaut TCP KeepAlive value on a server is usually 2 hours. If your are connecting to the QM as an MQ Client over a SVRCONN channel, and the server's KeepAlive is 2 hours, and the QM has been told to use KeepAlive (set by the MQ Admin in the qm.ini file) I can see how the QM would terminate your channel after 2 hours of no activity.
Why does your app stay connected for over 2 hours doing nothing? Wouldn't it make more sense to disconnect from MQ and reconnect when you have something to do?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| System9 |
| Posted: Sat Oct 20, 2007 7:47 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
This app has to run continuosly through out the day.it could be idle for couple of hours at times ,because of no users or for some other reasons.
so every time it has to be manually restarted to get the connection back.
Are we having any settings that keep the connection or channel alive for ever ,until and unless if there are any issues from qmanager..? |
|
| Back to top |
|
|
| System9 |
| Posted: Sat Oct 20, 2007 7:51 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Sorry to miss this.I am using Jboss application server.I saw other jboss apps using mq running fine with out this issue.
Thanks
Srikanth |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
