Hi,
I'm using websphere 7.0.0.9 over windows with a topology like this:
physical-server-1 Cell01 DMgr Node01 w/Server01
physical-server-2 Node02 w/Server02
The Node02 is federated to Cell01 and works fine for a few weeks (i'm testing a clustered application over server01 and server02, nothing special)
But now in administrative console over physical-server-1 the Node02 is marked as stopped, when it's really running.
At Node02 a ffdc incident is created with this stacktrace when the Node02 is starting:
[7/20/10 16:47:51:359 CLT] FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.ws.management.component.JMXConnectors.initDiscovery ProbeId:202 Reporter:com.ibm.ws.management.component.JMXConnectors@5dc85dc8 java.lang.NullPointerException at com.ibm.ws.management.component.JMXConnectors$EndPtCollector.(JMXConnectors.java:1866) at com.ibm.ws.management.component.JMXConnectors.initDiscovery(JMXConnectors.java:392) at com.ibm.ws.management.component.JMXConnectors.propertyChange(JMXConnectors.java:2111) at java.beans.PropertyChangeSupport.doFirePropertyChange(Unknown Source) at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source) at java.beans.PropertyChangeSupport.doFirePropertyChange(Unknown Source) at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source) at com.ibm.wsspi.runtime.component.WsComponentImpl.setState(WsComponentImpl.java:409) at com.ibm.ws.runtime.component.ComponentImpl.setState(ComponentImpl.java:144) at com.ibm.ws.runtime.component.ComponentImpl.setStartState(ComponentImpl.java:164) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:510) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:298) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666) at com.ibm.ws.runtime.WsServer.main(WsServer.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213) at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93) at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340) at org.eclipse.core.launcher.Main.basicRun(Main.java:282) at org.eclipse.core.launcher.Main.run(Main.java:981) at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:340) at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:110)
This is not a firewall or network issue, because i'm running the same scenario in linux at parallel using other physical servers at the same network.
I'm really stuck on this, this isn't the first time this happen!
Thanks in advance.