Petals SE KPI

When a JDBCException raised during notification processing, it is totally killed

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    JDBCException are runtime exceptions wrapped into other spring DataAccessException specific runtime exception.
    Notification Storage is a single thread launched by the se-kpi to process notification and store them in DB. If a JDBCException (like DataIntegrityViolation for forbidden duplicate entries) is thrown during notification storage, this thread is killed and never recreated. So notification processing is down.

    DataAccessException must be catch to avoid this issue.

    Show
    JDBCException are runtime exceptions wrapped into other spring DataAccessException specific runtime exception. Notification Storage is a single thread launched by the se-kpi to process notification and store them in DB. If a JDBCException (like DataIntegrityViolation for forbidden duplicate entries) is thrown during notification storage, this thread is killed and never recreated. So notification processing is down. DataAccessException must be catch to avoid this issue.
  • Environment:
    petals esb 3.1.1, petals view ( notif proc ) 1.3

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
16s
1
Olivier Fabre
Wed, 23 Mar 2011 - 14:37:27 +0100

People

Dates

  • Created:
    Wed, 23 Mar 2011 - 14:37:11 +0100
    Updated:
    Wed, 23 Mar 2011 - 14:38:39 +0100