Tell me a little more: OS, JVM, Version etc....
Were you hot-deploying - i.e. copying your ear into jboss/deploy ? If so, and it was a large ear or a slow copy the file may not have been complete when jboss saw it and began to unpack it. To avoid this, copy the ear to somewhere on the same filesystem as the deploy dir, then move it into that dir. A move/rename will be more atomic than a copy. Or you could deploy via the JMX agen - I prefer this because it is synchronous. If this isn't it, perhaps you are deploying into a context that has already been populated. Or maybe resources in the ear were being hit by clients at the time of redeployment and could not be released ? Mail me your log and I'll take a look at it. Jules Andreas Schaefer wrote: > Hi Geeks > > I ran into a problem with redeployment of EAR files > containing a WAR file on JBoss 2.4 with Jetty. > > The problem is that I had to deploy/undeploy several > times to finally get all the changes deployed. Both times > previous calles to a page returned with an error. > > Do you encounter similar issues ? > > xxxxxxxxxxxxxxxxx > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > xxxxxxxxxxxxxxxxx > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
