[jira] Commented: (GERONIMO-3561) monitoring plugin: mrc-server needs to be a plugin in order to pull in a database
[ https://issues.apache.org/jira/browse/GERONIMO-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538956 ] Viet Hung Nguyen commented on GERONIMO-3561: by making mrc-server a plugin, it can pull openejb onto the minimal server, likewise MEJB and the derby database. Your third point is a good one. Right now, it is hardcoded in the client to connect to port 4201. Maybe we should allow this option to be configurable. I never thought about the server having more than one geronimo instance running on it. Thanks for pointing that out. > 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.
[jira] Commented: (GERONIMO-3561) monitoring plugin: mrc-server needs to be a plugin in order to pull in a database
[ https://issues.apache.org/jira/browse/GERONIMO-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538944 ] Anita Kulshreshtha commented on GERONIMO-3561: -- - You could use EJB timer service. - Since mrc-server is as EJB app, it can not be installed on the minimal server. - Yes, The monitoring console(client) will know how to connect to mrc-server. My question is how do you tell the mrc-server which geronimo instance (OpenEJB Port) it is supposed to monitor. - I have applied GERONIMO-3561 and GERONIMO-3564 patches in rev. 590502. > 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.
[jira] Commented: (GERONIMO-3561) monitoring plugin: mrc-server needs to be a plugin in order to pull in a database
[ 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.
[jira] Commented: (GERONIMO-3561) monitoring plugin: mrc-server needs to be a plugin in order to pull in a database
[ 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.
