[
https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michele Mazzucco reopened AXIS2-1940:
-------------------------------------
Environment: a service running inside tomcat acts like a client (i.e. uses
fireAndForget).
If there's a burst of send using fireAndForget (in my case to the same
destination) some messages are not received if there's no
a Thread.sleep() call:
1 - From previous posts I understand Thread.sleep is only needed on the client
side (i.e. if the client does not run inside a container)
2 - Different fireAndForget() are issued by different threads
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
