geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-962) App client does not have a J2EEServer gbean, which causes some other jsr-77 beans not to start
Date Sat, 10 Dec 2005 02:31:09 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-962?page=all ]

Dain Sundstrom updated GERONIMO-962:
------------------------------------

    Fix Version: 1.1
                     (was: 1.0)

> App client does not have a J2EEServer gbean, which causes some other jsr-77 beans not
to start
> ----------------------------------------------------------------------------------------------
>
>          Key: GERONIMO-962
>          URL: http://issues.apache.org/jira/browse/GERONIMO-962
>      Project: Geronimo
>         Type: Bug
>   Components: application client
>     Versions: 1.0-M5
>     Reporter: David Jencks
>      Fix For: 1.1

>
> The app client does not have a jsr-77 gbean for J2EEServer.  However, if you deploy a
connector on the app client, it's ResourceAdapterModule jsr-77 gbean will have a reference
to a client-side J2EEServer gbean, so it won't start.  This doesn't seem to have any dreadful
consequences, although you should get a notice in the app client shutdown like:
> 23:03:11,428 ERROR [GBeanInstance] GBeanInstance should already be stopped before die()
is called: objectName=geronimo.client:JCAResource=tranql/rars/tranql-connector-1.0-20050716.rar,name=MySQL,J2EEServer=client,J2EEApplication=client-application,j2eeType=JCAConnectionFactory
state=starting
> When starting up, you will see something like:
> 23:03:05,670 DEBUG [GBeanSingleReference] Waiting to start geronimo.client:name=tranql/rars/tranql-connector-1.0-20050716.rar,J2EEServer=client,J2EEApplication=client-application,j2eeType=ResourceAdapterModule
because no targets are running for reference J2EEServer matching the patternspatterns geronimo.client:j2eeType=J2EEServer,name=client
> We should fix this by either removing the reference to the J2EEServer gbean, removing
the ResourceAdapterModuleGBean (I don't think this is practical since it has useful info in
it) or adding a client side J2EEServer gbean.
> The same problem applies to the JCAConnectionManager gbean, although no complaint appears
in the log.

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