Java-Monitor not working on tomcat 6.0

[irshadkhan84]

Hi All,

I am new on this site. Please help me

I have downloaded java-monitor from http://java-monitor.com site and installed according to given instruction on Tomcat 6.0.But when i try see output it gives following Error:

Jul 22, 2009 10:09:46 PM com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception (it will retry in five minutes): Connection reset by peer: connect
java.net.SocketException: Connection reset by peer: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:122)
at com.javamonitor.Collector.init(Collector.java:157)
at com.javamonitor.Collector.push(Collector.java:74)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:131)
at java.lang.Thread.run(Unknown Source)

[kjkoster]

Dear irshadkhan84,

Does the host ever show up in Java-monitor and then lose the connectiont, or does it never connect at all?

Are you behind an HTTP proxy?

Kees Jan

[irshadkhan84]

Dear Kees Jaan

Thanks.....

No, it is not showing and shows following message on Java-Monitor

This panel shows the status of the Java application servers that you monitor on-line using Java-monitor. At this time, you do not have any servers that are being monitored. To get started, download your probe and follow the installation instructions.

Yes I am behind a HTTP Proxy Server.

please reply as soon as possible.....

regards
Irshad Khan


Dear irshadkhan84,

Does the host ever show up in Java-monitor and then lose the connectiont, or does it never connect at all?

Are you behind an HTTP proxy?

Kees Jan

[kjkoster]

Dear Irshad,

From what you tell me I think that your local network configuration is blocking the traffic. The default behaviour of the Java-monitor probe is to connect to the Java-monitor servers directly. It does not know that it has to use a proxy server to reach them.

What you can try is to configure your JVM to connect via the proxy server (http://java.sun.com/javase/6/docs/technotes/guides/net/proxies.html) as shown below:

java -Dhttp.proxyHost=proxy.example.com -Dhttp.proxyPort=8080 -Dhttp.noProxyHosts=”localhost|127.0.0.1” ...

Of course, you have to fill in your own hosts and ports here. :)

If this is a Tomcat server on UNIX, you can also try this before you start Tomcat:

% JAVA_OPTS="${JAVA_OPTS} -Dhttp.proxyHost=proxy.example.com -Dhttp.proxyPort=8080 -Dhttp.noProxyHosts=localhost|127.0.0.1"
% export JAVA_OPTS
% bin/startup.sh


Kees Jan

[irshadkhan84]

Dear Kees Jan,

I have tried with what you have suggested.but i am able to see any output
also at this time it was not throws any exception.it directly goes java-monitor.com

please suggest me what is the problem?

Regards
Irshad

Dear Irshad,

From what you tell me I think that your local network configuration is blocking the traffic. The default behaviour of the Java-monitor probe is to connect to the Java-monitor servers directly. It does not know that it has to use a proxy server to reach them.

What you can try is to configure your JVM to connect via the proxy server (http://java.sun.com/javase/6/docs/technotes/guides/net/proxies.html) as shown below:

java -Dhttp.proxyHost=proxy.example.com -Dhttp.proxyPort=8080 -Dhttp.noProxyHosts=”localhost|127.0.0.1” ...

Of course, you have to fill in your own hosts and ports here. :)

If this is a Tomcat server on UNIX, you can also try this before you start Tomcat:

% JAVA_OPTS="${JAVA_OPTS} -Dhttp.proxyHost=proxy.example.com -Dhttp.proxyPort=8080 -Dhttp.noProxyHosts=localhost|127.0.0.1"
% export JAVA_OPTS
% bin/startup.sh


Kees Jan

[kjkoster]

Dear Irshad,

I investigated the problem you reported and it looks like you have uncovered a bug in Java-monitor's probe. It did not actually honour the settings that I gave you. Thank you for bringing this problem to our attention.

