Discussion:
Orbix + IT_POA_LOCATOR issue
(too old to reply)
PVN
2009-08-27 09:41:50 UTC
Permalink
Hi,

Am very new to CORBA and POA. Issue is one of our CORBA servers fails
to keep POA object at runtimes for unknown reasons , this is not
occuring always. We are not sure about this unknown reasons and why
its not occuring always.

Our POA uses below policies for activating it :

POA Policies
--------------------
user_policies[0] =
root_poa.create_lifespan_policy
(LifespanPolicyValue.PERSISTENT);
user_policies[1] =
root_poa.create_id_assignment_policy
(IdAssignmentPolicyValue.USER_ID);
user_policies[2] =
root_poa.create_servant_retention_policy
(ServantRetentionPolicyValue.RETAIN);
user_policies[3] =
root_poa.create_request_processing_policy
(RequestProcessingPolicyValue.USE_SERVANT_MANAGER);

try
{
return root_poa.create_POA("tasusers",
root_manager,user_policies);
}

We start CORBA server at runtimes and activates the POA on runtime .
When the user tries to login the application on first time (after
restarting the application which will be first user ) it creates POA
object using user id and uses for further invocation.

Sometimes for that first time after restart, this POA object has been
created and removed from application and application becomes
unusable.

In below log we can see it activates POA and removes their after. Any
ides why its causing ?

Log from locator.log below

Wed, 26 Aug 2009 17:24:41.0000000 [genesis-1:30850] (IT_POA_LOCATOR:4)
I - New PERSISTENT POA entered into cache.
POA name: norkom_poa.TASServer
ORB Name: norkom_orb.TASServer
Wed, 26 Aug 2009 17:24:41.0000000 [genesis-1:30850] (IT_POA_LOCATOR:4)
I - New PERSISTENT POA entered into cache.
POA name: tasusers
ORB Name: norkom_orb.TASServer
Wed, 26 Aug 2009 17:25:00.0000000 [genesis-1:30850] (IT_POA_LOCATOR:5)
I - PERSISTENT POA removed from cache.
POA name: tasusers
ORB Name: norkom_orb.TASServer
Wed, 26 Aug 2009 17:25:00.0000000 [genesis-1:30850] (IT_POA_LOCATOR:5)
I - PERSISTENT POA removed from cache.
POA name: norkom_poa.TASServer
ORB Name: norkom_orb.TASServer
Wed, 26 Aug 2009 17:25:24.0000000 [genesis-1:30850] (IT_POA_LOCATOR:
67) I - POA norkom_poa.TASServer (ORB name norkom_orb.TASServer) not
in cache; asking node daemon "iona_services.node_daemon.genesis-1" to
find or activate the POA


Any help on this will be very much appreciated.

Thanks
Ciaran McHale
2009-08-27 09:59:07 UTC
Permalink
[Has problems with an Orbix application and provides some
messages from the locator's log file]
The messages from the locator's log file that you provide do not
show any relevant information. Diagnostic messages from your client
and server applications may be more helpful. For example, if the
client application catches a CORBA exception then it should print
that out; that might provide some useful information. Or if the
server is crashing then perhaps you could try starting the server
from inside a debugger.


Regards,
Ciaran.
--
Ciaran McHale, www.CiaranMcHale.com
Email: ciaran _ mchale @ yahoo . co . uk
Mobile: +44-(0)7866-416-134
Loading...