Be sure all the jars are left out of jboss-service.xml from conf/default.
After that, there is a problem with removing the classloaders for jars you
deployed... I'm considering what the best way to fix it is... I don't want
to get too complicated.. but should be there very soon.
I still haven't
marc fleury wrote:
> |Hot-deploying the Jetty service works fine.
Hhhhmmm.
The stuff checked in at the moment works - but I want to go further
try this:
rm deploy/jetty-service.xml
rm lib/ext/jetty-plugin
put this in plugins/jetty/build.xml:
-8<8<
|
|Cheers,
|David
|
|> -Original Message-
|> From: marc fleury [mailto:[EMAIL PROTECTED]]
|> Sent: Friday, September 21, 2001 8:57 AM
|> To: [EMAIL PROTECTED]
|> Subject: RE: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
|>
|>
|> |Hot-deploying the Jetty service works fin
t but I suddenly got real busy at work and haven't had time.
Cheers,
David
> -Original Message-
> From: marc fleury [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 21, 2001 8:57 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
&
|Hot-deploying the Jetty service works fine.
What happened to the idea of creating your own directory layout space upon
deployment from the JSR I thought that was very useful...
do you still require this? it would be very useful for me to work with a
specific case
marcf
|
|Hot-undeploying gene
on 1-09-17 02.44, Julian Gosnell at [EMAIL PROTECTED] wrote:
> [JettyService] Initialized
> [JettyService] Starting
> [Jetty] start HttpServer version Jetty/3.1.RC9
> [JettyService] Stopped
> java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method)
>
David Maplesden wrote:
> Ahh, this is a bug I came across about two weeks ago when developing my own
> mbean.
>
> It is actually a bug in the MBeanServerImpl when working with mbeans that
> use the default domain in the object name (i.e. ":service=Jetty" instead of
> "SomeDomain:service=Jetty").
omain name in your object name the problem goes away.
>
> David.
>
> > -Original Message-
> > From: Julian Gosnell [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 17, 2001 12:09 PM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-dev] JSR/SAR (Jetty) U
Bug reported to JMX team but no response up to now.
Andy
- Original Message -
From: "David Maplesden" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 16, 2001 5:02 PM
Subject: RE: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
> Ahh, this is
em goes away.
>
> David.
>
> > -Original Message-
> > From: Julian Gosnell [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 17, 2001 12:09 PM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
> >
> >
> &
:09 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
>
>
>
> Hot-deploying the Jetty service works fine.
>
> Hot-undeploying generates the following exception :
>
>
> [AutoDeployer] Auto undeploy of
> file:/mnt/megalodon
Hot-deploying the Jetty service works fine.
Hot-undeploying generates the following exception :
[AutoDeployer] Auto undeploy of
file:/mnt/megalodon/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0alpha/deploy/jetty-service.xml
[JettyService] Stopping
[Jetty] Stopped SocketListener on 0.0.0.0
12 matches
Mail list logo
