| Author |
Message
|
| pietrom |
 Posted: Wed Jul 29, 2015 6:06 am Post subject: MQ queue Get inhibit/allow - JMS comm channel error |
 |
|
Newbie
Joined: 29 Jul 2015
Posts: 4
Location: Rome, Italy
|
Dear all,
We have the following environmet:
- WebSphere Application Server 7.0 on Linux SO
- WebSphere MQ 7.0 on Linux SO
Initially the JMS channel (WebSphere Application Server) was reading messages from the queue. To do some checks, GET was set to ‘inhibited’ on the MQ queue from MQ Explorer.(Please note that the comm channel was not stopped ). Then GET is set back to ‘ALLOW’ but the comm channel doesn’t read any data.
The error description from channel monitoring is
A channel error occurred. The detailed error (if any) : JMS error:MQJMS2002: failed to get message from MQ queue, Linked error:MQJE001: Completion Code 2, Reason 2016, Error Code:MQJMS2002
So we tried stopping and starting the comm channel in Channel monitoring but the channel is still in the same error.
We have seen this before, Websphere Application Server restarting solve this issue, but are trying to understand why this happens and why is there need restart Application Server?
Any help would be highly appreciated.
Thanks a lot.
Pietro |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jul 29, 2015 6:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Might be easier next time to stop and restart the relevant MDB.
That is really what it boils down to. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Jul 29, 2015 7:05 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| fjb_saper wrote: |
Might be easier next time to stop and restart the relevant MDB.
That is really what it boils down to. |
correct
@pietrom
did you try to stop and start the listeners before the server restart.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| pietrom |
| Posted: Wed Jul 29, 2015 7:54 am Post subject: |
|
|
Newbie
Joined: 29 Jul 2015
Posts: 4
Location: Rome, Italy
|
Hello thanks for Your support.
@Gaya3
Do You mean restarting the Message Engine?
Thanks a lot. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 29, 2015 8:12 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| pietrom wrote: |
Hello thanks for Your support.
@Gaya3
Do You mean restarting the Message Engine?
Thanks a lot. |
No, we're not talking about the SIBus Message Engine. We are talking about the MDB support.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Jul 29, 2015 10:17 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| fjb_saper wrote: |
| pietrom wrote: |
Hello thanks for Your support.
@Gaya3
Do You mean restarting the Message Engine?
Thanks a lot. |
No, we're not talking about the SIBus Message Engine. We are talking about the MDB support. |
I am talking about the MDB Listeners stop and start in the WAS JVM
Application Servers --> <<AppSrvr>> --> Message listener service --> Listener Ports
if you are using SIB then the troubleshooting goes in a different way, I presume your Application in WAS is directly connecting to MQ using WebSphere MQ Provider (not through Default Messaging Provider)
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| pietrom |
| Posted: Wed Jul 29, 2015 10:28 am Post subject: |
|
|
Newbie
Joined: 29 Jul 2015
Posts: 4
Location: Rome, Italy
|
In our environment MDB is deployed inside a main websphere application, so restarting this application would cause a major disruption of service.
At this point is it is better to restart the application server
Thanks a lot for support.
Pietro  |
|
| Back to top |
|
|
| pietrom |
| Posted: Wed Jul 29, 2015 10:34 am Post subject: |
|
|
Newbie
Joined: 29 Jul 2015
Posts: 4
Location: Rome, Italy
|
| It's right, our Application in WAS is directly connecting to MQ using WebSphere MQ Provider (not through Default Messaging Provider). |
|
| Back to top |
|
|
|
|
