[omniORB] error message coming from ORB.

[shashi bhushan singh]

An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040313/830919c8/attachment.htm
-------------- next part --------------
Hi Alex/All,

Client and Server both are using OmniORB4.
 
Let me detail the secnario =>

A ---------------------->calls a method X on server ---->B

In function X, B calls a method using A's reference.

A <---------------------Calls method Y from within method X----B

A is killed now(Ctrl C).

B gets COMM_FAILURE while calling Y.After getting COMM_FAILURE, inside function X, B tries to fetch A's reference using a NamingService (...infinitely....) and keeps on calling Y using newly obtained references. As A is still down, B keeps on getting TRANSIENT exception. So in a way method X is not complete until B is able to get proper reference of A from naming service and call of Y is success.

But after some number of reries(~50), B dumps core with ORB throwing error message mentioned in previous mail.

I don't have any understanding of OmniORB code. Can you tell me what this check in the code means, so that I can somehow relate it to my scenario. It seems like some linked list operation ....,just guessing... :-)

Its a bit urgent. Any help is highly appreciated.

-Shashi

On Thu, 11 Mar 2004 Alex Tingle wrote :
>You need to provide more information:
>
>Which version of omniORB are you using (client and server)?
>Try running the server with the trace level turned up
>(-ORBtraceLevel 20).
>
>-Alex Tingle
>
>--
>On 11 Mar 2004, at 09:09, shashi bhushan singh wrote:
>
>>Hi,
>>
>>Can someone help me understand meaning of this message =>
>>===========================>
>>omniORB: Assertion failed.  This indicates a bug in the application
>>using
>>omniORB, or maybe in omniORB itself. e.g. using the ORB after it has
>>been shut down.
>>  file: giopImpl12.cc
>>  line: 319
>>  info: g->pd_strand->servers.next != &g->pd_strand->servers
>>omniORB: Assertion failed -- mutex should not be held.
>>  This is probably a bug in omniORB. Please submit a report
>>  (with stack trace if possible) to <omniorb at omniorb.org>.
>>    file: giopRope.cc
>>    line: 364
>>===========================>
>>I don't have proper stack trace for this as my app is multithread and I
>>am using linux 2.2.14 (this version always shows stack for last thread
>>outstanding).
>>
>>Scenario =>
>>Client is invoking a call on server and server goes down (killed).
>>
>>-Shashi
>>
>>
>>
>>
>><ATT07346.txt>
>