[jira] Commented: (GERONIMO-4021) monitoring console takes too long to recognize that a server is offline
[ https://issues.apache.org/jira/browse/GERONIMO-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599167#action_12599167 ] Viet Hung Nguyen commented on GERONIMO-4021: isReachable() uses ICMP echo requests, which aren't always supported by the destination host. This will lead to an inaccurate assessment of whether or not the server is online. monitoring console takes too long to recognize that a server is offline --- Key: GERONIMO-4021 URL: https://issues.apache.org/jira/browse/GERONIMO-4021 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.2 Whenever the monitoring plugin attempts to monitor a server that is offline/doesn't exist, it takes way too long to load the page. We need to reduce this timeout period. I suggest that we add a parameter for the admin to set as the timeout period somewhere in the portlet. By default, we can choose to have this timeout parameter be set to 5000 milliseconds. We can use the InetAddress class to call isReachable(int timeout) to see if the server is online. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3996: --- Component/s: monitoring Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen closed GERONIMO-4014. -- Resolution: Fixed Thanks David. Everything looks fine. simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: David Jencks Assignee: Viet Hung Nguyen Fix For: 2.2 Attachments: GERONIMO-4014-2.diff, GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3996: -- Assignee: Viet Hung Nguyen (was: Erik B. Craig) Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Viet Hung Nguyen Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597321#action_12597321 ] Viet Hung Nguyen commented on GERONIMO-3996: Committed to trunk 656823. Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Viet Hung Nguyen Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen closed GERONIMO-3996. -- Resolution: Fixed Fix Version/s: 2.1 2.2 Committed revision 656911 in branches/2.1 Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Viet Hung Nguyen Priority: Minor Fix For: 2.2, 2.1 When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4021) monitoring console takes too long to recognize that a server is offline
monitoring console takes too long to recognize that a server is offline --- Key: GERONIMO-4021 URL: https://issues.apache.org/jira/browse/GERONIMO-4021 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.2 Whenever the monitoring plugin attempts to monitor a server that is offline/doesn't exist, it takes way too long to load the page. We need to reduce this timeout period. I suggest that we add a parameter for the admin to set as the timeout period somewhere in the portlet. By default, we can choose to have this timeout parameter be set to 5000 milliseconds. We can use the InetAddress class to call isReachable(int timeout) to see if the server is online. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596887#action_12596887 ] Viet Hung Nguyen commented on GERONIMO-4014: David, When I applied your patch and to test the JMX feature, I got the following error when I install the agent-car-jmx plugin. The ejb app seems to be doing fine though. 14:32:34,562 ERROR [MasterRemoteControlJMX] org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper java.lang.ClassCastException: org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper at org.apache.geronimo.monitoring.MasterRemoteControlJMX.init(MasterRemoteControlJMX.java:103) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.xbean.recipe.ObjectRecipe.createInstance(ObjectRecipe.java:390) at org.apache.xbean.recipe.ObjectRecipe.create(ObjectRecipe.java:194) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:910) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:189) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:549) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530) at org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:672) at org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:592) at org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:737) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: David Jencks Fix For: 2.2 Attachments: GERONIMO-4014-2.diff, GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4018) SnapshotConfigXMLBuilder having issues with jaxb when using agent--car-jmx
SnapshotConfigXMLBuilder having issues with jaxb when using agent--car-jmx -- Key: GERONIMO-4018 URL: https://issues.apache.org/jira/browse/GERONIMO-4018 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Viet Hung Nguyen JAXB is used to modify the snapshot-config.xml file for both types of querying (ejb and jmx). Strangely, it works fine for the ejb app, but I get this error when I use the agent-jmx-car. 15:11:43,578 ERROR [SnapshotConfigXMLBuilder] org.apache.geronimo.monitoring.snapshot doesnt contain ObjectFactory.class or jaxb.index javax.xml.bind.JAXBException: org.apache.geronimo.monitoring.snapshot doesnt contain ObjectFactory.class or jaxb.index at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132) at javax.xml.bind.ContextFinder.find(ContextFinder.java:285) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) at org.apache.geronimo.monitoring.snapshot.SnapshotConfigXMLBuilder.clinit(SnapshotConfigXMLBuilder.java:45) at org.apache.geronimo.monitoring.MasterRemoteControlJMX.getSnapshotDuration(MasterRemoteControlJMX.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4018) SnapshotConfigXMLBuilder having issues with jaxb when using agent--car-jmx
[ https://issues.apache.org/jira/browse/GERONIMO-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-4018. Resolution: Fixed Committed revision 656417 in trunk. SnapshotConfigXMLBuilder having issues with jaxb when using agent--car-jmx -- Key: GERONIMO-4018 URL: https://issues.apache.org/jira/browse/GERONIMO-4018 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Viet Hung Nguyen JAXB is used to modify the snapshot-config.xml file for both types of querying (ejb and jmx). Strangely, it works fine for the ejb app, but I get this error when I use the agent-jmx-car. 15:11:43,578 ERROR [SnapshotConfigXMLBuilder] org.apache.geronimo.monitoring.snapshot doesnt contain ObjectFactory.class or jaxb.index javax.xml.bind.JAXBException: org.apache.geronimo.monitoring.snapshot doesnt contain ObjectFactory.class or jaxb.index at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132) at javax.xml.bind.ContextFinder.find(ContextFinder.java:285) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) at org.apache.geronimo.monitoring.snapshot.SnapshotConfigXMLBuilder.clinit(SnapshotConfigXMLBuilder.java:45) at org.apache.geronimo.monitoring.MasterRemoteControlJMX.getSnapshotDuration(MasterRemoteControlJMX.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4019) add the ability to preview a graph
add the ability to preview a graph -- Key: GERONIMO-4019 URL: https://issues.apache.org/jira/browse/GERONIMO-4019 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Viet Hung Nguyen Priority: Minor I think it will make the monitoring portlet more user-friendly if there was a preview graph option before the admin had to create the graph. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596595#action_12596595 ] Viet Hung Nguyen commented on GERONIMO-4014: Thanks David, I never thought about organizing the agent like that. If no one else has any objections, can you commit it? simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Reporter: David Jencks Fix For: 2.2 Attachments: GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3774) monitoring agent should separate any constant assignment inside one class
[ https://issues.apache.org/jira/browse/GERONIMO-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581076#action_12581076 ] Viet Hung Nguyen commented on GERONIMO-3774: Committed revision 639641 in trunk. monitoring agent should separate any constant assignment inside one class - Key: GERONIMO-3774 URL: https://issues.apache.org/jira/browse/GERONIMO-3774 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Trivial Fix For: 2.2 There are constant variables such as DEFAULT_RETENTION that are used by both the agent-jmx and agent-ejb. These constants should be placed inside a class dedicated to just constants in agent-jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3774) monitoring agent should separate any constant assignment inside one class
[ https://issues.apache.org/jira/browse/GERONIMO-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3774: --- Affects Version/s: (was: 2.2) 2.1.1 monitoring agent should separate any constant assignment inside one class - Key: GERONIMO-3774 URL: https://issues.apache.org/jira/browse/GERONIMO-3774 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Trivial Fix For: 2.2 There are constant variables such as DEFAULT_RETENTION that are used by both the agent-jmx and agent-ejb. These constants should be placed inside a class dedicated to just constants in agent-jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3774) monitoring agent should separate any constant assignment inside one class
[ https://issues.apache.org/jira/browse/GERONIMO-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3774: --- Affects Version/s: (was: 2.1.1) (was: 2.1) monitoring agent should separate any constant assignment inside one class - Key: GERONIMO-3774 URL: https://issues.apache.org/jira/browse/GERONIMO-3774 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Trivial Fix For: 2.2 There are constant variables such as DEFAULT_RETENTION that are used by both the agent-jmx and agent-ejb. These constants should be placed inside a class dedicated to just constants in agent-jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3765) monitoring console throws IllegalArgumentException when editting a bad server
[ https://issues.apache.org/jira/browse/GERONIMO-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen closed GERONIMO-3765. -- Resolution: Cannot Reproduce Fix Version/s: 2.2 2.1.1 I cannot produce this error anymore. Maybe it was fixed without me knowing. monitoring console throws IllegalArgumentException when editting a bad server - Key: GERONIMO-3765 URL: https://issues.apache.org/jira/browse/GERONIMO-3765 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.1, 2.2 When someone adds a server (that does not exist) and he/she tries to edit the server's information, the console throws an IllegalArgumentException when I click on Test these settings because the snapshot duration and snapshot retention are passed in as null. We need to allow the user to alter these values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3925) Monitoring agent should use JAXB to do XML manipulation
[ https://issues.apache.org/jira/browse/GERONIMO-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3925: -- Assignee: Viet Hung Nguyen Monitoring agent should use JAXB to do XML manipulation --- Key: GERONIMO-3925 URL: https://issues.apache.org/jira/browse/GERONIMO-3925 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen xmlbeans is currently used to write out the xml in the monitoring agent. JAXB should be used to manipulation XML. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3925) Monitoring agent should use JAXB to do XML manipulation
[ https://issues.apache.org/jira/browse/GERONIMO-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580785#action_12580785 ] Viet Hung Nguyen commented on GERONIMO-3925: Committed revision 639303 for trunk. Monitoring agent should use JAXB to do XML manipulation --- Key: GERONIMO-3925 URL: https://issues.apache.org/jira/browse/GERONIMO-3925 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen xmlbeans is currently used to write out the xml in the monitoring agent. JAXB should be used to manipulation XML. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3925) Monitoring agent should use JAXB to do XML manipulation
[ https://issues.apache.org/jira/browse/GERONIMO-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3925: --- Patch Info: [Patch Available] Affects Version/s: (was: 2.2) Monitoring agent should use JAXB to do XML manipulation --- Key: GERONIMO-3925 URL: https://issues.apache.org/jira/browse/GERONIMO-3925 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen xmlbeans is currently used to write out the xml in the monitoring agent. JAXB should be used to manipulation XML. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3833. Resolution: Fixed Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578600#action_12578600 ] Viet Hung Nguyen commented on GERONIMO-3833: Thanks for pointing this out Jarek. Committed revision 636991 in trunk. I also committed the 2.1 branch. Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577898#action_12577898 ] Viet Hung Nguyen commented on GERONIMO-3833: Committed revision 636392 to trunk removing hard coded mbean name. dynamically fetches it instead. Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578142#action_12578142 ] Viet Hung Nguyen commented on GERONIMO-3833: Committed revision 636624 to 2.1 branch. Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3833: -- Assignee: Viet Hung Nguyen Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3804. Resolution: Fixed Fix Version/s: 2.1 monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx -- Key: GERONIMO-3804 URL: https://issues.apache.org/jira/browse/GERONIMO-3804 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Fix For: 2.1 Attachments: geronimo-3804.patch the mconsole does not detect any servers connected using jmx when trying to add a graph. I suspect it has something to do with the db query, because it detects all servers connected through MEJB just fine. I checked to ensure an instance of the server-jmx was present in the mconsole db and it is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3790) monitoring agent should provide jmx support
[ https://issues.apache.org/jira/browse/GERONIMO-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3790. Resolution: Fixed monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3790.patch, geronimo-3790.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3803: --- Attachment: geronimo-3803.patch monitoring plugin: agent-jmx does not provide the correct interface for mconsole Key: GERONIMO-3803 URL: https://issues.apache.org/jira/browse/GERONIMO-3803 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3803.patch the agent-jmx does not specify the right method signatures that the mconsole needs to run properly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole
monitoring plugin: agent-jmx does not provide the correct interface for mconsole Key: GERONIMO-3803 URL: https://issues.apache.org/jira/browse/GERONIMO-3803 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3803.patch the agent-jmx does not specify the right method signatures that the mconsole needs to run properly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx
monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx -- Key: GERONIMO-3804 URL: https://issues.apache.org/jira/browse/GERONIMO-3804 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Priority: Critical the mconsole does not detect any servers connected using jmx when trying to add a graph. I suspect it has something to do with the db query, because it detects all servers connected through MEJB just fine. I checked to ensure an instance of the server-jmx was present in the mconsole db and it is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3804: -- Assignee: Viet Hung Nguyen (was: Erik B. Craig) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx -- Key: GERONIMO-3804 URL: https://issues.apache.org/jira/browse/GERONIMO-3804 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical the mconsole does not detect any servers connected using jmx when trying to add a graph. I suspect it has something to do with the db query, because it detects all servers connected through MEJB just fine. I checked to ensure an instance of the server-jmx was present in the mconsole db and it is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3804: --- Attachment: geronimo-3804.patch monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx -- Key: GERONIMO-3804 URL: https://issues.apache.org/jira/browse/GERONIMO-3804 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3804.patch the mconsole does not detect any servers connected using jmx when trying to add a graph. I suspect it has something to do with the db query, because it detects all servers connected through MEJB just fine. I checked to ensure an instance of the server-jmx was present in the mconsole db and it is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3790) monitoring agent should provide jmx support
[ https://issues.apache.org/jira/browse/GERONIMO-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3790: --- Attachment: geronimo-3790.patch fixes the isSnapshotRunning(). Sorry, I forgot to implement it even when I had a TODO tag next to it. Thanks for pointing it out for me. monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3790.patch, geronimo-3790.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3790) monitoring agent should provide jmx support
monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3790) monitoring agent should provide jmx support
[ https://issues.apache.org/jira/browse/GERONIMO-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3790: --- Attachment: geronimo-3790.patch need to run the following commands with this patch: svn add plugins/monitoring/agent-jmx svn add plugins/monitoring/agent-car-jmx -Viet monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3790.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3790) monitoring agent should provide jmx support
[ https://issues.apache.org/jira/browse/GERONIMO-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3790: --- Patch Info: [Patch Available] I tested the stopping and starting of the agent taking snapshots. Needs further testing. monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3790.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3766) monitoring agent should be separated into mejb, jmx, and jar utility classes
[ https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3766. Resolution: Fixed monitoring agent should be separated into mejb, jmx, and jar utility classes Key: GERONIMO-3766 URL: https://issues.apache.org/jira/browse/GERONIMO-3766 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: monitoring Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3766.patch in order to modularize the monitoring agent, I suggest the following breakdown: agent-ejb which will contain anything MEJB related, so that only this will pull in OpenEJB agent-jmx which will have the code for JMX connections agent-jar -which will have the utility classes/functions that are used by both agent-ejb and agent-jmx So, when packaging these JARs into an EAR, agent-ejb + agent-jar will make up the agent MEJB plugin agent-jmx + agent-jar will make up the agent JMX plugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3774) monitoring agent should separate any constant assignment inside one class
monitoring agent should separate any constant assignment inside one class - Key: GERONIMO-3774 URL: https://issues.apache.org/jira/browse/GERONIMO-3774 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 Priority: Trivial There are constant variables such as DEFAULT_RETENTION that are used by both the agent-jmx and agent-ejb. These constants should be placed inside a class dedicated to just constants in agent-jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3765) monitoring console throws IllegalArgumentException when editting a bad server
[ https://issues.apache.org/jira/browse/GERONIMO-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3765: --- Component/s: monitoring monitoring console throws IllegalArgumentException when editting a bad server - Key: GERONIMO-3765 URL: https://issues.apache.org/jira/browse/GERONIMO-3765 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 When someone adds a server (that does not exist) and he/she tries to edit the server's information, the console throws an IllegalArgumentException because the snapshot duration and snapshot retention are passed in as null. We need to allow the user to alter these values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3765) monitoring console throws IllegalArgumentException when editting a bad server
monitoring console throws IllegalArgumentException when editting a bad server - Key: GERONIMO-3765 URL: https://issues.apache.org/jira/browse/GERONIMO-3765 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen When someone adds a server (that does not exist) and he/she tries to edit the server's information, the console throws an IllegalArgumentException because the snapshot duration and snapshot retention are passed in as null. We need to allow the user to alter these values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3766) monitoring agent should be separated into mejb, jmx, and jar utility classes
monitoring agent should be separated into mejb, jmx, and jar utility classes Key: GERONIMO-3766 URL: https://issues.apache.org/jira/browse/GERONIMO-3766 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: monitoring Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 in order to modularize the monitoring agent, I suggest the following breakdown: agent-ejb which will contain anything MEJB related, so that only this will pull in OpenEJB agent-jmx which will have the code for JMX connections agent-jar -which will have the utility classes/functions that are used by both agent-ejb and agent-jmx So, when packaging these JARs into an EAR, agent-ejb + agent-jar will make up the agent MEJB plugin agent-jmx + agent-jar will make up the agent JMX plugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3765) monitoring console throws IllegalArgumentException when editting a bad server
[ https://issues.apache.org/jira/browse/GERONIMO-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3765: --- Description: When someone adds a server (that does not exist) and he/she tries to edit the server's information, the console throws an IllegalArgumentException when I click on Test these settings because the snapshot duration and snapshot retention are passed in as null. We need to allow the user to alter these values. (was: When someone adds a server (that does not exist) and he/she tries to edit the server's information, the console throws an IllegalArgumentException because the snapshot duration and snapshot retention are passed in as null. We need to allow the user to alter these values.) monitoring console throws IllegalArgumentException when editting a bad server - Key: GERONIMO-3765 URL: https://issues.apache.org/jira/browse/GERONIMO-3765 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 When someone adds a server (that does not exist) and he/she tries to edit the server's information, the console throws an IllegalArgumentException when I click on Test these settings because the snapshot duration and snapshot retention are passed in as null. We need to allow the user to alter these values. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3766) monitoring agent should be separated into mejb, jmx, and jar utility classes
[ https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3766: --- Attachment: geronimo-3766.patch this patch needs the following commands to be executed with it: svn delete applications/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/MBeanHelper.java svn delete applications/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/snapshot/SnapshotConfigXMLBuilder.java svn delete applications/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/snapshot/SnapshotDBHelper.java svn add applications/monitoring/agent-jar monitoring agent should be separated into mejb, jmx, and jar utility classes Key: GERONIMO-3766 URL: https://issues.apache.org/jira/browse/GERONIMO-3766 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: monitoring Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3766.patch in order to modularize the monitoring agent, I suggest the following breakdown: agent-ejb which will contain anything MEJB related, so that only this will pull in OpenEJB agent-jmx which will have the code for JMX connections agent-jar -which will have the utility classes/functions that are used by both agent-ejb and agent-jmx So, when packaging these JARs into an EAR, agent-ejb + agent-jar will make up the agent MEJB plugin agent-jmx + agent-jar will make up the agent JMX plugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3753) monitoring portlet is not up to date with dojo 1.0
monitoring portlet is not up to date with dojo 1.0 -- Key: GERONIMO-3753 URL: https://issues.apache.org/jira/browse/GERONIMO-3753 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 Priority: Trivial I noticed that when a user clicks on a Graph's name, the graph does not render correctly. I'm pretty sure it has something to do with the new version of dojo. So we need to update monitoringPopUpGraph.jsp to reflect the new version of dojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3753) monitoring portlet is not up to date with dojo 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3753: --- Attachment: geronimo-3753.patch monitoring portlet is not up to date with dojo 1.0 -- Key: GERONIMO-3753 URL: https://issues.apache.org/jira/browse/GERONIMO-3753 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 Priority: Trivial Attachments: geronimo-3753.patch I noticed that when a user clicks on a Graph's name, the graph does not render correctly. I'm pretty sure it has something to do with the new version of dojo. So we need to update monitoringPopUpGraph.jsp to reflect the new version of dojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3753) monitoring portlet is not up to date with dojo 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3753: --- Patch Info: [Patch Available] monitoring portlet is not up to date with dojo 1.0 -- Key: GERONIMO-3753 URL: https://issues.apache.org/jira/browse/GERONIMO-3753 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 Priority: Trivial Attachments: geronimo-3753.patch I noticed that when a user clicks on a Graph's name, the graph does not render correctly. I'm pretty sure it has something to do with the new version of dojo. So we need to update monitoringPopUpGraph.jsp to reflect the new version of dojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3753) monitoring portlet is not up to date with dojo 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3753. Resolution: Fixed monitoring portlet is not up to date with dojo 1.0 -- Key: GERONIMO-3753 URL: https://issues.apache.org/jira/browse/GERONIMO-3753 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 Priority: Trivial Attachments: geronimo-3753.patch I noticed that when a user clicks on a Graph's name, the graph does not render correctly. I'm pretty sure it has something to do with the new version of dojo. So we need to update monitoringPopUpGraph.jsp to reflect the new version of dojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3739) SnapshotDBHelper in the monitoring agent should not have static methods
SnapshotDBHelper in the monitoring agent should not have static methods --- Key: GERONIMO-3739 URL: https://issues.apache.org/jira/browse/GERONIMO-3739 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 Attachments: geronimo.patch The SnapshotDBHelper in the monitoring agent is a utility class right now. Other pieces of code can just use it by statically accessing its methods. However, this is a dangerous practice if the DataSources are not set properly before using it. So I suggest to force other pieces of code to instantiate the SnapshotDBHelper object first before using it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3739) SnapshotDBHelper in the monitoring agent should not have static methods
[ https://issues.apache.org/jira/browse/GERONIMO-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3739: --- Attachment: geronimo.patch SnapshotDBHelper in the monitoring agent should not have static methods --- Key: GERONIMO-3739 URL: https://issues.apache.org/jira/browse/GERONIMO-3739 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 Attachments: geronimo.patch The SnapshotDBHelper in the monitoring agent is a utility class right now. Other pieces of code can just use it by statically accessing its methods. However, this is a dangerous practice if the DataSources are not set properly before using it. So I suggest to force other pieces of code to instantiate the SnapshotDBHelper object first before using it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3739) SnapshotDBHelper in the monitoring agent should not have static methods
[ https://issues.apache.org/jira/browse/GERONIMO-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3739. Resolution: Fixed Fix Version/s: 2.1 SnapshotDBHelper in the monitoring agent should not have static methods --- Key: GERONIMO-3739 URL: https://issues.apache.org/jira/browse/GERONIMO-3739 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.patch The SnapshotDBHelper in the monitoring agent is a utility class right now. Other pieces of code can just use it by statically accessing its methods. However, this is a dangerous practice if the DataSources are not set properly before using it. So I suggest to force other pieces of code to instantiate the SnapshotDBHelper object first before using it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3726) monitoring plugin displays misleading warning message
[ https://issues.apache.org/jira/browse/GERONIMO-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3726. Resolution: Fixed Fix Version/s: 2.1 monitoring plugin displays misleading warning message - Key: GERONIMO-3726 URL: https://issues.apache.org/jira/browse/GERONIMO-3726 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 Priority: Trivial Fix For: 2.1 Attachments: geronimo-3726.patch When there is only one statistic name specified for a graph (i.e. there isn't an operation to perform onto another statistical value), the GraphsBuilder still attempts to fetch snapshot data for a null statistics name. There needs to be a check on this, so that the message does not show up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3730) monitoring plugin to support jmx connections in mconsole
monitoring plugin to support jmx connections in mconsole Key: GERONIMO-3730 URL: https://issues.apache.org/jira/browse/GERONIMO-3730 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen There should be another collecting agent that does not use MEJB, but JMX instead. This should probably be a separate plugin than the existing agent because we do not want to pull in OpenEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3719) Monitoring agent uses sun classes
[ https://issues.apache.org/jira/browse/GERONIMO-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3719: -- Assignee: Viet Hung Nguyen Monitoring agent uses sun classes - Key: GERONIMO-3719 URL: https://issues.apache.org/jira/browse/GERONIMO-3719 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: David Jencks Assignee: Viet Hung Nguyen Fix For: 2.1 SnapshotConfigXMLBuilder uses a couple sun classes to write out xml. This doesn't work on non-sun jvms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3726) monitoring plugin displays misleading warning message
[ https://issues.apache.org/jira/browse/GERONIMO-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3726: --- Attachment: geronimo-3726.patch monitoring plugin displays misleading warning message - Key: GERONIMO-3726 URL: https://issues.apache.org/jira/browse/GERONIMO-3726 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 Priority: Trivial Attachments: geronimo-3726.patch When there is only one statistic name specified for a graph (i.e. there isn't an operation to perform onto another statistical value), the GraphsBuilder still attempts to fetch snapshot data for a null statistics name. There needs to be a check on this, so that the message does not show up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3726) monitoring plugin displays misleading warning message
monitoring plugin displays misleading warning message - Key: GERONIMO-3726 URL: https://issues.apache.org/jira/browse/GERONIMO-3726 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 Priority: Trivial Attachments: geronimo-3726.patch When there is only one statistic name specified for a graph (i.e. there isn't an operation to perform onto another statistical value), the GraphsBuilder still attempts to fetch snapshot data for a null statistics name. There needs to be a check on this, so that the message does not show up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554451 ] Viet Hung Nguyen commented on GERONIMO-3714: Thanks, I never had the time to set up my linux box at home to redo the patch. Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3714. Resolution: Fixed Fix Version/s: 2.1 Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554170 ] Viet Hung Nguyen commented on GERONIMO-3714: that's weird. I just pulled down a fresh trunk and applied the patch just fine. I will try it on a linux machine when I have the time. Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3714: --- Attachment: geronimo-3714.patch The root cause of this is because the skipCount value is equal to 0 in some instances because of integer division. With skipCount = 0, it is meaningless to the method getSpecificStatistics() in the agent. Whenever this happens, I set skipCount = 1, meaning, grab each snapshot without skipping any in between. Additionally, I also reformatted the MRCConnector.java to abide by the Apache Geronimo coding standards specified at http://geronimo.apache.org/coding-standards.html. Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3714: --- Attachment: (was: geronimo-3714.patch) Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3714) Monitoring console does no error checking on add/edit graph timeframe
[ https://issues.apache.org/jira/browse/GERONIMO-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3714: --- Attachment: geronimo-3714.patch I forgot to add the JS checks to ensure that the user cannot specify anything less than 2*(snapshot_duration) for the graph's time window. So I have added that stuff in this new patch Monitoring console does no error checking on add/edit graph timeframe - Key: GERONIMO-3714 URL: https://issues.apache.org/jira/browse/GERONIMO-3714 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Viet Hung Nguyen Attachments: geronimo-3714.patch Currently the Monitoring console does no error checking on add/edit graph timeframe, it is therefore possible to define graphs that will break the page. There should be javascript checks to prevent the user from entering values anything less than 3*(snapshot duration) and anything more than the archive cutoff point, UNLESS 'show archive' is checked -- 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_12550987 ] Viet Hung Nguyen commented on GERONIMO-3693: Anita, Correct me if I'm wrong, but you are saying that min/max values by TimeStatistics and RangeStatistics should be just one value. So we shouldn't be able to display it in a line graph? 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-3702) monitoring client to display a graph when the graph name is clicked on
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 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] Updated: (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:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3702: --- Attachment: geronimo-3702.patch Before committing please execute the following command: svn add client/client-war/src/main/webapp/monitoringPopUpGraph.jsp Thanks, Viet 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 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] Resolved: (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:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3702. Resolution: Fixed Fix Version/s: 2.1 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] Resolved: (GERONIMO-3693) monitoring client does not perform operations correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3693. Resolution: Fixed Fix Version/s: 2.1 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-3693) monitoring client does not perform operations correctly
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 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] Updated: (GERONIMO-3693) monitoring client does not perform operations correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3693: --- Attachment: geronimo-3693.patch 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 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-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_12550287 ] Viet Hung Nguyen commented on GERONIMO-3678: those sql statements should be deleted actually, that was why I did not update the statements. Right now, nothing shows up as being prepopulated in the DB. 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] Resolved: (GERONIMO-3679) Montitoring console should display 'available statistics' in a more organized way
[ https://issues.apache.org/jira/browse/GERONIMO-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3679. Resolution: Fixed Fix Version/s: 2.1 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 Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3679.patch 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] Updated: (GERONIMO-3554) monitoring plugin: client should use an ArrayList instead of a Vector
[ https://issues.apache.org/jira/browse/GERONIMO-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3554: --- Attachment: geronimo-3554.patch monitoring plugin: client should use an ArrayList instead of a Vector - Key: GERONIMO-3554 URL: https://issues.apache.org/jira/browse/GERONIMO-3554 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 Priority: Trivial Attachments: geronimo-3554.patch There are some places in the client code where Vectors are used. ArrayLists would be a better type for this particular instance because of efficiency. Vectors are used for synchronization purposes, which the client does not need to do. ArrayLists would be faster and serve the same purpose in this case. -- 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_12549532 ] Viet Hung Nguyen commented on GERONIMO-3685: I think by leaving all of the graph generation up to the admin to decide which numbers (statistics) to graph, along with the ability to perform mathematical operations (e.g. division) on them, it will give the admin enough freedom to achieve what you have laid out here. I do not think the way the monitoring client displays the TimeStatistics and BoundedRangeStatistics is necessarily wrong, because the monitoring client does not dictate this. It is up to the admin to create the graphs that he/she wishes to view. But I may have missed your point. If so, can you please explain it to me again? Thanks, Viet 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] Resolved: (GERONIMO-3554) monitoring plugin: client should use an ArrayList instead of a Vector
[ https://issues.apache.org/jira/browse/GERONIMO-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3554. Resolution: Fixed Fix Version/s: 2.1 monitoring plugin: client should use an ArrayList instead of a Vector - Key: GERONIMO-3554 URL: https://issues.apache.org/jira/browse/GERONIMO-3554 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 Priority: Trivial Fix For: 2.1 Attachments: geronimo-3554.patch There are some places in the client code where Vectors are used. ArrayLists would be a better type for this particular instance because of efficiency. Vectors are used for synchronization purposes, which the client does not need to do. ArrayLists would be faster and serve the same purpose in this case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
[ https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3676. Resolution: Fixed Fix Version/s: 2.1 monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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-3676.patch The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (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:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3678: --- Attachment: geronimo-3678.patch 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 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] Assigned: (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:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3678: -- Assignee: Viet Hung Nguyen 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 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] Assigned: (GERONIMO-3679) Montitoring console should display 'available statistics' in a more organized way
[ https://issues.apache.org/jira/browse/GERONIMO-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3679: -- Assignee: Viet Hung Nguyen 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 Assignee: Viet Hung Nguyen 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] Resolved: (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:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3678. Resolution: Fixed Fix Version/s: 2.1 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] Updated: (GERONIMO-3679) Montitoring console should display 'available statistics' in a more organized way
[ https://issues.apache.org/jira/browse/GERONIMO-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3679: --- Attachment: geronimo-3679.patch 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 Assignee: Viet Hung Nguyen Attachments: geronimo-3679.patch 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-3675) monitoring client incorrectly pads graph's statistics
monitoring client incorrectly pads graph's statistics - Key: GERONIMO-3675 URL: https://issues.apache.org/jira/browse/GERONIMO-3675 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3675.patch The monitoring client has problems when it attempts to pad some graph's stats with 0's. The result is that only a couple of snapshots are retained at the end of the process. Thus, the graph cannot be drawn at times. Additionally, if the timeframe of a graph is specified to be anywhere from greater than 7 days to less than 30 days, the graph will pull a lot of snapshots, because of the hardcoded number of snapshots for a weekly and monthly timeframe. There needs to be some sort of default number of pulled snapshots so this case will not happen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3675) monitoring client incorrectly pads graph's statistics
[ https://issues.apache.org/jira/browse/GERONIMO-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3675: --- Attachment: geronimo-3675.patch monitoring client incorrectly pads graph's statistics - Key: GERONIMO-3675 URL: https://issues.apache.org/jira/browse/GERONIMO-3675 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3675.patch The monitoring client has problems when it attempts to pad some graph's stats with 0's. The result is that only a couple of snapshots are retained at the end of the process. Thus, the graph cannot be drawn at times. Additionally, if the timeframe of a graph is specified to be anywhere from greater than 7 days to less than 30 days, the graph will pull a lot of snapshots, because of the hardcoded number of snapshots for a weekly and monthly timeframe. There needs to be some sort of default number of pulled snapshots so this case will not happen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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 The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3675) monitoring client incorrectly pads graph's statistics
[ https://issues.apache.org/jira/browse/GERONIMO-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3675. Resolution: Fixed Fix Version/s: 2.1 monitoring client incorrectly pads graph's statistics - Key: GERONIMO-3675 URL: https://issues.apache.org/jira/browse/GERONIMO-3675 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 Priority: Critical Fix For: 2.1 Attachments: geronimo-3675.patch The monitoring client has problems when it attempts to pad some graph's stats with 0's. The result is that only a couple of snapshots are retained at the end of the process. Thus, the graph cannot be drawn at times. Additionally, if the timeframe of a graph is specified to be anywhere from greater than 7 days to less than 30 days, the graph will pull a lot of snapshots, because of the hardcoded number of snapshots for a weekly and monthly timeframe. There needs to be some sort of default number of pulled snapshots so this case will not happen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
[ https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3676: --- Attachment: (was: geronimo-3676.patch) monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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 Attachments: geronimo-3676.patch The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
[ https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3676: --- Attachment: geronimo-3676.patch this new patch also changes a little bit of the UI stuff. It's not important in terms of functionality, but it looks better, and makes more sense monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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 Attachments: geronimo-3676.patch The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3668) monitoring client should encrypt all passwords
[ https://issues.apache.org/jira/browse/GERONIMO-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3668. Resolution: Fixed Fix Version/s: 2.1 monitoring client should encrypt all passwords -- Key: GERONIMO-3668 URL: https://issues.apache.org/jira/browse/GERONIMO-3668 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Fix For: 2.1 Attachments: geronimo-3668.patch We need to encrypt all passwords that are stored in the DB. Right now, they are not encrypted in any way. I suggest we use the EncryptionManager to encrypt/decrypt these passwords. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
[ https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3676: --- Attachment: geronimo-3676.patch monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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 Attachments: geronimo-3676.patch The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
[ https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3676: --- Attachment: geronimo-3676.patch monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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 Attachments: geronimo-3676.patch The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3676) monitoring client throws an error message when there are no graphs present
[ https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3676: --- Attachment: (was: geronimo-3676.patch) monitoring client throws an error message when there are no graphs present -- Key: GERONIMO-3676 URL: https://issues.apache.org/jira/browse/GERONIMO-3676 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 The monitoring client throws displays Error updating View Jetty Web Connector 60 mins null when it is trying to update a Views page without any graphs. This is not the desired behavior. Additionally, when a graph is deleted, the number of graphs in the Views table is not updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3660) monitoring collecting agent needs to have a local interface for the MRC
[ https://issues.apache.org/jira/browse/GERONIMO-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3660. Resolution: Fixed Fix Version/s: 2.1 monitoring collecting agent needs to have a local interface for the MRC --- Key: GERONIMO-3660 URL: https://issues.apache.org/jira/browse/GERONIMO-3660 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-3660.patch The collecting agent (server side) needs to have a local interface. This will allow the collecting agent to get a hold of the ejb to process some data too. As a temporary solution, I used a RemoteInitialContextFactory to get a hold of the EJB which resides locally on that machine. However, Jarek submitted a patch to openEJB which now allows LocalInitialContextFactory to authenticate an EJB lookup, so we need to make use of it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3666) monitoring plugin to provide for a way to access archive data
monitoring plugin to provide for a way to access archive data - Key: GERONIMO-3666 URL: https://issues.apache.org/jira/browse/GERONIMO-3666 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: ubnutu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen We need to modify the Graphs table schema a little bit to account for the archiving option. Additionally, we need to update the edit/add jsp pages to allow this to be configured. Finally, we need to fill the numbers by pulling from the Archived database (on the mrc-server side) in the case where the user is wanting to view the archived data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3666) monitoring plugin to provide for a way to access archive data
[ https://issues.apache.org/jira/browse/GERONIMO-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3666: --- Attachment: geronimo-3666.patch this patch requires an svn delete mrc-server/mrc-ejb/src/main/java/org/apache/geronimo/monitor/SMP.java Thanks, Viet monitoring plugin to provide for a way to access archive data - Key: GERONIMO-3666 URL: https://issues.apache.org/jira/browse/GERONIMO-3666 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: ubnutu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3666.patch We need to modify the Graphs table schema a little bit to account for the archiving option. Additionally, we need to update the edit/add jsp pages to allow this to be configured. Finally, we need to fill the numbers by pulling from the Archived database (on the mrc-server side) in the case where the user is wanting to view the archived data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3554) monitoring plugin: client should use an ArrayList instead of a Vector
[ https://issues.apache.org/jira/browse/GERONIMO-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3554: -- Assignee: Viet Hung Nguyen monitoring plugin: client should use an ArrayList instead of a Vector - Key: GERONIMO-3554 URL: https://issues.apache.org/jira/browse/GERONIMO-3554 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 Priority: Trivial There are some places in the client code where Vectors are used. ArrayLists would be a better type for this particular instance because of efficiency. Vectors are used for synchronization purposes, which the client does not need to do. ArrayLists would be faster and serve the same purpose in this case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3666) monitoring plugin to provide for a way to access archive data
[ https://issues.apache.org/jira/browse/GERONIMO-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3666. Resolution: Fixed Fix Version/s: 2.1 monitoring plugin to provide for a way to access archive data - Key: GERONIMO-3666 URL: https://issues.apache.org/jira/browse/GERONIMO-3666 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: ubnutu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3666.patch We need to modify the Graphs table schema a little bit to account for the archiving option. Additionally, we need to update the edit/add jsp pages to allow this to be configured. Finally, we need to fill the numbers by pulling from the Archived database (on the mrc-server side) in the case where the user is wanting to view the archived data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3668) monitoring client should encrypt all passwords
[ https://issues.apache.org/jira/browse/GERONIMO-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3668: --- Attachment: geronimo-3668.patch monitoring client should encrypt all passwords -- Key: GERONIMO-3668 URL: https://issues.apache.org/jira/browse/GERONIMO-3668 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3668.patch We need to encrypt all passwords that are stored in the DB. Right now, they are not encrypted in any way. I suggest we use the EncryptionManager to encrypt/decrypt these passwords. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3668) monitoring client should encrypt all passwords
monitoring client should encrypt all passwords -- Key: GERONIMO-3668 URL: https://issues.apache.org/jira/browse/GERONIMO-3668 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3668.patch We need to encrypt all passwords that are stored in the DB. Right now, they are not encrypted in any way. I suggest we use the EncryptionManager to encrypt/decrypt these passwords. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3660) monitoring collecting agent needs to have a local interface for the MRC
[ https://issues.apache.org/jira/browse/GERONIMO-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3660: --- Attachment: geronimo-3660.patch monitoring collecting agent needs to have a local interface for the MRC --- Key: GERONIMO-3660 URL: https://issues.apache.org/jira/browse/GERONIMO-3660 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 Attachments: geronimo-3660.patch The collecting agent (server side) needs to have a local interface. This will allow the collecting agent to get a hold of the ejb to process some data too. As a temporary solution, I used a RemoteInitialContextFactory to get a hold of the EJB which resides locally on that machine. However, Jarek submitted a patch to openEJB which now allows LocalInitialContextFactory to authenticate an EJB lookup, so we need to make use of it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3660) monitoring collecting agent needs to have a local interface for the MRC
monitoring collecting agent needs to have a local interface for the MRC --- Key: GERONIMO-3660 URL: https://issues.apache.org/jira/browse/GERONIMO-3660 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 Attachments: geronimo-3660.patch The collecting agent (server side) needs to have a local interface. This will allow the collecting agent to get a hold of the ejb to process some data too. As a temporary solution, I used a RemoteInitialContextFactory to get a hold of the EJB which resides locally on that machine. However, Jarek submitted a patch to openEJB which now allows LocalInitialContextFactory to authenticate an EJB lookup, so we need to make use of it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3659) monitoring client needs to allow the retention period to be configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3659: --- Attachment: geronimo-3659.patch erik and I have decided to take out the configuration during the adding of the server phase. If the user wants to configure the server, he/she will have to go through the edit page monitoring client needs to allow the retention period to be configurable Key: GERONIMO-3659 URL: https://issues.apache.org/jira/browse/GERONIMO-3659 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 Attachments: geronimo-3659.patch The Edit Server and Add Server pages should allow the admin to configure the retention period of the snapshots. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3659) monitoring client needs to allow the retention period to be configurable
[ https://issues.apache.org/jira/browse/GERONIMO-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3659: --- Attachment: (was: geronimo-3659.patch) monitoring client needs to allow the retention period to be configurable Key: GERONIMO-3659 URL: https://issues.apache.org/jira/browse/GERONIMO-3659 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 The Edit Server and Add Server pages should allow the admin to configure the retention period of the snapshots. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3659) monitoring client needs to allow the retention period to be configurable
monitoring client needs to allow the retention period to be configurable Key: GERONIMO-3659 URL: https://issues.apache.org/jira/browse/GERONIMO-3659 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 Attachments: geronimo-3659.patch The Edit Server and Add Server pages should allow the admin to configure the retention period of the snapshots. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
