Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Imaging and Process Management
11g Release 1 (11.1.1)

Part Number E12782-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to current chapter
Up
Go to next page
Next
View PDF

10.18 Deciphering Nested Stack Errors

A nested stack error, also called a nested exception, is basically an error that has been wrapped by another error, which is standard with Java and other languages to help provide more context to the issue. You can usually find the nested exception by locating the caused by string in the stack trace as shown in bold in the following example. If there is not enough information provided by the Oracle I/PM error, look deeper into the error message to see if other components are involved. Oracle I/PM uses nested stack errors to display repository related problems, BPEL issues, or problems caused by other components. After you locate the possible initial error, check the diagnostic logs for more troubleshooting information.

In the following example, the TCM-00787 error is occurring because the default provider within the Oracle Content Server repository was corrupted and reset (see boldface text).

[2009-06-11T09:56:21.720-07:00] [ipm_server1] [ERROR] []
[oracle.imaging.ui.backing.application.LifecycleState] [tid:
[ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 
0000I7GFuQ9F8DT6uBj8EH1AC2Ut0000WK,0] [APP: imaging#11.1.1.1.0] IPM UI Exception[[
oracle.imaging.ImagingException: TCM-00787: A repository error has occurred. Contact your system administrator for assistance.
        stackTraceId: 9-1244739381674
        faultType: SYSTEM
        faultDetails:
          ErrorCode = oracle.stellent.ridc.protocol.ServiceException,
ErrorMessage = File
'/app/stellent/content/10gR3/proxy1/data/providers/defaultfilestore/provider.hda' 
does not exist.
        at
oracle.imaging.repository.ucm.UcmErrors.convertRepositoryError(UcmErrors.java:108)
        at
oracle.imaging.repository.ucm.UcmLifecycleOperationImpl.getStorageRules(UcmLifecycleOperationImpl.java:58)
...
<...snip...>
        at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)        
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)  at
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: oracle.stellent.ridc.protocol.ServiceException: File
'/app/stellent/content/10gR3/proxy1/data/providers/defaultfilestore/provider.hda'does not exist.
       at
oracle.stellent.ridc.protocol.ServiceResponse.getResponseAsBinder(ServiceResponse.java:116)
at
oracle.stellent.ridc.protocol.ServiceResponse.getResponseAsBinder(ServiceResponse.java:92)
at
oracle.imaging.repository.ucm.UcmResponse.<init>(UcmResponse.java:61)
at
oracle.imaging.repository.ucm.UcmRequest.makeOneServiceCall(UcmRequest.java:310)       
at 
oracle.imaging.repository.ucm.UcmRequest.makeServiceCallWithRetries(UcmRequest.java:228)        
at 
oracle.imaging.repository.ucm.UcmRequest.makeServiceCall(UcmRequest.java:210)        
at 
oracle.imaging.repository.ucm.UcmLifecycleOperationImpl.getStorageRules(UcmLifecycleOperationImpl.java:53)        
... 234 more