Author |
Message
|
dotaneli |
Posted: Mon Oct 27, 2014 6:08 am Post subject: AMQ9620 with return code '5' |
|
|
Voyager
Joined: 19 Oct 2005 Posts: 99 Location: Israel
|
Hi all
MQ client 7.5 is communicating with a qmgr v. 7.5.
The client receives the following error in his end.
Any ideas?:
12/10/2014 08:04:04 - Process(8048.6) User(UserName) Program(SomeProcess.exe)
Host(XXXXXXXXXXX) Installation(Installation1)
VRMF(7.5.0.0)
AMQ9620: Internal error on call to SSL function on channel 'xxxxx' to host
'xxxxxxx (xxxxxxxx)(xxxx)פ
[1]'.
EXPLANATION:
An error indicating a software problem was returned from a function which is used to provide SSL or TLS support. The error code returned was '5'. The function call was 'gsk_secure_soc_write'.
Thank you |
|
Back to top |
|
 |
Vitor |
Posted: Mon Oct 27, 2014 6:17 am Post subject: Re: AMQ9620 with return code '5' |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
dotaneli wrote: |
Any ideas? |
- Bad client install (e.g. just using one of the jar files rather than the installed client)
- Bad or missing keystore on the client end
- client is using a connection method that doesn't support SSL (e.g. MQSERVER)
Other causes are undoubtably possible and may be more probable. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
hughson |
Posted: Mon Oct 27, 2014 7:30 am Post subject: Re: AMQ9620 with return code '5' |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
dotaneli wrote: |
AMQ9620: Internal error on call to SSL function on channel 'xxxxx' to host
'xxxxxxx (xxxxxxxx)(xxxx)פ
[1]'.
EXPLANATION:
An error indicating a software problem was returned from a function which is used to provide SSL or TLS support. The error code returned was '5'. The function call was 'gsk_secure_soc_write'. |
GSKit return code 5 is GSK_INVALID_STATE, which means "The handle is in an invalid state for operation, such as performing an init operation on a handle twice."
Were there any errors at the queue manager end at the same time?
I'm not sure how you could cause such an error with any kind of misconfiguration. Suggest you raise a PMR to get it looked at.
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
dotaneli |
Posted: Mon Oct 27, 2014 7:41 am Post subject: |
|
|
Voyager
Joined: 19 Oct 2005 Posts: 99 Location: Israel
|
Vitor and Morag - thanks for your quick replies.
I'll try the PMR way although it always takes a really long time and effort.
I think that it's one of those dark corners of MQ where a fresh installation might solve the situation. |
|
Back to top |
|
 |
JosephGramig |
Posted: Mon Oct 27, 2014 9:16 am Post subject: Re: AMQ9620 with return code '5' |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
dotaneli wrote: |
...VRMF(7.5.0.0) |
I'm sure the L2 PMR folks will point out you need to apply maintenance which is currently 7.5.0.4. Also do this for the client. |
|
Back to top |
|
 |
dotaneli |
Posted: Tue Oct 28, 2014 1:29 am Post subject: |
|
|
Voyager
Joined: 19 Oct 2005 Posts: 99 Location: Israel
|
Hi again,
I tried to recreate the problem between my pc and the destination qmgr.
I'm currently getting AMQ9641, although CipherSpec is in place and identical between the sender (in the channel table) and the receiver.
Anyone familiar with AMQ9641? |
|
Back to top |
|
 |
dotaneli |
Posted: Tue Oct 28, 2014 1:34 am Post subject: |
|
|
Voyager
Joined: 19 Oct 2005 Posts: 99 Location: Israel
|
Appologies: Obviously I meant client->server channel, not sender->receiver |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Oct 28, 2014 4:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Code: |
536909377 0x20009641 rrcE_SSL_REMOTE_BAD_CIPHER
MESSAGE:
Remote CipherSpec error for channel '<insert one>' to host '<insert two>'.
EXPLANATION:
The remote end of channel '<insert one>' on host '<insert two>' 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. |
So what do the remote logs say?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
dotaneli |
Posted: Tue Oct 28, 2014 10:53 pm Post subject: |
|
|
Voyager
Joined: 19 Oct 2005 Posts: 99 Location: Israel
|
Hi
Says about the same.
CipherSpec not specified. Although it is indeed specified. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Oct 29, 2014 7:02 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
dotaneli wrote: |
Hi
Says about the same.
CipherSpec not specified. Although it is indeed specified. |
At both ends of the channel? Can you prove that? Do they match?
My experience has been that when it says CipherSpec not specified, indeed a cipherspec is missing at one end of the channel...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
dotaneli |
Posted: Sat Nov 01, 2014 10:12 am Post subject: |
|
|
Voyager
Joined: 19 Oct 2005 Posts: 99 Location: Israel
|
Thanks all.
I don't know why CipherSpec issue was raised by MQ.
I regenerated the kdb and sth files.
All is well now.
Apologies for not being able to spot the issue and enrich the rest of you.
Thanks again. |
|
Back to top |
|
 |
JosephGramig |
Posted: Mon Nov 03, 2014 7:56 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
If all you did was regenerate the key store, then most likely the label was incorrect (misspelling) that goes with the certificate. |
|
Back to top |
|
 |
|