[omniORB] Tcp connection broken between two corba remote calls

[Ridgway, Richard (London)]

Do you keep an object reference to the remote object during the
interval? There are various parameters that indicate how quickly idle
connections are recycled, and how connections in general are managed.
Take a look in the omniorb documentation. I think the one I had to tweak
was -ORBoutConScanPeriod.

Richard

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Bruno
Carlus
Sent: 11 March 2009 13:25
To: omniorb-list at omniorb-support.com
Subject: [omniORB] Tcp connection broken between two corba remote calls


Hi,

a client of my own invokes a corba "ping" method on a server every 5 s 
but between two invocations the client seems to be disconnected from the

server:
the server sends a TCP frame with a reset flag and the communication 
switches to a new tcp connection with a new port on the client (old 
port+1), which creates memory problems on the client side (an embedded 
pc) ... The "ping"  invocation is nevertheless ok butcould there be a 
timeout condition at stake here that could force the current connection 
to break and restart between two calls ?

Thanks for your answers !

Bruno.

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

--------------------------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------------------------