geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-727) Problem determining attribute type in GBeanInstance.getAttribute
Date Thu, 21 Jul 2005 03:40:46 GMT
     [ ]
Aaron Mulder resolved GERONIMO-727:

    Fix Version: 1.0-M5
     Resolution: Fixed
      Assign To: Aaron Mulder

Same behavior, but better message.

> Problem determining attribute type in GBeanInstance.getAttribute
> ----------------------------------------------------------------
>          Key: GERONIMO-727
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: kernel
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>      Fix For: 1.0-M5

> If the Jetty port is taken (by a separate Tomcat instance) there is a series of exceptions
generated during startup.  Some of these are:
> Address already in use
> Exception occured while attempting to fully start: objectName=geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/
> Server,J2EEServer=geronimo,j2eeType=GBean,name=JettyWebConnector
> java.lang.IllegalStateException: Cannot transition to running state from failed
> java.lang.IllegalStateException: Attribute is not persistent Attribute Name: address,
Type: class, GBeanInstance: Jetty Connector HTTP
>         at org.apache.geronimo.gbean.runtime.GBeanAttribute.getPersistentValue(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.getAttribute(
>         at org.apache.geronimo.kernel.basic.BasicKernel.getAttribute(
>         at org.apache.geronimo.system.main.ProgressBarStartupMonitor.wrapUp(
> The last one is the one that concerns me here.  The attribute in question is JettyConnector.getAddress,
which is clearly not persistent (there's no setter, and the declaration in the GBeanInfo says
it's not persistent).  However, the logic in GBeanInstance.getAttribute:627 seems to conclude
that an attribute is persistent based on the state of the GBean not based on the characteristics
of the attribute itself -- I'm not sure what's going on here.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message