Hello,
Due to various character encoding complexities such as the system is
configured to receive UTF-16 and but receives UTF-8 streams etc.. following
exception throws by the httpcore library[0].
At this point the connection will be dropped. But upon receiving this kind
of errors we can recover
Deadlock between SingleClientConnManager.releaseConnection() and
SingleClientConnManager.shutdown()
---
Key: HTTPCLIENT-1127
URL: https://issues.apache.org/jira/browse
Please vote on releasing these packages as HttpComponents AsyncClient
4.0-alpha3. The vote is open for the at least 72 hours, and only votes
from HttpComponents PMC members are binding. The vote passes if at least
three binding +1 votes are cast and there are more +1 than -1 votes.
Packages:
http:
DefaultRequestDirector.tryConnect should make connectCount available
Key: HTTPCLIENT-1126
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1126
Project: HttpComponents HttpClien
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-1109:
--
Comment: was deleted
(was: Closed wrong issue by mistake.
Oleg)
> Parame
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-1109:
--
Comment: was deleted
(was: New connection pool and pooling connection mana
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1104.
---
Resolution: Fixed
Fix Version/s: (was: 4.2 Final)
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski reopened HTTPCLIENT-1109:
---
Closed wrong issue by mistake.
Oleg
> Parameterise connection reuse strate
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1122.
---
Resolution: Fixed
With new ManagedClientConnection implementation the ro
[
https://issues.apache.org/jira/browse/HTTPASYNC-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski moved HTTPCLIENT-258 to HTTPASYNC-8:
--
Fix Version/s: (was: Future)
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1109.
---
Resolution: Fixed
Fix Version/s: (was: Future)
[
https://issues.apache.org/jira/browse/HTTPCLIENT-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-786.
--
Resolution: Fixed
Most of impl.conn & impl.conn.tsccm introduced in 4.0 hav
On Fri, 2011-09-23 at 14:26 +0100, sebb wrote:
> The current JMeter release candidate uses zero retries (default) for
> the HC4 implementation, the default for HC3.1 (3) and Java (1 retry, I
> think).
>
> We noticed that the HC4 implementation shows occasional errors when
> run against some websit
The current JMeter release candidate uses zero retries (default) for
the HC4 implementation, the default for HC3.1 (3) and Java (1 retry, I
think).
We noticed that the HC4 implementation shows occasional errors when
run against some websites, whereas the HC3 does not.
When the HC4 implementation i
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=12473&projectId=77
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 23 Sep 2011 11:25:35 +
Finished at: Fri 23 Sep 2011 11:25:59 +
Total time: 24s
Build Trigger: Schedule
Build N
The Apache HttpComponents project is pleased to announce the release of
HttpComponents HttpCore 4.2-alpha2. This release comes with completely
redesigned and rewritten asynchronous HTTP protocol handlers. New
protocol handling API used in conjunction with connection pooling
components introduced in
16 matches
Mail list logo
