Project

General

Profile

Actions
Copy link

feature request #5356

open

Handle exceptions which require reconnect

Added by Cherian Mathew over 8 years ago. Updated about 3 years ago.

Status:
New
Priority:
New
Assignee:
Andreas Müller
Category:
taxeditor
Target version:
Release 5.46
Start date:
Due date:
% Done:

0%

Estimated time:
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.

Actions
Copy link
 #1

Updated by Cherian Mathew over 8 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.

Actions
Copy link
 #2

Updated by Andreas Müller over 3 years 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?

Actions
Copy link
 #3

Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 5.19 to Release 5.21
Actions
Copy link
 #4

Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 5.21 to Release 5.22
Actions
Copy link
 #5

Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 5.22 to Release 5.46
Actions
Copy link

Also available in: Atom PDF