In this case i don't think, it's the AutoDeployer. When i look at the
stack trace, ist has something to do whith the destroy() method of
org.jboss.ejb.plugins.AbstractInstanceCache and JMS. Seems to be
some implementation for the BeanCacheMonitor.
Ralf
Scott M Stark wrote:
>
> This has come up a number of times and the answer that has been given is that
> the current auto deployer needs to be redesigned to work correctly. When I
> asked about it, Marc replied:
>
> "The deployer was a first draft and is in need of serious
> rethinking/redesign. Usually we refactor but in this case I believe we need
> to seriously revisit that code."
>
> ----- Original Message -----
> From: "Ralf Purnhagen" <[EMAIL PROTECTED]>
> To: "jBoss" <[EMAIL PROTECTED]>
> Sent: Tuesday, January 09, 2001 11:54 AM
> Subject: [jBoss-User] Re: Auto-(Re)Deployment Failure
>
> > Hi Luke,
> >
> > you are not the only one, who got this stack trace. Benjamin Broll
> > and i have posted the same stack trace a few days ago. There has not
> > been any answer to our question yet, so we still have to wait ...
> >
> > Ralf
> >
> > Luke Taylor wrote:
> > >
> > > I've just built the latest CVS version of JBoss and deployed an app
> > > which I've been running without any problems. Everything is fine - the
> > > initial deployment goes without a hitch. But when I rebuild the app and
> > > copy the jar file to the jboss "deploy" directory the autodeployer
> > > cracks up with the stack trace below. It seems to run into problems
> > > attempting to undeploy the current version.
> > >
> > > The version I've been usin g up till now was quite a bit older (i.e.
> > > before the changes to the configuration files were implemented) and
> > > we've been running a live server on that without problems since before
> > > Christmas (very impressed btw. It's been our first EJB project and has
> > > been relatively painless thanks to the ease of use JBoss provides).
> > >
> > > Anyone got any ideas? It's obviously not a show-stopper because I can
> > > restart the server and the deployment succeeds, but it does seem like
> > > something may be broken in the current build.
> >
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
