| Author |
Message
|
| vikrant_a |
 Posted: Tue Oct 21, 2014 10:51 pm Post subject: Error Message :AMQ9665 |
 |
|
Newbie
Joined: 21 Oct 2014
Posts: 2
|
I have a qmanager running on linux with version 7.0.1.1 , having hundreds of SSL customers connecting to it , recently i'm seeing repeated below message in my AMQERR01.LOG . Now i'm not able to determine which channel is having this problem , many customers connected without any issue and no complaint so far , so not sure ,which channel is having this problem. Is there any way to find out ?
AMQ9665: SSL connection closed by remote end of channel '????'.
EXPLANATION:
The SSL connection was closed by the remote end of the channel during the SSL < handshake. The channel is '????'; in some cases its name cannot be determined < and so is shown as '????'. The channel did not start.
ACTION:
Check the remote end of the channel for SSL-related errors. Fix them and < restart the channel. |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Wed Oct 22, 2014 4:49 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| I would start by making sure your Qmgr had the latest fix which is 7.0.1.12. Then ensure the clients are also up to date. Note, your version of MQ hits EOS 30-Sep-2015. |
|
| Back to top |
|
|
| vikrant_a |
| Posted: Mon Oct 27, 2014 1:57 am Post subject: |
|
|
Newbie
Joined: 21 Oct 2014
Posts: 2
|
Thanks , as mentioned earlier i don't have any client complaining , it just that MQ keeps throwing this message in the logs.
Is there any way to find out the actual channel who is having this issue ? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Oct 27, 2014 4:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The most likely cause is someone trying to connect to a channel that requires SSL but they are not using SSL. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Oct 27, 2014 5:03 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Turn on SSL Events on the Queue Manager level. Perhaps the cause of the error is something that will cause the QM to produce an event messages, which may have more information.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Oct 27, 2014 6:39 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Contact the folks at the client-end. Ask them to look in the error logs at their end.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| tczielke |
| Posted: Mon Oct 27, 2014 12:17 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
You probably can catch it with a trace. Of course, use prudence on how long you keep the trace on. The -l option does put a limit on your trace file size.
If your channels run on the amqrmppa process, you could do something like the following:
strmqtrc -m qmgr -t all -p amqrmppa
after diagnostic collecting data:
endmqtrc -a
dspmqtrc * (to format trace data)
I am pretty sure the AMQ error message tells you the amrmppa pid and thread number that issued the AMQ error. You can then look at the trace for that pid.tid, and I think it does give you the ip address of the client end. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Oct 28, 2014 4:21 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| vikrant_a wrote: |
| Thanks , as mentioned earlier i don't have any client complaining... |
Is not a good reason to avoid keeping your infrastructure up to date. You are at least two years out of date on maintenance. |
|
| Back to top |
|
|
|
|
