Petals SE POJO

Concurrent processings of a service provider are not stable

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.4.1
  • Fix Version/s: 2.5.0, 2.6.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The concurrent processing of a service provider is not stable. It is due to the actual POJO design that is not stateless:

    • only one instance of POJO is loaded on SU deployment,
    • on each message processing, the JBI listener is set on the POJO.
      If several processing are concurrent, the JBI listener is changed, and strange problems can occur.

    The JBI listener must be set as parameter on POJO methods called to process messages.

    SU developped with previous versions of the SE POJO will not be compatible with the new one.

    Show
    The concurrent processing of a service provider is not stable. It is due to the actual POJO design that is not stateless:
    • only one instance of POJO is loaded on SU deployment,
    • on each message processing, the JBI listener is set on the POJO. If several processing are concurrent, the JBI listener is changed, and strange problems can occur.
    The JBI listener must be set as parameter on POJO methods called to process messages. SU developped with previous versions of the SE POJO will not be compatible with the new one.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Tue, 23 May 2017 - 12:39:30 +0200
Field Original Value New Value
Priority Critical [ 2 ]
Description The concurrent processing of a service provider is not stable. It is due to the actual POJO design that is not stateless:
* only one instance of POJO is loaded on SU deployment,
* on each message processing, the JBI listener is set on the POJO.
If several processing are concurrent, the JBI listener is changed, and strange problems can occur.

The JBI listener must be set as parameter on POJO methods called to process messages. 		The concurrent processing of a service provider is not stable. It is due to the actual POJO design that is not stateless:
* only one instance of POJO is loaded on SU deployment,
* on each message processing, the JBI listener is set on the POJO.
If several processing are concurrent, the JBI listener is changed, and strange problems can occur.

The JBI listener must be set as parameter on POJO methods called to process messages.

*SU developped with previous versions of the SE POJO will not be compatible with the new one.*
Christophe DENEUX made changes - Tue, 23 May 2017 - 12:39:38 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Tue, 23 May 2017 - 12:39:42 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Tue, 23 May 2017 - 12:56:48 +0200
Summary Concurrent processing of a service provider is not stable Concurrent processings of a service provider are not stable
Christophe DENEUX made changes - Tue, 23 May 2017 - 13:01:00 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 2.5.0 [ 10695 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Mon, 23 Apr 2018 - 12:30:53 +0200
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Mon, 23 Apr 2018 - 12:40:19 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Mon, 23 Apr 2018 - 12:40:43 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 2.6.0 [ 10829 ]
Fix Version/s 2.5.0 [ 10695 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Mon, 23 Apr 2018 - 12:40:53 +0200
Fix Version/s 2.5.0 [ 10695 ]

People

Dates

  • Created:
    Tue, 23 May 2017 - 12:37:56 +0200
    Updated:
    Mon, 23 Apr 2018 - 12:40:53 +0200
    Resolved:
    Mon, 23 Apr 2018 - 12:40:43 +0200
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.