on 12-14-2011 6:18 AM
Hi.
We are experiencing an error at the 'Call Adapter' stage of the pipeline. It seems as if the message is unable to move from the integration engine to the adapter engine with this error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
The HTML dump says u2013
java.lang.NullPointerException:
at com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders.setHeader(TransportHeaders.java:169)
at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1437)
at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1122)
at com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(XIEventHandler.java:791)
at com.sap.engine.messaging.impl.spi.ServerConnectionImpl.request(ServerConnectionImpl.java:237)
at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:417)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
This occurred after an SLD update. Does anyone know how to fix this issue?
Thanks
Regards
Riaz
So do you mean only receiver SOAP adapter related scenario has this problem? Are other java based adapter scenarios working?
Regards,
Prateek Raj Srivastava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prateek
I have tested a simple file adapter scenario and it too fails at the 'Call Adapter' stage of the pipeline. So the issue is definitely between the integration engine and the adapter engine. The integration engine does not seem able to reach the adapter due to that Nullpointer Exception.
Regards
Riaz
Hi
I have tried restarting the Java Stack and channel. Neither have worked.
The issue is not on the channel level, it is the disconnect between the integration engine and adapter engine. The channel is never even reached because the message cannot leave the integration engine to get out through the adapter engine.
Regards
Riaz
go to TCODE--> SM59 and then expand TCPIP and then you can see AI_RUNTIME_JCOSERVER --> double click on that and then you can see the connectivity test there just click on that and check if the RFC is successfull or not
follow the same to AI_DIRECTORY_JCOSERVER also
REf: http://help.sap.com/saphelp_nw04/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
HI Riaz,
Can you please try to answer the below questions, so that we can have a clue to work on the issue.
1. What is the sender and receiver.
2. Are you using Business system defined in the SLD or using Business Service?
3. Is this interface previously working properly or getting issues while development?
4. What is the version of PI ?
5. Try to replicate the same scenario and check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys
1. Sender - Backend ERP (ECC) calling enterprise service, Receiver - SOAP Web service. Both are business systems internal to the network
2. Both sender and receiver are Business systems which are registered in the SLD.
3. This interface was previously working, until the LSD was updated, then it began.
4. PI 7.10
5. All the scenarios which use this type of communication (Proxy to SOAP) are failing at the same stage
I have also logged an OSS call with SAP and they are currently looking at the issue.
Regards
Riaz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All
Everything is fine in the SLDCHECK. .
SAP Note 1452307 refers to a 'java.lang.ClassCastException' however our error is a 'java.lang.NullPointerException', also it speaks about the issue when the system is highly loaded, this is not the case in our system, there are very few messages passing through the system at one time.
I have read through the sdn posts, but we do not have any of their symptoms.
Any other ideas?
Thanks
Riaz
Hi,
Check this SAP note # 1452307
Regards
Ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check "SLDCHECK" and see everything looks good or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.