This is not a bug, rather something to do with client timing out. Could happen due to network connection status - I assume you were using wireless.
On Wed, Sep 19, 2012 at 1:31 PM, Chamara Ariyarathne <[email protected]>wrote: > Has anyone seen this before; > [2012-09-19 13:24:12,081] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,082] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,082] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,053] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,083] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,055] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,055] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,081] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,080] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,079] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > [2012-09-19 13:24:12,078] WARN - HttpCoreNIOSender Connection closed by > client : 192.168.71.1 > > With a test of 100 concurrency; for a proxy service which the endpoint is > appserver axis2service; esb failed to respond and finally this log > appeared. Also the CPU consumption was so high. > > -- > *Chamara Ariyarathne* > Senior Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; *+94772786766* > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
