That's true. Hot deploy doesn't seem to be working all the times. Even we have faced the same issue with hot deploy. Though the server says (from the log), that it undeployed the bean, it actually doesn't seem to be doing so.
We've tried to look around, and found some stuff in the tmp directory, under directory. The tmp directory has deploy directory under which there are many jar files. You would see your ejb jar file with a name tmpxxxx.jar (for example tmp1990ejbtestbean.jar). If you do a jar tvf on this jar, you would find the bean classes in it. Now, if you compile another version of your bean and put it in the deployment path, the server would redeploy it. While redeploying, it tries to delete this tmp1990ejbtestbean.jar from that directory (sometimes it fails to delete this file). After the redeployment, another temp file is created, for example like: tmp2000ejbtestbean.jar. I guess this is where the problem is. If it's not able to delete the earlier temp file, it doesn't update the bean information (or whatever it is). In this case, I see multiple tmpbeanjar files for the same bean in this directory. HTH, Thanks, Kalyan. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854870#3854870 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854870 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
