[
https://issues.apache.org/jira/browse/GERONIMO-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538642
]
Anita Kulshreshtha commented on GERONIMO-3561:
----------------------------------------------
Viet and Erik,
Thanks for submitting numerous patches. I played around with the version of
the plugin in the sandbox and peeked at the code.
Here are my biggest concerns:
1. The EJBs (MasterRemoteControl) should not be managing any threads. The specs
do not allow this.
2. In a realistic environment the plugin (mrc-server) will NEVER be loaded in
the same jvm as the server being monitored. It
can reside on the same machine and act as a helper for the monitoring console
(aka client in the sandbox). Could you please
clarify where these components will be loaded and how they will authenticate
and work together?
> 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.
