Unable to trace. Unable to trace successfully. java.lang.AssertionError: intradoc.common.ServiceException (Doc ID 1900918.1)

Last updated on OCTOBER 05, 2016

Applies to:

Oracle WebCenter Content - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms


There are stuck threads on the Content Server and the logs show the following type of error:

6/21/14 11:04 PM Unable to trace. Unable to trace successfully. java.lang.AssertionError: intradoc.common.ServiceException: !$Unable to report messages successfully.. Unable to report messages successfully. java.lang.AssertionError: intradoc.common.ServiceException: !$Unable to trace successfully.. Unable to trace successfully. java.lang.AssertionError: intradoc.common.ServiceException: !$Unable to report messages successfully.. Unable to report messages successfully. java.lang.AssertionError. . .

 

This error was in a kind of recursive loop where the first time it showed up there was only one entry that starts with "Unable to report. . .", the second listing had two, the third had three etc.

 

Changes

The Trace sections were updated to include more troubleshooting information.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms