axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Date Thu, 19 Feb 2009 06:05:01 GMT

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

Darren commented on AXIS2-1940:
-------------------------------

As the code indicates, the sendAndReceive and sendRobust will be handled directly by the AxisEngine,
while sendxxNoneblocking and fireAndForget will be queued in the ThreadPool and scheduled
for execution.

This fireAndForget method is quite confusing for the first time use. :-) 

> 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
>            Assignee: 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.


Mime
View raw message