I have just updated the probe to follow these configuration properties. Could you please delete the old probe you have on your system and download a fresh one (http://java-monitor.com/lemongrass/java-monitor-probe.zip), then extract and install it as before.

This new version of the probe should follow the http.proxyHost and http. proxyPort system properties. If it works, it prints a line like this:

Jul 23, 2009 11:26:42 PM com.javamonitor.Collector findProxy
INFO: using proxy HTTP @ localhost/127.0.0.1:80

Would you mind trying that for me, please?
Kees Jan

[irshadkhan84]

Dear Kees Jan,

Thanks for reply.I am using windows machine and tomcat 6.0.Is there any portability problem with windows machine.
I have tried with new updated probe with http.proxyHost and http. proxyPort system properties.
But it is giving following error:

Jul 24, 2009 9:41:16 AM com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception (it will retry in five minutes): Connection reset by peer: connect
java.net.SocketException: Connection reset by peer: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:133)
at com.javamonitor.Collector.init(Collector.java:168)
at com.javamonitor.Collector.push(Collector.java:85)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:131)
at java.lang.Thread.run(Unknown Source)

With regards
Irshad

[kjkoster]

Dear Irshad,

If this is a Windows service, please check that you have configured the options in the right place. As you can read here, this is not straightforward (http://java-monitor.com/forum/showthread.php?t=205).

Also, did you see the message like the one below in the logs:

Jul 23, 2009 11:26:42 PM com.javamonitor.Collector findProxy
INFO: using proxy HTTP @ localhost/127.0.0.1:80

If that message is missing, Tomcat did not pick up on the proxy settings and the Java-monitor probe can't use them.

Kees Jan

[irshadkhan84]

Dear Kees Jan,

I have tried with http.proxyHost and http.proxyPort Apche in Tomcat properties where other java option like

-Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 6.0
-Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 6.0
-Djava.endorsed.dirs=C:\Program Files\Apache Software Foundation\Tomcat 6.0\common\endorsed
-Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat 6.0\temp
-Djava.util.logging.manager=org.apache.juli.ClassLo aderLogManager
-Djava.util.logging.config.file=C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\logging.properties

are set.No i have not seen messgae instead i have seen following exception:

Jul 24, 2009 3:55:44 PM com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception (it will retry in five minutes): Connection reset by peer: connect
java.net.SocketException: Connection reset by peer: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:133)
at com.javamonitor.Collector.init(Collector.java:168)
at com.javamonitor.Collector.push(Collector.java:85)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:131)
at java.lang.Thread.run(Unknown Source)

regards
Irshad

[kjkoster]

Dear Irshad,

The fact that it does not say "INFO: using proxy HTTP @ localhost/127.0.0.1:80" means that Tomcat does not see the proxy config settings you did.

Hummm... Either you have not set the properties in the right place (I'm no Windows guy, so I cannot help you there), or maybe you have not restarted Tomcat with the new settings. I cannot tell from here.

Could you please try running Tomcat in a DOS box and setting the options on the command line?

Kees Jan

[irshadkhan84]

Dear Kees Jan,

Ok I will try on Linux machine and get back to you.Thanks for help.

regads
Irshad

[smhaller]

Hi Irshad and Jan,

i get very similar error message on my WinXP site and I'm pretty sure that the proxy settings are passed to tomcat. As the other values passed at the same time are needed by the application and working fine.



Here's the error:

29.07.2009 13:37:08 com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception (it will retry in five minutes): Connection timed out: connect
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:516)
at java.net.Socket.connect(Socket.java:466)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:179)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:133)
at com.javamonitor.Collector.init(Collector.java:168)
at com.javamonitor.Collector.push(Collector.java:85)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:131)
at java.lang.Thread.run(Thread.java:595)

Regards,
Stefan

[kjkoster]

Dear Irshad and Stephan

I just started a Windows machine to test this out and all I can say is that it works for me. Sorry. :confused:

Stephan, could you please check that you have the log line that reads "INFO: using proxy HTTP @ ...". If that log line is not there, you have not set the option correctly.

Would you two mind trying it using the exact command sequence that I used, please?

Here is what I did:
http://java-monitor.com/misc/windows-proxy-example.png

The green circle is where I set the command line option to configure Tomcat and the yellow circle shows that Java-monitor picked up on the settings.

How this works for Tomcat servers that run as Windows services I have no idea. I am not a Windows guy.

Kees Jan

[smhaller]

Hi,

i just did what you suggested but with no luck. I also downloaded again the latest version, just to be sure.

Here's the result:

