Product:  OpenFusion JacORB

Version: All

Description:

Unexpected POA creation exception : Failed to register POA

Resolution:

The JacOrb IMR will not allow a POA to be registered if a POA with that name is already registered, if multiples are not allowed and the registered POA is still alive.

If the IMR gets a registration request for a POA, it first checks if it already has a POA registered for that name. If so, it checks whether multiples are allowed. If multiples are not allowed it checks whether the registered POA is still active, if not it allows registration of the new POA.

If the registered POA is still active the IMR will not allow registration of a second POA with the same name. Therefore, we believe that in this case the process from the original NotificationService is still active when the IMR pings it and it therefore will not allow another registration.

One way to check what is registered with the IMR is to use the IMR manager.

"jac_IMR_mgr -l" will list the services registered with the IMR. If the above request shows that the OpenFusion.NotificationService is registered "jac_IMR_mgr -l -n OpenFusion.NotificationService" will list the server details for that service.

If the IMR has any server registrations, using the server id displayed POA registrations can be checked:

jac_IMR_mgr -l -s

If a server is found to be registered it can be killed using:

jac_IMR_mgr -k -n OpenFusion.NotificationService

This calls shutdown on the Server and should allow the re-registration of the OpenFusion.NotificationService. If the IMR is stopped and restarted it will have no registrations if the -n option is used. If -n is not used the IMR loads data from it's data file. If it finds server registrations it pings them to see if they are still running and only retains details of servers that are running (so it the server is no longer running at restart of the IMR no details are recorded).