[omniORB] FW: omniORB-list Digest, Vol 14, Issue 10

[Green, Wallace J]

The actual problem was pretty simple and relatively easy to find once I
turned on the OMNI trace facility.  It turns out that the object name I
was binging in the server was the URL name instead of the interface
name.  When I changed this to the interface name, everything worked
fine.

Thank you all for your help.

Wally Green

-----Original Message-----
From: omniorb-list-request at omniorb-support.com
[mailto:omniorb-list-request at omniorb-support.com] 
Sent: Friday, June 11, 2004 4:00 AM
To: omniorb-list at omniorb-support.com
Subject: omniORB-list Digest, Vol 14, Issue 10


Send omniORB-list mailing list submissions to
	omniorb-list at omniorb-support.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.omniorb-support.com/mailman/listinfo/omniorb-list
or, via email, send a message with subject or body 'help' to
	omniorb-list-request at omniorb-support.com

You can reach the person managing the list at
	omniorb-list-owner at omniorb-support.com

When replying, please edit your Subject line so it is more specific than
"Re: Contents of omniORB-list digest..."


Today's Topics:

   1. RE: Server on dedicated port (Wernke zur Borg)


----------------------------------------------------------------------

Message: 1
Date: Fri, 11 Jun 2004 10:12:03 +0200
From: "Wernke zur Borg" <Wernke.zurBorg at anite.com>
Subject: RE: [omniORB] Server on dedicated port
To: <omniorb-list at omniorb-support.com>
Message-ID: <200406110813.i5B8D0221192 at maia.anitesystems.de>
Content-Type: text/plain;	charset="us-ascii"

I also use the omniINSPOA, and it works fine for me.

I guess your problem is the URI that you supply to
resolve_initial_references on the client, could you post it? It should
be of the form "corbaloc::<host>:<port>/<key>".

But the problem could also be on the server, where the INSPOA must
activate your object by calling activate_object_with_id. The OID passed
to that call is obtained from a call of
PortableServer::string_to_ObjectId(<key>).

I do not use ORBpoaUniquePersistentSystemIds, I do not believe it is
necessary for this purpose.

Hope it helps.

Wernke

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Green,
Wallace J
Sent: 09 June 2004 19:33
To: omniorb-list at omniorb-support.com
Subject: [omniORB] Server on dedicated port

I am trying to develop a relatively simple server using OmniOrb on
Linux.

I'd like the server to run on a dedicated port.  I'd also like a client
to be able to resolve this server using "resolve_initial_references".
I'm trying to reduce the number of processes running so I'm avoiding the
nameserver.

I have set the server to create an object (with id) using the INSpoa.  I
run the server with the ORBpoaUniquePersistentSystemIds and ORBendPoint
Command line options.  When the server runs, I can see it listening on
the desired port by using "netstat".

I have set an InitRef  entry in the omni configuration file and try to
"resolve_initial_references" in the client.  The
resolve_initial_refererences does return a non-null object, but when
this object is narrowed, I get an error "omniORB: ERROR -- the
application attempted to invoke an operation on a nil reference.".

So, obviously I'm doing something wrong.  Does anyone have any clues? It
would be real nice if someone had a set of example programs which do
this type of operation that work.



Wally Green

_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list




------------------------------

_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list


End of omniORB-list Digest, Vol 14, Issue 10
********************************************