From the same machine we can do a succesfull call to this webservice with SOAP UI. In the call a security token is provided. The only other security is the certificate, which is in place on the bods server and which is referenced to in the axis2.xml
We also ran the job from the command line and this is where it stops/hangs:
[Tue Oct 27 17:30:51 2015] [debug] …\src\core\engine\phase.c(210) Invoke the handler AddressingOutHandler within the phase MessageOut
[Tue Oct 27 17:30:51 2015] [info] Starting addressing out handler
[Tue Oct 27 17:30:51 2015] [debug] …\src\modules\mod_addr\addr_out_handler.c(133) No action present. Stop processing addressing
[Tue Oct 27 17:30:51 2015] [debug] …\src\core\transport\http\sender\http_transport_sender.c(246) ctx_epr:https://service2.loyaltyinabox.com/facade/NSX/ManagementAndControl/1.2/Service.svc
[Tue Oct 27 17:30:51 2015] [debug] …\src\core\transport\http\sender\http_transport_sender.c(805) using axis2 native http sender.
[Tue Oct 27 17:30:51 2015] [debug] …\src\core\transport\http\sender\http_sender.c(416) msg_ctx_id:urn:uuid:4f368906-fe60-4cfc-b76a-9e56c6a7f8b6
The other wsdl (acceptance) does not stop there:
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\engine\phase.c(210) Invoke the handler AddressingOutHandler within the phase MessageOut
[Tue Oct 27 14:01:14 2015] [info] Starting addressing out handler
[Tue Oct 27 14:01:14 2015] [debug] …\src\modules\mod_addr\addr_out_handler.c(133) No action present. Stop processing addressing
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\transport\http\sender\http_transport_sender.c(246) ctx_epr:http://acc2.luntronics.com/facade/NSX/ManagementAndControl/1.2/Service.svc
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\transport\http\sender\http_transport_sender.c(805) using axis2 native http sender.
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\transport\http\sender\http_sender.c(416) msg_ctx_id:urn:uuid:f38b4219-e28b-4f7d-a699-de3330c256db
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\transport\http\sender\http_transport_sender.c(822) OP name axutil_qname_get_localpart = http://www.w3.org/2004/08/wsdl/out-in
[Tue Oct 27 14:01:14 2015] [debug] …\axiom\src\soap\soap_builder.c(930) Identified soap version is soap11
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\engine\phase.c(210) Invoke the handler request_uri_based_dispatcher within the phase Transport
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\engine\phase.c(210) Invoke the handler AddressingInHandler within the phase Transport
[Tue Oct 27 14:01:14 2015] [info] Starting addressing in handler
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\engine\phase.c(210) Invoke the handler addressing_based_dispatcher within the phase Transport
[Tue Oct 27 14:01:14 2015] [debug] …\src\core\engine\phase.c(210) Invoke the handler LoggingInHandler within the phase PreDispatch
[Tue Oct 27 14:01:14 2015] [info] Starting logging in handler …
In fiddler we see that a tunnel is created but that’s all. The client (BODS) does not call the webservice.
14.2.3.549 is not affected, could be something else, if the problem is because of openSSL lib then the job will crash and if you run the same job from command line with -D -np you will see a error related to openSSL linking on the output
I think the affected versions are
14.2.3.570, 14.2.3.618
Thanks for the reply Manoj. Attached is my axis2_log.txt file from running from command file with -np -D. As you will see my job crashes at exactly the same point as Robert’s, and I don’t have the text ‘OpenSSL’ anywhere in the log. axis2_log.txt (8.0 KB)
Thanks for your reply. I don’t get any OPENSSL message when running from the command line, only the below warning:
Warning: ORB::BOA_init: hostname lookup returned `localhost’ (127.0.0.1/::1)
Use the -OAhost option to select some other hostname
I am running the job on the command line via a command file exported from the Admin Console, and it uses AL_RWJobLauncher, not al_engine, not sure if that would make a difference ? At the bottom of my reply is the output from the AL_RWJobLauncherLog.txt.
I had a look at that note and would like to advise you of the following:
The error is occurring with version 4.2 SP03, whereas the note specifies the problem is with 4.2 SP03 PL2.
The note instructs applying SP03 PL3 to resolve, does that imply all later versions should also resolve, because I have upgraded a separate test platform to 4.2 SP05 PL2 and I still get exactly the same error ?
(14.2.3.549) 11_10_2015 16:18:22 (6872): CRWJobLauncherApp::InitInstance called.
(14.2.3.549) 11_10_2015 16:18:23 (6872): Connected to CMS Server : zrhsrid01.sap.rcf.co.za:6400 of CMS Cluste : @zrhsrid01.sap.rcf.co.za:6400
(14.2.3.549) 11_10_2015 16:18:23 (6872): Connected to CMS Server : zrhsrid01.sap.rcf.co.za:6400 of CMS Cluste : @zrhsrid01.sap.rcf.co.za:6400
(14.2.3.549) 11_10_2015 16:18:24 (6872): Launching Job and waiting for completion. inet address inet:ZRHSRID01:3500, GUID <403c417f_e49e_4c0d_968f_37100c0ec750>. (BODI-1250132)
(14.2.3.549) 11_10_2015 16:18:24 (6872): XML_REQUEST:
(14.2.3.549) 11_10_2015 16:18:24 (6872): <?xml version="1.0" encoding="UTF-8"?>
Hi Manoj, I am also facing the same issue, Web Service with SSL hangs.
On job termination, the last line in axis2_log.txt is the following:
[Tue Feb 23 14:13:59 2016] [debug] …\src\core\transport\http\sender\http_sender.c(416) msg_ctx_id:urn:uuid:8b62535d-e406-4e4d-90f3-9d285c4d3f4e
We are using DS 4.2 SP6. (14.2.6.994).
The test WSDL is https://webservice.aspsms.com/aspsmsx2.asmx?WSDL. I have exported the .crt file from firefox (as explained in one of your earlier posts) and altered the axis.xml to enable https and the server_path.
I have also raised an incident with SAP (98035 / 2016) couple of weeks ago.
(BOB member since 2011-01-06)