You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/02/07 11:36:05 UTC
[jira] Resolved: (AXIS2-1940) fireAndForget and Thread.sleep
[ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-1940.
--------------------------------------
Resolution: Fixed
Hi Michele;
Well I am using sendRobust most of the time and I have not faced any problem with that , therefore I think you can use that.
> fireAndForget and Thread.sleep
> ------------------------------
>
> Key: AXIS2-1940
> URL: https://issues.apache.org/jira/browse/AXIS2-1940
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Environment: java 1.5
> Reporter: Michele Mazzucco
> Assigned To: Deepal Jayasinghe
>
> After calling sender.fireAndForget() the documentation (http://ws.apache.org/axis2/1_1/dii.html - one way client) suggests to use Thread.sleep(500) to ensure that the message is delivered to the receiver.
> Over the last few months I've tuned this value up to 200 ms - in a LAN environment - but the overhead is still to high and in some circumstances it causes the tomcat thread pool to exhaust.
> The problem is described http://www.mail-archive.com/axis-user%40ws.apache.org/msg22703.html and http://www.mail-archive.com/axis-user%40ws.apache.org/msg22747.html.
> This issue is particularly serious because it does not depend on the environment (i.e cpu or network speed).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org