C:\SISWEB~1\APACHE~1.17\bin>catalina.bat version
Using CATALINA_BASE: C:\SISwebMAX\webmaxTest\Tomcat
Using CATALINA_HOME: C:\SISWEB~1\APACHE~1.17
Using CATALINA_TMPDIR: C:\SISwebMAX\webmaxTest\Tomcat\temp
Using JRE_HOME: C:\SISwebMAX\jdk1.5.0_08
Server version: Apache Tomcat/5.5.17
Server built: Apr 14 2006 02:08:29
Server number: 5.5.17.0
OS Name: Windows XP
OS Version: 5.1
Architecture: x86
JVM Version: 1.5.0_08-b03
JVM Vendor: Sun Microsystems Inc.

C:\SISWEB~1\APACHE~1.17\bin>catalina.bat run
Using CATALINA_BASE: C:\SISwebMAX\webmaxTest\Tomcat
Using CATALINA_HOME: C:\SISWEB~1\APACHE~1.17
Using CATALINA_TMPDIR: C:\SISwebMAX\webmaxTest\Tomcat\temp
Using JRE_HOME: C:\SISwebMAX\jdk1.5.0_08
29.07.2009 16:27:59 org.apache.catalina.core.AprLifecycleListenerlifec ycleEvent

INFO: The Apache Tomcat Native library which allows optimal performance in produ
ction environments was not found on the java.library.path: C:\SISwebMAX\jdk1.5.0
_08\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOW S\system32;C:\WINDOWS;C:\WINDO
WS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\Microsoft SQL Serv
er\80\Tools\BINN
29.07.2009 16:27:59 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8200
29.07.2009 16:27:59 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 484 ms
29.07.2009 16:27:59 org.apache.catalina.core.StandardService start
INFO: Starting service webmaxTestTomcat
29.07.2009 16:28:00 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.17
29.07.2009 16:28:00 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
29.07.2009 16:28:00 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive java-monitor.war
29.07.2009 16:28:00 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive max.war
CoreServlet.init(),propFile../webmax.properties
PropertyBase.PropertyBase()propertyClassMax::::../webmax.properties
29.07.2009 16:28:01 org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8200
29.07.2009 16:28:01 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
29.07.2009 16:28:01 org.apache.catalina.startup.Catalina start
INFO: Server startup in 1375 ms
29.07.2009 16:28:23 com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SCHWERWIEGEND: This probe was hit by an unexpected exception (it will retry in f
ive minutes): Connection timed out: connect
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:516)
at java.net.Socket.connect(Socket.java:466)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:179)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:133)
at com.javamonitor.Collector.init(Collector.java:168)
at com.javamonitor.Collector.push(Collector.java:85)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorC
ollector.java:131)
at java.lang.Thread.run(Thread.java:595)

I hope this helps to find some more things.

I cannot see any difference except that i run a specific app and with tomcat 5

Regards,
Stefan

[kjkoster]

Dear Stefan ,

Could you please also post the output of the command "SET" just befure you start Tomcat? Thus:


> catalina.bat version
...
> set
...
> catalina.bat run
...


Kees Jan

[smhaller]

Hi Jan,

here are the settings specified:

C:\SISWEB~1\APACHE~1.17\bin>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Stefan\Application Data
CATALINA_BASE=C:\SISwebMAX\webmaxTest\Tomcat
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=SIX-TKHLF-TEST
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Stefan
JAVA_HOME=C:\SISwebMAX\jdk1.5.0_08
JAVA_OPTS=-Dhttp.proxyHost=10.23.209.109 -Dhttp.proxyPort=8080
JRE_HOME=C:\SISwebMAX\jdk1.5.0_08
LOGONSERVER=\\SIX-TKHLF-TEST
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\Sys tem32\Wbem;C:\Program Files\In
tel\DMIX;C:\Program Files\Microsoft SQL Server\80\Tools\BINN
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WS F;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 2, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0f02
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\Stefan\LOCALS~1\Temp
TMP=C:\DOCUME~1\Stefan\LOCALS~1\Temp
USERDOMAIN=SIX-TKHLF-TEST
USERNAME=Stefan
USERPROFILE=C:\Documents and Settings\Stefan
VBOX_INSTALL_PATH=C:\Program Files\Sun\xVM VirtualBox\
windir=C:\WINDOWS
-------------
As you can see, the proxy settings are there but tomcat does not pick them up. Even when starting manually and not via windows service manager.

