Re: [Dev] Social.core prints a broken pipe exception after a BAM restart

2014-11-13 Thread Ruchira Wageesha
@Manu, Can you please have a look? On Wed, Nov 12, 2014 at 11:56 PM, Amila Maha Arachchi ami...@wso2.com wrote: Hi all, There was a situation where we had to restart BAM. When BAM was restarted, social.core component in AF started printing the following log continuously. Had to restart AF

Re: [Dev] Social.core prints a broken pipe exception after a BAM restart

2014-11-13 Thread Manuranga Perera
Hi amila, I'll take a look On 13 Nov 2014 15:37, Ruchira Wageesha ruch...@wso2.com wrote: @Manu, Can you please have a look? On Wed, Nov 12, 2014 at 11:56 PM, Amila Maha Arachchi ami...@wso2.com wrote: Hi all, There was a situation where we had to restart BAM. When BAM was restarted,

Re: [Dev] Social.core prints a broken pipe exception after a BAM restart

2014-11-13 Thread Yumani Ranaweera
Could you also move the ticket to in-progress state. Thanks, Yumani On Thu, Nov 13, 2014 at 10:35 PM, Manuranga Perera m...@wso2.com wrote: Hi amila, I'll take a look On 13 Nov 2014 15:37, Ruchira Wageesha ruch...@wso2.com wrote: @Manu, Can you please have a look? On Wed, Nov 12, 2014

[Dev] Social.core prints a broken pipe exception after a BAM restart

2014-11-12 Thread Amila Maha Arachchi
Hi all, There was a situation where we had to restart BAM. When BAM was restarted, social.core component in AF started printing the following log continuously. Had to restart AF to get rid of it. Have you experienced this? I think something is wrong with the way connections are handled? This