Dear PI Experts,

I have a synchronous scenario "Proxy to Webservice" in my PI 7.11.

I need wssec security with UsernameToken in this webservice.So I am using the SOAP AXIS Receiver adapter.

I put axis.jar, commons-discovery-0.2.jar, commons-logging-1.0.4.jar, commons-net-1.0.0-dev.jar, wsdl4j-1.5.1.jar, wss4j-1.5.6.jar, xmlsec-1.4.2.jar to a SDA Package com.sap.aii.af.axisproviderlib.sda and deployed it to system. The adapter looks quite nice now. wssec options are now green and ok.  (as mentioned in :   http://help.sap.com/saphelp_nw04/helpdata/de/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm )

Axis Adapter Message Servlet

Component Versions

Adapter Common Library Version: 1.7.1103.20090821155556.0000, NW711_03_REL (2009-08-22T10:17:14+0000)
Adapter Application Version: 1.7.1103.20090821155556.0000, NW711_03_REL (2009-08-22T10:17:50+0000)
Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)

Required Components

• Apache-Axis
  Found: org.apache.axis.AxisEngine at /usr/sap/PIE/DVEBMGS50/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/axis.jar
• Jakarta-Commons Discovery
  Found: org.apache.commons.discovery.Resource at /usr/sap/PIE/DVEBMGS50/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar
• Jakarta-Commons Logging
  Found: org.apache.commons.logging.Log at /usr/sap/PIE/DVEBMGS50/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.0.4.jar

Number of Missing Components: 0
Status: OK

I configured a SOAP AXIS Receiver Adapter SAP BAsis 7.11

Now when I start the scenario I get a timeout error after 3 minutes (during "getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender").

2013-12-18 21:12:00 Information    The message was successfully received by the messaging system. Protocol: XI URL: http://akhsap41:55000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2013-12-18 21:12:00 Information    Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.

2013-12-18 21:12:00 Information    Message successfully put into the queue.

2013-12-18 21:12:00 Information    The message was successfully retrieved from the request queue.

2013-12-18 21:12:00 Information    The message status was set to DLNG.

2013-12-18 21:12:00 Information    Delivering to channel: SOAP_AXIS_Receiver_test

2013-12-18 21:12:00 Information    Axis: entering AFAdapterBean

2013-12-18 21:12:00 Information    Axis: xioutbound-request mutation

2013-12-18 21:12:00 Information    Axis: mutated successfully

2013-12-18 21:12:00 Information    Axis: leaving AFAdapterBean

2013-12-18 21:12:00 Information    Axis: entering HandlerBean

2013-12-18 21:12:00 Information    Axis: getting handler xireq of java:com.sap.aii.axis.xi.XI30OutboundHandler

2013-12-18 21:12:00 Information    Axis: invoked successfully

2013-12-18 21:12:00 Information    Axis: leaving HandlerBean xireq of java:com.sap.aii.axis.xi.XI30OutboundHandler

2013-12-18 21:12:00 Information    Axis: entering HandlerBean

2013-12-18 21:12:00 Information    Axis: getting handler wssec of java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender

2013-12-18 21:12:00 Information    Axis: invoked successfully

2013-12-18 21:12:00 Information    Axis: leaving HandlerBean wssec of java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender

2013-12-18 21:12:00 Information    Axis: entering HandlerBean

2013-12-18 21:12:00 Information    Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender

2013-12-18 21:15:00 Fehler Synchronous timeout exceeded.

2013-12-18 21:15:00 Fehler The message status was set to FAIL.

2013-12-18 21:15:45 Fehler Axis: error in invocation: java.net.ConnectException: Connection timed out

2013-12-18 21:15:45 Fehler Adapter Framework caught exception: ; nested exception is: java.net.ConnectException: Connection timed out

2013-12-18 21:15:45 Fehler Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out. Setting message to status failed.

During Send I see my correct payload in rwb:

<uploadDocument><Document encoding="UTF-8">U3RyaW5nIDE=</Document><Settings test="true"/></uploadDocument>

After timeout:

<?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance/" xmlns:xsd="http://www.w3.org/2001/XMLSchema/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header><wsse:Security><wsse:UsernameToken><wsse:Username>s000a000c905</wsse:Username><wsse:Password>dcbr6th7</wsse:Password></wsse:UsernameToken></wsse:Security></env:Header><env:Body><uploadDocument xmlns="http://erb.eproc.brz.gv.at/ws/documentupload/20121205/"><Document encoding="UTF-8">PD94bWwgdmauthorization:Basic UElJU1VTRVI6a2FtcDA0eGUx

accept-encoding:gzip

sap-xi-messageid:52B08FBC574A31C0E10000000A7EAA15

content-length:3434

host:XXXXXsap41:iiiiiiii

user-agent:SAP NetWeaver Application Server (1.0;711)

content-type:multipart/related;boundary=SAP_80144F2318581ED39A8414E91B57108B_END;type="text/xml";start="<soap-80144F2318581ED39A8414E91AA6D363@sap.com>"

soapaction:"http://sap.com/xi/XI/Message/30"

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'><sap:MessageClass>ApplicationMessage</sap:MessageClass><sap:ProcessingMode>synchronous</sap:ProcessingMode><sap:MessageId>52b08fbc-574a-31c0-e100-00000a7eaa15</sap:MessageId><sap:TimeSent>2013-12-18T20:12:00Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party><sap:Service>SAPCORE_ISH_EA2_200</sap:Service></sap:Sender><sap:Receiver><sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_yyyyyy_TEST</sap:Service></sap:Receiver><sap:Interface namespace='http://XXXXXwien.at.sd.yyyyyyrechnung'>SI_In_Rechnung_Upload</sap:Interface></sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging><sap:System xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Record namespace='http://www.sap.com/webas/712/soap/features/runtime/metering/' name='CallingType'>SA</sap:Record></sap:System><sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Hop timeStamp='2013-12-18T20:12:00Z' wasRead='false'><sap:Engine type='BS'>SAPCORE_ISH_EA2_200</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>52b08fbc-574a-31c0-e100-00000a7eaa15</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2013-12-18T20:12:00Z' wasRead='false'><sap:Engine type='IS'>is.50.XXXXXsap41</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>52b08fbc-574a-31c0-e100-00000a7eaa15</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2013-12-18T20:12:00Z' wasRead='false'><sap:Engine type='AE'>af.pie.XXXXXsap41</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>52b08fbc-574a-31c0-e100-00000a7eaa15</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body><sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'><sap:Payload xlink:type='simple' xlink:href='cid:payload-52B08FBD574A31C0E10000000A7EAA15@sap.com'><sap:Name>MainDocument</sap:Name><sap:Description></sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest></SOAP:Body></SOAP:Envelope>

I have a similar scenario in a XI 7.0 with SOAP AXIS Receiver (with the additional jar-Files) and it is working well there!

Can anybody tell me why this happens?

Thanks All

Armin