ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIBV9 Soap Request javax.net.ssl.SSLHandshakeException

Post new topic  Reply to topic
 IIBV9 Soap Request javax.net.ssl.SSLHandshakeException « View previous topic :: View next topic » 
Author Message
Vamsi Krishna
PostPosted: Thu May 04, 2017 10:58 pm    Post subject: IIBV9 Soap Request javax.net.ssl.SSLHandshakeException Reply with quote

Acolyte

Joined: 12 May 2014
Posts: 53

Hello All,
I have a requirement of consuming a external SOAP web service. We have developed a flow for consuming the service, recently there are some changes done on on the provider service.
It is expecting protocol TLSv1.2 as it is not listed in the SOAP request node on version 9.0.0.1 we have updated to latest fix pack 9.0.0.7.

After the update we have configured TLSv1.2 in the soap request node tried to call the service from my local machine. It worked.

Similar procedure has been taken care on the server side as well(Windows Server 2012 R2).

Server has a proxy so I have mentioned the proxy details on the SOAP request node but it is throwing an error as mentioned below.

I have configured SOAP UI in the server and tested it. able to receive the response from the tool.

Could please someone try to help in resolving this exception.

ExceptionList
RecoverableException
File:CHARACTER:F:\build\slot1\S900_P\src\DataFlowEngine\MessageServices\ImbDataFlowNode.cpp
Line:INTEGER:1140
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmSOAPRequestNode
Name:CHARACTER:CONSUMER#FCMComposite_1_3.gen/Ping_eAdapterStreamedService_CONSUMER#FCMComposite_1_1
Label:CHARACTER:CONSUMER.Ping_eAdapterStreamedService.Request
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
Insert
Type:INTEGER:14
Text:CHARACTER:CONSUMER.Ping_eAdapterStreamedService.Request
RecoverableException
File:CHARACTER:F:\build\slot1\S900_P\src\WebServices\WSLibrary\ImbSOAPRequestNode.cpp
Line:INTEGER:846
Function:CHARACTER:ImbSOAPRequestNode::requestData
Type:CHARACTER:ComIbmSOAPRequestNode
Name:CHARACTER:CONSUMER#FCMComposite_1_3.gen/Ping_eAdapterStreamedService_CONSUMER#FCMComposite_1_1
Label:CHARACTER:CONSUMER.Ping_eAdapterStreamedService.Request
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3754
Text:CHARACTER:Error occurred in ImbSOAPRequestHelper::makeSOAPRequest()
RecoverableException
File:CHARACTER:F:\build\slot1\S900_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp
Line:INTEGER:3676
Function:CHARACTER:ImbSOAPRequestHelper::logWebServiceInvocationException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3162
Text:CHARACTER:WebService Request Exception
Insert
Type:INTEGER:12
Text:CHARACTER:436f6e74656e742d4c656e6774683a203730320d0a436f6e74656e742d547970653a20746578742f786d6c3b20636861727365743d7574662d380d0a486f73743a2061677974726e73657276696365732e77697365677269642e6e65740d0a534f4150416374696f6e3a2022687474703a2f2f436172676f576973652e636f6d2f654875622f323031302f30362f654164617074657253747265616d6564536572766963652f50696e67220d0a50726f78792d436f6e6e656374696f6e3a204b6565702d416c6976650d0a0d0a
Insert
Type:INTEGER:12
Text:CHARACTER:3c3f786d6c2076657273696f6e3d22312e302220656e636f64696e673d227574662d38223f3e3c4e53313a456e76656c6f706520786d6c6e733a4e53313d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f223e3c4e53313a4865616465723e3c4e53323a536563757269747920786d6c6e733a4e53323d22687474703a2f2f646f63732e6f617369732d6f70656e2e6f72672f7773732f323030342f30312f6f617369732d3230303430312d7773732d777373656375726974792d7365636578742d312e302e7873642220777373653d22687474703a2f2f646f63732e6f617369732d6f70656e2e6f72672f7773732f323030342f30312f6f617369732d3230303430312d7773732d777373656375726974792d7365636578742d312e302e78736422207773753d22687474703a2f2f646f63732e6f617369732d6f70656e2e6f72672f7773732f323030342f30312f6f617369732d3230303430312d7773732d777373656375726974792d7574696c6974792d312e302e787364223e3c4e53323a557365726e616d65546f6b656e204e53323a49643d2242617369634874747042696e64696e675f654164617074657253747265616d6564536572766963655f706f6c696379223e3c4e53323a557365726e616d653e45494c757365723c2f4e53323a557365726e616d653e3c4e53323a50617373776f72643e45314c5534543c2f4e53323a50617373776f72643e3c2f4e53323a557365726e616d65546f6b656e3e3c2f4e53323a53656375726974793e3c2f4e53313a4865616465723e3c4e53313a426f64793e3c4e53333a50696e6720786d6c6e733a4e53333d22687474703a2f2f436172676f576973652e636f6d2f654875622f323031302f3036223e3c2f4e53333a50696e673e3c2f4e53313a426f64793e3c2f4e53313a456e76656c6f70653e
Insert
Type:INTEGER:5
Text:CHARACTER:
Insert
Type:INTEGER:5
Text:CHARACTER:
Insert
Type:INTEGER:5
Text:CHARACTER:
RecoverableException
File:CHARACTER:F:\build\slot1\S900_P\src\WebServices\WSLibrary\ImbWSRequest.cpp
Line:INTEGER:470
Function:CHARACTER:ImbWSRequest::makeWSRequest
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3152
Text:CHARACTER:A Web Service request has detected a SOCKET error whilst invoking a web service via a proxy server located at host &1, on port &2, on path &3.
Insert
Type:INTEGER:5
Text:CHARACTER:localhost
Insert
Type:INTEGER:2
Text:CHARACTER:8080
Insert
Type:INTEGER:5
Text:CHARACTER:/
SocketException
File:CHARACTER:F:\build\slot1\S900_P\src\WebServices\WSLibrary\ImbSocket.cpp
Line:INTEGER:1314
Function:CHARACTER:ImbSocketJNIManager::handleGeneralJavaException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3165
Text:CHARACTER:An error occurred whilst performing an SSL socket operation
Insert
Type:INTEGER:5
Text:CHARACTER:initiateSslHandshake
Insert
Type:INTEGER:5
Text:CHARACTER:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
Back to top
View user's profile Send private message
martinb
PostPosted: Fri May 05, 2017 2:48 am    Post subject: Reply with quote

Master

Joined: 09 Nov 2006
Posts: 210
Location: UK

To help understand this one, could you first clarify, when you tested with SOAPui, where you on the some host as IIB and routing though the proxy at localhost:8080 ?

Also please can you double check that you have deployed the change to SOAPRequest node to set TLSv1.2.


Last edited by martinb on Fri May 05, 2017 3:32 am; edited 1 time in total
Back to top
View user's profile Send private message
Vamsi Krishna
PostPosted: Fri May 05, 2017 3:14 am    Post subject: Reply with quote

Acolyte

Joined: 12 May 2014
Posts: 53

martinb wrote:
To help understand this one, could you first clarify, when you tested with SOAPui, where you on the some host as IIB and routing though the proxy at localhost:8080 ?


Hi Martin,
The localhost is not the real proxy address I just mentioned localhost as an example but yes both the proxy servers tested are of same name.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIBV9 Soap Request javax.net.ssl.SSLHandshakeException
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.