[omniORB] omniorb_2.8 client blocking problem

[Jason Chu]

Hi, I am new to this subscription list.

I have a multi-thread omniob_2.8 client talking to another multi-thread
Java 1.5 server. We have a situation here where one of the thread
blocks when it calls this CORBA method:

(Auto-generated code)
Mcs::OutputGreekSequence * Mcs::_proxy_QuantModel::value(const
Mcs::ModelInput & input)
{
_0RL_pc_8e49803906fbc191_00000000 _call_desc("value", 6, input);

OmniProxyCallWrapper::invoke(this, _call_desc);
return _call_desc.result();
}

Looking at the server side log, there are no traces of this method ever
been invoked. It is as if the message sent from client is lost all
together. However the other client threads are happily running along
continuing to talk to the server and the server is also replying to
those other threads. So I know the server hasn't crashed. Also if I
was to resend this same request a second time, I do get a reply, hence I
know it is message specific.

I know this is vague, so I am happy to provide whatever info you
require. Also we can't move from omniorb_2.8.

My question is:

Does CORBA guarantee delivery of the "invoke(....)", i.e. does it
guarantee that when a client calls invoke(...) the server will actually
received the call? Can "invoke" get lost like packets over the network?
I can't see any traces of the server ever having received the request.

Maybe this is because of my lack of undering of CORBA, I just need some
input as I don't even know where to start with this?

Jason







If there is any advice in this email, it is general advice only and has been prepared by Macquarie Bank Limited ABN 46 008 583 542 or one of its subsidiaries ("Macquarie"). It does not take into account investors' objectives, financial situation or needs. Before acting on this general advice, investors should obtain independent advice before making any financial investment decision. If any financial product is mentioned, investors should consider the Product Disclosure Statement (PDS) for that product (if any). Copies of the PDS may be obtained free of charge from Macquarie.

Macquarie has made every reasonable effort to ensure the information provided is correct, but Macquarie makes no representation nor any warranty as to whether the information is accurate, complete or up to date. To the extent permitted by law, Macquarie accepts no responsibility for any errors or misstatements, negligent or otherwise. The information provided may be based on assumptions or market conditions and may change without notice.

Macquarie, its associates, officers or employees may also have interests in the financial products referred to in this information by acting in various roles. They may buy or sell the financial products as principal or agent and as such may effect transactions which are not consistent with any recommendations (if any in this information). Macquarie or its associates may also receive fees or brokerage for acting in the above capacities.

The information in this email is confidential. If you are not the intended recipient, you are not authorised to use the information in this email in any way. Macquarie does not guarantee the integrity of any emails or attached files. The view or opinions expressed are the author's own and may not reflect the view or opinions of Macquarie.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060531/f951a886/attachment.htm

[Duncan Grisby]

On Wednesday 31 May, "Jason Chu" wrote:

[...]

Post by Jason Chu
Does CORBA guarantee delivery of the "invoke(....)", i.e. does it
guarantee that when a client calls invoke(...) the server will actually
received the call? Can "invoke" get lost like packets over the network?
I can't see any traces of the server ever having received the request.

Yes, CORBA guarantees that the invoke will actually happen. The call is
sent across a TCP connection, so it can't be lost due to packet loss.

I suggest you run your omniORB client with a command line argument of
-ORBtraceLevel 25. That should give some indication of what the client
thinks it is doing, and whether the problem is on the client or server.

Cheers,

Duncan.