March 2012 - rhq-users - Fedora Mailing-Lists

by Ian Springer

...are now published to the JBoss Releases repo, e.g. the domain jar is at: https://repository.jboss.org/nexus/content/repositories/releases/org/rhq/... To add RHQ dependencies to your Maven project, add the following repo to either your pom or settings.xml: <repository> <id>jboss-public-repo-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> <snapshots> <enabled>false</enabled> </snapshots> </repository>

11 years, 11 months

4
6
0 / 0

RHQ 4.3.0 failed to register JMX Server

by Aurélio Calegari

Hello, I'm a big fan of RHQ and have been using RHQ 3.0 for a long while. I currently just started migrating to RHQ 4.3.0 and I was testing it. I'm unable to register a JMX Server manually as I used to. Here's my settings: Agent running on a windows box, server on a Fedora. On the windows platform (below its27940), in the inventory, I tried to add a new JMX Service: Which connects well with JVisualVM: But iwhen I hit Finish, I got an error message in the server side and the following stack trace in the agent side: 2012-03-22 08:32:00,971 INFO [ResourceDiscoveryComponent.invoker.daemon-94] (ems.impl.jmx.connection.DConnection)- Found 154 MBeans - starting load... 2012-03-22 08:32:00,986 ERROR [WorkerThread#0[10.35.12.74:46690]] (rhq.core.pc.inventory.InventoryManager)- Manual add failed for resource of type [JMX Server] and parent resource id [10001] java.lang.reflect.UndeclaredThrowableException at $Proxy73.discoverResource(Unknown Source) at org.rhq.core.pc.inventory.InventoryManager.discoverResource(InventoryManager.java:357) at org.rhq.core.pc.inventory.InventoryManager.manuallyAddResource(InventoryManager.java:687) 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:597) at org.rhq.enterprise.communications.command.impl.remotepojo.server.RemotePojoInvocationCommandService.execute(RemotePojoInvocationCommandService.java:184) 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:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288) at $Proxy0.execute(Unknown Source) at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290) at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) Caused by: java.lang.Exception: Discovery component invocation failed. at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:296) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to [Ljava.lang.Object; at javax.management.openmbean.TabularDataSupport.get(TabularDataSupport.java:260) at org.rhq.plugins.jmx.JMXDiscoveryComponent.getJavaVersion(JMXDiscoveryComponent.java:267) at org.rhq.plugins.jmx.JMXDiscoveryComponent.discoverResource(JMXDiscoveryComponent.java:247) 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:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:292) ... 5 more Do you have any thoughts? Regards Aurelio

12 years, 3 months

1
1
0 / 0

JMX plugin issue

by LUND, CARSTEN (CARSTEN)

