Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via ibm.com by Unknown author, 1 year ago
FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred.  The unexpected exception is chained to this exception. Message was: null
via ibm.com by Unknown author, 1 year ago
FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred.  The unexpected exception is chained to this exception. Message was: null
via ibm.com by Unknown author, 1 year ago
FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurredThe unexpected exception is chained to this exception. Message was: null
com.filenet.api.exception.EngineRuntimeException: FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred.  The unexpected exception is chained to this exception. Message was: null	at com.filenet.apiimpl.util.J2EEUtilWS.handleException(J2EEUtilWS.java:116)	at com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:224)	at com.filenet.api.util.UserContext.doAs(UserContext.java:143)	at filenet.jpe.cm.CMQueueInfo.getQueueMethodsFromTheClass(CMQueueInfo.java:1065)	at filenet.jpe.cm.CMQueueInfo.initialSetup(CMQueueInfo.java:1154)	at filenet.jpe.cm.CMQueueInfo.getMethod(CMQueueInfo.java:1111)	at filenet.jpe.cm.CMQueueInfo.validate(CMQueueInfo.java:1516)	at filenet.jpe.cm.CMQueueInfo.validateQueueDefinition(CMQueueInfo.java:1534)	at filenet.jpe.cm.CMConfigManager.validateQueueDefinition(CMConfigManager.java:1321)	at filenet.jpe.rpc.ejb.EJB_rpc_transferConfig.execute(EJB_rpc_transferConfig.java:453)	at filenet.jpe.rpc.ejb.EJBAsyncRunnable_TransferConfig.run(EJBAsyncRunnable_TransferConfig.java:151)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)