| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Socket Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| vickykarumbhu |
 Posted: Thu Jul 09, 2015 1:34 am Post subject: Socket Error |
 |
|
Newbie
Joined: 08 Jun 2015
Posts: 6
|
| I'm getting this exception while trying to hit an URL through HTTPRQ node.An error occurred whilst performing an SSL socket operation. Kindly help me on this |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jul 09, 2015 2:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What exception?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| vickykarumbhu |
| Posted: Thu Jul 09, 2015 2:39 am Post subject: i'm getting a error like this |
|
|
Newbie
Joined: 08 Jun 2015
Posts: 6
|
| Code: |
(0x01000000:Name ):RecoverableException = (
(0x03000000:NameValue):File = 'F:\build\slot1\S800_P\src\WebServices\WSLibrary\ImbWSRequest.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 256 (INTEGER)
(0x03000000:NameValue):Function = 'ImbWSRequest::makeWSRequest' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 3152 (INTEGER)
(0x03000000:NameValue):Text = 'A Web Service request has detected a SOCKET error whilst invoking a web service located at host &1, on port &2, on path &3.' (CHARACTER) |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 09, 2015 4:41 am Post subject: Re: Socket Error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vickykarumbhu wrote: |
| An error occurred whilst performing an SSL socket operation. |
First prove that you can reach that URL from the broker's machine, just to rule out any network craziness or port-in-use problems.
When you discover that you can (and I expect that you can), verify that the SSL set up on the broker side is correct (i.e. configured according to the InfoCenter) and it's correct for SSL communication to that URL (i.e. the correct signer certs in trust stores).
There should be rather more to than error message than the single line posted and that may be probative. If it's possible, and it may not be, get the target URL to use HTTP not HTTPS for testing purposes. If you can call it in clear, this will point the finger firmly at the SSL set up on one or both sides.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
