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 ode-dev by Fernando Lozano, 1 year ago
Deployed directory null no longer there!
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!
org.apache.ode.bpel.iapi.ContextException: Deployed directory null no longerthere! at org.apache.ode.store.ProcessStoreImpl.load(ProcessStoreImpl.java:600) at org.apache.ode.store.ProcessStoreImpl$6.call(ProcessStoreImpl.java:455) at org.apache.ode.store.ProcessStoreImpl$Callable.call(ProcessStoreImpl.java:695) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595)