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

java.lang.Exception: 	at weblogic.transaction.internal.CoordinatorDescriptor.init(CoordinatorDescriptor.java:176)	at weblogic.transaction.internal.CoordinatorDescriptor.(CoordinatorDescriptor.java:128)	at weblogic.transaction.internal.ServerCoordinatorDescriptor.(ServerCoordinatorDescriptor.java:258)	at weblogic.transaction.internal.ServerCoordinatorDescriptor.getOrCreate(ServerCoordinatorDescriptor.java:953)	at weblogic.transaction.internal.ServerCoordinatorDescriptor.getOrCreate(ServerCoordinatorDescriptor.java:371)	at weblogic.transaction.internal.ServerCheckpoint.onRecovery(ServerCheckpoint.java:175)	at weblogic.transaction.internal.StoreTransactionLoggerImpl.recover(StoreTransactionLoggerImpl.java:441)	at weblogic.transaction.internal.StoreTransactionLoggerImpl.init(StoreTransactionLoggerImpl.java:230)	at weblogic.transaction.internal.StoreTransactionLoggerImpl.init(StoreTransactionLoggerImpl.java:212)	at weblogic.transaction.internal.StoreTransactionLoggerImpl.(StoreTransactionLoggerImpl.java:121)	at weblogic.transaction.internal.ServerTransactionManagerImpl.recover(ServerTransactionManagerImpl.java:933)	at weblogic.transaction.internal.TransactionRecoveryService.startOwnRecoveryIfNeeded(TransactionRecoveryService.java:214)	at weblogic.transaction.internal.TransactionRecoveryService.resume(TransactionRecoveryService.java:165)	at weblogic.transaction.internal.TransactionRecoveryService.start(TransactionRecoveryService.java:181)	at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)	at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)