|
Problem(Abstract) |
Submitting a request from a remote client to a mixed
release WebSphere® Application Server cell, with a cluster containing both
v5.02 and v6.0 nodes, results in the following errors:
12 (top)/clusters/IOPCluster/tm javax.naming.Context
ERROR: Context "(top)/clusters/IOPCluster/tm" will not be dumped.
Failure during listBindings() or hasMore() method.
Exception: javax.naming.PartialResultException: org.omg.CORBA.OBJECT_NOT_
EXIST:
23 (top)/clusters/IOPCluster/wm javax.naming.Context
ERROR: Context "(top)/clusters/IOPCluster/wm" will not be dumped.
Failure during listBindings() or hasMore() method.
Exception: javax.naming.PartialResultException: org.omg.CORBA.OBJECT_NOT_
EXIST: |
|
|
|
Cause |
The abbreviations tm and wm represent TimerManager and
WorkManager. The CommonJ TimerManager and WorkManager are new in v6.0.
These do not exist in
v5, which is why they are not being bound in the v5 server. |
|
|
Resolving the
problem |
This is expected behavior because the CommonJ TimerManager
and WorkManager are resources that are new to v6 and should not be found
in v5. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|