Monday, May 23, 2011

RHQ 4.0.1 released

RHQ logo wallpaper

 

 

The RHQ team has just released version 4.0.1 of its server management and monitoring software.

This release is a bugfix release over RHQ 4 which was released earlier this month. The biggest change is the addition of support for IE 7 and 8, as well as the fix for a memory leak that came from how JBossAS internally has set up the pools for MDBs and SLSBs.

You can browse the full release notes, which also contain a link to the download.

Jay Shaughnessy has written a blog post on what was necessary with SmartGWT to get it to work on IE7 and 8.

Wednesday, May 04, 2011

And I thought JBossAS had long stack traces ...

05-04 21:49:32.865: ERROR/AndroidRuntime(10036): FATAL EXCEPTION: main        java.lang.IndexOutOfBoundsException: Invalid index 12, size is 12        at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:255)        at java.util.ArrayList.get(ArrayList.java:308)        at de.bsd.zwitscher.StatusAdapter.getView(StatusAdapter.java:79)        at android.widget.AbsListView.obtainView(AbsListView.java:1943)        at android.widget.ListView.makeAndAddView(ListView.java:1756)        at android.widget.ListView.fillDown(ListView.java:656)        at android.widget.ListView.fillSpecific(ListView.java:1314)        at android.widget.ListView.layoutChildren(ListView.java:1587)        at android.widget.AbsListView.onLayout(AbsListView.java:1794)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1542)        at android.widget.LinearLayout.layoutHorizontal(LinearLayout.java:1527)        at android.widget.LinearLayout.onLayout(LinearLayout.java:1316)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.FrameLayout.onLayout(FrameLayout.java:400)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1542)        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1403)        at android.widget.LinearLayout.onLayout(LinearLayout.java:1314)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.FrameLayout.onLayout(FrameLayout.java:400)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.FrameLayout.onLayout(FrameLayout.java:400)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1542)        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1403)        at android.widget.LinearLayout.onLayout(LinearLayout.java:1314)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.FrameLayout.onLayout(FrameLayout.java:400)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.FrameLayout.onLayout(FrameLayout.java:400)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1542)        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1403)        at android.widget.LinearLayout.onLayout(LinearLayout.java:1314)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.widget.FrameLayout.onLayout(FrameLayout.java:400)        at android.view.View.layout(View.java:9330)        at android.view.ViewGroup.layout(ViewGroup.java:3795)        at android.view.ViewRoot.performTraversals(ViewRoot.java:1201)        at android.view.ViewRoot.handleMessage(ViewRoot.java:1944)        at android.os.Handler.dispatchMessage(Handler.java:99)        at android.os.Looper.loop(Looper.java:126)        at android.app.ActivityThread.main(ActivityThread.java:3997)        at java.lang.reflect.Method.invokeNative(Native Method)        at java.lang.reflect.Method.invoke(Method.java:491)        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)        at dalvik.system.NativeStart.main(Native Method)

 

 

RHQ 4 - alerting on call time data

One of the features of RHQ 4 (I think it was hidden in RHQ 3 already) is alerting on Call time data (aka Response time data). This code was contributed by Frank Brüseke quite some time ago (thanks again, Frank).

By default that feature is hidden (inRHQ 3 only; RHQ 4 has it enabled by default), so you first have to enable it in the system settings:

 

Bildschirmfoto 2011 05 04 um 09 54 41
System settings
Now (and don't forget to enable the gathering of call time data) when you go to a resource that has calltime data (e.g. stateless session beans or web apps), you can define alerts on call time data. In the first step, you select one of the two available options:
Bildschirmfoto 2011 05 04 um 10 14 54
Add alert condition
Here you can select crossing/matching of a threshold or change of a calltime value. In the last step you need to provide the call time entry to check and some reference values:
Bildschirmfoto 2011 05 04 um 10 15 05
Select condition values and comparator
In the last section you can also give a regular expression on what to alert; this allows you limit e.g. the methods that will be checked for SLSBs or the URLs for web applications.
As always: please provide feedback. When the feedback is positive, we may un-hide this feature for future versions of RHQ.

 

RHQ 4 - alerting on call time data

One of the features of RHQ 4 (I think it was hidden in RHQ 3 already) is alerting on Call time data (aka Response time data). This code was contributed by Frank Brüseke long quite some time ago.

By default that feature is hidden, so you first have to enable it in the system settings:

Bildschirmfoto 2011 05 04 um 09 54 41
System settings
Now (and don't forget to enable the gathering of call time data) when you go to a resource that has calltime data (e.g. stateless session beans or web apps), you can define alerts on call time data. In the first step, you select one of the two available options:
Bildschirmfoto 2011 05 04 um 10 14 54
Add alert condition
Here you can select crossing/matching of a threshold or change of a calltime value. In the last step you need to provide the call time entry to check and some reference values:
Bildschirmfoto 2011 05 04 um 10 15 05
Select condition values and comparator
In the last section you can also give a regular expression on what to alert; this allows you limit e.g. the methods that will be checked for SLSBs or the URLs for web applications.
As always: please provide feedback. When the feedback is positive, we may un-hide this feature for future versions of RHQ.

Monday, May 02, 2011

RHQ 4 released

RHQ logo wallpaper

The RHQ team is proud to have released version 4.0 of RHQ monitoring and management project after 10 month of hard work. Most prominent change is the huge rewrite of most parts of the GUI in GWT.

 

Bildschirmfoto 2011 04 28 um 21 02 19

 

New features include:

  • new SmartGWT-based GUI
  • support for Postgres 9.0
  • support for deleting Agent plugins
  • support for executing an RHQ CLI script when an alert fires (for more info, see this blog)
  • improved authorization for content repositories - public/private repos, repo owners, and MANAGE_REPOSITORIES priv
  • Much improved MySQL agent-plugin (by Steve Milidge)
  • New logfile alert-sender (by Steve Milidge)

Note that Internet Explorer is not fully supported (we expect to fully support it soon) - FireFox and Webkit-based browsers are fine.

You can browse the release notes to see a more detailed list of changes, new features and also known issued.

The binaries are available from SourceForge.