[omniORB] Persistence Problem with Corbalocs

[Wernke zur Borg]

Ok, I see the problem now.
 
No, I do not try to re-use an IOR after restart of the server, and my
software does not even allow it. I always re-evaluate the IOR when I need
it, and that's only at the very beginning of the client process. This
corbaloc IOR is just used once for bootstrapping. When the server goes down
I have to restart the client anyway.
 
I am currently unsure if your IOR should survive server restarts. Looking at
the parts an IOR is composed of I would not see any reason why it should
not, as all components (especially the object key) are fixed. But I may be
wrong.
 
Sorry, I can't help any further.
 
Wernke

  _____  

From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of joe
Sent: 17 September 2004 14:46
To: omniorb-list at omniorb-support.com
Subject: RE: [omniORB] Persistence Problem with Corbalocs


Wernke,
 
Thanks for the reply.  I have only begun to stringify my IORs recently in
attempt to debug this problem.  I do use a simple object key and
activate_object_with_id() on the server and then corbaloc::<host>:<port>/key
on the client.  The object reference that I get from this works initially
but then fails to work if the server is killed and then restarted without
restarting the client.  Can you verify that using corbalocs you are able to
kill the servant and bring it back without restarting the client and that
the object reference works again?
 
Thanks,
Joe
 
 
-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Wernke zur
Borg
Sent: Thursday, September 16, 2004 11:53 PM
To: omniorb-list at omniorb-support.com
Subject: RE: [omniORB] Persistence Problem with Corbalocs
 
I am not quite sure about your problem, but if you already use the
omniINSPOA, why do you stringify your IORs?
 
Use a simple object key, activate_object_with_id() on the server and
corbaloc::<host>:<port>/<key> on the client. No need to stringify anything.
This works fine for me.
 
Wernke
 
  _____  

From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of joe
Sent: 17 September 2004 00:33
To: 'Omniorb'
Subject: [omniORB] Persistence Problem with Corbalocs
All,
 
I have a persistent servant (using insPOA) that prints its IOR string using
orb.object_to_string.  The servant behaves persistently if I use the IOR
that is printed by the servant in my client by using an orb.string_to_object
and a _narrow.  I am able to kill the servant application and bring it back
and the client object reference is able to access the object when the
servant comes back.  The client object reference works until I kill the
servant and never comes back when the servant is restarted if I use a
corbaloc in the client.  I printed the IOR in the client that is obtained
from the corbaloc and an object_to_string and it is different from the IOR
that the servant outputs.
Any insight would be appreciated.
 
Thanks and Regards,
Joe
 
Joe Wilhelmi
RTLogic
719.598.2801 ext 1162
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040917/b87f9df0/attachment-0001.htm