[
https://issues.apache.org/jira/browse/JENA-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735017#comment-13735017
]
Andy Seaborne commented on JENA-498:
------------------------------------
As checked in, yes. I have found this to be the safest setup; no risk of
lock-up. The commented code is a note - I can remove it if you think it does
more harm than good. I suspect that the real fix was made when I was tracking
down stream use and properly closing, including when an HTTP 4xx or 5xx was
returned.
> Multiple repeated use of HttpOp.execHttpPost leads to "No buffer space
> available (maximum connections reached?)"
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JENA-498
> URL: https://issues.apache.org/jira/browse/JENA-498
> Project: Apache Jena
> Issue Type: Bug
> Components: RIOT
> Affects Versions: Jena 2.10.1, Fuseki 0.2.7
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 2.10.2
>
>
> From
> http://mail-archives.apache.org/mod_mbox/jena-users/201308.mbox/%3CCAE5DGJjODJJ-o5t4gJCGqc6mXPyLgDbsDgD%2BxM0eU6WZVacbbw%40mail.gmail.com%3E
> See
> http://stackoverflow.com/questions/6068423/java-net-socketexception-no-buffer-space-available-maximum-connections-reached
> Things to check:
> * The SO link suggests having only one HttpClient.
> * Make sure the POST is closed (entity consumed)
> * Call HttpRequestBase.reset()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
