Since you have a reference to objects that have a reference to the old
versions of the classes, the old versions of the classes can't be
discarded.
Have you tried this with a full .ear deployment? (from below I assume
that you're deploying the servlet and EJBs separately) .ear deployment
should work. This would be the answer for production.
-danch
Jonas Bergström wrote:
> Hi folks,
>
> I posted a message a couple of months ago about hot undeployment. I reveived
> two answers, neither work, so I'm trying again...
>
> My servlet (Tomcat in-process) has a reference to an EJB. After hot
> undeploying the EJB, the servlet is still able to invoke methods on the EJB.
> Why?
>
> The tmp-files in /tmp/deploy/Default can't be removed since the JBoss
> process has locked them.
> The EJB class is only visible for the EJB itself, neither JBoss or the
> servlet has it in their classpath's.
>
> This is causing a problem since new versions of the EJB is not recognized by
> the servlet. It IS recognized if the servlet creates a new reference on each
> request, but that seems very unefficient.
>
>
> Am running JBoss 2.2.1 and Tomcat 3.2.1 on Windows 2000 Server.
>
>
> Thanks / Jonas
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
