cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP 500 Internal Server Error in SXMB_MONI

Former Member
0 Kudos

Hello,

Getting HTTP 500 Internal Server Error while running some Synchronous Scenario of ECC -> PI -> Legacy system (SOAP adapter). Following are the errors received in SXMB_MONI.

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIAdapterFramework</SAP:Category> 
  <SAP:Code area="MESSAGE">GENERAL</SAP:Code> 
  <SAP:P1 /> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error</SAP:AdditionalText> 
  <SAP:Stack /> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <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>N</SAP:Retry> 
  </SAP:Error>

Both the errors are not regular but comes up every now and than. If the scenario is re-run from ECC than it works.

Please advise.

Thanks a lot

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Please check your content type in MONI. The content type should be text/xml for soap adapters.

Thanks

Uaruna

Former Member
0 Kudos

Hi Unnamalai,

We are also facing same kind of error, The content is coming as TEXT/HTML. Just wanted to ask if it is the error with the payload/data or something we have to change in PI?

Below is the error:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 System.ServiceModel.ServiceActivationException

Regards,

Akshat Saluja

Former Member
0 Kudos

Hi Chanakya,

Please see this link for http error.

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Thanks

Nidhi

former_member200962
Active Contributor
0 Kudos

Check the request format (message structure) that XI/ PI is sending to the Legacy System and also verify the Target URL in SOAP channel.

For more information check point6 of this blog: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Regards,

Abhishek.

Former Member
0 Kudos

Thanks Abhishek!!

I am getting these error once in 10-20 messages, in the rest I am getting proper response from client. I dont think it is Target URL issue.

With regards to the point no 6 of the link provided I have added following entries in SOAP adapter:

Processing Sequence:

Module Name: localejbs/AF_Modules/MessageTransformBean

Type: Local Enterprise Bean

Module Key: SOAP

Module Cnfiguration:

Module key: SOAP

Parameter name: Transform.ContentType

parameter Value: text/xml

I am not getting

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error</SAP:AdditionalText>

currently. But testing is going on will update if it occurs again.

But still getting

<SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>

error very frequently!!

Regards

lars_ottawa2
Explorer
0 Kudos

Hi Chanakya,

do you have access to the mentioned HTML content? Normally, in an synchronous scenario the HTML content will be send within the response and can be viewed within the payload section of a message.

Regards,

Lars

Former Member
0 Kudos

Thanks a lot Nidhi. I am looking at the notes provided.

Thanks a lot Lars. Please find the content of HTML content:

java.lang.ClassCastException: class com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders:interface:com.sap.aii.af.ms.ifc9(at the rate)com.sap.engine.boot.loader.ResourceMultiParentClassLoader(at the rate)6f9702b1(at the rate)alive incompatible with class com.sap.engine.interfaces.messaging.spi.transport.HTTPHeaders:interface:com.sap.aii.af.ms.ifc(at the rate)com.sap.engine.boot.loader.ResourceMultiParentClassLoader@6f9702b1(at the rate)alive
	at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:447)
	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:162)
	at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
	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:73)
	at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
	at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
	at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
	at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
	at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
	at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
	at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
	at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
	at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
	at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
	at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
	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.MemoryStatisticFilter.process(MemoryStatisticFilter.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.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
	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:428)
	at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
	at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
	at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
	at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
	at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)

Regards

lars_ottawa2
Explorer
0 Kudos

Hi Chanakya,

have look at the following SAP Note: 1452307 (Sync-XI resp-message fails with ClassCastException in PI 711)

Perhaps it will help you...

Regards,

Lars

Former Member
0 Kudos

Thanks Lars.

We are using PI 7.11 SP4 and note 1452307 is already applied but still getting the same error.

Regards

Former Member
0 Kudos
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <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>N</SAP:Retry> 
  </SAP:Error>

I am still getting the above error and very frequently. The difference between messages where getting this error and where not is:

NO ERROR:

In Synchronous the outbound and inbound service interfaces are correct in SXMB_MONI (Outbound Service Interface in Outbound messge and Inbound Service Interface in Inbound message)

ERROR:

In Synchronous both Outbound and Inbound Service Interfaces are same. (Outbund Service Interfaces in both OUtbound and Inbound message)

But even in case of error the whole scenario is working perfectly fine in the background as the client's legacy system is getting messages and it shows this error in SAP PI 7.11 system.

There is no issue with configuration as the messages are running successful as well. Getting this error on and off.

Regards

Former Member
0 Kudos

Hello All,

In trying to resolve teh issue we have upgraded PI 7.11 to SP 5 level but still the problem persits.

Any help!!

Regards

srikanth_srinivasan3
Active Participant
0 Kudos

Hi

Error could be due to standard content handling filter mechanism. In other words, few characters in XML message are not seem to be allowed while sending a messages to IE.

Solution:

- Deactivate the Standard Authorization-Handler Content Filter in Transaction SMICM

- Menu -> Goto -> HTTP-Plugin -> Authorization-Handler.

- After deactivation of this filter we could use the "Test Message" tool again.

-

Srikanth Srinivasan

Edited by: Srikanth Srinivasan on Jun 18, 2010 4:20 PM

Former Member
0 Kudos

Dear All,

The problem has been resolved by the workaround provided by Mark Smyth in the following thread.

Thanks a lot

gopalkrishna_baliga
Participant
0 Kudos

Hi Chanakya,

Can you explain the workaround given by Mark a bit more?

Where do I need to change the "messaging.synMessageRemove.removeBody" parameter?

What config tool Mark is referring to?

What is NWA?

Thanks

Gopal

Edited by: gopalkrishna baliga on Aug 9, 2010 10:22 AM

Former Member
0 Kudos

Hi Gopal,

Change the "messaging.synMessageRemove.removeBody" parameter of the "com.sap.aii.af.ms.svc" service in the NWA (NetWeaver Administrator) or in the Config Tool. Change the value from "True" to "False".

To access NWA: http://<hostname>:<port>/nwa

Also check note #1452307, it was supposed to be updated sometime in June. If it is than apply that note and problem will be resolved otherwise use the workaround mentioned above.

Regards