This question can be asked in a variety of different ways, more notably: "My application server is failing to load my deployments because it tries to before the deployment is done".

The real issue is that the application server's "polling" time is set to such a short interval, that it's checking the new deployment directory so often and so quickly that it's trying to load your deployment before MyEclipse is done copying it out.

The only workaround for this issue is to increase your application server's polling time to a longer interval so it isn't checking so frequently.

One of our power-users gkelley passed along the following information on the topic:

It seems as if once autodeployment of an EAR has failed, OC4J won't attempt to re-autodeploy that EAR in the future, even if one manually deletes and recreates the EAR in the autodeploy directory. One can set the "polling" interval for OC4J. For more info, see http://download.oracle.com/docs/cd/B31017_01/web.1013/b28950/threadpool.htm