axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Mazzucco (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Date Sat, 06 Jan 2007 22:35:27 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462755
] 

Michele Mazzucco commented on AXIS2-1940:
-----------------------------------------

Bjorn,

thanks very much for your reply. The documentation I've mentioned is http://ws.apache.org/axis2/1_1/dii.html
(One Way Client section) isn't very clear, but what you say does make sense.
Yes, I'm using the fireAndForget inside tomcat (which sometimes works as client), so do you
think is safe to remove the sleep call?

I've found out that this issue had already been raised several month ago (http://mail-archives.apache.org/mod_mbox/ws-axis-user/200606.mbox/%3C1149163629.447ed86dc7ee9@maili.uku.fi%3E).
Supposing your advice is correct, the problem remains on the client side because, as Jouko
and I say, the sleep wastes a lot of time, reducing considerably the rate at which messages
can be sent.


Finally, what about the problem described here http://mail-archives.apache.org/mod_mbox/ws-axis-user/200606.mbox/%3C1149163629.447ed86dc7ee9@maili.uku.fi%3E?

Best regards,
Michele 

> fireAndForget and Thread.sleep
> ------------------------------
>
>                 Key: AXIS2-1940
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1940
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: client-api
>         Environment: java 1.5
>            Reporter: Michele Mazzucco
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message