Originally posted at:
All of a sudden, running RDM tasks against a particular bladeserver, causes IBM Director to flip out with the following event:
Unhandled JVM Exception
Application: 'TWGServer (TWGVersion 5.10 2005-10-18 build id 1104)'
Thread Name: NMO Shutdown for:-422
Thread Group: ServiceThreadGroup
Exception Type: java.lang.ClassCastException: com.tivoli.twg.tier.TieredManagedObject
Stack Trace: java.lang.ClassCastException: com.tivoli.twg.tier.TieredManagedObject
at com.ibm.rdm.template.base.ClientShutdownRequest.run(ClientShutdownRequest.java:126)
at java.lang.Thread.run(Thread.java:568)
This happens consistantly, even after restarting the IBM Server service, or even when placing the Bladeserver in another slot, or even in another Bladecenter chassis.
No idea why it would happen with a particular blade server. It happens when the server is both on and off, so its probably nothing to do with the server itself, but the way RDM is pushing or queueing the task,.. strange though that RDM service doesnt crash instead!
I am beginning to think that the Metadata IBM director has on these particual server is somehow corrupted, and when Director tries to query it for a shutdown/startup action, it causes the crash.
I am still waiting on approval for our Director support pack purchase, but in the mean time, has anyone else seen this?
All of a sudden, running RDM tasks against a particular bladeserver, causes IBM Director to flip out with the following event:
Unhandled JVM Exception
Application: 'TWGServer (TWGVersion 5.10 2005-10-18 build id 1104)'
Thread Name: NMO Shutdown for:-422
Thread Group: ServiceThreadGroup
Exception Type: java.lang.ClassCastException: com.tivoli.twg.tier.TieredManagedObject
Stack Trace: java.lang.ClassCastException: com.tivoli.twg.tier.TieredManagedObject
at com.ibm.rdm.template.base.ClientShutdownRequest.run(ClientShutdownRequest.java:126)
at java.lang.Thread.run(Thread.java:568)
This happens consistantly, even after restarting the IBM Server service, or even when placing the Bladeserver in another slot, or even in another Bladecenter chassis.
No idea why it would happen with a particular blade server. It happens when the server is both on and off, so its probably nothing to do with the server itself, but the way RDM is pushing or queueing the task,.. strange though that RDM service doesnt crash instead!
I am beginning to think that the Metadata IBM director has on these particual server is somehow corrupted, and when Director tries to query it for a shutdown/startup action, it causes the crash.
I am still waiting on approval for our Director support pack purchase, but in the mean time, has anyone else seen this?