Petals ESB Container

Message Persistance Service should be asynchronous

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Won't Fix
  • Affects Version/s: 4.1.0
  • Fix Version/s: 5.0.1
  • Component/s: Persistence
  • Security Level: Public
  • Description:
    Hide

    The current/default persitence service stores messages in a synchronous way (org.ow2.petals.system.persistence.PersistenceServiceImpl#addMessageExchange).
    This operation can be time consuming and should be asynchronous.

    In order to ease the developer life, I suggest to create a PersistenceManager which implements org.ow2.petals.system.persistence.PersistenceService and delegate storage to a default synchronous service. The asynchronous stuff has to be done in the manager.

    Show
    The current/default persitence service stores messages in a synchronous way (org.ow2.petals.system.persistence.PersistenceServiceImpl#addMessageExchange). This operation can be time consuming and should be asynchronous. In order to ease the developer life, I suggest to create a PersistenceManager which implements org.ow2.petals.system.persistence.PersistenceService and delegate storage to a default synchronous service. The asynchronous stuff has to be done in the manager.
  • Environment:
    *

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 17 Jul 2012 - 15:06:30 +0200

In my mind, this service was used by the RouterMonitor to store message exchanges as a monitoring purpose and was used with the Petals web console.
I think that it not a persistence service in a message delivery warranty purpose.

So this service could be simply removed !

Show
Christophe DENEUX added a comment - Tue, 17 Jul 2012 - 15:06:30 +0200 In my mind, this service was used by the RouterMonitor to store message exchanges as a monitoring purpose and was used with the Petals web console. I think that it not a persistence service in a message delivery warranty purpose. So this service could be simply removed !
Hide
Permalink
Christophe Hamerling added a comment - Tue, 17 Jul 2012 - 16:39:14 +0200

Need to check, it may also be used to send again messages in case of failures

Show
Christophe Hamerling added a comment - Tue, 17 Jul 2012 - 16:39:14 +0200 Need to check, it may also be used to send again messages in case of failures
Hide
Permalink
Victor NOËL added a comment - Mon, 29 Feb 2016 - 11:00:37 +0100

Persistence service is being removed: PETALSESBCONT-402

Show
Victor NOËL added a comment - Mon, 29 Feb 2016 - 11:00:37 +0100 Persistence service is being removed: PETALSESBCONT-402
Victor NOËL made changes - Mon, 29 Feb 2016 - 11:00:37 +0100
Field Original Value New Value
Resolution Won't Fix [ 2 ]
Status New [ 10000 ] Resolved [ 10004 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Christophe DENEUX made changes - Mon, 29 Feb 2016 - 13:06:02 +0100
Fix Version/s 5.0.1 [ 10579 ]
Priority Blocker [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Resolved Resolved
1321d 23h 35m
1
Victor NOËL
Mon, 29 Feb 2016 - 11:00:37 +0100



People

Dates

  • Created:
    Tue, 17 Jul 2012 - 12:24:54 +0200
    Updated:
    Mon, 29 Feb 2016 - 13:06:02 +0100
    Resolved:
    Mon, 29 Feb 2016 - 11:00:37 +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.