[
https://wso2.org/jira/browse/ESBJAVA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25839#action_25839
]
Hiranya Jayathilaka commented on ESBJAVA-593:
---------------------------------------------
Apache Synapse migrated to the latest httpcore and httpcore-nio versions
sometime back and keeping in sync with Synapse we have also moved WSO2 ESB to
the latest httpcore/httpcore-nio versions. Next ESB release will ship with the
latest httpcore/httpcore-nio jars.
> Timeout bug with http2jms transport, waiting for HTTP response 202 ACCEPTED
> (because of httpcore-4.0-beta1.jar and httpcore-nio-4.0-beta1.jar)
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-593
> URL: https://wso2.org/jira/browse/ESBJAVA-593
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: 1.7.1, 2.0
> Environment: Suse Linux 10 Enterprise Server, Windows XP
> Professional,
> Reporter: Alexander Schleif
> Assignee: Ruwan Linton
>
> Our test scenario: Like Synpase Example 251 (Axis2 1.4-Client -> WSO2
> ESB1.7.1 -> ActiveMQ), difference: Client waits for HTTP Response 202
> Accepted (in the example client sends the request with fireAndForget(), so
> you don't realize that bug ).
> We had problems with the http2jms transport waiting on the client for a HTTP
> Response 202 Accepted: The JMS Message is alwasy delivered to JMS (ActiveMQ)
> at once, but sometimes it lasts to the socket timeout of the client (it was
> exactly the value of http.socket.timeout configured in the client) until it
> receives HTTP 202. The problem happens very often (>95% of the requests) on
> Linux (Suse Linux 10 ES), rarely on Windows. But even on Windows sometimes
> the problem occured. When we debugged the code, we realized that the end of
> the chunks of the HTTP-reponse (0) ist not send to the client. So the the
> client does not recognize that the http response is already complete.
> Our Solution:
> Use the final versions of httpcore4 and http-nio4
> (httpcore-4.0.jar,httpcore-nio-4.0.jar) instead of the beta versions
> (httpcore-4.0-beta1.jar, httpcore-nio-4.0-beta1.jar) in WSO2 ESB. They
> beta-versions are used both in WSO2 ESB1.7 and the WSO2 ESB2.0 .
> Even Axis2 1.4 uses beta's of httpcore and httpcore-nio. I think it would be
> useful to replace them in Axis2, too.
> Kind regards,
> Alex
--
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
_______________________________________________
Esb-java-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