additionally:

here is what is going on when running as a service:

[2009-07-29 16:18:27] [info] Starting service...
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[0] -Xrs
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[1] -Dcatalina.base=C:\SISwebMAX\webmaxTest\Tomcat
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[2] -Dcatalina.home=C:\SISwebMAX\apache-tomcat-5.5.17
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[3] -Djava.endorsed.dirs=C:\SISwebMAX\apache-tomcat-5.5.17\common\endorsed
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[4] -Djava.io.tmpdir=C:\SISwebMAX\webmaxTest\Tomcat\tem p
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[5] -Djava.util.logging.manager=org.apache.juli.ClassLo aderLogManager
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[6] -Djava.util.logging.config.file=C:\SISwebMAX\webmax Test\Tomcat\conf\logging.properties
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[7] -Dwebmax.log.dir=C:/SISwebMAX/webmaxTEST/Tomcat/logs
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[8] -Djava.http.proxyHost=10.23.209.109
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[9] -Djava.http.proxyPort=8080[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[10] -Djava.http.nonProxyHosts=localhost|127.0.0.1
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[11] -Djava.class.path=C:\SISwebMAX\apache-tomcat-5.5.17/bin/bootstrap.jar
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[12] vfprintf
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[13] -Xmx256m
[2009-07-29 16:18:28] [485 javajni.c] [debug] argv[0] = start
[2009-07-29 16:18:29] [945 prunsrv.c] [debug] Java started org/apache/catalina/startup/Bootstrap


Regards,
Stefan

[kjkoster]

Dear Stefan,

I will test some more, then. However, I spotted one mistake for the service:


2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[8] -Djava.http.proxyHost=10.23.209.109
[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[9] -Djava.http.proxyPort=8080[2009-07-29 16:18:27] [399 javajni.c] [debug] Jvm Option[10] -Djava.http.nonProxyHosts=localhost|127.0.0.1


That should be -Dhttp.proxyHost, and not -Djava.http.proxyHost. Could you please verify that you are using the right setting here?

Kees Jan

[smhaller]

Hi Jan,

those settings were just a test to see if there's any difference in progress, so I changed them back already.

Regards,
Stefan

[romu31]

got the same issue .

i have other app running in my tomcat . only Java-monitor.

I m also redirected to http://www.java-monitor.com/ .

[kjkoster]

Hi romu31,

Could you please post the first few lines of your Tomcat's startup sequence? Are you behind an HTTP proxy?

The redirection is intentional. You can view the stats and graphs on Java-monitor.com. Just log in to the forum to see them on-line.

Kees Jan

[romu31]

morning ,

file startup.bat

set JAVA_HOME=C:\Romu\dev\GEEK\jdk1.6.0_14
set JAVA_OPTS=" -Dhttp.noProxyHosts=localhost -Dhttp.proxyHost=192.9.201.36 -Dhttp.proxyPort=3128"

logs :


C:\Romu\dev\GEEK\apache-tomcat-6.0.20\bin>startup
Using CATALINA_BASE: C:\Romu\dev\GEEK\apache-tomcat-6.0.20
Using CATALINA_HOME: C:\Romu\dev\GEEK\apache-tomcat-6.0.20
Using CATALINA_TMPDIR: C:\Romu\dev\GEEK\apache-tomcat-6.0.20\temp
Using JRE_HOME: C:\Romu\dev\GEEK\jdk1.6.0_14
C:\Romu\dev\GEEK\apache-tomcat-6.0.20\bin>

25 ao¹t 2009 11:04:32 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performanc
e in production environments was not found on the java.library.path: C:\Romu\dev
\GEEK\jdk1.6.0_14\bin;.;C:\WINDOWS\Sun\Java\bin;C: \WINDOWS\system32;C:\WINDOWS;C
:\Program Files\Java\jdk1.5.0_16\bin;C:\Perl\bin;C:\oracle\o ra92\bin;C:\Program
Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\syst
em32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Progra m Files\Windows Imaging\;C:\Pr
ogram Files\TortoiseSVN\bin;C:\Program Files\QuickTime\QTSystem\;C:\Romu\dev\apa
che-maven-2.0.9\bin
25 ao¹t 2009 11:04:32 org.apache.coyote.http11.Http11Protocol init
INFO: Initialisation de Coyote HTTP/1.1 sur http-8080
25 ao¹t 2009 11:04:32 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 447 ms
25 ao¹t 2009 11:04:32 org.apache.catalina.core.StandardService start
INFO: DÚmarrage du service Catalina
25 ao¹t 2009 11:04:32 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
25 ao¹t 2009 11:04:32 org.apache.catalina.startup.HostConfig deployWAR
INFO: DÚploiement de l'archive java-monitor.war de l'application web
25 ao¹t 2009 11:04:33 org.apache.coyote.http11.Http11Protocol start
INFO: DÚmarrage de Coyote HTTP/1.1 sur http-8080
25 ao¹t 2009 11:04:33 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
25 ao¹t 2009 11:04:33 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=null
25 ao¹t 2009 11:04:33 org.apache.catalina.startup.Catalina start
INFO: Server startup in 858 ms
25 ao¹t 2009 11:04:55 com.javamonitor.JavaMonitorCollector$CollectorDriv er run
GRAVE: This probe was hit by an unexpected exception: No route to host: connect
java.net.NoRouteToHostException: No route to host: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:180)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:133)
at com.javamonitor.Collector.init(Collector.java:168)
at com.javamonitor.Collector.push(Collector.java:85)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorC
ollector.java:134)
at java.lang.Thread.run(Thread.java:619)

