Hi Sanjiva, indeed this could be a valid approach, but I have to add some details. If Asankha is right with his evaluation, and I'm quite sure he is, then this is an issue which on the one hand needs to be fixed properly but on the other hand does not block us at all. Unfortunately we currently don't use keep alive at all. Since a few days I know why. The developers of our client-side dynamic proxy had to deactivate keep alive due to a bug in the some bea web bridge. I don't know the details. My hope was that we can change this after the migration from Bea to JBoss has been finished. For now we might have to live without keep alive anyhow. :-( I just stumbled about that problem as I tried to test the graceful instance shutdown, which we really need - clusterwide. Beause I didn't know the cause for the issue, it worried me a lot. Regards, Eric
I'll re-run the same test without having keep alive activated in SoapUI just to verify our current understand is correct. Will get back to you soon. ________________________________ Von: [EMAIL PROTECTED] im Auftrag von Sanjiva Weerawarana Gesendet: Di 06.05.2008 21:37 An: [email protected] Betreff: Re: AW: AW: AW: AW: AW: [esb-java-dev] AsynchronousCloseException How about a workaround? If JBoss is reducing keepalive times under load to 5-10ms, that's not much value there at all .. so what happens if we turn off keep alive? (The proper solution is of course the right thing but this workaround may work to get Eric past this issue.) Sanjiva.
<<winmail.dat>>
_______________________________________________ Esb-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