I have some issue connecting to Java Process using the JMX Plugin. I tried both RHQ 4.0.1 and 4.3 and I get the stack trace below (from 4.3). Using jdk1.6.0_23 for both RHQ agent and Java process. When using jconsole I have no issue connecting. I earlier (it may have been using 4.0.0) remember being able to do it without any trouble. Thanks, Carsten java.lang.reflect.UndeclaredThrowableException at $Proxy80.discoverResource(Unknown Source) at org.rhq.core.pc.inventory.InventoryManager.discoverResource(InventoryManager.java:357) at org.rhq.core.pc.inventory.InventoryManager.manuallyAddResource(InventoryManager.java:687) 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:597) at org.rhq.enterprise.communications.command.impl.remotepojo.server.RemotePojoInvocationCommandService.execute(RemotePojoInvocationCommandService.java:184) 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:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288) at $Proxy0.execute(Unknown Source) at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290) at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) Caused by: java.lang.Exception: Discovery component invocation failed. at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:296) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.RuntimeException: Failed to connection to connector address [service:jmx:rmi:///jndi/rmi://localhost:5555/jmxrmi]. at org.rhq.plugins.jmx.JMXDiscoveryComponent.discoverResource(JMXDiscoveryComponent.java:241) 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:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:292) ... 5 more Caused by: org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Invalid connection type - class [LocalVMTypeDescriptor] not found. at org.rhq.plugins.jmx.util.ConnectionProviderFactory.createConnectionProvider(ConnectionProviderFactory.java:45) at org.rhq.plugins.jmx.JMXDiscoveryComponent.discoverResource(JMXDiscoveryComponent.java:236) ... 10 more

12 years, 3 months

2
3
0 / 0

The correct backfilling behavior?

by Jay Shaughnessy

Coming soon there will be some enhancements to Availability handling. See http://rhq-project.org/display/RHQ/Design-Availability+Checking for more. In a recent internal demo we starting debating what the "right" RHQ behavior should be for backfilling agents. The server periodically checks for "suspect" agents. Suspect agents are agents that the server thinks should be up, but that have not contacted the server in a while. If an agent does not contact the server for a long enough period then the suspect agent is considered down and agent is "backfilled". In currently release versions backfilling is the act of assigning the platform resource for that agent DOWN. And also all of its children DOWN. In the current development version we introduce a new availability type, UNKNOWN, which represents the fact that we don't actually know what the resource's availability is because the agent is not reporting to us. So, in the development version backfilling currently assigns the platform DOWN and all of its children UNKNOWN. This reflects the fact that we really don't know what the availability of the monitored resources is when the agent is not reporting. The question is whether this goes far enough? It was suggested that perhaps the platform should also be set to UNKNOWN and the the RHQ Agent Resource (and its children) should be set DOWN, assuming it's actually in inventory. Logically, the platform/machine may not actually be DOWN. But its avail status has historically been a reflection of RHQ monitoring on the platform. In fact, if it is not set DOWN when the agent is DOWN, then it will never be set DOWN, only UP and UNKNOWN. The RHQ Agent resource is actually a resource like any other, a monitored AS server. Should it be treated differently? I think the real question is what works best for user's needs, particularly alerting. My current opinion is that it should stay as is (DOWN platform/UNKNOWN children), as it allows the platform resource to be marked down and placed in the problem resources portlet. And I don't see real value in special-casing the RHQ Agent resource. But, when thinking about this, realize that you can now alert on Goes NOT UP, so you could actually alert on a platform being set to UNKNOWN. Thoughts?

12 years, 3 months

2
1
0 / 0

Introducing RHQ Db Setup tool

by Romain Pelisse

Hi all, As I've been installing and reinstalling RHQ here and there, I've grown quite bored of always having to manually input all the database parameter manually. More than that, I feel that for large setup (I mean several hundreds of server and services to monitor) it will be crucial to easily defined "domain" and fire up - in automated manner, new instance of RHQ (to take care of new domain for instance). For all those reason, I wrapped up a rather simple java class<https://github.com/rpelisse/rhq-db-setup/blob/master/src/main/java/org/re...>using HtmlUnit <http://mvnrepository.com/artifact/htmlunit/htmlunit> to "trigger" the installation. It is package as a simple jar (actually, a "fat jar" meaning that all required dependencies are within the jar), and it is designed to be used in command line within a script: $ java -cp ./target/jon-setup-1.0-jar-with-dependencies.jar org.redhat.jboss.rqh.autodb.RHQDatabaseInstaller -s http://localhost:7080/installer/start.jsf -u rhqauto -p rhqautopass -d jdbc:postgresql://postgresql-8.4:5432/rhqautoinstall -v Setting up database for RHQ Server running on: http://localhost:7080/installer/start.jsf Database URL: jdbc:postgresql://postgresql-8.4:5432/rhqautoinstall Database Username: rhqauto Database Password: rhqautopass Database Driver: org.postgresql.Driver Database XA Datasource: org.postgresql.xa.PGXADataSource ... Waiting for installer to finish... [execution time: 1601ms] Finished with HTTP code:200 Waiting for RHQ Server to finish its installation [3000ms] ... DB setup for server http://localhost:7080/installer/start.jsf done. This version has been tested on Linux against a RHQ 4.x setup with Postgres 8.4, but it should work transparently with Oracle or Windows (well, as far as Window works). It would probably also work with RHQ 3.x, with some tweaking (if you do those tweaks, please publish and pull them). I've licensed this project under LGPL, so we should be able to do pretty much whatever you want, as long as you offer back any changes. @RHQ developers: assuming users find this useful, you should NOT change the installer's form name or id in the coming release - unless, of course, you fixed this issue and offer a clean mechanism to setup RHQ in complete automated manner. Source code: https://github.com/rpelisse/rhq-db-setup Technical notes: For those who cares, I've managed to do this program in one (size-reasonable) class by using cool libs such as Lombok<http://projectlombok.org/>, JCommander <http://jcommander.org> and JSoup <http://Jsoup.org>. -- Romain PELISSE, *"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett* http://belaran.eu/wordpress/belaran

12 years, 3 months

2
2
0 / 0

Participation in Google Summer of Code 2012

by Heiko W.Rupp

Hi, JBoss.org and Fedora have been accepted into Google Summer of code. RHQ has registered several ideas with jboss.org - see https://community.jboss.org/wiki/GSOC12Ideas So if you want to work on RHQ as a GSoC project you can apply at the JBoss organization. For this you do not need to pick an entry from the list provided, but you can also bring up your own topics. If you have questions, please contact me Heiko -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht München HRB 153243 Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera

12 years, 3 months

1
0
0 / 0

JBossAS6 WAR monitoring

by Herbert de Borba

Hey all, I'm trying to monitor JBossAS 6 with RHQ 4.1 and achieving partial success on the matter. While RHQ server recognizes the JBossAS6 server, it fails on showing deployed Tomcat applications and it's respective metrics. I'm attaching two screenshots, "RHQJBossAS6-pic1.png" shows JBossAS6 being monitored, while "RHQJBossAS6-pic2.png" shows a JBossAS 4.2.1 GA. On the first picture, there is a "JBoss Web" node, but I can't find the web applications on there. The 4.2.1GA one shows the "Applications" node with it's deployed WAR on there. What can I do to monitor JBossAS6 deployed WARs? Regards. -- Herbert Mattei de Borba herbertdeborba(a)gmail.com

12 years, 3 months

2
3
0 / 0

RHQ 4.3 Released

by Stefan Negrea

The RHQ team is pleased to announce the immediate availability of RHQ 4.3 You can read the release notes here: http://rhq-project.org/display/RHQ/Release+Notes+4.3.0 Downloads are available from SourceForge: http://sourceforge.net/projects/rhq/files/rhq/rhq-4.3.0/ Stefan (on behalf of the RHQ team)

12 years, 3 months

4
6
0 / 0

Fwd: RHQ 4.3 Released

by Herbert de Borba

Is it possible to force the language on server? I know it's possible on browser but it's not desirable, because all pages will be affected. Regards. 2012/3/8 Herbert de Borba <herbertdeborba(a)gmail.com> > Yes this seems to be the case, rhq is in pt-BR after the update here in > our pt-BR browsers. > Thanks for explaining. > > > 2012/3/8 Ian Springer <ian.springer(a)redhat.com> > >> Looking at the code it looks like this could occur if you're using a >> locale other than English. Is that the case? >> >> private int populateConfigurationValue(DashboardPortlet >> storedPortlet, String propertyKey, String defaultKeyValue) { >> int configuredValue; >> if ((storedPortlet != null) && >> (storedPortlet.getConfiguration().getSimple(propertyKey) != null)) { >> //retrieve and translate to int >> String retrieved = >> storedPortlet.getConfiguration().getSimple(propertyKey).getStringValue(); >> if (retrieved.equals(MSG.common_label_unlimited())) { >> configuredValue = -1; >> } else { >> configuredValue = Integer.parseInt(retrieved); >> } >> } else {//create setting if not already there. >> storedPortlet.getConfiguration().put(new >> PropertySimple(propertyKey, defaultKeyValue)); >> configuredValue = -1; >> } >> return configuredValue; >> } >> >> In a non-English locale, MSG.common_label_unlimited() would have a value >> of "unlimited_in_some_non_English_language". But if the value currently >> stored in your preferences was "unlimited", then the else block would get >> executed and Integer.parseInt("unlimited") would be called. >> >> We shouldn't be storing localized messages as configuration values. In >> this case, we should just store -1 as the value. >> >> I think we can come up with some SQL you could use to workaround this. >> Stay tuned. >> >> >> On 03/08/2012 03:38 PM, Herbert de Borba wrote: >> >> Installed it to update a running 4.1 server, and the following error is >> shown while trying to access the dashboard. The dashboard itself is blank. >> >> java.lang.NumberFormatException:For input string: "unlimited" >> >> >> --- STACK TRACE FOLLOWS --- >> For input string: "unlimited" >> at Unknown.java_lang_Exception_Exception__Ljava_lang_String_2V(Unknown Source) >> at Unknown.java_lang_RuntimeException_RuntimeException__Ljava_lang_String_2V(Unknown Source) >> >> >> at Unknown.java_lang_IllegalArgumentException_IllegalArgumentException__Ljava_lang_String_2V(Unknown Source) >> at Unknown.java_lang_NumberFormatException_NumberFormatException__Ljava_lang_String_2V(Unknown Source) >> >> >> at Unknown.java_lang_Number__1_1parseAndValidateInt__Ljava_lang_String_2IIII(Unknown Source) >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_portlets_recent_problems_ProblemResourcesPortlet_$populateConfigurationValue__Lorg_rhq_enterprise_gui_coregui_client_dashboard_portlets_recent_problems_ProblemResourcesPortlet_2Lorg_rhq_core_domain_dashboard_DashboardPortlet_2Ljava_lang_String_2Ljava_lang_String_2I(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_portlets_recent_problems_ProblemResourcesPortlet_$configure__Lorg_rhq_enterprise_gui_coregui_client_dashboard_portlets_recent_problems_ProblemResourcesPortlet_2Lorg_rhq_enterprise_gui_coregui_client_dashboard_PortletWindow_2Lorg_rhq_core_domain_dashboard_DashboardPortlet_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_portlets_recent_problems_ProblemResourcesPortlet_configure__Lorg_rhq_enterprise_gui_coregui_client_dashboard_PortletWindow_2Lorg_rhq_core_domain_dashboard_DashboardPortlet_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_PortletFactory_buildPortlet__Ljava_lang_String_2Lorg_rhq_enterprise_gui_coregui_client_dashboard_PortletWindow_2Lorg_rhq_core_domain_dashboard_DashboardPortlet_2Lorg_rhq_core_domain_common_EntityContext_2Lorg_rhq_enterprise_gui_coregui_client_dashboard_Portlet_2(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_PortletWindow_onInit__V(Unknown Source) >> at Unknown.com_smartgwt_client_widgets_BaseWidget_doInit__V(Unknown Source) >> at Unknown.com_smartgwt_client_widgets_Window_create__Lcom_google_gwt_core_client_JavaScriptObject_2(Unknown Source) >> >> >> at Unknown.com_smartgwt_client_widgets_BaseWidget_$getOrCreateJsObj__Lcom_smartgwt_client_widgets_BaseWidget_2Lcom_google_gwt_core_client_JavaScriptObject_2(Unknown Source) >> at Unknown.com_smartgwt_client_widgets_layout_Layout_$addMember__Lcom_smartgwt_client_widgets_layout_Layout_2Lcom_smartgwt_client_widgets_Canvas_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_PortalLayout_$addPortletWindow__Lorg_rhq_enterprise_gui_coregui_client_dashboard_PortalLayout_2Lorg_rhq_enterprise_gui_coregui_client_dashboard_PortletWindow_2ILorg_rhq_enterprise_gui_coregui_client_dashboard_PortalColumn_2(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_DashboardView_$loadPortletWindows__Lorg_rhq_enterprise_gui_coregui_client_dashboard_DashboardView_2V(Unknown Source) >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_DashboardView_$buildPortlets__Lorg_rhq_enterprise_gui_coregui_client_dashboard_DashboardView_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_DashboardView_onInit__V(Unknown Source) >> at Unknown.com_smartgwt_client_widgets_BaseWidget_doInit__V(Unknown Source) >> at Unknown.com_smartgwt_client_widgets_layout_VLayout_create__Lcom_google_gwt_core_client_JavaScriptObject_2(Unknown Source) >> >> >> at Unknown.com_smartgwt_client_widgets_BaseWidget_$getOrCreateJsObj__Lcom_smartgwt_client_widgets_BaseWidget_2Lcom_google_gwt_core_client_JavaScriptObject_2(Unknown Source) >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_DashboardsView_$updateDashboards__Lorg_rhq_enterprise_gui_coregui_client_dashboard_DashboardsView_2Ljava_util_List_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_dashboard_DashboardsView$1$1_onPermissionsLoaded__Ljava_util_Set_2V(Unknown Source) >> at Unknown.org_rhq_enterprise_gui_coregui_client_PermissionsLoader$1_$onSuccess__Lorg_rhq_enterprise_gui_coregui_client_PermissionsLoader$1_2Ljava_util_Set_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_PermissionsLoader$1_onSuccess__Ljava_lang_Object_2V(Unknown Source) >> at Unknown.com_google_gwt_user_client_rpc_impl_RequestCallbackAdapter_$onResponseReceived__Lcom_google_gwt_user_client_rpc_impl_RequestCallbackAdapter_2Lcom_google_gwt_http_client_Request_2Lcom_google_gwt_http_client_Response_2V(Unknown Source) >> >> >> at Unknown.org_rhq_enterprise_gui_coregui_client_util_rpc_TrackingRequestCallback_onResponseReceived__Lcom_google_gwt_http_client_Request_2Lcom_google_gwt_http_client_Response_2V(Unknown Source) >> at Unknown.com_google_gwt_http_client_Request_$fireOnResponseReceived__Lcom_google_gwt_http_client_Request_2Lcom_google_gwt_http_client_RequestCallback_2V(Unknown Source) >> >> >> at Unknown.com_google_gwt_http_client_RequestBuilder$1_onReadyStateChange__Lcom_google_gwt_xhr_client_XMLHttpRequest_2V(Unknown Source) >> at Unknown.anonymous(Unknown Source) >> at Unknown.com_google_gwt_core_client_impl_Impl_apply__Ljava_lang_Object_2Ljava_lang_Object_2Ljava_lang_Object_2Ljava_lang_Object_2(Unknown Source) >> >> >> at Unknown.com_google_gwt_core_client_impl_Impl_entry0__Ljava_lang_Object_2Ljava_lang_Object_2Ljava_lang_Object_2Ljava_lang_Object_2(Unknown Source) >> at Unknown.anonymous(Unknown Source) >> at Unknown.anonymous(Unknown Source) >> >> Regards. >> >> >> 2012/3/7 Stefan Negrea <snegrea(a)redhat.com> >> >>> >>> The RHQ team is pleased to announce the immediate availability of RHQ 4.3 >>> >>> You can read the release notes here: >>> http://rhq-project.org/display/RHQ/Release+Notes+4.3.0 >>> >>> Downloads are available from SourceForge: >>> http://sourceforge.net/projects/rhq/files/rhq/rhq-4.3.0/ >>> >>> >>> >>> Stefan (on behalf of the RHQ team) >>> >>> _______________________________________________ >>> rhq-users mailing list >>> rhq-users(a)lists.fedorahosted.org >>> https://fedorahosted.org/mailman/listinfo/rhq-users >>> >> >> >> >> -- >> Herbert Mattei de Borba >> herbertdeborba(a)gmail.com >> >> >> >> _______________________________________________ >> rhq-users mailing listrhq-users@lists.fedorahosted.orghttps://fedorahosted.org/mailman/listinfo/rhq-users >> >> >> >> -- >> Ian Springer >> Principal Software Developer >> JBoss Operations Network >> Red Hatian.springer(a)redhat.com >> >> > > > -- > Herbert Mattei de Borba > herbertdeborba(a)gmail.com > > -- Herbert Mattei de Borba herbertdeborba(a)gmail.com -- Herbert Mattei de Borba herbertdeborba(a)gmail.com

12 years, 3 months

1
0
0 / 0

monitoring custom data from database queries

by John Mazzitelli

I just posted a blog on a little known feature that is pretty cool. I thought it was neat - I figured it has a lot of uses, so why not point it out to people in case they find it can help them: http://management-platform.blogspot.com/2012/03/monitoring-custom-data-fr... Its essentially a way to collect metric data from simple SQL queries. But because its a "normal" metric, you can track it historically over time on the graph view, you can alert on, etc.

12 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

rhq-users March 2012