My Oracle Support Banner

Flow Traces Not Visible in Enterprise Manager (Doc ID 1339886.1)

Last updated on MARCH 27, 2020

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.
***Checked for relevance on 02-June-2014***


After deploying an application to the Enterprise Manager and testing it, you try to check the "Flow traces" by clicking on a Composite Instance-ID.
You receive a pop-up window with the error:

"Error 500--Internal Server Error - The server encountered an unexpected condition which prevented it from fulfilling the request."

This happens when trying to expand any flow trace of any composite in EM.

Checking the AdminServer log you can see the following stack trace:

<Error> <HTTP> <fru3118v> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <f68db67a0d74c1ea:10088898:1312df565bb:-7ff4-000000000000184a> <BEA-101019> <[ServletContext@1498181426[app:em module:/em path:/em spec-version:2.5]] Servlet failed with IOException Stream closed
at oracle.xml.parser.v2.XMLReader.pushXMLReader(
at oracle.xml.parser.v2.XMLParser.parse(
at oracle.jsp.parse.XMLUtil.getDocument(
at oracle.jsp.parse.OracleJsp2Java.transformImpl(
at oracle.jsp.parse.OracleJsp2Java.transform(
at oracle.jsp.runtimev2.JspPageCompiler.attemptCompilePage(
at oracle.jsp.runtimev2.JspPageCompiler.compileBothModes(
at oracle.jsp.runtimev2.JspPageCompiler.parseAndGetTreeNode(
at oracle.jsp.runtimev2.JspPageInfo.compileAndLoad(
at oracle.jsp.runtimev2.JspPageTable.compileAndServe(
at oracle.jsp.runtimev2.JspPageTable.service(
at oracle.jsp.runtimev2.JspServlet.internalService(
at oracle.jsp.runtimev2.JspServlet.service(


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.