NoSuchObjectException when redeploying

Question

I get the following exception when redeploying. Is this the expected
behavior?
<Jun 4, 2003 9:49:02 AM PDT> <Error> <Tracking> <402201> <EventService
failure w
hile attempting dispatch of Behavior Tracking event: Event [portalApp @
SessionE
ndEvent @ Wed Jun 04 09:49:02 PDT 2003 ]
{session-id=2eg5cRlzJqkX2l111Ok1ZOvZXZ2
WeupkzqCGT6mtmcgMX03XV2IS!-1740880684!1054744633146}.
java.rmi.NoSuchObjectException: Bean is already undeployed.
at
weblogic.ejb20.manager.BaseEJBManager.preInvoke(BaseEJBManager.java:9
5)
at
weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.ja
va:126)
at
weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:12
7)
at
weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObje
ct.java:61)
at
com.bea.p13n.events.internal.EventServiceBean_kh7q5h_EOImpl.dispatchE
vent(EventServiceBean_kh7q5h_EOImpl.java:29)
at
com.bea.p13n.tracking.TrackingEventHelper.dispatchEvent(TrackingEvent
Helper.java:96)
at
com.bea.p13n.tracking.listeners.SessionEventListener.sessionDestroyed
(SessionEventListener.java:87)
at
weblogic.servlet.internal.WebAppServletContext.notifySessionDestroyed
(WebAppServletContext.java:2312)
at
weblogic.servlet.internal.session.SessionData.remove(SessionData.java
:728)
at
weblogic.servlet.internal.session.MemorySessionContext.invalidateSess
ion(MemorySessionContext.java:61)
at
weblogic.servlet.internal.session.MemorySessionContext$SessionCleanup
Action.run(MemorySessionContext.java:121)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:780)
at
weblogic.servlet.internal.session.MemorySessionContext.shutdown(Memor
ySessionContext.java:77)
at
weblogic.servlet.internal.WebAppServletContext.destroyServlets(WebApp
ServletContext.java:4884)
at
weblogic.servlet.internal.WebAppServletContext.shutdown(WebAppServlet
Context.java:4797)
at
weblogic.servlet.internal.ServletContextManager.removeContext(Servlet
ContextManager.java:156)
at
weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:609
at
weblogic.servlet.internal.WebAppModule.rollback(WebAppModule.java:448
at
weblogic.j2ee.J2EEApplicationContainer.rollbackModule(J2EEApplication
Container.java:1624)
at
weblogic.j2ee.J2EEApplicationContainer.rollback(J2EEApplicationContai
ner.java:949)
at
weblogic.j2ee.J2EEApplicationContainer.rollback(J2EEApplicationContai
ner.java:932)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
er.java:584)
at
weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
veDeployer.java:1062)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
loyer.java:730)
at
weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
dler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>

Answer 1

i think your code that you mention has no problem. but in other part
here is some tips for that kind of exception
A NoSuchObjectException is thrown if an attempt is made to invoke a method on an object that no longer exists in the remote virtual machine. If a NoSuchObjectException occurs attempting to invoke a method on a remote object, the call may be retransmitted and still preserve RMI's "at most once" call semantics. A NoSuchObjectException is also thrown by the method java.rmi.server.RemoteObject.toStub and by the unexportObject methods of java.rmi.server.UnicastRemoteObject and java.rmi.activation.Activatable and