
CORBAClnt
Page 51
Reported Issues
!
corbaclnt is blocked on a request to the CORBA server, and if the server does not
respond, due to a network, server crash or infinite loop on the server side, that
corbaclnt gets frozen and there will be a permanent deny of services from corbaclnt,
until it is terminated and restarted. This is a known problem with no re-design or
threaded implementation planned.
If a request for resource comes from an application to periq, and the service is not
registered, then currently periq does not return any response to the corresponding
application (vrto).
!
This issue pertains to MPS RDB systems (Solaris only) that interface with a CORBA
server. If Periq is restarted using the commands:
srp periq -stop
srp periq -start
while applications are running, vrto occurs. After this event, applications cannot
execute CORBA requests.
To correct this issue, restart the CORBA servers.
Comentários a estes Manuais