You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2013/08/03 21:51:48 UTC
[jira] [Updated] (JENA-498) Multiple repeated use of
HttpOp.execHttpPost leads to "No buffer space available (maximum
connections reached?)"
[ https://issues.apache.org/jira/browse/JENA-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne updated JENA-498:
-------------------------------
Summary: Multiple repeated use of HttpOp.execHttpPost leads to "No buffer space available (maximum connections reached?)" (was: Multipel use of HttpOp.execHttpPost leading to "No buffer space available (maximum connections reached?)")
> 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
> Reporter: Andy Seaborne
>
> 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