Two days ago, our server needed to be shut down but all was well. JBoss worked flawlessly. But, after the shutdown, a few little quirks emerged for some odd reason. The biggest and foremost is the hot deploy. When I put a newer version of an EJB into the container, the server actually says it's undeploying the old version and deploying the new version. However, when I load my client, nothing has changed. Keep in mind, this worked last week.

It's almost like all the EJB's are being cached somewhere and not updated.

I don't want it to cache anything right now. This is just our development server so quick little "let's see if this bean works now" deployments are all we are after. I would like it to 'refresh' after I deploy a new EJB.

Reload the client and the call to the method returns "foo 1", but with a restart of the server, it would return "bar 34"

Alright, as for what I think it was...I was working (on a seperate project) on calling one EJB from another. The autodeploy worked as normal for the first couple of times, then it stopped. So I removed the bean that calls the second bean, restarted the server one more time and wallah! works again.

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.

I have the problem that I have an .ear-file referencing another .ear-file.Each of the .ear-files has it's own loader repository configured via the jboss-app.xml and parent delegation is set to false. Futhermore in the ear-deployer.xml the isolated and the callbyvalue attributes are set to true.