While using `rdf4j`, I encountered this error, which I reported on [their repo](https://github.com/eclipse/rdf4j/issues/4473).

It only happens on Virtuoso 7.2.8 and above.

I came across [this forum ](https://groups.google.com/g/rdf4j-users/c/mYijXw3Oa24):
> At the HTTP level a connection can often be reused to reduce latency, but sometimes this connection gets closed by the server while the client still thinks the connection is open.

>Older versions of Apache HttpClient checked for stale connections themselves, and simply opened a new one when necessary. For the current version we had to add a custom retry handler that serves the same purpose, and this handler logs these warnings.

Is there anything I can do from `virtuoso.ini` file to workaround this?
Closing stale connection with Openlink Virtuoso Docker image version > 7.2.7
This is a GitHub Issue
repo:virtuoso-opensource
owner:openlink
Title : Closing stale connection with Openlink Virtuoso Docker image version > 7.2.7
Issue date:

--- start body ---
While using `rdf4j`, I encountered this error, which I reported on [their repo](https://github.com/eclipse/rdf4j/issues/4473).

It only happens on Virtuoso 7.2.8 and above.

I came across [this forum ](https://groups.google.com/g/rdf4j-users/c/mYijXw3Oa24):
> At the HTTP level a connection can often be reused to reduce latency, but sometimes this connection gets closed by the server while the client still thinks the connection is open.

>Older versions of Apache HttpClient checked for stale connections themselves, and simply opened a new one when necessary. For the current version we had to add a custom retry handler that serves the same purpose, and this handler logs these warnings.

Is there anything I can do from `virtuoso.ini` file to workaround this?
--- end body ---
