Petals SE POJO

Unable to manage expired asynch message in su-pojo

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.2.6
  • Fix Version/s: 2.2.7, 2.3.0
  • Component/s: None
  • Security Level: Public
  • Description:

    The JBIListener.onExpiredAsyncJBIMessage method , just return false.

    So we can't manage expired asynch message in a su-pojo.

  • Environment:
    Petals 3.1.3
    windows xp

Attachments

  1. Zip Archive
    petals-se-pojo-2.2.7-SNAPSHOT.zip
    (4.99 MB)
    Christophe DENEUX
    Sat, 17 Mar 2012 - 11:55:13 +0100

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1d 17h 47m
1
Christophe DENEUX
Sat, 17 Mar 2012 - 11:02:49 +0100
Open Open In Progress In Progress
12s
1
Christophe DENEUX
Sat, 17 Mar 2012 - 11:03:01 +0100
In Progress In Progress Resolved Resolved
5d 2h 7m
1
Christophe DENEUX
Thu, 22 Mar 2012 - 13:10:10 +0100
Resolved Resolved Open Open
14s
1
Christophe DENEUX
Thu, 22 Mar 2012 - 13:10:24 +0100
Open Open In Progress In Progress
4d 51m
1
Christophe DENEUX
Mon, 26 Mar 2012 - 15:02:14 +0200
In Progress In Progress Resolved Resolved
19s
1
Christophe DENEUX
Mon, 26 Mar 2012 - 15:02:33 +0200

People

Dates

  • Created:
    Thu, 15 Mar 2012 - 17:15:00 +0100
    Updated:
    Mon, 26 Mar 2012 - 15:02:33 +0200
    Resolved:
    Mon, 26 Mar 2012 - 15:02:33 +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.