Fri Jul 5 16:46:36 CEST 2002
The proper way to destroy an Orber object is to use corba:dispose/1.
Sounds like that client-side ORB never terminates the connection. When
Orber acts as a client-side ORB you should set the iiop_connection_timeout
option (acts like a GC and terminates all "out-going" connections which
haven't been used for T seconds). I also recomend that you set
iiop_timeout and iiop_setup_connection_timeout (see chapter 5.2 in the
User's Guide). The number of Orber objects you've started isn't the
problem since Orber uses one proxy per client-ORB; use orb.destroy();
(Java) to stop it. Now you might wonder why 2 TCP connections are used.
Well, that's because the Client-ORB requests it, which is common.
If you're using the latest version of Orber you can easily check the
amount of "out-going" connections Orber holds (one per host/port) by
Have a nice weekend
P.S. If you use Orber to access Mnesia, then it might be a very good idea
to use pseudo-objects. D.S.
> Hello everyone,
> One of my nodes is going down regularly because it is running out of file
> descriptors oever a period of time (about 20 hours). I've had the same node
> running for the past six months with no outage at all using R7B but now I've
> added orber and upgraded to R8B.
> The client is a WebLogic app server which creates CORBA objects in my node.
> Each object seems to result in the opening of 2 TCP connections. What is
> happening here? MY file descriptor limit is set to 512 and I have about 50
> mnesia tables in total. Has anyone else seen this kind of behaviour.
> One thing I do is try limit the number of objects created. I do this by
> killing old objects (erlang gen_servers) when a new create request is
> created which exceed the max number of allowed objects. Is this what might
> be causing the problem - is there a more graceful way of deleting an object?
> NOTICE AND DISCLAIMER:
> This email (including attachments) is confidential. If you have received
> this email in error please notify the sender immediately and delete this
> email from your system without copying or disseminating it or placing any
> reliance upon its contents. We cannot accept liability for any breaches of
> confidence arising through use of email. Any opinions expressed in this
> email (including attachments) are those of the author and do not necessarily
> reflect our opinions. We will not accept responsibility for any commitments
> made by our employees outside the scope of our business. We do not warrant
> the accuracy or completeness of such information.
More information about the erlang-questions