[
https://issues.apache.org/jira/browse/GERONIMO-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538788
]
Viet Hung Nguyen commented on GERONIMO-3561:
--------------------------------------------
Anita, thanks for voicing your concerns. I was unaware that EJBs specs did not
allow for ejbs to manage threads. I am currently looking for alternative ways
to provide the same capabilities. One of which is the JMX Timer API (namely the
javax.management.timer package in J2SE). Let me know what you think or have
better solutions.
In response to your second concern, we are using a remote authentication
procedure provided by OpenEJB. The monitoring console (client) will have to
have the authentication information beforehand, so that it can authenticate
itself with the monitored server. We have tested this type of connection where
one machine connects to another to grab statistics.
Thanks,
Viet
> monitoring plugin: mrc-server needs to be a plugin in order to pull in a
> database
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-3561
> URL: https://issues.apache.org/jira/browse/GERONIMO-3561
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
> Affects Versions: 2.1
> Environment: windows
> Reporter: Viet Hung Nguyen
> Attachments: geronimo-3561.patch
>
>
> the mrc-server should be packaged in a CAR so that it can install on a
> minimal assembly. Also, as suggested by Paul Mcmahan and David Jencks, the
> datasources used should be a plugin itself so that we are not bound to just
> use the default derby DB.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
