[jira] Commented: (GERONIMO-3697) Monitoring Console fix ups
[ https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572456#action_12572456 ] Anita Kulshreshtha commented on GERONIMO-3697: -- This completes the MEJB version of Monitoring Console. Issues related to JMX version of Monitoring Console should be handled in a new issue. Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3697) Monitoring Console fix ups
[ https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3697. Resolution: Fixed Fix Version/s: 2.1 Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3530) provide activemq destination and connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572455#action_12572455 ] Anita Kulshreshtha commented on GERONIMO-3530: -- IMO, we need to implement the Stats defined by the specs ( JSR77.24 through JSR77.29). This patch does not implement them. provide activemq destination and connector stats Key: GERONIMO-3530 URL: https://issues.apache.org/jira/browse/GERONIMO-3530 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: linux, windows Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Fix For: 2.2 Attachments: geronimo-3530.patch there are some stats that can easily be surfaced with how we use AMQ in our source. These are JSR 77 compliant statistics that are being provided by AMQ (DestinationStatistics and ConnectorStatistics). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1293) Provide tomcat statistics
[ https://issues.apache.org/jira/browse/GERONIMO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-1293. The ServletStats(JSR77) can easily be added when we incorporate 'Servlet' J2EEManagedObject. Alternately a user can get raw servlet statistics from mbeanserver. Provide tomcat statistics - Key: GERONIMO-1293 URL: https://issues.apache.org/jira/browse/GERONIMO-1293 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Tomcat Affects Versions: 1.0-M5 Environment: All environments Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Minor Fix For: 2.0, 2.1 Attachments: geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.1-SNAPSHOT.war, geronimo-stats-2.0-SNAPSHOT.war, management.patch, management.patch, management.patch, project.patch, properties.patch, properties.patch, stats.zip, stats.zip, stats.zip, statsApp.zip, tomcat-builder.patch, tomcat.patch, tomcat.patch, tomcat.patch, tomcat.patch, TomcatWebAppContext.patch Provide following statistics for tomcat : 1. Per Host/Container - a. Initially provide the following per connector statistics for each connector - Cummulative statistics about all request handled by this connector since the stat were turned on. b. If time (before 1.0 release) permits, use 'a' to generate (rename/compute) statistics similar to the ones provided by Jetty 2. Per application - a.. processingTime : The cumulative processing times of all servlets in this StandardContext b. startTime - The time this context was started. c. startupTime - The time (in milliseconds) it took to start this context. d.. tldScanTime() - Later add session statistics and jsp statistics. 3. Per Servlet - Explore using statistics from RequestInfo to provide statistics for a servlet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3755) application-1.2 schema does not exist
[ https://issues.apache.org/jira/browse/GERONIMO-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559972#action_12559972 ] Anita Kulshreshtha commented on GERONIMO-3755: -- The schemas for geronimo 2.0+ are described here: http://geronimo.apache.org/apache-geronimo-v20-xml-schemas.html i.e. you need http://geronimo.apache.org/xml/ns/j2ee/application-2.0. Please feel free to update the information in the samples :) application-1.2 schema does not exist - Key: GERONIMO-3755 URL: https://issues.apache.org/jira/browse/GERONIMO-3755 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2 Environment: Mac OS X Tiger, Java 1.5 Reporter: Aurimas Valionis Priority: Blocker I want to create a plan for ear application and I follow the samples, there should be application-1.2 schema available on http://geronimo.apache.org/xml/ns/j2ee/application-1.2; but it is not there. Would you upload the schema? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-1775) Internationalization of the Admin Console
[
https://issues.apache.org/jira/browse/GERONIMO-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559487#action_12559487
]
Anita Kulshreshtha commented on GERONIMO-1775:
--
could you have used the i18N facilities defined by PLT.6.2 Portlet Resource
Bundle and PLT.21.10 Resource Bundles in the JSR 168 Specification?
e.g. somehing like this in portlet.xml:
{code:xml}
portlet
...
portlet-info
titleStock Quote Portlet/title
short-titleStock/short-title
keywordsfinance,stock market/keywords
resource-bundlecom.foo.myApp.QuotePortlet/resource-bundle
/portlet-info
...
/portlet
{code}
Internationalization of the Admin Console
-
Key: GERONIMO-1775
URL: https://issues.apache.org/jira/browse/GERONIMO-1775
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Reporter: Yeray Cabrera Santana
Assignee: Donald Woods
Priority: Minor
Fix For: 2.1
Attachments: chinese_console.JPG, GERONIMO-1775-1.patch,
GERONIMO-1775-2.patch, GERONIMO-1775.patch, screen1.GIF
Provide the internationalization of the administration console so it can be
translated to different languages. This is a feature I would like to
contribute with.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-1775) Internationalization of the Admin Console
[
https://issues.apache.org/jira/browse/GERONIMO-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559487#action_12559487
]
akulshre edited comment on GERONIMO-1775 at 1/16/08 6:02 AM:
---
could you have used the i18N facilities defined by PLT.6.2 Portlet Resource
Bundle and PLT.21.10 Resource Bundles in the JSR 168 Specification?
e.g. somehing like the following in portlet.xml and use standard keywords
javax.portlet.title, javax.portlet.short-title, and
javax.portlet.keywords.
{code:xml}
portlet
...
supported-localezh/supported-locale
resource-bundlecom.foo.myApp.QuotePortlet/resource-bundle
portlet-info
titleStock Quote Portlet/title
short-titleStock/short-title
keywordsfinance,stock market/keywords
/portlet-info
...
/portlet
{code}
was (Author: akulshre):
could you have used the i18N facilities defined by PLT.6.2 Portlet
Resource Bundle and PLT.21.10 Resource Bundles in the JSR 168 Specification?
e.g. somehing like this in portlet.xml:
{code:xml}
portlet
...
portlet-info
titleStock Quote Portlet/title
short-titleStock/short-title
keywordsfinance,stock market/keywords
resource-bundlecom.foo.myApp.QuotePortlet/resource-bundle
/portlet-info
...
/portlet
{code}
Internationalization of the Admin Console
-
Key: GERONIMO-1775
URL: https://issues.apache.org/jira/browse/GERONIMO-1775
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Reporter: Yeray Cabrera Santana
Assignee: Donald Woods
Priority: Minor
Fix For: 2.1
Attachments: chinese_console.JPG, GERONIMO-1775-1.patch,
GERONIMO-1775-2.patch, GERONIMO-1775.patch, screen1.GIF
Provide the internationalization of the administration console so it can be
translated to different languages. This is a feature I would like to
contribute with.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3645) Monitoring plugins build fails
[ https://issues.apache.org/jira/browse/GERONIMO-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3645. Resolution: Fixed Fix Version/s: 2.1 Monitoring plugins build fails -- Key: GERONIMO-3645 URL: https://issues.apache.org/jira/browse/GERONIMO-3645 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Anita Kulshreshtha Fix For: 2.1 Monitoring plugins build fails when there is a clean (empty) local maven repository due to lack of the artifacts org.apache.geronimo.modules:modules and org.apache.geronimo.configs:configs Need to sift through poms and clean up to prevent this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3712) Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats
[ https://issues.apache.org/jira/browse/GERONIMO-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3712. Resolution: Fixed Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats --- Key: GERONIMO-3712 URL: https://issues.apache.org/jira/browse/GERONIMO-3712 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, Jetty, management Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 Jetty WebConnector has a ConnectionsCount statistics which should be included in TimeStatistics named ConnectionsDuration. JettyWebContainer has a RequestCount statistics which should be included in TimeStatistics named RequestDuration. Currently the average value is stored in TimeStatistics.count. which is incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3441) Server monitoring and management
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3441. Resolution: Fixed Fix Version/s: 2.1 rev. 580468 - Initial check in to sandbox Server monitoring and management Key: GERONIMO-3441 URL: https://issues.apache.org/jira/browse/GERONIMO-3441 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: general Affects Versions: 2.1 Environment: All Reporter: Erik B. Craig Assignee: Anita Kulshreshtha Fix For: 2.1 Attachments: mrc-client.zip, mrc-server.zip, mrc.zip, screenshot1.jpg, screenshot2.jpg, stats.patch Currently, there is not a good way of surfacing Geronimo's server information so that an administrator can monitor the server's status. The architecture of using MBeans is established, but not fully exploited. This enhancement will take advantage of what Geronimo currently offers and extend it so that a server can tap into a cluster of servers and extract information from specific Geronimo servers or even aggregates of Geronimo servers. The goal is to have one machine be able to reach out to all Geronimo servers in order to fetch data or even alter their state. This will be especially useful in the case of someone having to monitor a large number of Geronimo servers. Viet Nguyen and myself have completed a bit of framework towards this goal, to be attached to this jira In-depth information can be found in the confluence wiki here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3702) monitoring client to display a graph when the graph name is clicked on
[ https://issues.apache.org/jira/browse/GERONIMO-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553358 ] Anita Kulshreshtha commented on GERONIMO-3702: -- The graph names displayed on 'Edit view' page are all same! It displays view name not graph name! The link works and displays the correct graph. This used to work before this change. monitoring client to display a graph when the graph name is clicked on -- Key: GERONIMO-3702 URL: https://issues.apache.org/jira/browse/GERONIMO-3702 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3702.patch the monitoring client has graph names displayed as links so that the user can click on it to display the single graph, instead of having to add it to a view to look at the graph. this should be implemented to open up a new window with that graph. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3712) Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats
Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats --- Key: GERONIMO-3712 URL: https://issues.apache.org/jira/browse/GERONIMO-3712 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: management Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 Jetty WebConnector has a ConnectionsCount statistics which should be included in TimeStatistics named ConnectionsDuration. JettyWebContainer has a RequestCount statistics which should be included in TimeStatistics named RequestDuration. Currently the average value is stored in TimeStatistics.count. which is incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3712) Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats
[ https://issues.apache.org/jira/browse/GERONIMO-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3712: - Component/s: Jetty console Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats --- Key: GERONIMO-3712 URL: https://issues.apache.org/jira/browse/GERONIMO-3712 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, Jetty, management Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 Jetty WebConnector has a ConnectionsCount statistics which should be included in TimeStatistics named ConnectionsDuration. JettyWebContainer has a RequestCount statistics which should be included in TimeStatistics named RequestDuration. Currently the average value is stored in TimeStatistics.count. which is incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3712) Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats
[ https://issues.apache.org/jira/browse/GERONIMO-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553218 ] Anita Kulshreshtha commented on GERONIMO-3712: -- Committed in rev. 605403 Remove redundent statisitcs from JettyConnectorStats and JettyWebConnectorStats --- Key: GERONIMO-3712 URL: https://issues.apache.org/jira/browse/GERONIMO-3712 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, Jetty, management Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 Jetty WebConnector has a ConnectionsCount statistics which should be included in TimeStatistics named ConnectionsDuration. JettyWebContainer has a RequestCount statistics which should be included in TimeStatistics named RequestDuration. Currently the average value is stored in TimeStatistics.count. which is incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3645) Monitoring plugins build fails
[ https://issues.apache.org/jira/browse/GERONIMO-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha reassigned GERONIMO-3645: Assignee: Anita Kulshreshtha (was: Erik B. Craig) - Fixed the build, see GERONIMO-3697 - Rev 605407 : moved to server/trunk/applications. Monitoring plugins build fails -- Key: GERONIMO-3645 URL: https://issues.apache.org/jira/browse/GERONIMO-3645 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Anita Kulshreshtha Monitoring plugins build fails when there is a clean (empty) local maven repository due to lack of the artifacts org.apache.geronimo.modules:modules and org.apache.geronimo.configs:configs Need to sift through poms and clean up to prevent this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3697) Monitoring Console fix ups
[ https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553235 ] Anita Kulshreshtha commented on GERONIMO-3697: -- Committed Rev 603737, 604183, 604186, 604644, 605063, 605082, 605406, 605407, and 605412 - Removed unnecessary dependencies from poms, Fix poms, - Removed unnecessary jars from wars. TODO - Remove the remaining 2 jars. Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3678) Monitoring console should accept a port no for server to be monitored
[ https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552454 ] Anita Kulshreshtha commented on GERONIMO-3678: -- It would be nice to have all server addresses displayed as IPaddr:portno in all the portlets. Monitoring console should accept a port no for server to be monitored - Key: GERONIMO-3678 URL: https://issues.apache.org/jira/browse/GERONIMO-3678 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3678.patch Currently the Monitoring Console accepts an IP address for the server to be monitored. This works for default geronimo instances. For non default installations we need to be able to specify the EJB port.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3697) Monitoring Console fix ups
[ https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550973 ] Anita Kulshreshtha commented on GERONIMO-3697: -- *rev 603613:* - Fix the tag used for generating names for TimeStatistics. The value returned is total count not current time. - Turn of annoying 'could not turn Stats on for .' message. Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3697) Monitoring Console fix ups
[ https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550973 ] akulshre edited comment on GERONIMO-3697 at 12/12/07 6:19 AM: *rev 603613:* - Fix the tag used for generating names for TimeStatistics. The value returned is total count not current time. - Turn off annoying 'could not turn Stats on for .' message. was (Author: akulshre): *rev 603613:* - Fix the tag used for generating names for TimeStatistics. The value returned is total count not current time. - Turn of annoying 'could not turn Stats on for .' message. Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3693) monitoring client does not perform operations correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550983 ] Anita Kulshreshtha commented on GERONIMO-3693: -- Viet, Is it possible to use the min/max values given by TimeStatistics or Rangestatistics instead of computing it 'over the observed period'? The value returned is maximum since the measurement started which is not same as the max value during graphing period. monitoring client does not perform operations correctly --- Key: GERONIMO-3693 URL: https://issues.apache.org/jira/browse/GERONIMO-3693 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3693.patch Currently the second operand value is not being pulled from the mrc-server, instead there the second operand value is being assigned the first operand value. Additionally, the javascript that is generated from StatsGraph.java does not check to see if there is a division by zero. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3693) monitoring client does not perform operations correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551000 ] Anita Kulshreshtha commented on GERONIMO-3693: -- - Correct! There is no need to plot min and max value graphs separately. For example it does not make sense to plot graph for HeapSizeMax with min, max and avg! It would be nice if these values (min, max) could be used to plot say JVMHeapCurrent graph. - The TimeStatistics is a bit tricky. The min, max values are for totaltime/count. And it should be possible to draw 'count' graph and 'total time' graph separately. IIRC Erik said that Dojo 1.0.1 does not allow us to plot min, max, avg in the graph. If we switch to 1.0.1 we will need to redo this part monitoring client does not perform operations correctly --- Key: GERONIMO-3693 URL: https://issues.apache.org/jira/browse/GERONIMO-3693 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3693.patch Currently the second operand value is not being pulled from the mrc-server, instead there the second operand value is being assigned the first operand value. Additionally, the javascript that is generated from StatsGraph.java does not check to see if there is a division by zero. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3697) Monitoring Console fix ups
Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3678) Monitoring console should accept a port no for server to be monitored
[ https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550439 ] Anita Kulshreshtha commented on GERONIMO-3678: -- Rev 603235, Removed SQL to populate DB with the default data. Monitoring console should accept a port no for server to be monitored - Key: GERONIMO-3678 URL: https://issues.apache.org/jira/browse/GERONIMO-3678 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3678.patch Currently the Monitoring Console accepts an IP address for the server to be monitored. This works for default geronimo instances. For non default installations we need to be able to specify the EJB port.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3678) Monitoring console should accept a port no for server to be monitored
[ https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550278 ] Anita Kulshreshtha commented on GERONIMO-3678: -- This patch does not work. There is SQL error in 'insert into servers... at line 165 in o.a.g.plugin.monitoring.util.DBManager. The no. of columns do not match the no. of values supplied in the insert statement. Monitoring console should accept a port no for server to be monitored - Key: GERONIMO-3678 URL: https://issues.apache.org/jira/browse/GERONIMO-3678 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3678.patch Currently the Monitoring Console accepts an IP address for the server to be monitored. This works for default geronimo instances. For non default installations we need to be able to specify the EJB port.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549845 ] Anita Kulshreshtha commented on GERONIMO-3685: -- Could you please explain what I should do to draw a graph for 'time taken to process a single request' aka request time and does it work? I am editing TomcatWebRequestTimeSecond60Min graph. Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly - Key: GERONIMO-3685 URL: https://issues.apache.org/jira/browse/GERONIMO-3685 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Environment: All Reporter: Anita Kulshreshtha Priority: Critical Fix For: 2.1 . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'totalTime/count' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly
Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly - Key: GERONIMO-3685 URL: https://issues.apache.org/jira/browse/GERONIMO-3685 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Environment: All Reporter: Anita Kulshreshtha Priority: Critical Fix For: 2.1 . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'count/totalTime' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3685: - Description: . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'totalTime/count' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. was: . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'count/totalTime' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly - Key: GERONIMO-3685 URL: https://issues.apache.org/jira/browse/GERONIMO-3685 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Environment: All Reporter: Anita Kulshreshtha Priority: Critical Fix For: 2.1 . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'totalTime/count' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3679) Montitoring console should display 'available statistics' in a more organized way
Montitoring console should display 'available statistics' in a more organized way - Key: GERONIMO-3679 URL: https://issues.apache.org/jira/browse/GERONIMO-3679 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Currently the Monitoring Console shows all statistics in a list. It is very hard to make out what they are for. We need to categorize them according to their J2EETypes, e.g. for J2EEType=WebModule, we should list them under Web Applications. The non standard J2EEtype, e.g WebConnectors should go under a separate category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3680) The Monitoring agent should optimize DB activity
The Monitoring agent should optimize DB activity Key: GERONIMO-3680 URL: https://issues.apache.org/jira/browse/GERONIMO-3680 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Currently the agent needs to be loaded in the same JVM as the server being monitored. The agent skews the statistics being monitered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3680) The Monitoring agent should optimize DB activity
[ https://issues.apache.org/jira/browse/GERONIMO-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3680: - Attachment: view4.jpg This graph was drawn with Monitoring console running locally with portoffset=10. The agent was running in the default instance. The commiitted transaction graph shows Tx committed every interval (5 minutes). There was no other application running on G. The Monitoring agent should optimize DB activity Key: GERONIMO-3680 URL: https://issues.apache.org/jira/browse/GERONIMO-3680 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Attachments: view4.jpg Currently the agent needs to be loaded in the same JVM as the server being monitored. The agent skews the statistics being monitered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3681) The Monitoring Console should allow the type of graph to be chosen
[ https://issues.apache.org/jira/browse/GERONIMO-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3681: - Summary: The Monitoring Console should allow the type of graph to be chosen (was: The Monitoring Console should all the type of graph to be chosen) The Monitoring Console should allow the type of graph to be chosen -- Key: GERONIMO-3681 URL: https://issues.apache.org/jira/browse/GERONIMO-3681 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha The CountStatistics can be displayed in 2 ways, the raw count and the throughput/utilization (count/sec). For raw count like ErrorCount a bar graph is more appropriate. The curvedArea is good for throughput. The user should be able to choose which graph style (bar, curvedArea, etc) to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3682) The Monitoring Console should keep information about Stats available from a managed object
The Monitoring Console should keep information about Stats available from a managed object -- Key: GERONIMO-3682 URL: https://issues.apache.org/jira/browse/GERONIMO-3682 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha The monitoring console should do a getStats on each of the available StatisticsProvider (without the query being enabled). It should use this information to build a DB about the nature of the statistics. This information should be used to fill in the default values in 'add a graph page'. Currently the description, x label, y label show as empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3681) The Monitoring Console should all the type of graph to be chosen
The Monitoring Console should all the type of graph to be chosen Key: GERONIMO-3681 URL: https://issues.apache.org/jira/browse/GERONIMO-3681 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha The CountStatistics can be displayed in 2 ways, the raw count and the throughput/utilization (count/sec). For raw count like ErrorCount a bar graph is more appropriate. The curvedArea is good for throughput. The user should be able to choose which graph style (bar, curvedArea, etc) to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3645) Monitoring plugins build fails
[ https://issues.apache.org/jira/browse/GERONIMO-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548260 ] Anita Kulshreshtha commented on GERONIMO-3645: -- You could try removing all unnecessary dependencies from all the poms and use 'provided' scope for the ones available from the server. Monitoring plugins build fails -- Key: GERONIMO-3645 URL: https://issues.apache.org/jira/browse/GERONIMO-3645 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Monitoring plugins build fails when there is a clean (empty) local maven repository due to lack of the artifacts org.apache.geronimo.modules:modules and org.apache.geronimo.configs:configs Need to sift through poms and clean up to prevent this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3662) Provide JCA Resource statistics
Provide JCA Resource statistics --- Key: GERONIMO-3662 URL: https://issues.apache.org/jira/browse/GERONIMO-3662 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: connector Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Provide JCAResource statistics defined by JCAStats JRR77.6.18 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3664) JNDIView Portlet should list ResourceAdaptors and its JCAManagedConnectionFactories for RAR Modules
JNDIView Portlet should list ResourceAdaptors and its JCAManagedConnectionFactories for RAR Modules --- Key: GERONIMO-3664 URL: https://issues.apache.org/jira/browse/GERONIMO-3664 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha JNDI portlet should display at least the following information for RARs: ResourceAdapterModule- ResourceAdapters- JCAResources- JCAConnectoinFactories- names e.g.the system-database.../car will have two entries - NoTxDatasource and SystemDatasource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3608) Move Jetty*Stats and Jetty*StatsImpl to geronimo-management
[ https://issues.apache.org/jira/browse/GERONIMO-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3608. Resolution: Fixed Fix Version/s: 2.1 Move Jetty*Stats and Jetty*StatsImpl to geronimo-management Key: GERONIMO-3608 URL: https://issues.apache.org/jira/browse/GERONIMO-3608 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty, management Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Fix For: 2.1 Move Jetty*Stats and Jetty*StatsImpl to geronimo-management . The relevant discussion can be found at - http://www.nabble.com/Re%3A-Can-we-deal-generically-with-container-specific-jsr77-statistics--p13688310s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3608) Move Jetty*Stats and Jetty*StatsImpl to geronimo-management
Move Jetty*Stats and Jetty*StatsImpl to geronimo-management Key: GERONIMO-3608 URL: https://issues.apache.org/jira/browse/GERONIMO-3608 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Jetty, management Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Move Jetty*Stats and Jetty*StatsImpl to geronimo-management . The relevant discussion can be found at - http://www.nabble.com/Re%3A-Can-we-deal-generically-with-container-specific-jsr77-statistics--p13688310s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3608) Move Jetty*Stats and Jetty*StatsImpl to geronimo-management
[ https://issues.apache.org/jira/browse/GERONIMO-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543754 ] Anita Kulshreshtha commented on GERONIMO-3608: -- committed in rev. 596514, also fixed statistics names in WebContainerStatsImpl to comply with JSR77.6.10.1.1 Move Jetty*Stats and Jetty*StatsImpl to geronimo-management Key: GERONIMO-3608 URL: https://issues.apache.org/jira/browse/GERONIMO-3608 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty, management Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Move Jetty*Stats and Jetty*StatsImpl to geronimo-management . The relevant discussion can be found at - http://www.nabble.com/Re%3A-Can-we-deal-generically-with-container-specific-jsr77-statistics--p13688310s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2898) Can't edit Jetty SSL Connector in Geronimo console
[ https://issues.apache.org/jira/browse/GERONIMO-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-2898. Can't edit Jetty SSL Connector in Geronimo console -- Key: GERONIMO-2898 URL: https://issues.apache.org/jira/browse/GERONIMO-2898 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.0-M2 Environment: Linux Reporter: Karthiga Rajeevani Ratnam Assignee: Anita Kulshreshtha Fix For: 2.0-M5 Attachments: 2898-new.patch, 2898.patch, JettySSLConnector Error.jpg I tried to edit JettySSLConnector listed under Network Listeners and got the following error in command prompt. 15:06:50,729 ERROR [PortletFragment] Error in Portlet java.lang.IllegalArgumentException: No such method found (getMinThreads on org.apache.geronimo.jetty6.JettyWebConnector$$EnhancerByCGLIB$$5aaaf276) at org.apache.geronimo.console.BasePortlet.getProperty(BasePortlet.java:92) at org.apache.geronimo.console.webmanager.ConnectorPortlet.doView(ConnectorPortlet.java:388) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:133) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:67) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:192) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:133) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:67) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:192) at
[jira] Closed: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3490. Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Fix For: 2.1 Attachments: geronimo-3490.patch, geronimo-3490b.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3587) Move TomcatWebConnector stats objects from under o/a/g/management to o/a/g/tomcat/stats
[ https://issues.apache.org/jira/browse/GERONIMO-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540740 ] Anita Kulshreshtha commented on GERONIMO-3587: -- Joe, Please see https://issues.apache.org/jira/browse/GERONIMO-3586#action_12540569. Move TomcatWebConnector stats objects from under o/a/g/management to o/a/g/tomcat/stats --- Key: GERONIMO-3587 URL: https://issues.apache.org/jira/browse/GERONIMO-3587 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: management, Tomcat Affects Versions: 2.1 Reporter: Joe Bohn Priority: Minor There are currently Tomcat specific implementations under o/a/g/management. These should be included under tomcat. We're trying to get things more modular so that tomcat specific elements are only included if tomcat itself is installed. Likewise for Jetty. Having these elements under management pulls Tomcat specific items into the image when Tomcat itself is not included. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3586) monitoring plugin: collecting agent should have separate jetty and tomcat plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540811 ] Anita Kulshreshtha commented on GERONIMO-3586: -- For the instance of Tomcat, it works fine because mrc-server depends on MEJB which depends on G-management, which is where the Tomcat stuff is located. However, since Jetty is still in G-jetty6 and nothing depends on it, it fails to be visible by the mrc-server. This is a perfect example of why the Jetty*Stats and Jetty*StatsImpl classes should be in g-management and not in g-jetty6. Otherwise we will need two versions of Monitoring console (client, mrc-server,..). Though you could use JSR77 to get all the info you need from any StatsImpl, e.g. if a StatsImpl (could be a Jetty*StatsImpl) has a statistic named XYX, it will have a method named getXYZ. Using this you could get all Statistics in the StatsImpl. The mrc-server also consumes too many resources, in its current form it can not be loaded in the same JVM as the server to be monitored. monitoring plugin: collecting agent should have separate jetty and tomcat plugins - Key: GERONIMO-3586 URL: https://issues.apache.org/jira/browse/GERONIMO-3586 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Attachments: geronimo-3586.patch The collecting agent plugin needs to have separate jetty and tomcat plugins in order to accommodate for the differences in container specific dependencies on stats implementation (.e.g JettyContainerStatsImpl and JettyConnectorStatsImpl). When the collecting agent was an EAR, this was not a problem; however, as a plugin, it is more tied down to having to specify all dependencies in the plugin's classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3586) monitoring plugin: collecting agent should have separate jetty and tomcat plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540787 ] Anita Kulshreshtha commented on GERONIMO-3586: -- The code in the sandbox is still a work in progress. In a realistic situation the monitoring console (aka client in sandbox) will NEVER be loaded in the same server (JVM) as the server it is supposed to monitor. As for the monitoring plugin, the mrc-server should not need any container specific class. That is the spirit of JSR77. May I ask where these classes are needed? monitoring plugin: collecting agent should have separate jetty and tomcat plugins - Key: GERONIMO-3586 URL: https://issues.apache.org/jira/browse/GERONIMO-3586 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Attachments: geronimo-3586.patch The collecting agent plugin needs to have separate jetty and tomcat plugins in order to accommodate for the differences in container specific dependencies on stats implementation (.e.g JettyContainerStatsImpl and JettyConnectorStatsImpl). When the collecting agent was an EAR, this was not a problem; however, as a plugin, it is more tied down to having to specify all dependencies in the plugin's classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3586) monitoring plugin: collecting agent should have separate jetty and tomcat plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540957 ] Anita Kulshreshtha commented on GERONIMO-3586: -- Prasad, The (tomcat) Stats and StatsImpl in question are _management_ interfaces. There is NO CONTAINER SPECIFIC code in them. They do not need container code to compile. These are no different than EJBStats, JTAStats or many other Stats in g-management package. The same should be true for Jetty. This is why I propose that we move the Jetty*Stats* to g-managemnt. Joe, We need to distinguish between the server the tool is running on and the server that is being monitored. Yes we can have two versions of the tool (just like console). But that does not mean that a tool running on tomcat can not monitor a server instance running on Jetty. An important difference between admin console and monitoring console is that admin console administers the server it resides on, but a realistic monitoring console NEVER monitors the server it resides in. I hope this is helpful. monitoring plugin: collecting agent should have separate jetty and tomcat plugins - Key: GERONIMO-3586 URL: https://issues.apache.org/jira/browse/GERONIMO-3586 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Attachments: geronimo-3586.patch The collecting agent plugin needs to have separate jetty and tomcat plugins in order to accommodate for the differences in container specific dependencies on stats implementation (.e.g JettyContainerStatsImpl and JettyConnectorStatsImpl). When the collecting agent was an EAR, this was not a problem; however, as a plugin, it is more tied down to having to specify all dependencies in the plugin's classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3586) monitoring plugin: collecting agent should have separate jetty and tomcat plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540545 ] Anita Kulshreshtha commented on GERONIMO-3586: -- Viet, The mrc-server code should not need to refer to any specific stats or statsImpl. Could you please elaborate why you need to know about them? However we do need to move the Jetty*Stats and Jetty*StatsImpl to geronimo-management (o.a.g.management.geronimo.stats) module. monitoring plugin: collecting agent should have separate jetty and tomcat plugins - Key: GERONIMO-3586 URL: https://issues.apache.org/jira/browse/GERONIMO-3586 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Attachments: geronimo-3586.patch The collecting agent plugin needs to have separate jetty and tomcat plugins in order to accommodate for the differences in container specific dependencies on stats implementation (.e.g JettyContainerStatsImpl and JettyConnectorStatsImpl). When the collecting agent was an EAR, this was not a problem; however, as a plugin, it is more tied down to having to specify all dependencies in the plugin's classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3587) Move TomcatWebConnector stats objects from under o/a/g/management to o/a/g/tomcat/stats
[ https://issues.apache.org/jira/browse/GERONIMO-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540550 ] Anita Kulshreshtha commented on GERONIMO-3587: -- I strongly disagree with this. These stats DO NOT pull anything specific to tomcat in a Jetty image. Move TomcatWebConnector stats objects from under o/a/g/management to o/a/g/tomcat/stats --- Key: GERONIMO-3587 URL: https://issues.apache.org/jira/browse/GERONIMO-3587 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: management, Tomcat Affects Versions: 2.1 Reporter: Joe Bohn Priority: Minor There are currently Tomcat specific implementations under o/a/g/management. These should be included under tomcat. We're trying to get things more modular so that tomcat specific elements are only included if tomcat itself is installed. Likewise for Jetty. Having these elements under management pulls Tomcat specific items into the image when Tomcat itself is not included. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3586) monitoring plugin: collecting agent should have separate jetty and tomcat plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540569 ] Anita Kulshreshtha commented on GERONIMO-3586: -- Joe, Please see my comment https://issues.apache.org/jira/browse/GERONIMO-3587#action_12540550. These are management interfaces . Although they do know about the specifics of the containers, they do not need the container itself. A monitoring console will use this information to monitor any g instance i.e. jetty or tomcat, irrespective of what the monitoring console itself is running on. monitoring plugin: collecting agent should have separate jetty and tomcat plugins - Key: GERONIMO-3586 URL: https://issues.apache.org/jira/browse/GERONIMO-3586 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Attachments: geronimo-3586.patch The collecting agent plugin needs to have separate jetty and tomcat plugins in order to accommodate for the differences in container specific dependencies on stats implementation (.e.g JettyContainerStatsImpl and JettyConnectorStatsImpl). When the collecting agent was an EAR, this was not a problem; however, as a plugin, it is more tied down to having to specify all dependencies in the plugin's classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3527) Monitoring client needs default viewmode when selecting servers from the list
[ https://issues.apache.org/jira/browse/GERONIMO-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539779 ] Anita Kulshreshtha commented on GERONIMO-3527: -- GERONIMO-3577 patch applied in rev 591545. Monitoring client needs default viewmode when selecting servers from the list - Key: GERONIMO-3527 URL: https://issues.apache.org/jira/browse/GERONIMO-3527 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Currently selecting a server from the list in the monitoring client portlet links to #, must create a default view for this in the same styling of the default view for the 'views', with additional server-related functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3527) Monitoring client needs default viewmode when selecting servers from the list
[ https://issues.apache.org/jira/browse/GERONIMO-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539505 ] Anita Kulshreshtha commented on GERONIMO-3527: -- GERONIMO-3576 patch applied in rev. 591189. Monitoring client needs default viewmode when selecting servers from the list - Key: GERONIMO-3527 URL: https://issues.apache.org/jira/browse/GERONIMO-3527 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Currently selecting a server from the list in the monitoring client portlet links to #, must create a default view for this in the same styling of the default view for the 'views', with additional server-related functionality. -- 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-3527) Monitoring client needs default viewmode when selecting servers from the list
[ https://issues.apache.org/jira/browse/GERONIMO-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538947 ] Anita Kulshreshtha commented on GERONIMO-3527: -- GERONIMO-3566 patch applied in rev 590509. Monitoring client needs default viewmode when selecting servers from the list - Key: GERONIMO-3527 URL: https://issues.apache.org/jira/browse/GERONIMO-3527 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Currently selecting a server from the list in the monitoring client portlet links to #, must create a default view for this in the same styling of the default view for the 'views', with additional server-related functionality. -- 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.
[jira] Commented: (GERONIMO-3527) Monitoring client needs default viewmode when selecting servers from the list
[ https://issues.apache.org/jira/browse/GERONIMO-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537808 ] Anita Kulshreshtha commented on GERONIMO-3527: -- GERONIMO-3551 patch applied in rev 588469. Thanks Erik! Why is 'system, manager' being stored in the DB (MonitoringClientDB.sql)? Monitoring client needs default viewmode when selecting servers from the list - Key: GERONIMO-3527 URL: https://issues.apache.org/jira/browse/GERONIMO-3527 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Currently selecting a server from the list in the monitoring client portlet links to #, must create a default view for this in the same styling of the default view for the 'views', with additional server-related functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3558) monitoring plugin: reenable the archiving of snapshot statistics using a database
[ https://issues.apache.org/jira/browse/GERONIMO-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537814 ] Anita Kulshreshtha commented on GERONIMO-3558: -- Patch applied in rev 588476. Thanks Viet! The private methods do not need @RolesAllowed annotations (MasterRemoteControl.java). monitoring plugin: reenable the archiving of snapshot statistics using a database - Key: GERONIMO-3558 URL: https://issues.apache.org/jira/browse/GERONIMO-3558 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3558.patch The archiving of snapshot statistics was taken out due to the migrating from XML to DB. This feature needs to be hooked up again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3550) Monitoring client needs basic page for default serverview
[ https://issues.apache.org/jira/browse/GERONIMO-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537303 ] Anita Kulshreshtha commented on GERONIMO-3550: -- Patch committed in rev 587875, Thanks! Monitoring client needs basic page for default serverview -- Key: GERONIMO-3550 URL: https://issues.apache.org/jira/browse/GERONIMO-3550 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: GERONIMO-3550.patch The monitoring client needs a basic default page when you click on the servers listed... this will be improved upon, which is why this is a small subtask to get the basics implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3527) Monitoring client needs default viewmode when selecting servers from the list
[ https://issues.apache.org/jira/browse/GERONIMO-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537476 ] Anita Kulshreshtha commented on GERONIMO-3527: -- GERONIMO-3553 patch applied in rev 588109. Thanks Erik! Monitoring client needs default viewmode when selecting servers from the list - Key: GERONIMO-3527 URL: https://issues.apache.org/jira/browse/GERONIMO-3527 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Currently selecting a server from the list in the monitoring client portlet links to #, must create a default view for this in the same styling of the default view for the 'views', with additional server-related functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3557) monitoring plugin: collecting agent to use datasources
[ https://issues.apache.org/jira/browse/GERONIMO-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537482 ] Anita Kulshreshtha commented on GERONIMO-3557: -- Partial patch committed in rev 588121. There are conflicts in MasterRemoteControl.java. Could you please resubmit the patch for MasterRemoteControl.java? Thanks. monitoring plugin: collecting agent to use datasources -- Key: GERONIMO-3557 URL: https://issues.apache.org/jira/browse/GERONIMO-3557 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Attachments: geronimo-3557.patch Collecting agent should use the injected DataSources to talk to the DBs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3557) monitoring plugin: collecting agent to use datasources
[ https://issues.apache.org/jira/browse/GERONIMO-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537489 ] Anita Kulshreshtha commented on GERONIMO-3557: -- MasterRemoteControl patch applied in rev 588129. monitoring plugin: collecting agent to use datasources -- Key: GERONIMO-3557 URL: https://issues.apache.org/jira/browse/GERONIMO-3557 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Attachments: geronimo-3557.patch, geronimo-3557.patch Collecting agent should use the injected DataSources to talk to the DBs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3547) Monitoring client needs to connect via mejb instead of jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537178 ] Anita Kulshreshtha commented on GERONIMO-3547: -- Erik, Could you please create the patch against the latest source (rev 587666). Monitoring client needs to connect via mejb instead of jmx -- Key: GERONIMO-3547 URL: https://issues.apache.org/jira/browse/GERONIMO-3547 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: GERONIMO-3547.patch The monitoring client previously connected to the monitoring server via JMX. This has changed due to security concerns, and needs to be updated so that it will connect using MEJB instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3547) Monitoring client needs to connect via mejb instead of jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537180 ] Anita Kulshreshtha commented on GERONIMO-3547: -- Please ignore my earlier comment. I was using the wrong patch. Patch committed to rev 587714, thanks! Monitoring client needs to connect via mejb instead of jmx -- Key: GERONIMO-3547 URL: https://issues.apache.org/jira/browse/GERONIMO-3547 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: GERONIMO-3547.patch The monitoring client previously connected to the monitoring server via JMX. This has changed due to security concerns, and needs to be updated so that it will connect using MEJB instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3541) monitoring plugin: collecting agent needs to use a database to store the snapshots instead of xml
[ https://issues.apache.org/jira/browse/GERONIMO-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537191 ] Anita Kulshreshtha commented on GERONIMO-3541: -- Joe, thanks for taking care of the patch. monitoring plugin: collecting agent needs to use a database to store the snapshots instead of xml - Key: GERONIMO-3541 URL: https://issues.apache.org/jira/browse/GERONIMO-3541 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Joe Bohn Attachments: geronimo-3541.patch The DB needs to be populated with snapshot statistics. Also, the functions used to query snapshots needs to be migrated from reading from XML files to a DB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3530) provide activemq destination and connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha reassigned GERONIMO-3530: Assignee: Anita Kulshreshtha provide activemq destination and connector stats Key: GERONIMO-3530 URL: https://issues.apache.org/jira/browse/GERONIMO-3530 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: linux, windows Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3530.patch there are some stats that can easily be surfaced with how we use AMQ in our source. These are JSR 77 compliant statistics that are being provided by AMQ (DestinationStatistics and ConnectorStatistics). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3537) monitoring plugin: collecting agent needs to reenable snapshots
[ https://issues.apache.org/jira/browse/GERONIMO-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536093 ] Anita Kulshreshtha commented on GERONIMO-3537: -- Patch applied in rev 586231 monitoring plugin: collecting agent needs to reenable snapshots --- Key: GERONIMO-3537 URL: https://issues.apache.org/jira/browse/GERONIMO-3537 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Environment: windows Reporter: Viet Hung Nguyen Attachments: geronimo-3537.patch The collecting agent's snapshot feature, where it collects statistics and stores it, was disabled due to reconfiguring the MRC-server to become secured. The snapshots feature needs to be re-enabled, and configured so that it can get access to the statistics too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3530) provide activemq destination and connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536084 ] Anita Kulshreshtha commented on GERONIMO-3530: -- Viet, Thanks for the patch! How do these statistics relate to JMSStats defined by JSR77.24 through JSR77.29? provide activemq destination and connector stats Key: GERONIMO-3530 URL: https://issues.apache.org/jira/browse/GERONIMO-3530 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: linux, windows Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3530.patch there are some stats that can easily be surfaced with how we use AMQ in our source. These are JSR 77 compliant statistics that are being provided by AMQ (DestinationStatistics and ConnectorStatistics). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3533) monitoring pluging: cleanup poms
[ https://issues.apache.org/jira/browse/GERONIMO-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535540 ] Anita Kulshreshtha commented on GERONIMO-3533: -- Patch applied in rev 585475 monitoring pluging: cleanup poms Key: GERONIMO-3533 URL: https://issues.apache.org/jira/browse/GERONIMO-3533 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: linux Reporter: Viet Hung Nguyen Attachments: geronimo-3533.patch We need to clean up the pom.xmls at almost every level. Also, the current collecting agent plugin is not compiling due to the some recent changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3520) missing jsr-77 stats for JTA
[ https://issues.apache.org/jira/browse/GERONIMO-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535556 ] Anita Kulshreshtha commented on GERONIMO-3520: -- Txmaanger patch applied to rev 584554 at txmanager/trunk geronimo patch applied to rev 585497 with minor modifications, Nice Work Viet, Thanks! I have mistakenly entered wrong jira # 3250 in the logs, Sorry for the goof.. missing jsr-77 stats for JTA Key: GERONIMO-3520 URL: https://issues.apache.org/jira/browse/GERONIMO-3520 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, transaction manager Affects Versions: 2.0.2, 2.1 Environment: linux Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3520.patch, jms-mdb-sample-ear-2.0-SNAPSHOT.ear, txmanagerStats.patch we need to surface transaction statistics defined by the JSR 77 spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3535) monitoring plugin: collecting agent needs to be secured
[ https://issues.apache.org/jira/browse/GERONIMO-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535814 ] Anita Kulshreshtha commented on GERONIMO-3535: -- Patch applied in rev 585796 monitoring plugin: collecting agent needs to be secured --- Key: GERONIMO-3535 URL: https://issues.apache.org/jira/browse/GERONIMO-3535 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Attachments: geronimo-3535.patch Currently, the collecting agent is a GBean. However, we cannot access the secured MEJB through a GBean. A possible solution is to make this GBean into an EJB and have the client side of the monitoring plugin remotely access it with some credentials for authentication. The authorization will then percolate over to allow the EJB (the x-GBean) to access the secured MEJB too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535389 ] Anita Kulshreshtha commented on GERONIMO-3490: -- I have changed isStatisticsProvider to mean stats capable for now. We might have to revisit this later. The components that provide statistics on demand now implement LazyStatisticsProvider (suggestion for better name welcome). committed in rev 585308 Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3490.patch, geronimo-3490b.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3520) missing jsr-77 stats for JTA
[ https://issues.apache.org/jira/browse/GERONIMO-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha reassigned GERONIMO-3520: Assignee: Anita Kulshreshtha missing jsr-77 stats for JTA Key: GERONIMO-3520 URL: https://issues.apache.org/jira/browse/GERONIMO-3520 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, transaction manager Affects Versions: 2.0.2, 2.1 Environment: linux Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3520.patch, jms-mdb-sample-ear-2.0-SNAPSHOT.ear, txmanagerStats.patch we need to surface transaction statistics defined by the JSR 77 spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2879) Provide JTA resource statistics
[ https://issues.apache.org/jira/browse/GERONIMO-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534507 ] Anita Kulshreshtha commented on GERONIMO-2879: -- committed in rev 584390. Remaining work will be committed in GERONIMO-3520 Provide JTA resource statistics --- Key: GERONIMO-2879 URL: https://issues.apache.org/jira/browse/GERONIMO-2879 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: management Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Minor Provide JTA resource statistics required by JTAStats and possibly few more like TransactionTime and ExceptionCount -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3456. Resolution: Fixed Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.diff, configs.patch, configs.patch, GERONIMO-3456.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, mejb.diff, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3520) missing jsr-77 stats for JTA
[ https://issues.apache.org/jira/browse/GERONIMO-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534003 ] Anita Kulshreshtha commented on GERONIMO-3520: -- Viet, It might be possible to optimize the computation of ActiveCount by incrementing/decrementing a counter when ever the transactions are associated/disassociated instead of going through the Map every time. Could you please explain how/where the transactions are started in the attached application ear? missing jsr-77 stats for JTA Key: GERONIMO-3520 URL: https://issues.apache.org/jira/browse/GERONIMO-3520 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, transaction manager Affects Versions: 2.0.2, 2.1 Environment: linux Reporter: Viet Hung Nguyen Attachments: geronimo-3520.patch, jms-mdb-sample-ear-2.0-SNAPSHOT.ear, txmanagerStats.patch we need to surface transaction statistics defined by the JSR 77 spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3520) missing jsr-77 stats for JTA
[ https://issues.apache.org/jira/browse/GERONIMO-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533724 ] Anita Kulshreshtha commented on GERONIMO-3520: -- Could you please provide a test/application to test this patch? missing jsr-77 stats for JTA Key: GERONIMO-3520 URL: https://issues.apache.org/jira/browse/GERONIMO-3520 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, transaction manager Affects Versions: 2.0.2, 2.1 Environment: linux Reporter: Viet Hung Nguyen Attachments: geronimo-3520.patch, txmanagerStats.patch we need to surface transaction statistics defined by the JSR 77 spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3522) monitoring client needs ability to tell if snapshot thread is running, control proper stop/start of thread
[ https://issues.apache.org/jira/browse/GERONIMO-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533926 ] Anita Kulshreshtha commented on GERONIMO-3522: -- Patch applied in rev 583662 monitoring client needs ability to tell if snapshot thread is running, control proper stop/start of thread -- Key: GERONIMO-3522 URL: https://issues.apache.org/jira/browse/GERONIMO-3522 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Viet Hung Nguyen Assignee: Erik B. Craig Attachments: GERONIMO-3522.patch the monitoring client needs to be able tell whether or not the snapshot thread is actually collecting any data, control stop/start of the thread -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3526) Monitoring client should query server list
[ https://issues.apache.org/jira/browse/GERONIMO-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533572 ] Anita Kulshreshtha commented on GERONIMO-3526: -- Patch committed in rev 583343. It might be useful to use a single jira with subtasks, if necessary, to keep track of all the activity. Monitoring client should query server list -- Key: GERONIMO-3526 URL: https://issues.apache.org/jira/browse/GERONIMO-3526 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: GERONIMO-3526.patch Monitoring client should query server list when the main page is displayed, to acquire 'up' status, as well as status of snapshot thread for a quick glance at everything. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3524) monitoring server has problems with stop/starting snapshot
[ https://issues.apache.org/jira/browse/GERONIMO-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533573 ] Anita Kulshreshtha commented on GERONIMO-3524: -- Committed in rev 583346. monitoring server has problems with stop/starting snapshot -- Key: GERONIMO-3524 URL: https://issues.apache.org/jira/browse/GERONIMO-3524 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Environment: windows Reporter: Viet Hung Nguyen Attachments: geronimo-3524.patch, geronimo-3524b.patch the thread that executes the snapshots is using Thread.sleep(x). A condition is checked in between these sleeps to know whether or not to continue the thread. This means that the thread is not stopped immediately. In fact, it can take up to X (the duration between snapshots) seconds before it comes to a full stop. As a result, this affects the starting feature because it is restricted to have only one thread running at any given time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3517) Monitoring client needs to read from local database
[ https://issues.apache.org/jira/browse/GERONIMO-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533249 ] Anita Kulshreshtha commented on GERONIMO-3517: -- Patch applied in rev 583038 Monitoring client needs to read from local database --- Key: GERONIMO-3517 URL: https://issues.apache.org/jira/browse/GERONIMO-3517 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: GERONIMO-3517.patch Monitoring client needs to read from local database for views, server connection information and individual graphs information. The code must be modified to allow for this, as well as automatic population of the local database if it is either not created or simply empty. This is a stepping stone to getting the Monitoring client much more configurable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532452 ] Anita Kulshreshtha commented on GERONIMO-3490: -- A substantially modified version of the patch applied to rev 581936. I do not have a working build, please test with JMXViewer. Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3490.patch, geronimo-3490b.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source
[ https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532213 ] Anita Kulshreshtha commented on GERONIMO-3498: -- This patch attached at 11.36 A.M. does not apply. Refactor Monitoring plugin packaging and source --- Key: GERONIMO-3498 URL: https://issues.apache.org/jira/browse/GERONIMO-3498 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Blocker Attachments: GERONIMO-3498.patch The maven build method/order for the Monitoring plugin in sandbox must be restructured so the package is created as an ear to include derby datasource definitions for using to query and store configurations as well as graphing information -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3497) collecting agent needs to turn on statistics collection for all monitored StatisticsProvider
[ https://issues.apache.org/jira/browse/GERONIMO-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532225 ] Anita Kulshreshtha commented on GERONIMO-3497: -- patch applied in rev 581706 collecting agent needs to turn on statistics collection for all monitored StatisticsProvider Key: GERONIMO-3497 URL: https://issues.apache.org/jira/browse/GERONIMO-3497 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Environment: windows xp Reporter: Viet Hung Nguyen Attachments: geronimo-3497.patch By default, all stats that can be enabled/disabled are turned off. When the collecting agent is deployed, it should turn on all Stats that the admin wishes to track. If not, the collecting agent will be looking at a bunch of useless numbers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source
[ https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532234 ] Anita Kulshreshtha commented on GERONIMO-3498: -- Patch applied to rev 581709. The patch had conflicts. I was still getting the old patch. It is not necessary to remove the old patch. This makes it easy to find/load the new patch. Refactor Monitoring plugin packaging and source --- Key: GERONIMO-3498 URL: https://issues.apache.org/jira/browse/GERONIMO-3498 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Blocker Attachments: GERONIMO-3498.patch The maven build method/order for the Monitoring plugin in sandbox must be restructured so the package is created as an ear to include derby datasource definitions for using to query and store configurations as well as graphing information -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source
[ https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532245 ] Anita Kulshreshtha commented on GERONIMO-3498: -- Should be fixed in rev 581714 Refactor Monitoring plugin packaging and source --- Key: GERONIMO-3498 URL: https://issues.apache.org/jira/browse/GERONIMO-3498 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Blocker Attachments: GERONIMO-3498.patch The maven build method/order for the Monitoring plugin in sandbox must be restructured so the package is created as an ear to include derby datasource definitions for using to query and store configurations as well as graphing information -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3493) collecting agent should have configuration files in its own space under /var/monitoring/
[ https://issues.apache.org/jira/browse/GERONIMO-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531563 ] Anita Kulshreshtha commented on GERONIMO-3493: -- patch applied in rev 581014 collecting agent should have configuration files in its own space under /var/monitoring/ Key: GERONIMO-3493 URL: https://issues.apache.org/jira/browse/GERONIMO-3493 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Environment: windows xp Reporter: Viet Hung Nguyen Attachments: geronimo-3493.patch as of now the the configuration and snapshot information files are stored under GERONIMO_HOME/var/. We should have these files listed under its separate directory /var/monitoring/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531319 ] Anita Kulshreshtha commented on GERONIMO-3490: -- hmm something does not seem right - - The start time should not change with every sample. - The lastSample time is updated with every click, but other values are not being updated. I would expect at least requestCount to be updated on every click just like the containerStats. - If the stats are always on, what are statsStartedAt and statsOn(), and collectStatistics are for? Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3490.patch, geronimo-3490b.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha reassigned GERONIMO-3490: Assignee: Anita Kulshreshtha Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Attachments: geronimo-3490.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531240 ] Anita Kulshreshtha commented on GERONIMO-3490: -- Thanks Viet for the patch! I played around with the patch a bit and have a few more suggestions: - 1. You should not need to compute the startTime from LastSampleTime. - 2. When the statistics are not being collected, the starttime/LastsampleTime shows: Start Time: Wed Dec 31 19:00:00 EST 1969, i.e. the value 0. I am OK with all 0's in 'Empty' stats. We could change our stats portlet to display for 0 ms. WDYT? - 3. Since the stats are disabled by default, I had to either go to 'webserver' page to enable the container stats or set 'collectStatistics' attribute via JMXViewer. After that I was able to view JettyContainerStats from JMXViewer. I could not enable the connector stats from the console because the operation statsOn' threw exception. I could not view any real connector data. Do you think we should add an enableStats button to stats page in JMXViewer? It would be nice if you could fix #1. Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Attachments: geronimo-3490.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3441) Server monitoring and management
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha reassigned GERONIMO-3441: Assignee: Anita Kulshreshtha (was: Erik B. Craig) Server monitoring and management Key: GERONIMO-3441 URL: https://issues.apache.org/jira/browse/GERONIMO-3441 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: general Affects Versions: 2.1 Environment: All Reporter: Erik B. Craig Assignee: Anita Kulshreshtha Attachments: mrc-client.zip, mrc-server.zip, mrc.zip, screenshot1.jpg, screenshot2.jpg, stats.patch Currently, there is not a good way of surfacing Geronimo's server information so that an administrator can monitor the server's status. The architecture of using MBeans is established, but not fully exploited. This enhancement will take advantage of what Geronimo currently offers and extend it so that a server can tap into a cluster of servers and extract information from specific Geronimo servers or even aggregates of Geronimo servers. The goal is to have one machine be able to reach out to all Geronimo servers in order to fetch data or even alter their state. This will be especially useful in the case of someone having to monitor a large number of Geronimo servers. Viet Nguyen and myself have completed a bit of framework towards this goal, to be attached to this jira In-depth information can be found in the confluence wiki here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3441) Server monitoring and management
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530421 ] Anita Kulshreshtha commented on GERONIMO-3441: -- I have few more comments/questions: - Where are the The startTime and lastSampleTime for each statistic being set/updated? The startTime is the time the statistic collection was started. The resetStats() sets this time to current time. You might need to initialize Jetty's statistics collection mechanism during resetStats. - Where is statisticsProvider attribute being set to true for JettyContainer? - Does tomcat module compile with the stats.patch? Does Jetty provide per connector statistics? Could you please resubmit stats.patch with above changes? Server monitoring and management Key: GERONIMO-3441 URL: https://issues.apache.org/jira/browse/GERONIMO-3441 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: general Affects Versions: 2.1 Environment: All Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: MRC-server.zip, screenshot1.jpg, screenshot2.jpg, stats.patch, statsportlet.zip Currently, there is not a good way of surfacing Geronimo's server information so that an administrator can monitor the server's status. The architecture of using MBeans is established, but not fully exploited. This enhancement will take advantage of what Geronimo currently offers and extend it so that a server can tap into a cluster of servers and extract information from specific Geronimo servers or even aggregates of Geronimo servers. The goal is to have one machine be able to reach out to all Geronimo servers in order to fetch data or even alter their state. This will be especially useful in the case of someone having to monitor a large number of Geronimo servers. Viet Nguyen and myself have completed a bit of framework towards this goal, to be attached to this jira In-depth information can be found in the confluence wiki here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530423 ] Anita Kulshreshtha commented on GERONIMO-3456: -- committed in rev579616. The default security settings are - - admin - read access - To get R/W access create a mejb-admin group (GeronimoGroupPrincipal). Any user in this group will have R/W access Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.diff, configs.patch, configs.patch, GERONIMO-3456.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, mejb.diff, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3456: - Attachment: GERONIMO-3456.patch GERONIMO-3456 is the latest patch Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.diff, configs.patch, configs.patch, GERONIMO-3456.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, mejb.diff, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529693 ] Anita Kulshreshtha commented on GERONIMO-3481: -- The deployer syntax is deploy.bat . --port=n IIRC, the deployer has 1099 hard coded, i.e. if the port is not specified it will use 1099. Since we use same server image for all instances, I thought this interpretation was OK. This is one way to tell the deployer which server instance to deploy to. Of course we could do more, e.g. infer from geronimo_opts and use the right server instance. Offline deployer throws BIND Exception when port 1099 is in use --- Key: GERONIMO-3481 URL: https://issues.apache.org/jira/browse/GERONIMO-3481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1, 2.0.x, 2.1 Environment: G 2.0.1 - Running multiple instances Reporter: Vamsavardhana Reddy Assignee: David Jencks Fix For: 2.0.2, 2.0.x, 2.1 Attachments: GERONIMO-3481-1.patch, GERONIMO-3481-2.patch, GERONIMO-3481-2a.patch, GERONIMO-3481-weird.patch Offline deployer throws Bind Exception when port 1099 is in use. Here is a scenario steps in which the problem is experienced. 1. Extract G-2.0.1-Tomcat distro to C:\ 2. Create a dir myserver under C:\geronimo-j2ee-tomcat-2.0.1 and copy C:\geronimo-j2ee-tomcat-2.0.1\var to C:\geronimo-j2ee-tomcat-2.0.1\myserver\var (all sub-directories). 3. Edit C:\geronimo-j2ee-tomcat-2.0.1\myserver\var\config-substitutions.properties to set PortOffset=10. 4. Open a command window and start Geronimo. Since org.apache.geronimo.server.name is not set, this will start the default server instance. 5. Open a second command window, set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=myserver. This will be command window to run the second server instance with name myserver 6. Run deploy.bat --offline list-modules. At step 6, I am getting a BIND Exception since port 1099 is in use (by the default server instance) and the offline deployer is attempting to start rmi naming on port 1099. Since, this deploy command is run against second server instance, I would expect that it uses the configuration properties of myserver in which case it should use port 1109 to start rmi-naming if at all there is a need. When port 1099 is not in use, the offline deployer works as expected by updating proper config.xml file when a configuration is deployed/undeployed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529723 ] Anita Kulshreshtha commented on GERONIMO-3456: -- The openejb deployer had to be modified to deploy applications without starting the openejb configuration. Once the patches for openejb and openejb-builder attached to [1] are committed, I will commit this work. [1] http://issues.apache.org/jira/browse/GERONIMO-3481 Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.diff, configs.patch, configs.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, mejb.diff, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3456: - Attachment: configs.patch - config.patch (created from configs dir) for building mejb config Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.patch, configs.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3456: - Attachment: configs.diff The configs.patch has duplicates. Please use configs.diff Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.diff, configs.patch, configs.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3456: - Attachment: mejb.diff The mejb.patch also has duplicates. please apply mejb.diff to applications dir Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.diff, configs.patch, configs.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, mejb.diff, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3456: - Attachment: mejb-war-2.1-SNAPSHOT.war - The app mejb-war-2.1-SNAPSHOT.war is an app to access MEJB Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, mejb-war-2.1-SNAPSHOT.war, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3456) Make MEJB security configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3456: - Attachment: mejb-ejb-2.1-SNAPSHOT.jar configs.patch mejb.patch - mejb.patch deploys MEJB as an EJB module. The JNDI lookup is (available from var/geronimo.log) mejb-ejb/ejb/mgmt/MEJB/javax.managemment.j2ee.ManagementHome. - configs.patch disables the old MEJB - The mejb-ejb jar is attached for convenience. mejbuser' role is mapped to admin Make MEJB security configurable --- Key: GERONIMO-3456 URL: https://issues.apache.org/jira/browse/GERONIMO-3456 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB, security Affects Versions: 2.0.1, 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Critical Fix For: 2.0.2, 2.1 Attachments: configs.patch, mejb-ear-2.1-SNAPSHOT.ear, mejb-ejb-2.1-SNAPSHOT.jar, MEJB.java, mejb.patch Currently access to MEJB is not controlled. Add configurable security for MEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527749 ] Anita Kulshreshtha commented on GERONIMO-2964: -- Vamsi thanks! Could you please add SUID to Holder class in g-j2ee and retest? Caused by: java.io.InvalidClassException: org.apache.geronimo.j2ee.annotation.Ho lder; local class incompatible: stream classdesc serialVersionUID = 822160424416 6047988, local class serialVersionUID = 6192393604530969651 at We need to more careful about modifying serializable classes. Cannot specify the Tomcat work directory for a web application -- Key: GERONIMO-2964 URL: https://issues.apache.org/jira/browse/GERONIMO-2964 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Affects Versions: 1.2, 2.0-M5 Reporter: Aman Nanner Priority: Minor Fix For: 1.2, 2.1 Attachments: g2964.war, GERONIMO-2964-combined-new.patch, GERONIMO-2964-combined.patch, GERONIMO-2964.patch, tomcat-config-workdir.patch, tomcat-workdir.patch In Tomcat, a work directory can be specified for a web application in a WEB-INF/context.xml file. The GeronimoStandardContext does not permit the user to specify a work directory, and so the work directory defaults to var/catalina/work/web-app. I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to permit the user to optionally specify a work directory. This work directory is then propagated into the TomcatContext. I've tested this and it seems to work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527805 ] Anita Kulshreshtha commented on GERONIMO-2964: -- I did not expect SUID change to work.. The Holder class http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-j2ee/src/main/java/org/apache/geronimo/j2ee/annotation/Holder.java?sortdir=downr1=566236r2=568253 changes a List to a Set, which is equivalent to deleting a field. This is not a compatible change as described here: http://java.sun.com/j2se/1.5.0/docs/guide/serialization/spec/version.html#6678 This is likely to produce unexpected behavior irrespective of your patch. If we want to promise upward compatibility to our users, we need to fix this. Cannot specify the Tomcat work directory for a web application -- Key: GERONIMO-2964 URL: https://issues.apache.org/jira/browse/GERONIMO-2964 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Affects Versions: 1.2, 2.0-M5 Reporter: Aman Nanner Assignee: Vamsavardhana Reddy Priority: Minor Fix For: 2.0.2, 2.0.x, 2.1 Attachments: g2964.war, GERONIMO-2964-combined-new.patch, GERONIMO-2964-combined.patch, GERONIMO-2964.patch, tomcat-config-workdir.patch, tomcat-workdir.patch In Tomcat, a work directory can be specified for a web application in a WEB-INF/context.xml file. The GeronimoStandardContext does not permit the user to specify a work directory, and so the work directory defaults to var/catalina/work/web-app. I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to permit the user to optionally specify a work directory. This work directory is then propagated into the TomcatContext. I've tested this and it seems to work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
