Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
(not version related)
-
None
-
None
Description
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!