| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| When is an error not an error ? AMQ9641: Remote CipherSpec |
« View previous topic :: View next topic » |
| Author |
Message
|
| bobgosling |
 Posted: Fri Jan 20, 2012 1:24 am Post subject: When is an error not an error ? AMQ9641: Remote CipherSpec |
 |
|
Novice
Joined: 16 Jan 2004
Posts: 12
Location: London , UK
|
I am seeing an error in the client side errors logs ( /var/mqm/errors/AMQERR*.LOG )
Whenever my C++ interfaces connect to a queue on starting up in the morning I get an error as follows :
-----------------------------------------------------------------------------------
01/20/2012 12:08:11 AM - Process(13188.1) User({redacted}) Program({redacted})
AMQ9641: Remote CipherSpec error for channel '{redacted}'.
EXPLANATION:
The remote end of channel '{redacted}' has had a CipherSpec error. The channel
did not start.
ACTION:
Review the error logs on the remote system to discover the problem with the
CipherSpec.
------------------------------------------------------------------------------------
However, the interfaces logs no error and carries on and appears to have connected OK. It can read or write to the queue with no problems and no further errors get logged.
Why bother fixing this you may ask ! Well, I just abhor problems that I don't understand. This is happening in all dev , UAT and production areas and it makes me nervous. I would like to clear it up.
The MQ administrator assures me that the channel CipherSpec is set to TRIPLE_DES_SHA_US , and that's the value set in the C++ interfaces ( MQCD structure field SSLCipherSpec )
All other SSL configs appear to be OK. $MQSSLKEYR, $MQCHLLIB & $MQCHLTAB are all correct. key.kdb file has been checked and contains the correct certifcates. As I said, the interface does connect OK so there is clearly something not quite right somewhere.
Any ideas gratefully acknowledged. I am now banging my head against the desk over this one. |
|
| Back to top |
|
 |
| bobgosling |
| Posted: Fri Jan 20, 2012 1:29 am Post subject: missed a bit |
|
|
Novice
Joined: 16 Jan 2004
Posts: 12
Location: London , UK
|
Sorry, missed a bit of information.
Obtained a new client connection table from MQ admin in case there was a problem there but it did not fix the problem.
Also have noticed that the code had missed setting MQSCO.Version = MQSCO_CURRENT_VERSION but that also did not fix it.
dspmqver gives :
Name: WebSphere MQ
Version: 6.0.2.6
CMVC level: p600-206-090217
BuildType: IKAP - (Production) |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Jan 20, 2012 2:33 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What concurrent errors (if any) are appearing in the queue manager log? Also, if you are using the variables I would not expect you to use the MQSCO structure too - is it not a case of one or the other, or are there additional fields being passed via the structure within the MQCONNX call?
_________________
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
|
|
|
|
