DWR in Monitorplugin fails, causes statistics to be inaccessible


Statistics are no longer shown in the Monitoring plugin.

Rolling back the plugin to code to SVN revision 11291 does not solve the problem.

DWR fails with these messages, which will be logged to Error when a user tries to access http://localhost:9090/plugins/monitoring/stats-dashboard.jsp




Guenther Niess
January 30, 2010, 12:53 AM

Hi slicer321, feel free to debug and write a patch, that fixes this issue with 1.1.4. I would really like to review it. I for myself don't care much about the monitoring plugin, but want to push the next release and have a working plugin for the most plattforms.

Guenther Niess
January 30, 2010, 12:44 AM

Ok, I downgraded the DWR version to 1.1.3 which works fine for me, so I think we don't need to go back to 1.1.1. Please report if someone has an issue with that.

B Eagle
January 30, 2010, 12:43 AM

To confirm previous findings, I do see the error messages in the error.log file, but in contrast the stats-dashboard.jsp is displays properly on my server, e.g Server->Statistics does show graphs "Current Users", "Active Conversations", and so properly. Was there a missing function as well? It may be useful to debug this so that dwr can be updated to latest, but at the same time I believe all the other dependent plugins work fine without updating. My configuration is as follows. Also note I did update dwr.jar everywhere to 1.1.4 to be consistent across all the plugins.

Openfire 3.6.3, rev.10959.
Monitoring Service 1.1.1
Fastpath Service 4.1.0
Fastpath Webchat 4.0.0
Search 1.4.3

Dwr.jar 1.1.4
Jetty libs 6.1.18
Xstream 1.3.1
Base OS is FreeBSD 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 amd64.
Java JDK version is Diablo Java(TM) SE Runtime Environment (build 1.6.0_07-b02).

Guus der Kinderen
January 29, 2010, 11:34 PM

If the original version (1.1.1) doesn't have the problem, I vote for rolling back.

Guenther Niess
January 29, 2010, 5:31 AM

Oh, I'm not sure about the assumption of the two identical DWR libs, it seems before they were also identical (version 1.1.1). But adding the monitoring libs to the ClassLoader of Openfire would fix the issue.

Your pinned fields
Click on the next to a field label to start pinning.


Gaston Dombiak


Guus der Kinderen