thanks man, will do

marc


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Hugo Jos� Pinto
> Sent: Wednesday, August 16, 2000 5:20 PM
> To: jBoss
> Subject: Re: [jBoss-User] Non-deterministic shutdown behavior in jBoss
>
>
> Marc,
>
> > security manager was added recently and depends on things that
> are removed
> > before, this is know behaviour, doesn't look good and adding the proper
> try
> > catch should do the trick
>
>  Got it...
>
>     In EJBSecurityManagerService.java, changing method stopService() like
> the code below solves it.
>
>   ----------CHANGE:
>
>    protected void stopService()
>    {
>   try
>   {
>    // Remove SM from JNDI
>    new InitialContext().unbind(JNDI_NAME);
>   } catch (Exception e)
>   {
>    log.exception(e);
>   }
>    }
>
>    -----------TO:
>
>    import javax.naming.CommunicationException;
>
>    +
>
>    protected void stopService()
>    {
>   try
>   {
>    // Remove SM from JNDI
>    try {
>     Context ctx = new InitialContext();
>         ctx.unbind(JNDI_NAME);
>    } catch (CommunicationException e) {
>     // DO NOTHING: Naming Service has already been stopped!
>    }
>   } catch (Exception e)
>   {
>    log.exception(e);
>   }
> }
>
>
> Best Regards,
>
> Hugo Jos� Pinto
>
>
> ----- Original Message -----
> From: "marc fleury" <[EMAIL PROTECTED]>
> To: "jBoss" <[EMAIL PROTECTED]>
> Sent: Thursday, August 17, 2000 1:03 AM
> Subject: RE: [jBoss-User] Non-deterministic shutdown behavior in jBoss
>
>
> > security manager was added recently and depends on things that
> are removed
> > before, this is know behaviour, doesn't look good and adding the proper
> try
> > catch should do the trick
> >
> > marc
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Hugo Jos� Pinto
> > > Sent: Wednesday, August 16, 2000 4:38 PM
> > > To: jBoss
> > > Subject: [jBoss-User] Non-deterministic shutdown behavior in jBoss
> > >
> > >
> > >     Guys,
> > >
> > >     I'm really sorry to post such a crappy question, but I'm getting
> this
> > > strange behaviour where, about half the times I shutdown jBoss, I get
> the
> > > following stack trace...
> > >
> > >     Does anyone know why is this happening? Is it jBoss or is it JMX?
> > >
> > >     Thanks in advance,
> > >
> > >     Hugo Jos� Pinto
> > >
> > >
> > > [Default] jBoss 2.0 Started
> > > Shutdown
> > > Shutting down 22 MBeans
> > > [JMX RMI Adaptor] Stopping
> > > [JMX RMI Adaptor] Stopped
> > > [JMX RMI Adaptor] Destroying
> > > [JMX RMI Adaptor] Destroyed
> > > [Transaction manager] Stopping
> > > [Transaction manager] Stopped
> > > [Transaction manager] Destroying
> > > [Transaction manager] Destroyed
> > > [DataSource] Stopping
> > > [DataSource] Stopped
> > > [DataSource] Destroying
> > > [DataSource] Destroyed
> > > [Simple Realm Mapping] Stopping
> > > [Simple Realm Mapping] Stopped
> > > [Simple Realm Mapping] Destroying
> > > [Simple Realm Mapping] Destroyed
> > > [Webserver] Stopping
> > > [Webserver] Stopped
> > > [Webserver] Destroying
> > > [Webserver] Destroyed
> > > [Hypersonic] Stopping
> > > [Hypersonic] Stopped
> > > [Hypersonic] Destroying
> > > [Hypersonic] Destroyed
> > > [Auto deployer] Stopping
> > > [Auto deployer] Stopped
> > > [Auto deployer] Destroying
> > > [Auto deployer] Destroyed
> > > [Naming] Stopping
> > > [Naming] Stopped
> > > [Naming] Destroying
> > > [Naming] Destroyed
> > > [Security manager] Stopping
> > > [Security manager] javax.naming.CommunicationException.  Root
> exception
> is
> > > java.
> > > rmi.NoSuchObjectException: no such object in table
> > > [Security manager]      at
> > > sun.rmi.transport.StreamRemoteCall.exceptionReceivedF
> > > romServer(StreamRemoteCall.java:245)
> > > [Security manager]      at
> > > sun.rmi.transport.StreamRemoteCall.executeCall(Stream
> > > RemoteCall.java:220)
> > > [Security manager]      at
> > > sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
> > >
> > > [Security manager]      at
> org.jnp.server.NamingServer_Stub.unbind(Unknown
> > > Sourc
> > > e)
> > > [Security manager]      at
> > > org.jnp.interfaces.NamingContext.unbind(NamingContext
> > > .java:414)
> > > [Security manager]      at
> > > org.jnp.interfaces.NamingContext.unbind(NamingContext
> > > .java:402)
> > > [Security manager]      at
> > > javax.naming.InitialContext.unbind(InitialContext.jav
> > > a:374)
> > > [Security manager]      at
> > > org.jboss.security.EJBSecurityManagerService.stopServ
> > > ice(EJBSecurityManagerService.java:90)
> > > [Security manager]      at
> > > org.jboss.util.ServiceMBeanSupport.stop(ServiceMBeanS
> > > upport.java:118)
> > > [Security manager]      at
> > > org.jboss.util.ServiceMBeanSupport.destroy(ServiceMBe
> > > anSupport.java:133)
> > > [Security manager]      at java.lang.reflect.Method.invoke(Native
> Method)
> > > [Security manager]      at
> > > javax.management.MBeanServer.invoke(MBeanServer.java:
> > > 1635)
> > > [Security manager]      at
> > > javax.management.MBeanServer.invoke(MBeanServer.java:
> > > 1501)
> > > [Security manager]      at org.jboss.Main$2.run(Main.java:178)
> > > [Security manager] Stopped
> > > [Security manager] Destroying
> > > [Security manager] Destroyed
> > > [DataSource] Stopping
> > > Shutting done
> > >
> > >
> > >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe:        [EMAIL PROTECTED]
> > > To unsubscribe:      [EMAIL PROTECTED]
> > > Problems?:           [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
>
>



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to