RE: [mico-devel] Remote method call Time-out
Hi, I am using the latest snapshot of mico (2008-03-19). I could not found the parameter you have suggested. But I have found a way to achieve the desired result by using Request Time Out policy with policy manager (i.e by creating the timeout policy with RELATIVE_RT_TIMEOUT_POLICY_TYPE and setting the timeout value). I get proper TimeOut exceptions when I unplug the client's network cable after few calls to the server. The problem I am facing now is that the ORB crashes if I continue to make calls on the broken network for another 10 mins. Though I get TimeOut exceptions for all such calls, but after 10 mins the ORB crashes inadvertently. The only line I get in the trace is iop.cc:3435: failed assertion `0' P.S: I have tested this on Mac and windows with the timeout policy samples given with the mico ORB. On windows it crashes just after unplugging the cable and on Mac the crash happens after 10 mins. I would be obliged if you can provide any help or direction on this. Regards Ashish From: rssh [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 7:46 PM To: Ashish Kumar Sharma; mico-devel@mico.org Subject: Re: [mico-devel] Remote method call Time-out On Tue, 22 Apr 2008 17:09:22 +0530, Ashish Kumar Sharma wrote Hi, I have a requirement to use remote method call time-out functionality when using mico ORB on the client side. I am using the latest snapshot dated 19-03-2008. Can you please advice me on how to achieve this. I remember that I patched mico to add -ORBCallTimeout option in 2004 Hope, this still must work. Regards, Ashish Kumar Sharma Sr. Software Engineer Enterprise - RD www.quark.com CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone (172.229.9460) or return e-mail message ([EMAIL PROTECTED]) and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. -- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
RE: [mico-devel] Remote method call Time-out
Hi, I'm not able to find any assert on the iop.cc:3435. Have you modified the code? If so, how do your changes look? Cheers, Karel Ashish Kumar Sharma wrote: Hi, I am using the latest snapshot of mico (2008-03-19). I could not found the parameter you have suggested. But I have found a way to achieve the desired result by using Request Time Out policy with policy manager (i.e by creating the timeout policy with RELATIVE_RT_TIMEOUT_POLICY_TYPE and setting the timeout value). I get proper TimeOut exceptions when I unplug the client's network cable after few calls to the server. The problem I am facing now is that the ORB crashes if I continue to make calls on the broken network for another 10 mins. Though I get TimeOut exceptions for all such calls, but after 10 mins the ORB crashes inadvertently. The only line I get in the trace is iop.cc:3435: failed assertion `0' P.S: I have tested this on Mac and windows with the timeout policy samples given with the mico ORB. On windows it crashes just after unplugging the cable and on Mac the crash happens after 10 mins. I would be obliged if you can provide any help or direction on this. Regards Ashish From: rssh [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 7:46 PM To: Ashish Kumar Sharma; mico-devel@mico.org Subject: Re: [mico-devel] Remote method call Time-out On Tue, 22 Apr 2008 17:09:22 +0530, Ashish Kumar Sharma wrote Hi, I have a requirement to use remote method call time-out functionality when using mico ORB on the client side. I am using the latest snapshot dated 19-03-2008. Can you please advice me on how to achieve this. I remember that I patched mico to add -ORBCallTimeout option in 2004 Hope, this still must work. Regards, Ashish Kumar Sharma Sr. Software Engineer Enterprise - RD www.quark.com CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone (172.229.9460) or return e-mail message ([EMAIL PROTECTED]) and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel -- Karel Gardas [EMAIL PROTECTED] ObjectSecurity Ltd. http://www.objectsecurity.com ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
RE: [mico-devel] Remote method call Time-out
Oh.. it's at iop.cc:3423 in the function void MICO::IIOPProxy::abort_invoke (CORBA::ORBMsgId id) I haven't done any modifications to the code. thanks Regards Ashish -Original Message- From: Karel Gardas [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 23, 2008 6:01 PM To: Ashish Kumar Sharma Cc: rssh; mico-devel@mico.org Subject: RE: [mico-devel] Remote method call Time-out Hi, I'm not able to find any assert on the iop.cc:3435. Have you modified the code? If so, how do your changes look? Cheers, Karel Ashish Kumar Sharma wrote: Hi, I am using the latest snapshot of mico (2008-03-19). I could not found the parameter you have suggested. But I have found a way to achieve the desired result by using Request Time Out policy with policy manager (i.e by creating the timeout policy with RELATIVE_RT_TIMEOUT_POLICY_TYPE and setting the timeout value). I get proper TimeOut exceptions when I unplug the client's network cable after few calls to the server. The problem I am facing now is that the ORB crashes if I continue to make calls on the broken network for another 10 mins. Though I get TimeOut exceptions for all such calls, but after 10 mins the ORB crashes inadvertently. The only line I get in the trace is iop.cc:3435: failed assertion `0' P.S: I have tested this on Mac and windows with the timeout policy samples given with the mico ORB. On windows it crashes just after unplugging the cable and on Mac the crash happens after 10 mins. I would be obliged if you can provide any help or direction on this. Regards Ashish From: rssh [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 7:46 PM To: Ashish Kumar Sharma; mico-devel@mico.org Subject: Re: [mico-devel] Remote method call Time-out On Tue, 22 Apr 2008 17:09:22 +0530, Ashish Kumar Sharma wrote Hi, I have a requirement to use remote method call time-out functionality when using mico ORB on the client side. I am using the latest snapshot dated 19-03-2008. Can you please advice me on how to achieve this. I remember that I patched mico to add -ORBCallTimeout option in 2004 Hope, this still must work. Regards, Ashish Kumar Sharma Sr. Software Engineer Enterprise - RD www.quark.com CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone (172.229.9460) or return e-mail message ([EMAIL PROTECTED]) and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel -- Karel Gardas [EMAIL PROTECTED] ObjectSecurity Ltd. http://www.objectsecurity.com ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
