FULL PRODUCT VERSION :


ADDITIONAL OS VERSION INFORMATION :
SunOS ix-app-tst 5.10 Generic_147148-26 i86pc i386 i86pc

A DESCRIPTION OF THE PROBLEM :
The issue occurs when the standard naming service and all servers are restarted , the client faces this issue. The client is also a orb server registered in different naming service

org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: SUN minor code: 202 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.badServerId(ORBUtilSystemException.java:8133)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.badServerId(ORBUtilSystemException.java:8155)
at com.sun.corba.se.impl.orb.ORBImpl.handleBadServerId(ORBImpl.java:1447)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.checkServerId(CorbaServerRequestDispatcherImpl.java:391)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:166)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1680)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1540)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:922)
at com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:181)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:694)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:451)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1189)
at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:417)

REGRESSION. Last worked in version 6u43

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Create a orb server in a naming service, execute some action from a client that is also a orb server in different naming service
crash the server in the first naming service and restart
getting bad server id exception
the encoding used is for the Arabic Encoding and the java versions
In the first case: 1.5
Second case : 1.6

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Connection should happen smoothly even after the restart

ERROR MESSAGES/STACK TRACES THAT OCCUR :
org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: SUN minor code: 202 completed: No
at com.sun.corba.se.impl.logging.ORBUtilSystemException.badServerId(ORBUtilSystemException.java:8133)
at com.sun.corba.se.impl.logging.ORBUtilSystemException.badServerId(ORBUtilSystemException.java:8155)
at com.sun.corba.se.impl.orb.ORBImpl.handleBadServerId(ORBImpl.java:1447)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.checkServerId(CorbaServerRequestDispatcherImpl.java:391)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:166)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1680)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1540)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:922)
at com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:181)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:694)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:451)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1189)
at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:417)

REPRODUCIBILITY :
This bug can be reproduced always.