geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1589) Deploy CORBA EJB with TSS; config with CORBA Server is not started but no error message
Date Mon, 06 Feb 2006 05:01:03 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1589?page=comments#action_12365239 ] 

Aaron Mulder commented on GERONIMO-1589:
----------------------------------------

To add insult to injury, errors are produced when the application is shut down:

GBeanInstance should already be stopped before die() is called:...

I got about 8 of these indicating that various servlets and things failed to start (presumably
on account of the session bean not starting), so the application was in fact totally crippled.

> Deploy CORBA EJB with TSS; config with CORBA Server is not started but no error message
> ---------------------------------------------------------------------------------------
>
>          Key: GERONIMO-1589
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1589
>      Project: Geronimo
>         Type: Bug
>   Components: OpenEJB, CORBA, kernel
>     Versions: 1.0
>     Reporter: Aaron Mulder
>      Fix For: 1.1

>
> The j2ee-corba configuration defines the CORBA "Server".
> I added a TSS to an EJB JAR, and the TSS has a reference to the Server running in the
j2ee-corba configuration.
> The deployment completed successfully, yet the j2ee-corba configuration was still not
running.  What happened here?  From the log, it looks like the TSSBean failed to start waiting
on the Server, and the SessionBean failed to start waiting on the TSSBean.  This should have
resulted in some kind of message during dpeloyment, if not outright failing the deployment.
 Or better yet, it should have just started the j2ee-corba configuration.
> This would be cured by setting j2ee-corba as a parent or import for the EJB JAR, but
I forgot, and it still should have produced a warning or error message as is!

-- 
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


Mime
View raw message