SAP Knowledge Base Article - Preview

1620740 - 500 Internal Server Error: processing requests via ICM

Symptom

500 internal server error occurs when processing requests via ICM and below exception can be seen in the default traces :

“500 Internal Server Error is returned for HTTP request com.sap.bc.proj.jstartup.fca.FCAException: Output broken (-7). at com.sap.bc.proj.jstartup.fca.impl2.FCAConnection.getOutBuf3(Native Method) at com.sap.bc.proj.jstartup.fca.impl2.FCAConnection.getOutBuf(FCAConnection.java:302)”

The SAP Netweaver AS Java default traces show the following exception:
[EXCEPTION]
com.sap.bc.proj.jstartup.fca.FCAException: Output broken (-7).
at com.sap.bc.proj.jstartup.fca.impl2.FCAConnection.getOutBuf3(Native Method)
at com.sap.bc.proj.jstartup.fca.impl2.FCAConnection.getOutBuf(FCAConnection.java:302)
at com.sap.bc.proj.jstartup.fca.impl2.FCAOutputStream.write(FCAOutputStream.java:93)

You may also observe error "Could not find taskguid -1" in the default trace.


Read more...

Environment

  • SAP NetWeaver All versions
  • SAP Composition Environment All versions
  • SAP Process Integration All versions
  • SAP Solution Manager All versions

Product

SAP Composition Environment all versions ; SAP NetWeaver Application Server for Java all versions ; SAP NetWeaver all versions ; SAP Process Integration all versions ; SAP Solution Manager all versions

Keywords

500 Internal Server Error, ICM request, Output broken (-7), FCAException, FCAConnection.java:302 , KBA , BC-JAS-WEB , Web Container, HTTP, JavaMail, Servlets , BC-CST-IC , Internet Communication Manager , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.