After a long examination of the forum, where there are quite a few ClassCastException-problems. I decided to change my build. Previously I built a server.jar and a client.jar. The EJBs were of course deployed from the server.jar, while I put the client.jar in the WEB-INF/lib-catalog of my .war-file. I put the server.jar and the .war into a .ear for deployment. A class might be in both the server.jar and the client.jar, and it seems like this, combined with different ClassLoaders, may have caused the problem.
When I don't create the client.jar, my problem has disappeared. I haven't quite figured out why the problem arose after hot-deploy, and not before, but I guess it is merely a question of digging. Any comments?
I encounter the same problem, I have a ejb-jar and a ejb-client.jar in my war-file I add the client-jar and after a redeploy I get a classcastexception (I wonder why because the client-jar hasn't changed). I resolve it via a shutdown of the whole jboss and then delete the folder under catalina/work/localhost/$Context-Root and then restart jboss.
I haven't found a better way, but it has cost me a day to find out that the classcastexception seems to be not a "real" classcastexception.
If you have information how to make a real redeploy with the tomcat, please let me know. I also tried to stop just the EmbeddedCatalinaSX, then delete the folder and then restart the EmbeddedCatalinaSX but that didn't work (also redeploy after restart did not work).
I have this problem too.
It's quite annoying.
Does anyone has a workaround?