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] Updated: (AXIS2-1940) fireAndForget and Thread.sleep
Date Sat, 06 Jan 2007 22:24:27 GMT

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

Michele Mazzucco updated AXIS2-1940:
------------------------------------

    Description: 
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).

  was:
After calling sender.fireAndForget() the documentation suggests to use Thread.sleep(500) to
ensure that the message is delivered to the receiver. 
After 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 isssue is particularly serious because it does not depend on the environment (i.e cpu
or network speed).


added the link to the documentation

> 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