Skip to Content
0

HTTP_PROCESS_ERROR( No Information Available for Audit Key): Http to Http scenario

Nov 01, 2016 at 12:30 PM

142

avatar image

Hi

We have http to http scenario where our sender channel captures below error,

Error in processing caused by: java.lang.IllegalArgumentException: Unknown DeliverySemantics: EO?IDENTIFIER=VALUE


And after using XPI inspector we found below error

No Information Available for Audit Key : HTTP_PROCESS_STARTED

500 Internal Server Error is returned for HTTP request

Received no SAPLogonTicket. Authentication stack:

Can anyone suggest.

Thanks

10 |10000 characters needed characters left characters exceeded

Can you post the URL which you are using

0
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Raghuraman S Nov 01, 2016 at 01:06 PM
0

Hello SAP PI,

Is your sender HTTP channel up and running?

Share
10 |10000 characters needed characters left characters exceeded
SAP PI Nov 01, 2016 at 01:10 PM
0

Hi

Yes actually sender system had an upgrade hence once they test with new system we face above error, but when with the old setup it is still successful.

Authentication stack: [sap.com/com.sap.aii.adapter.http.app*HttpAdapter].
[EXCEPTION]
com.sap.security.core.server.jaas.DetailedLoginException: Received no SAP Authentication Assertion Ticket.
at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.login(EvaluateAssertionTicketLoginModule.java:240)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:254)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:66)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:282)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:111)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
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:78)
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:78)
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:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

This is the error seen in XPI inspector: EvaluateAssertionTicketLoginModule,

Thanks

Share
10 |10000 characters needed characters left characters exceeded
SAP PI Nov 03, 2016 at 08:44 AM
0

Hi All

By using a packet sniffer sender party was able to capture the differences between the old version and the new version, a small difference in the output message was found and fixed.

Thanks

Share
10 |10000 characters needed characters left characters exceeded