Petals ESB Container

Remove the Persistence subsystem

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.0
  • Fix Version/s: 5.0.1
  • Component/s: Persistence
  • Security Level: Public
  • Description:
    Hide

    The Persistence service is responsible of storing exchanges in a SQL database.

    It was used for two things:

    • By the Router Monitor service to store exchanges that were monitored (see PETALSESBCONT-400).
    • By the Priority Orderer module to store exchange in case there is no more memory available in the JVM (in specific cases, see PETALSESBCONT-401).

    Following the removal of both subsystems and the action around PETALSESBCONT-339, the Persistence service has no reason to exist anymore.

    Show
    The Persistence service is responsible of storing exchanges in a SQL database. It was used for two things:
    • By the Router Monitor service to store exchanges that were monitored (see PETALSESBCONT-400).
    • By the Priority Orderer module to store exchange in case there is no more memory available in the JVM (in specific cases, see PETALSESBCONT-401).
    Following the removal of both subsystems and the action around PETALSESBCONT-339, the Persistence service has no reason to exist anymore.
  • Environment:
    -

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Mon, 29 Feb 2016 - 10:22:56 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Mon, 29 Feb 2016 - 10:23:13 +0100
Link This issue depends on PETALSESBCONT-400 [ PETALSESBCONT-400 ]
Victor NOËL made changes - Mon, 29 Feb 2016 - 10:23:22 +0100
Link This issue depends on PETALSESBCONT-401 [ PETALSESBCONT-401 ]
Victor NOËL made changes - Mon, 29 Feb 2016 - 10:23:52 +0100
Description The Persistence service is responsible of storing exchanges in a SQL database.

It was used for two things:
 * By the Router Monitor service to store exchanges that were monitored
 * By the Priority Orderer (see PETALSESBCONT-401) module to store exchange in case there is no more memory available in the JVM (in specific cases only).

Following the removal of both subsystems and the action around PETALSESBCONT-339, the Persistence service has no reason to exist anymore. 		The Persistence service is responsible of storing exchanges in a SQL database.

It was used for two things:
 * By the Router Monitor service to store exchanges that were monitored (see PETALSESBCONT-400).
 * By the Priority Orderer module to store exchange in case there is no more memory available in the JVM (in specific cases, see PETALSESBCONT-401).

Following the removal of both subsystems and the action around PETALSESBCONT-339, the Persistence service has no reason to exist anymore.
Victor NOËL made changes - Mon, 29 Feb 2016 - 10:24:07 +0100
Link This issue blocks PETALSESBCONT-339 [ PETALSESBCONT-339 ]
Victor NOËL made changes - Mon, 29 Feb 2016 - 10:24:36 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Tue, 1 Mar 2016 - 10:19:40 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.1 [ 10579 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Mon, 29 Feb 2016 - 10:22:42 +0100
    Updated:
    Tue, 1 Mar 2016 - 10:19:40 +0100
    Resolved:
    Tue, 1 Mar 2016 - 10:19:39 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.