[
https://wso2.org/jira/browse/COMMONS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Suriarachchi resolved COMMONS-61.
---------------------------------------
Resolution: Fixed
fixed with revision 14763.
Now it wait only for new messages. For new messages at the invoker worker it
sends the notification.
> Mercury: server fails to respond when restarting response channel in RM-dual
> channel invocation when request count increases
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: COMMONS-61
> URL: https://wso2.org/jira/browse/COMMONS-61
> Project: WSO2 Commons
> Issue Type: Bug
> Components: Mercury
> Reporter: Charitha Kankanamge
> Assignee: Amila Suriarachchi
> Priority: Critical
>
> I'm getting 'org.apache.commons.httpclient.NoHttpResponseException: The
> server localhost fail
> ed to respond' exception at the server side and following exception at client
> side when restarting response channel of a RM-dual channel invocation.
> 2008-03-13 12:55:36,140 INFO org.apache.axis2.transport.http.HTTPSender -
> Unable to sendViaPost to
> url[http://10.100.1.207:9763/services/Mercurymsgsequenceservice]
> org.apache.commons.httpclient.NoHttpResponseException: The server
> 10.100.1.207 failed to respond
> at
> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1976)
> at
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
> at
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:530)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:191)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:364)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:419)
> at org.wso2.mercury.workers.MessageWorker.run(MessageWorker.java:67)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> at java.lang.Thread.run(Unknown Source)
> Steps to reproduce:
> ===============
> 1. Send ~100 requests to a service which is configured with Mercury
> 2. Stop request channel
> 3. Restart the channel
> 4. Now stop the response channel
> 5. After a few minutes restart response channel
> Server fails to respond.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Commons-dev mailing list
Commons-dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commons-dev
