Project

General

Profile

Actions
Copy link

bug #10017

open

Progressmonitoring should be more fault-tolerant

Added by Katja Luther about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
New
Assignee:
Katja Luther
Category:
taxeditor
Target version:
Unassigned CDM tickets
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

Actually the progressmonitoring immediately throws exception when the server does not react, this should be handled with more fault-tolerance because bad performance or a unresponsive server also results in an exception, but should be excepted for 3 or 5 requests.

Actions
Copy link
 #1

Updated by Andreas Müller about 2 years ago

Katja Luther wrote:

Actually the progressmonitoring immediately throws exception when the server does not react, this should be handled with more fault-tolerance because bad performance or a unresponsive server also results in an exception, but should be excepted for 3 or 5 requests.

As far as I remember "not react" is already implemented. The issue here is handling exceptions thrown serverside during progressmonitoring. These should be catched by the client and only shown to the user if they appear each time and also with the message that it does not mean that the server side operation itself did not work correctly.

Actions
Copy link
 #2

Updated by Andreas Müller about 2 years ago

An example for such a server side thrown exception:

java : 1.8.0_321
org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [http://132.248.13.83:8080/cdmserver/cdm_flora_mexico/remoting/progressmonitor.service]; nested exception is org.apache.http.TruncatedChunkException: Truncated chunk (expected size: 32,768; actual size: 23,656)
               at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:226)
               at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:153)
               at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
               at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
               at com.sun.proxy.$Proxy51.getRemotingMonitor(Unknown Source)
               at eu.etaxonomy.taxeditor.model.AbstractUtility.executeMoniteredOperation(AbstractUtility.java:613)
               at eu.etaxonomy.taxeditor.navigation.navigator.operation.MoveTaxonOperation.lambda$0(MoveTaxonOperation.java:86)
...
Caused by: org.apache.http.TruncatedChunkException: Truncated chunk (expected size: 32,768; actual size: 23,656)
               at org.apache.http.impl.io.ChunkedInputStream.read(ChunkedInputStream.java:197)
               at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135)
               at java.io.ObjectInputStream$PeekInputStream.read(Unknown Source)
...
Actions
Copy link

Also available in: Atom PDF