Hi Asankha. I haven't received this error since we placed the mediator and task scheduler on different machines. It looks like just a lack of resources in the local machine. Remsy
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Asankha C. Perera Sent: September 24, 2008 6:35 AM To: [email protected] Subject: Re: [esb-java-user] abnormal connection close Remsy I will take a detailed look and get back to you.. btw, did you change the default log settings? I am seeing loads and loads of Axis2 debug log information :(. If you can, it would be better to Zip your full logs and email them directly to me to asankha AT wso2 DOT com. BTW, have you changed anything in your axis2.xml? If so, please do send that too asankha Schmilinsky, Remsy wrote: Hi Asankha, attached config and log files. I replaced the soap bodies with the word MESSAGE for condifential reasons. remsy -----Original Message----- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] Behalf Of Asankha C. Perera Sent: September 23, 2008 1:11 PM To: [email protected] Subject: Re: [esb-java-user] abnormal connection close Hi Remsy Is there a way I can contribute to resolve this ? Please send me the synapse.xml and a brief description about your scenario, and full logs. You can send it privately to me if any of the information is confidential. Any hints ? This is preventing us to do a proof-of-concept to demonstarte how useful wso2 is, I am concerned that it is difficult to reproduce, that is, there is no fixed test to find out the condition that makes it fail. With the above, I'm sure we can nail down the problem very quickly asankha
_______________________________________________ Esb-java-user mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
