| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Repeated AMQ9209 and AMQ9999 errors in AMERR01 |
« View previous topic :: View next topic » |
| Author |
Message
|
| nrameshmq |
 Posted: Tue Dec 19, 2017 10:44 pm Post subject: Repeated AMQ9209 and AMQ9999 errors in AMERR01 |
 |
|
Apprentice
Joined: 09 Aug 2017
Posts: 35
Location: India, Mumbai
|
Hi,
We are Configured DQM setup from AIX(MQ 8.0.0.6) TO Windows(MQ 7.5.0.2) Server. We are facing frequent channel retrying issues, But from Windows to AIX it is working fine. I am confusing that issue is with MQ Related or Network related or OS related.
These error logs we observed.
12/20/17 10:03:48 - Process(28246212.1) User(mqm) Program(runmqchl)
Host(PRACEM) Installation(Installation1)
VRMF(8.0.0.7) QMgr(QM_PROD)
AMQ9209: Connection to host '10.59.158.179(1415)' for channel 'AIX.TO.USD'
closed.
EXPLANATION:
An error occurred receiving data from '10.59.158.179(1415)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
The channel name is 'AIX.TO.USD'; in some cases it cannot be determined and
so is shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 4157 -------------------------------------------------------
12/20/17 10:03:48 - Process(28246212.1) User(mqm) Program(runmqchl)
Host(PRACEM) Installation(Installation1)
VRMF(8.0.0.7) QMgr(QM_PROD)
AMQ9999: Channel 'AIX.TO.USD' to host '10.59.158.179(1415)' ended
abnormally.
EXPLANATION:
The channel program running under process ID 28246212 for channel
'AIX.TO.SBIUSDC' ended abnormally. The host name is '10.59.158.179(1415)'; in
some cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrccca.c : 1090 -------------------------------------------------------
and sender channel defination is like this.
| Code: |
dis chl(AIX.TO.USD)
4 : dis chl(AIX.TO.USD)
AMQ8414: Display Channel details.
CHANNEL(AIX.TO.SBIUSDC) CHLTYPE(SDR)
ALTDATE(2017-10-22) ALTTIME(15.56.12)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CERTLABL( ) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(10.59.158.179(1415))
CONVERT(NO) DESCR( )
DISCINT(0) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(PROCESS) MCAUSER( )
MODENAME( ) MONCHL(QMGR)
MSGDATA( ) MSGEXIT( )
NPMSPEED(NORMAL) PASSWORD( )
PROPCTL(COMPAT) RCVDATA( )
RCVEXIT( ) RESETSEQ(1)
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USEDLQ(YES) USERID( )
XMITQ(XMITQ2)
|
i go through the some of articles with same errors, But those are related to Client and server setup.
Please suggest how to resolve.
_________________
Ramesh
------------- |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Dec 20, 2017 12:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Firstly, this caught my eye:
| Quote: |
dis chl(AIX.TO.USD)
4 : dis chl(AIX.TO.USD)
AMQ8414: Display Channel details.
CHANNEL(AIX.TO.SBIUSDC) CHLTYPE(SDR) |
Note the difference, so what is the actual channel name, or have you obfuscated some details?
Secondly, setting a DISCINT of zero is a sure way of having problems diagnosing channel issues - is there a particular reason why the channel needs to run continuously?
Thirdly, is there a pattern in this, e.g. the channel runs for the same length of time before the communication break and retry? If so, is there a firewall between the two servers, and have you engaged your networks people to check their settings?
_________________
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 |
|
|
| nrameshmq |
| Posted: Wed Dec 20, 2017 1:00 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2017
Posts: 35
Location: India, Mumbai
|
Thanks exerk,
Yes i obfuscated some details.
As per client requirement, We didn't implemented Channel triggering that's why i didn't mentioned DISCINT.
Channel is running for some time and going into retrying state, After some it is getting running. From our end ping is disabled, Is there any other option to check network is working fine.
_________________
Ramesh
------------- |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Dec 20, 2017 1:10 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| nrameshmq wrote: |
| ...As per client requirement, We didn't implemented Channel triggering that's why i didn't mentioned DISCINT... |
What is the client's justification for wanting 24/7 channel running time?
| nrameshmq wrote: |
| ...Channel is running for some time and going into retrying state, After some it is getting running.... |
You already stated that, so again, what is the pattern (if any) ?
| nrameshmq wrote: |
| ...From our end ping is disabled... |
By that I presume you mean non-MQ ping? And that wont necessarily show an issue anyway as the TTL will be magnitudes of order below a 24/7 channel run time.
| nrameshmq wrote: |
| ...Is there any other option to check network is working fine. |
Yes, it's a utility called EYNP - Engage Your Networks People!
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
