Technical Support

Monitoring of WebSphere cluster doesn't work properly.
Hi,

I was really excited with your software and the possibility of monitoring our
WebSphere cluster. After few tests I realized the software isn't working well
with Network Deployment.

Following the instructions in the documentation, I created a monitor for my
WS Cluster. Browsing that monitor I noticed that there isn't any information
about my cluster. The nodes and servers were not discovered.

Checking the stdout.txt I encountered the following error:

> java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 172.16.32.87; nested
> exception is: java.net.ConnectException: Connection refused]
> at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317) at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.jav
>a:248) at
> com.adventnet.appmanager.cam.MX4JRMIDiscovery$DiscoveryThread.run(MX4JRMIDi
>scovery.java:68) Caused by: javax.naming.ServiceUnavailableException [Root
> exception is java.rmi.ConnectException: Connection refused to host:
> 172.16.32.87; nested exception is: java.net.ConnectException: Connection
> refused]
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:18
>5) at javax.naming.InitialContext.lookup(InitialContext.java:351) at
> javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.jav
>a:1807) at
> javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:17
>77) at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:259) ...
> 2 more
> Caused by: java.rmi.ConnectException: Connection refused to host:
> 172.16.32.87; nested exception is: java.net.ConnectException: Connection
> refused
> at
> sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574) at
> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185) at
> sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171) at
> sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:93)
> ... 7 more
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at
> java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364) at
> java.net.Socket.connect(Socket.java:507)
> at java.net.Socket.connect(Socket.java:457)
> at java.net.Socket.<init>(Socket.java:365)
> at java.net.Socket.<init>(Socket.java:178)
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocket
>Factory.java:22) at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocket
>Factory.java:128) at
> sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569) ... 12
> more

It seems the software is trying to connect to my cluster using RMI instead of
SOAP. What's wrong?

Leaving the monitor the way it is for a few hours, it starts to collect data
in random intervals, behaving like it is getting timeouts once and a while.

Is there any way to make that software work correctly with ND? We are really
interested in buy that software. But only if it works smoothly in our
environment.

F�bio Gomes

------------------------------------------------------
This is posted using Application Manager feedback form