[omniORB] Persistence Problem with Corbalocs

[joe]

I do use orbendpoint to nail it down.

I have solved my problem.  Basically, I had multiple objects and didn't
realize it at the time.  One of those objects was instantiated using INS
and the other was not and I didn't realize it.

I appreciate all the help from the list.

Thanks,
Joe



-----Original Message-----
From: BaileyK at schneider.com [mailto:BaileyK at schneider.com] 
Sent: Friday, September 17, 2004 7:21 AM
To: joe
Cc: omniorb-list at omniorb-support.com
Subject: RE: [omniORB] Persistence Problem with Corbalocs


I have no problem using a corbaloc URI in a client that talks to a
server
that's been stopped/restarted (multiple times).  Maybe a dumb question,
but
you pin the port number of the server, right?



Kendall




 

                      "joe" <joe at rtlogic.com>

                      Sent by:                             To:
<omniorb-list at omniorb-support.com>                                      
                      omniorb-list-bounces at omniorb-        cc:

                      support.com                          Subject:  RE:
[omniORB] Persistence Problem with Corbalocs                        
 

 

                      09/17/2004 07:45 AM

 

 





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