Deploying but not starting?

[holeinone]

Hi lemongrass team,

I deployed java-monitor.war ut to no avail.
It looks like the war file is deployed but never starts collecting stats?
Name
CollectorServlet
Servlet Statistics:
Min (ms)|Max (ms)Average (ms)|Total (ms)# Invocations
9223372036854775807|0|NaN|0|0

I'm deploying to jboss 4.2.3GA by copying the java-monitor.war file to the default/deploy/ directory.

The above figures are displayed by the web-console of that jboss instance. Thereby, for me, prove that the .war file is actually deployed.

[kjkoster]

Dear holeinone,

Hmm. That's strange. No errors in the logs?

What version of Java do you use? You need 1.5+.

No firewalls and http proxies between your server and mine?
Kees Jan

[holeinone]

java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Server VM (build 1.5.0_14-b03, mixed mode).
There are firewalls between our domains, but I am able to ping as our firewall does not restrict outgoing traffic.

[kjkoster]

Dear honeinone,

Hmm. There could be a number of situations. 1) Perhaps JBoss suppresses the error messages that the probe tries to log. 2) Maybe the auto-start flag is not honoured for some reason?

Are you sure there is nothing in the logs?

Kees Jan

[holeinone]

1) Possible but not likely. I suppress a lot of logging because the system running on theta instance can be very verbose. Threshold is set on INFO level (log4j)
<!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
<category name="org.apache">
<priority value="WARN"/>
</category>

<!-- Limit the jacorb category to WARN as its INFO is verbose -->
<category name="jacorb">
<priority value="WARN"/>
</category>

<!-- HP:Limit the hibernate category to WARN as its DEBUG is verbose -->
<category name="org.hibernate">
<priority value="WARN"/>
</category>

<!-- HP:Limit the JBOSS category to INFO as its DEBUG is verbose -->
<category name="org.jboss">
<priority value="WARN"/>
</category>


<!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
<category name="org.jgroups">
<priority value="WARN"/>
</category>

<!-- Limit the org.quartz category to INFO as its DEBUG is verbose -->
<category name="org.quartz">
<priority value="WARN"/>
</category>

<!-- Limit the JSR77 categories -->
<category name="org.jboss.management">
<priority value="WARN"/>
</category>

<!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is verbose -->
<category name="org.jboss.serial">
<priority value="WARN"/>
</category>

2) The timer is already heavily used. Maybe this is why? (dont think so)

grep -i "monitor" server.log => NULL
Linux version 2.6.18-92.1.13.el5 (mockbuild@builder16.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed Sep 24 19:33:52 EDT 2008

[kjkoster]

Dear holeinone,

I just downloaded and deployed the probe in JBoss and I can confirm that your problem is a bug in my code. The probe thinks it is inside Tomcat and waits for some Tomcat-specific connectors to load. Since JBoss renames these, the wait never ends.

I will fix this issue shortly. Thank you for bringing this to my attention.

Kees Jan

[holeinone]

You found it, excellent!

H

[kjkoster]

Dear holeinone,

I fixed the code and uploaded a new version of the probe. Could you please delete your old probes and download a new one from the forum front page?

I took a little extra time to clean out some defunct JBoss detection code, and I learned a little more about the JMX query language.

At any rate, probes downloaded from now on should work well in JBoss. Could you please let me know if it does?

Kees Jan

PS. One issue remains that some items are not detected properly. That should be fixed in the next full release of Java-monitor, in a week or two.

[holeinone]

Congratulations, works like a charm