| Author |
Message
|
| harghgh |
 Posted: Mon May 11, 2015 5:52 am Post subject: AMQ9271 and AMQ9999 error in MQ logs. |
 |
|
Novice
Joined: 26 Jun 2012
Posts: 12
|
I am getting the below error in MQ logs for the server-conn channel C.CC1
AMQ9271: Channel 'C.CC1' timed out.
EXPLANATION:
A timeout occurred while waiting to receive from the other end of channel
'C.CC1'. The address of the remote end of the connection was
'192.168.2.11'.
ACTION:
The return code from the (recv) [TIMEOUT] 180 seconds call was 0 (X'0'). Record
these values and tell the systems administrator.
----- amqccaxa.c : 535 --------------------------------------------------------
2015-05-11 14:42:57 - Process(8724.7784) User(sysmqprd) Program(amqrmppa.exe)
Host(SEDNT2579) Installation(Installation1)
VRMF(8.0.0.1) QMgr(QM018T1)
AMQ9999: Channel 'C.CC1' to host '192.168.2.11' ended abnormally.
EXPLANATION:
The channel program running under process ID 8724(12416) for channel
'C.CC1' ended abnormally. The host name is '192.168.2.11'; in some
cases the host name cannot be determined and so is shown as '????'
The disconnect interval mentioned in the serv-conn channel but still channel is showing abnormal shutdown
Below is the details of the channel.
AMQ8414: Display Channel details.
CHANNEL(C.CC1) CHLTYPE(SVRCONN)
ALTDATE(2015-04-10) ALTTIME(20.12.02)
CERTLABL( ) COMPHDR(NONE)
COMPMSG(NONE) DESCR(SERVER CHANNEL)
DISCINT(600) HBINT(60)
KAINT(AUTO) MAXINST(200)
MAXINSTC(100) MAXMSGL(104857600)
MCAUSER( ) MONCHL(QMGR)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SHARECNV(40) SSLCAUTH(REQUIRED)
SSLCIPH( ) SSLPEER( )
TRPTYPE(TCP)
Its running on windows. and also the handle count of amqzlaa0 process increasing continously resulting in high memory utilization.
We have set the keep alive on QMGR and windows. but still no success. Please provide the help to resolve this errors and high memory utilization. |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon May 11, 2015 7:02 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Firewall...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| harghgh |
| Posted: Mon May 11, 2015 7:50 am Post subject: |
|
|
Novice
Joined: 26 Jun 2012
Posts: 12
|
| The windows firewall is off. To add more on the problem. There is SAP application which is connecting to this QMGR using this channel using MQ client v7.5.0.4. And MQ server is v 8.0.0.1. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon May 11, 2015 7:53 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What are the settings on the channel? SHARECONV etc.? And not forgetting that there are FixPacks subsequent to the one you have.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Last edited by exerk on Mon May 11, 2015 7:54 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 11, 2015 7:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| harghgh wrote: |
| The windows firewall is off. |
Has anyone told the windows firewall that?
| harghgh wrote: |
| To add more on the problem. There is SAP application which is connecting to this QMGR using this channel using MQ client v7.5.0.4. And MQ server is v 8.0.0.1. |
This sounds like a live system. Which means there are more firewalls and connection-terminating applicances at a network level than just the one built into windows. Assuming there's not a separate firewall product running on the windows server.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| harghgh |
| Posted: Mon May 11, 2015 8:02 am Post subject: |
|
|
Novice
Joined: 26 Jun 2012
Posts: 12
|
Here is the description of the channel.
AMQ8414: Display Channel details.
CHANNEL(C.CC1) CHLTYPE(SVRCONN)
ALTDATE(2015-04-10) ALTTIME(20.12.02)
CERTLABL( ) COMPHDR(NONE)
COMPMSG(NONE) DESCR(SERVER CHANNEL)
DISCINT(600) HBINT(60)
KAINT(AUTO) MAXINST(200)
MAXINSTC(100) MAXMSGL(104857600)
MCAUSER( ) MONCHL(QMGR)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SHARECNV(40) SSLCAUTH(REQUIRED)
SSLCIPH( ) SSLPEER( )
TRPTYPE(TCP)
sharecnv is set to 40. disconnect interval 600sec heartbeat is set 60 sec. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon May 11, 2015 8:11 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The first rule of MQ connectivity problems is blame the network team until they prove they haven't done something to block your channels.
That is, again, please doublecheck the network connectivity and firewalls. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 11, 2015 9:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
you also might want to reconsider the maxinst and maxinstc values if you switch sharecnv to 1 instead of 40...
See the notes about sharecnv and performance on MQ V8.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
