Manolito72
08-03-2010, 16:35
Hi there
I'm trying to look at load on my Tomcat server, as today in our Prod environment the Tomcat process was using over 1gb RAM (which is very high).
I deployed the war file today into our Tomcat environment and it looks like it extracted OK. At least I can see a java-monitor application under Tomcat Manager.
Unfortunately I know very little about Tomcat, but it is the web server that is used to manage SAP Business Objects here (and comes configured / deployed as part of that install).
I get this error in the stdout.log file
08-Mar-2010 14:57:13 com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception: 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:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:179)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:155)
at com.javamonitor.Collector.push(Collector.java:108)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:161)
at java.lang.Thread.run(Thread.java:595)
I am assuming this means I can't connect out to the java-manager, but I don't know enough about where to look for this
I can see that Java (build 1.6.0_17-b04) is the version running.
I can see that Proxy settings are the ones inherited from my browser, and I can get out to the internet from this application server logged on as the same service account that runs the Tomcat service.
So does the above suggest some other configuration within the Tomcat setup that is stopping connecting to java-monitor to log results? Any pointers?
Sorry, I'm not very technical when it comes to Tomcat, it is just the web server to run the apps I work with.
Thanks, Neil
I'm trying to look at load on my Tomcat server, as today in our Prod environment the Tomcat process was using over 1gb RAM (which is very high).
I deployed the war file today into our Tomcat environment and it looks like it extracted OK. At least I can see a java-monitor application under Tomcat Manager.
Unfortunately I know very little about Tomcat, but it is the web server that is used to manage SAP Business Objects here (and comes configured / deployed as part of that install).
I get this error in the stdout.log file
08-Mar-2010 14:57:13 com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception: 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:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:179)
at com.javamonitor.Collector.getLocalIp(Collector.jav a:155)
at com.javamonitor.Collector.push(Collector.java:108)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:161)
at java.lang.Thread.run(Thread.java:595)
I am assuming this means I can't connect out to the java-manager, but I don't know enough about where to look for this
I can see that Java (build 1.6.0_17-b04) is the version running.
I can see that Proxy settings are the ones inherited from my browser, and I can get out to the internet from this application server logged on as the same service account that runs the Tomcat service.
So does the above suggest some other configuration within the Tomcat setup that is stopping connecting to java-monitor to log results? Any pointers?
Sorry, I'm not very technical when it comes to Tomcat, it is just the web server to run the apps I work with.
Thanks, Neil