[JBoss JIRA] Created: (JBESB-1810) There is no retry limit when using transacted SQL listener

[JBoss JIRA] Created: (JBESB-2893)...

[JBoss JIRA] Created: (JBESB-2888)...

Jiri Pechanec (JIRA)

Friday, 13 June 2008 Fri, 13 Jun '08

9:33 a.m.

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: http://jira.jboss.com/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Jiri Pechanec (JIRA)

Friday, 13 June Fri, 13 Jun

9:33 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ http://jira.jboss.com/jira/browse/JBESB-1810?page=all ] Jiri Pechanec updated JBESB-1810: --------------------------------- Issue Type: Feature Request (was: Bug)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: http://jira.jboss.com/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Kevin Conner (JIRA)

Thursday, 6 November Thu, 6 Nov

4:38 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner reassigned JBESB-1810: ----------------------------------- Assignee: (was: Kevin Conner)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Daniel Bevenius (JIRA)

6:06 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Daniel Bevenius reassigned JBESB-1810: -------------------------------------- Assignee: Daniel Bevenius

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Daniel Bevenius (JIRA)

6:12 a.m.

New subject: [JBoss JIRA] Work started: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Work on JBESB-1810 started by Daniel Bevenius.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

Thursday, 13 November Thu, 13 Nov

6:10 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner reassigned JBESB-1810: ----------------------------------- Assignee: (was: Daniel Bevenius)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.2.1 CP5 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

6:10 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-1810: -------------------------------- Fix Version/s: 4.2.1 CP5 (was: 4.2.1 CP4) I am moving this back a release as it involves invasive changes to the current codebase. We need more time to consider this before continuing. The SOA issue appears to have been closed two weeks ago as 'Won't fix' but we will keep it open.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.2.1 CP5 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

6:12 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner reassigned JBESB-1810: ----------------------------------- Assignee: (was: Kevin Conner)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.2.1 CP5 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

6:12 a.m.

New subject: [JBoss JIRA] Work stopped: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Work on JBESB-1810 stopped by Kevin Conner.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Kevin Conner Priority: Critical Fix For: 4.2.1 CP5 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

6:12 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner reassigned JBESB-1810: ----------------------------------- Assignee: Kevin Conner

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Kevin Conner Priority: Critical Fix For: 4.2.1 CP5 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Mark Little (JIRA)

Saturday, 14 February Sat, 14 Feb

4:01 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Mark Little commented on JBESB-1810: ------------------------------------ I reopened the SOA issue as it shouldn't have been closed. Moved to a non-CP release too as it's a feature request.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.2.1 CP5 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

Wednesday, 15 April Wed, 15 Apr

9:07 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-1810: -------------------------------- Fix Version/s: 4.6 (was: 4.2.1 CP5)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.6 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Kevin Conner (JIRA)

Monday, 6 July Mon, 6 Jul

4:40 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-1810: -------------------------------- Fix Version/s: 4.7 (was: 4.6)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Daniel Bevenius (JIRA)

Friday, 9 October Fri, 9 Oct

5:47 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Daniel Bevenius reassigned JBESB-1810: -------------------------------------- Assignee: Daniel Bevenius

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Daniel Bevenius (JIRA)

6:03 a.m.

New subject: [JBoss JIRA] Work started: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Work on JBESB-1810 started by Daniel Bevenius.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Daniel Bevenius (JIRA)

Sunday, 11 October Sun, 11 Oct

10:07 a.m.

New subject: [JBoss JIRA] Work stopped: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Work on JBESB-1810 stopped by Daniel Bevenius.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Daniel Bevenius (JIRA)

10:09 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Daniel Bevenius reassigned JBESB-1810: -------------------------------------- Assignee: (was: Daniel Bevenius)

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Tom Fennelly (JIRA)

Monday, 12 October Mon, 12 Oct

4:55 a.m.

New subject: [JBoss JIRA] Work started: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Work on JBESB-1810 started by Tom Fennelly.

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Tom Fennelly Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Tom Fennelly (JIRA)

4:55 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Tom Fennelly reassigned JBESB-1810: ----------------------------------- Assignee: Tom Fennelly

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Tom Fennelly Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

Tom Fennelly (JIRA)

Monday, 19 October Mon, 19 Oct

6:45 a.m.

New subject: [JBoss JIRA] Closed: (JBESB-1810) There is no retry limit when using transacted SQL listener

[ https://jira.jboss.org/jira/browse/JBESB-1810?page=com.atlassian.jira.plu... ] Tom Fennelly closed JBESB-1810. ------------------------------- Resolution: Done trunk: 29656

...

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: https://jira.jboss.org/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assignee: Tom Fennelly Priority: Critical Fix For: 4.7 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ.

5327

days inactive

5820

days old

esb-issues@lists.jboss.org

Manage subscription

19 comments

5 participants

tags (0)

participants (5)

Daniel Bevenius (JIRA)
Jiri Pechanec (JIRA)
Kevin Conner (JIRA)
Mark Little (JIRA)
Tom Fennelly (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[JBoss JIRA] Created: (JBESB-1810) There is no retry limit when using transacted SQL listener