[admin]

Dear All,

We have just changed the proxy handling code in the probe. Some more testing revealed a bug in the local IP finding code.

Please delete your old probes and replace them with a new one, freshly downloaded from Java-monitor.com (http://java-monitor.com/lemongrass/java-monitor-probe.zip).

Please let us know if this fixes the proxy issues for you.

Kees Jan

[smhaller]

Hi Jan,

at least in my case it still doesn't solve the problem. Just checked it on Solaris side and Windows side too. Still get the timeout error:


10.09.2009 12:08:26 com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SCHWERWIEGEND: This probe was hit by an unexpected exception (it will retry in five minutes): Connection timed out: connect
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:516)
at java.net.Socket.connect(Socket.java:466)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:179)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:133)
at com.javamonitor.Collector.init(Collector.java:168)
at com.javamonitor.Collector.push(Collector.java:85)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:131)
at java.lang.Thread.run(Thread.java:595)


The proxy settings are placed at the startup:
[2009-09-10 12:07:57] [info] Starting service...
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[0] -Xrs
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[1] -Dcatalina.base=C:\SISwebMAX\webmaxTest\Tomcat
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[2] -Dcatalina.home=C:\SISwebMAX\apache-tomcat-5.5.28
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[3] -Djava.endorsed.dirs=C:\SISwebMAX\apache-tomcat-5.5.28\common\endorsed
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[4] -Djava.io.tmpdir=C:\SISwebMAX\webmaxTest\Tomcat\tem p
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[5] -Djava.util.logging.manager=org.apache.juli.ClassLo aderLogManager
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[6] -Djava.util.logging.config.file=C:\SISwebMAX\webmax Test\Tomcat\conf\logging.properties
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[7] -Dwebmax.log.dir=C:/SISwebMAX/webmaxTEST/Tomcat/logs
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[8] -Dhttp.proxyHost=10.23.209.109
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[9] -Dhttp.proxyPort=8080
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[10] -Dhttp.nonProxyHosts=localhost|127.0.0.1
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[11] -Djava.class.path=C:\SISwebMAX\apache-tomcat-5.5.28/bin/bootstrap.jar
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[12] vfprintf
[2009-09-10 12:07:57] [399 javajni.c] [debug] Jvm Option[13] -Xmx256m
[2009-09-10 12:07:57] [485 javajni.c] [debug] argv[0] = start
[2009-09-10 12:07:58] [945 prunsrv.c] [debug] Java started org/apache/catalina/startup/Bootstrap
[2009-09-10 12:07:59] [info] Service started in 1390 ms.

So I don't know. For me it looks like the probe is not able for some reason to find the way to the results reciever.

Thanks and regards,
Stefan