Weasis error: org.weasis.core.api.util.NetworkUtil: http response: Read timed out

[Rana Asim Wajid]

Any idea what could be causing this error when loading study in Weasis via JNLP....any way to increase the time out ?

13.09.2018 15:53:32.171 *ERROR* [Dicom Model-pool-4-thread-1] org.weasis.core.api.util.NetworkUtil: http response: Read timed out

13.09.2018 15:53:32.171 *ERROR* [Dicom Model-pool-4-thread-1] org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest: Download failed org.weasis.dicom.explorer.wado.DownloadException: Error on loading the XML Manifest from: http://172.28.98.133:8080/weasis-pacs-connector/RequestManifest?id=5
    at org.weasis.dicom.explorer.wado.DownloadManager.buildDicomSeriesFromXml(DownloadManager.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.downloadManifest(LoadRemoteDicomManifest.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.doInBackground(LoadRemoteDicomManifest.java)
13.09.2018 15:53:32.171 *INFO* [Dicom Model-pool-4-thread-1] org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest: Try donloaging again: [http://172.28.98.133:8080/weasis-pacs-connector/RequestManifest?id=5]
13.09.2018 15:53:32.171 *INFO* [SwingWorker-pool-6-thread-1] org.weasis.dicom.explorer.wado.DownloadManager: Downloading XML manifest: /weasis-pacs-connector/RequestManifest
13.09.2018 15:53:39.219 *ERROR* [SwingWorker-pool-6-thread-1] org.weasis.core.api.util.NetworkUtil: http response: Read timed out
13.09.2018 15:53:39.219 *ERROR* [SwingWorker-pool-6-thread-1] org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest: Download failed org.weasis.dicom.explorer.wado.DownloadException: Error on loading the XML Manifest from: http://172.28.98.133:8080/weasis-pacs-connector/RequestManifest?id=5
    at org.weasis.dicom.explorer.wado.DownloadManager.buildDicomSeriesFromXml(DownloadManager.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.downloadManifest(LoadRemoteDicomManifest.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.doInBackground(LoadRemoteDicomManifest.java)

[Rana Asim Wajid]

Anyone?

[Nicolas Roduit]

It means the service behind the URL cannot be processed. Look at the server log file. The is could be a security restriction or a misconfiguration.

[Rana Asim Wajid]

problem is this only happens when the server is under high load or the connection is slow like on a cell phone....is there any way to increase the time before time out occurs?

org.weasis.core.api.util.NetworkUtil: http response: Read timed out

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/uSaksoIQCO0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Regards,
Rana Asim Wajid

[Nicolas Roduit]

If it is the server that is overloaded then increasing the timeout would only worsen the situation. The default timeout is 7 seconds and it seems more appropriate to me to set an exception than to continue to overload the server.

It is the same for the network timeout it seems better to throw an exception than let the viewer hangs on many connections (for each image to download).

So if you get read timeout it means that the server is not sized for the request but even on mini-pc with low capacity I haven't seen this kind of issues.

Le vendredi 14 septembre 2018 16:38:44 UTC+2, Rana Asim Wajid a écrit :

problem is this only happens when the server is under high load or the connection is slow like on a cell phone....is there any way to increase the time before time out occurs?

org.weasis.core.api.util.NetworkUtil: http response: Read timed out

On Fri, 14 Sep 2018 at 19:30 Nicolas Roduit wrote:

It means the service behind the URL cannot be processed. Look at the server log file. The is could be a security restriction or a misconfiguration.

Le jeudi 13 septembre 2018 12:58:08 UTC+2, Rana Asim Wajid a écrit :

Any idea what could be causing this error when loading study in Weasis via JNLP....any way to increase the time out ?

13.09.2018 15:53:32.171 *ERROR* [Dicom Model-pool-4-thread-1] org.weasis.core.api.util.NetworkUtil: http response: Read timed out

13.09.2018 15:53:32.171 *ERROR* [Dicom Model-pool-4-thread-1] org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest: Download failed org.weasis.dicom.explorer.wado.DownloadException: Error on loading the XML Manifest from: http://172.28.98.133:8080/weasis-pacs-connector/RequestManifest?id=5
    at org.weasis.dicom.explorer.wado.DownloadManager.buildDicomSeriesFromXml(DownloadManager.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.downloadManifest(LoadRemoteDicomManifest.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.doInBackground(LoadRemoteDicomManifest.java)
13.09.2018 15:53:32.171 *INFO* [Dicom Model-pool-4-thread-1] org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest: Try donloaging again: [http://172.28.98.133:8080/weasis-pacs-connector/RequestManifest?id=5]
13.09.2018 15:53:32.171 *INFO* [SwingWorker-pool-6-thread-1] org.weasis.dicom.explorer.wado.DownloadManager: Downloading XML manifest: /weasis-pacs-connector/RequestManifest
13.09.2018 15:53:39.219 *ERROR* [SwingWorker-pool-6-thread-1] org.weasis.core.api.util.NetworkUtil: http response: Read timed out
13.09.2018 15:53:39.219 *ERROR* [SwingWorker-pool-6-thread-1] org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest: Download failed org.weasis.dicom.explorer.wado.DownloadException: Error on loading the XML Manifest from: http://172.28.98.133:8080/weasis-pacs-connector/RequestManifest?id=5
    at org.weasis.dicom.explorer.wado.DownloadManager.buildDicomSeriesFromXml(DownloadManager.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.downloadManifest(LoadRemoteDicomManifest.java)
    at org.weasis.dicom.explorer.wado.LoadRemoteDicomManifest.doInBackground(LoadRemoteDicomManifest.java)

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/uSaksoIQCO0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[Rana Asim Wajid]

Can you tell me how to increase the 7 second timeout just for testing?

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Regards,
Rana Asim Wajid

--

You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/uSaksoIQCO0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

[Nicolas Roduit]

In this case, it is hard coded.

Le samedi 15 septembre 2018 16:27:07 UTC+2, Rana Asim Wajid a écrit :

Can you tell me how to increase the 7 second timeout just for testing?

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Regards,
Rana Asim Wajid

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/uSaksoIQCO0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

[Rana Asim Wajid]

can you kindly add an option in the config file to change this?

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Regards,
Rana Asim Wajid

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/uSaksoIQCO0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[Nicolas Roduit]

If you can demonstrate that there is something wrong, I'm going to look at it. Otherwise, I have absolutely no time to help with tests.

[Rana Asim Wajid]

How do you want me to do that? Please guide me.

[Nicolas Roduit]

I mean by "demonstrate": give a reproducible test case.

My opinion is if you're out of the default timeout values there is something wrong with a configuration or the network. You can change the default time values in weasis but I think you will not solve the real problem. Nevertheless, I might not have understood an element, so in this case argue.

  

Le mardi 25 septembre 2018 16:33:41 UTC+2, Rana Asim Wajid a écrit :

How do you want me to do that? Please guide me.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

[Rana Asim Wajid]

This issue is that the timeout only occurs on very slow connections with high latency or when the pacs DB is under high load.

You said that "You can change the default time values in weasis but I think you will not solve the real problem". Could you please tell me how to do this as you previously said they were hard coded.

[Nicolas Roduit]

I've never seen such issues since 2009 (the public distribution of the application). If the PACS takes more than 7 seconds to start replying to the WADO request, it seems not usable.

The current configuration supports some network interruptions and will automatically ask you to redownload the missing images.

As I told you I cannot invest time for solving non-reproducible problems. 

You are still free to change the values and rebuild the project.

Le vendredi 28 septembre 2018 17:00:45 UTC+2, Rana Asim Wajid a écrit :

This issue is that the timeout only occurs on very slow connections with high latency or when the pacs DB is under high load.

You said that "You can change the default time values in weasis but I think you will not solve the real problem". Could you please tell me how to do this as you previously said they were hard coded.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/uSaksoIQCO0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

[Rana Asim Wajid]

Hi Nicolas,

                The problem keeps popping up again and again on all three of the servers I have tested on. The scenario is as follows: If the study is a small one (for example an xray or MRI) the problem never occurs but when the study is a large one with thousands of instances (CT scans or fluoroscopy studies) the timeout issue occurs very frequently.My wild guess is because the manifest file isn't generated in the allotted time because of the extremely large size of the study the timeout occurs. I hope this makes sense and you can help out.

On Thursday, 13 September 2018 15:58:08 UTC+5, Rana Asim Wajid wrote:

[Nicolas Roduit]

The read timeout is not the time of the complete returning the response, see https://stackoverflow.com/questions/24554342/understanding-urlconnection-setreadtimeout

Anyway I will increase the default timeout for the manifest and allow to inject a default configuration in the next release, see https://github.com/nroduit/Weasis/commit/9fbd0c2a7a35f4cf7381d5bb96895e265ddd7d10

[Asim Wajid]

Much appreciated. Look forward to the next release.

 

Regards,
Rana Asim Wajid