[tickets] [opensaf:tickets] #629 AMF brings down proxy before proxied component and then crashes
- **status**: review --> fixed - **Milestone**: future --> 4.3.3 - **Comment**: changeset: 5329:8971d56274c9 branch: opensaf-4.3.x parent: 5313:8418e7de7a92 user:ajo...@genband.com date:Fri May 30 17:15:21 2014 +0530 summary: amfnd: fix process of proxy proxied cleanup on OpenSAF shutdown [#629] changeset: 5330:9242ef1f1b8c branch: opensaf-4.4.x parent: 5320:2842c9b754a4 user:ajo...@genband.com date:Fri May 30 17:16:00 2014 +0530 summary: amfnd: fix process of proxy proxied cleanup on OpenSAF shutdown [#629] changeset: 5331:c5b6ac55fef8 tag: tip parent: 5328:9e3113028b07 user:ajo...@genband.com date:Fri May 30 17:16:23 2014 +0530 summary: amfnd: fix process of proxy proxied cleanup on OpenSAF shutdown [#629] [staging:8971d5] [staging:9242ef] [staging:c5b6ac] --- ** [tickets:#629] AMF brings down proxy before proxied component and then crashes** **Status:** fixed **Milestone:** 4.3.3 **Created:** Mon Nov 18, 2013 04:03 PM UTC by Alex Jones **Last Updated:** Fri May 02, 2014 04:46 PM UTC **Owner:** Alex Jones When shutting down OpenSAF, amfnd terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the SaAmfProxiedComponentCleanupCallbackT callback in the proxy, and the termination of the proxy is done via the CLC-CLI cleanup. There is a race condition here, such that if the proxy is terminated before the proxied component can respond to the cleanup callback, AMF will think that the proxied callback timed out, will report an error, and then crash. AMF should really wait until all proxied components of the proxy are terminated before terminating the proxy. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #629 AMF brings down proxy before proxied component and then crashes
- **status**: assigned --> review --- ** [tickets:#629] AMF brings down proxy before proxied component and then crashes** **Status:** review **Milestone:** future **Created:** Mon Nov 18, 2013 04:03 PM UTC by Alex Jones **Last Updated:** Fri May 02, 2014 03:01 PM UTC **Owner:** Alex Jones When shutting down OpenSAF, amfnd terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the SaAmfProxiedComponentCleanupCallbackT callback in the proxy, and the termination of the proxy is done via the CLC-CLI cleanup. There is a race condition here, such that if the proxy is terminated before the proxied component can respond to the cleanup callback, AMF will think that the proxied callback timed out, will report an error, and then crash. AMF should really wait until all proxied components of the proxy are terminated before terminating the proxy. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #629 AMF brings down proxy before proxied component and then crashes
- Description has changed: Diff: --- old +++ new @@ -1,9 +1,5 @@ -I have a proxy/proxied pair in two different service groups. The proxied is 2N, and the proxy is No Redundancy. When shutting down OpenSAF, AMF terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the callback in the proxy, and since AMF terminates the proxy, this callback times out and AMF reports an error. It then crashes. +When shutting down OpenSAF, amfnd terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the SaAmfProxiedComponentCleanupCallbackT callback in the proxy, and the termination of the proxy is done via the CLC-CLI cleanup. -Attached is trace output from amfnd. +There is a race condition here, such that if the proxy is terminated before the proxied component can respond to the cleanup callback, AMF will think that the proxied callback timed out, will report an error, and then crash. -The name of the proxy component is GbConfDProxy, and the name of the proxied component is GbConfD. Not to be confusing, but there is another component SafGbConfD, which is neither of these. - -The proxied component is told to terminate at 14:33:28.057538 via the callback through the proxy, and the proxy is immediately after told to terminate at 14:33:28.060670. And you can see at 14:33:58.194843 the proxied component failing because the callback timed out. - -Then at 14:34:24.374201 amfd crashes. +AMF should really wait until all proxied components of the proxy are terminated before terminating the proxy. - **Part**: d --> nd --- ** [tickets:#629] AMF brings down proxy before proxied component and then crashes** **Status:** assigned **Milestone:** future **Created:** Mon Nov 18, 2013 04:03 PM UTC by Alex Jones **Last Updated:** Tue Apr 29, 2014 06:05 PM UTC **Owner:** Alex Jones When shutting down OpenSAF, amfnd terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the SaAmfProxiedComponentCleanupCallbackT callback in the proxy, and the termination of the proxy is done via the CLC-CLI cleanup. There is a race condition here, such that if the proxy is terminated before the proxied component can respond to the cleanup callback, AMF will think that the proxied callback timed out, will report an error, and then crash. AMF should really wait until all proxied components of the proxy are terminated before terminating the proxy. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #629 AMF brings down proxy before proxied component and then crashes
- **status**: unassigned --> assigned - **assigned_to**: Alex Jones --- ** [tickets:#629] AMF brings down proxy before proxied component and then crashes** **Status:** assigned **Milestone:** future **Created:** Mon Nov 18, 2013 04:03 PM UTC by Alex Jones **Last Updated:** Mon Nov 18, 2013 04:03 PM UTC **Owner:** Alex Jones I have a proxy/proxied pair in two different service groups. The proxied is 2N, and the proxy is No Redundancy. When shutting down OpenSAF, AMF terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the callback in the proxy, and since AMF terminates the proxy, this callback times out and AMF reports an error. It then crashes. Attached is trace output from amfnd. The name of the proxy component is GbConfDProxy, and the name of the proxied component is GbConfD. Not to be confusing, but there is another component SafGbConfD, which is neither of these. The proxied component is told to terminate at 14:33:28.057538 via the callback through the proxy, and the proxy is immediately after told to terminate at 14:33:28.060670. And you can see at 14:33:58.194843 the proxied component failing because the callback timed out. Then at 14:34:24.374201 amfd crashes. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #629 AMF brings down proxy before proxied component and then crashes
--- ** [tickets:#629] AMF brings down proxy before proxied component and then crashes** **Status:** unassigned **Created:** Mon Nov 18, 2013 04:03 PM UTC by Alex Jones **Last Updated:** Mon Nov 18, 2013 04:03 PM UTC **Owner:** nobody I have a proxy/proxied pair in two different service groups. The proxied is 2N, and the proxy is No Redundancy. When shutting down OpenSAF, AMF terminates both the proxy and the proxied component at the same time. The termination of the proxied component is done through the callback in the proxy, and since AMF terminates the proxy, this callback times out and AMF reports an error. It then crashes. Attached is trace output from amfnd. The name of the proxy component is GbConfDProxy, and the name of the proxied component is GbConfD. Not to be confusing, but there is another component SafGbConfD, which is neither of these. The proxied component is told to terminate at 14:33:28.057538 via the callback through the proxy, and the proxy is immediately after told to terminate at 14:33:28.060670. And you can see at 14:33:58.194843 the proxied component failing because the callback timed out. Then at 14:34:24.374201 amfd crashes. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets