Project

General

Profile

feature request #5356

Handle exceptions which require reconnect

Added by Cherian Mathew over 5 years ago. Updated about 1 month ago.

Status:
New
Priority:
New
Category:
taxeditor
Target version:
Start date:
11/27/2015
Due date:
% Done:

0%

Severity:
normal

Description

There are some exceptions which should 'never' occur in remoting, but when they do the safest option is to perform a reconnect.

These include,

  • org.hibernate.LazyInitializationException: could not initialize proxy - no Session

  • java.lang.IllegalStateException: An entity copy was already assigned to a different entity

In the case of these exception, we should popup a cdm error dialog. with the extra hint to the user to reconnect.

History

#1 Updated by Cherian Mathew over 5 years ago

  • Target version changed from Remoting 5.0 to Remoting 6.0

This can be added to the exception handling in eu.etaxonomy.taxeditor.ApplicationWorkbenchAdvisor.

#2 Updated by Andreas Müller 4 months ago

  • Description updated (diff)
  • Target version changed from Remoting 6.0 to Release 5.19
  • Private changed from Yes to No

moving this open remoting 6.0 ticket to current milestone to decide what to do with it.

Is the above mentioned solution really possible?

#3 Updated by Andreas Müller 3 months ago

  • Target version changed from Release 5.19 to Release 5.21

#4 Updated by Andreas Müller about 1 month ago

  • Target version changed from Release 5.21 to Release 5.22

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)