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 Coderanch by Niteen Patil, 1 year ago
Deployed directory (unknown) no longer there!
via Coderanch by Qiao Lei, 1 year ago
Deployed directory (unknown) no longer there!
via ode-dev by Fernando Lozano, 1 year ago
Deployed directory null no longer there!
org.apache.ode.bpel.iapi.ContextException: Deployed directory (unknown) no longer there!	at org.apache.ode.store.ProcessStoreImpl.load(ProcessStoreImpl.java:636)	at org.apache.ode.store.ProcessStoreImpl$6.call(ProcessStoreImpl.java:492)	at org.apache.ode.store.ProcessStoreImpl$Callable.call(ProcessStoreImpl.java:734)	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)	at java.util.concurrent.FutureTask.run(Unknown Source)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)	at java.lang.Thread.run(Unknown Source)