WS Adapter: INTERNAL.WS_LOGICAL_PORT

Question

Hi,
I have an scenario ABAP PROXY->WS, but once the message is triggered in the proxy, i get this error as a responce payload:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">    <SOAP:Body>       <SOAP:Fault>          <faultcode>SOAP:Server</faultcode>          <faultstring>System Error</faultstring>          <detail>             <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">                <context/>                <code>INTERNAL.WS_LOGICAL_PORT</code>                <text>Error while determining logical port</text>             </s:SystemError>          </detail>       </SOAP:Fault>    </SOAP:Body> </SOAP:Envelope>|Re: SOAP->Proxy scenario, issue with WS adapter
The pipeline looks like this:
<Trace level="1" type="Timestamp">2009-06-01T16:07:45Z CHILE Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
  <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
  <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
  <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
  <Trace level="3" type="T">ADRESSMOD = SD</Trace>
  <Trace level="3" type="T">P_CLASS =</Trace>
  <Trace level="3" type="T">P_IFNAME =</Trace>
  <Trace level="3" type="T">P_METHOD =</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Unknown channel type: WS</Trace>
  <Trace level="3" type="T">PLSRVTYPE = WS</Trace>
  <Trace level="3" type="T">ADRESSMOD = SD</Trace>
  <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_WS_ADAPTER</Trace>
  <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
  <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
  <Trace level="3" type="T" />
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
<!--  ************************************
  -->
  <Trace level="3" type="System_Error">Error while determining logical port</Trace>
  </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
  <Trace level="3" type="T">Persisting message Status = 023</Trace>
  <Trace level="3" type="T">Message version 008</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="T">An Exception has occured</Trace>
  <Trace level="1" type="T">Error Text: Error while determining logical port</Trace>
  <Trace level="1" type="T">SystemError message generated. Guid: 5665C5D72F6D1DDE93D8CB24F2274600</Trace>
  <Trace level="1" type="T">Error during execution of message : 5665C5D72F6D1DDE93D8CAD99F13C600</Trace>
  <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 5665C5D72F6D1DDE93D8CAD99F13C600</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
<!--  ************************************
  -->
  <Trace level="3" type="T">Persisting message Status = 023</Trace>
  <Trace level="3" type="T">Message version 000</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </SAP:Trace>
  </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" />
  </SOAP:Body>
  </SOAP:Envelope>
Does anything knows what can be happening?
Thanks,
Ariel

Answer 1

Hi Abhishek,
Thanks for your response. Well, the error is on the PI server. I got the same error if I inject the message directly at the integration engine.
Changing the Comunication chanel from WS to SOAP, solves my problem, but I want to use the WS Adapter since I would like the whole message flowing in the ABAP stack.
Any other idea?
Thanks,
Ariel