geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Wilkins <>
Subject GBean configuration confusion
Date Wed, 04 Feb 2004 03:48:34 GMT

I've been chasing some "strange" behaviour with the GBeans configuration.

I'm not sure if these are bugs or just poor exception reporting.  But I'll
dump here just in case...

The ConfigurationParent object passed into the constuctor of the
JettyWebApplicationContext  is not in a valid state to do anything with.

If you try calling any methods on it, including toString, it gives you a
    java.lang.IllegalStateException: Proxy is stopped
I'm not sure what state this is meant to be in???

More annoyingly, if you do not catch this exception then the kernel start
mechanism does not handle it well - it continues on an NPEs later:

         at org.apache.geronimo.gbean.jmx.GBeanMBeanReference.handleNotification(
         at mx4j.server.interceptor.NotificationListenerMBeanServerInterceptor$ListenerWrapper.handleNotification(
         at org.apache.geronimo.gbean.jmx.AbstractManagedObject.sendNotification(
         at org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(
         at org.apache.geronimo.gbean.jmx.AbstractManagedObject.start(
         at org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(
         at org.apache.geronimo.gbean.jmx.GBeanMBean$8.invoke(
         at org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(
         at org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(
         at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(
         at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(
         at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(
         at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(
         at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(
         at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(
         at mx4j.server.MX4JMBeanServer.invoke(

So I think something in   needs a better catch block.
I'm not familiar enough with this code yet to guess where this should be..


View raw message