You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2004/12/07 19:45:11 UTC

[jira] Created: (GERONIMO-522) Misleading GBean Startup Error Message

Misleading GBean Startup Error Message
--------------------------------------

         Key: GERONIMO-522
         URL: http://nagoya.apache.org/jira/browse/GERONIMO-522
     Project: Apache Geronimo
        Type: Bug
  Components: kernel  
    Versions: 1.0-M3    
    Reporter: Aaron Mulder
 Assigned to: Dain Sundstrom 


If a GBean fails to start, the error message generated is (for example):

org.apache.geronimo.kernel.config.InvalidConfigException: Invalid GBean configuration for geronimo.config:name="org/apache/geronimo/Server"
        at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:379)
        at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
Caused by: java.net.BindException: Address already in use
        at java.net.PlainSocketImpl.socketBind(Native Method)

The problem is, it's not usually an invalid GBean configuration (which says to me, a syntax error in a config file or the like).  The GBean configuration is fine, it's really a startup error.  The message would be better if it said "Unable to start GBean XYZ, see the 'Caused By:' message below"

This commonly happens for network services when the port is already in use as above (arguably a configuration problem, but the user has typically done no configuration at all when it happens, because they probably just started Geronimo for the first time).

It commonly happens for applications when there's some sort of classloader problem resulting in the wrong classes being loaded or a class not being found.  (For example, Struts/Spring/Hibernate type web apps have a lot of Jakarta Common dependencies, and Tomcat supplies some of those that Geronimo doesn't, so an app that worked in Tomcat may not work in Geronimo if all the commons stuff isn't in the WAR).


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (GERONIMO-522) Misleading GBean Startup Error Message

Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-522?page=all ]
     
Dain Sundstrom closed GERONIMO-522:
-----------------------------------

    Resolution: Cannot Reproduce

That error message is no longer present in the server.

> Misleading GBean Startup Error Message
> --------------------------------------
>
>          Key: GERONIMO-522
>          URL: http://issues.apache.org/jira/browse/GERONIMO-522
>      Project: Geronimo
>         Type: Bug
>   Components: kernel
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder
>     Assignee: Dain Sundstrom

>
> If a GBean fails to start, the error message generated is (for example):
> org.apache.geronimo.kernel.config.InvalidConfigException: Invalid GBean configuration for geronimo.config:name="org/apache/geronimo/Server"
>         at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:379)
>         at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
> Caused by: java.net.BindException: Address already in use
>         at java.net.PlainSocketImpl.socketBind(Native Method)
> The problem is, it's not usually an invalid GBean configuration (which says to me, a syntax error in a config file or the like).  The GBean configuration is fine, it's really a startup error.  The message would be better if it said "Unable to start GBean XYZ, see the 'Caused By:' message below"
> This commonly happens for network services when the port is already in use as above (arguably a configuration problem, but the user has typically done no configuration at all when it happens, because they probably just started Geronimo for the first time).
> It commonly happens for applications when there's some sort of classloader problem resulting in the wrong classes being loaded or a class not being found.  (For example, Struts/Spring/Hibernate type web apps have a lot of Jakarta Common dependencies, and Tomcat supplies some of those that Geronimo doesn't, so an app that worked in Tomcat may not work in Geronimo if all the commons stuff isn't in the WAR).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira