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 "Michele Mazzucco (JIRA)" <ji...@apache.org> on 2007/01/05 11:15:27 UTC
[jira] Created: (AXIS2-1940) fireAndForget and Thread.sleep
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 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).
--
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
[jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462756 ]
Michele Mazzucco commented on AXIS2-1940:
-----------------------------------------
Is it possible that the problem described http://mail-archives.apache.org/mod_mbox/ws-axis-user/200606.mbox/%3C1149163629.447ed86dc7ee9@maili.uku.fi%3E is due to the many sleep() calls?
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
[jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468222 ]
Deepal Jayasinghe commented on AXIS2-1940:
------------------------------------------
Hi ;
If you use sendRobust , then you do not need to have sleep statement .
> 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
[jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ 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
[jira] Reopened: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-1940:
----------------------------------------
Assignee: Deepal Jayasinghe
> 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
> 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
[jira] Resolved: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Bjorn Townsend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462593 ]
Bjorn Townsend commented on AXIS2-1940:
---------------------------------------
Michele,
The example you're looking at (I assume it's http://ws.apache.org/axis2/1_0/userguide3.html) deals with writing a client using fireAndForget. A client thread would be likely to end prematurely as the docs say; however your emails state that you're using fireAndForget on the server side under Tomcat. I think that you can forego the Thread.sleep() when you're running on the server side under Tomcat's process since there's no danger of the Tomcat process ending before the request can be sent.
Good luck,
Bjorn
> 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 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).
--
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
[jira] Commented: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Darren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (AXIS2-1940) fireAndForget and Thread.sleep
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-1940.
--------------------------------------
Resolution: Fixed
if you are invoking the service inside a running thread then better to use fireAndForget else use sednRobust
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org