[
https://issues.apache.org/jira/browse/HTTPCLIENT-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17995760#comment-17995760
]
Oleg Kalnichevski edited comment on HTTPCLIENT-2379 at 7/4/25 12:38 PM:
------------------------------------------------------------------------
> I believe this is a serious issue
[~yhzdys] Nowhere did I say it was not serious. In fact I find it so serious so
I want to take time and come up with a proper solution
> With this check the first release delegates once (as designed); later
> releases are ignored, so the delegate pool never sees the entry again and the
> {{IllegalStateException}} disappears. I'm saying something stupid??
[~abernal] No, you are not. This is a fairly obvious and straight-forward of
making the immediate problem go disappear. But please consider this: with the
proposed change every time the pool gets a PoolEntry that looks not OK it _has_
to assume this PoolEntry has been previously released. What if it is not? What
if there was a defect in the caller code?
Oleg
was (Author: olegk):
> I believe this is a serious issue
[~yhzdys] Nowhere did I say it was not serious. In fact I find it so serious so
I do not want to take time and come up with a proper solution
> With this check the first release delegates once (as designed); later
> releases are ignored, so the delegate pool never sees the entry again and the
> {{IllegalStateException}} disappears. I'm saying something stupid??
[~abernal] No, you are not. This is a fairly obvious and straight-forward of
making the immediate problem go disappear. But please consider this: with the
proposed change every time the pool gets a PoolEntry that looks not OK it _has_
to assume this PoolEntry has been previously released. What if it is not? What
if there was a defect in the caller code?
Oleg
> Multiple removal of same PoolEntry causes IllegalStateException in
> H2SharingConnPool
> ------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-2379
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2379
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (async)
> Affects Versions: 5.5
> Reporter: yhzdys
> Priority: Major
> Fix For: 5.5.1, 5.6-alpha1
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> After enabling messageMultiplexing, the H2SharingConnPool is used to reuse
> PoolEntry.
> When making more than one request using the same connection, if the
> connection is closed,
> the pool.release(entry, reusable) method at H2SharingConnPool.java:183 will
> throw the following exception:
> ~~~java
> throw new IllegalStateException("Pool entry is not present in the set of
> leased entries");
> ~~~
> This occurs because the same connection is being removed multiple times.
> https://github.com/yhzdys/httpcomponents-client/commit/c8256b33c3adb45cfa2a49efb2dacfb611da9ac1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
