7:37 a.m.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Mark Little
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
7:33 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=all ]
Mark Little reassigned JBESB-719:
---------------------------------
Assignee: Daniel Bevenius (was: Mark Little)
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
2:49 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=all ]
Mark Little updated JBESB-719:
------------------------------
Fix Version/s: 4.2.1
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
10:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=comments#action_12374929 ]
Mark Little commented on JBESB-719:
-----------------------------------
Should really be configurable, as it is in JMS. Reliable delivery is not always needed.
But conversely, sometimes it is! Propose making this configurable (e.g., another option on
the JMSEpr), so the service deployer can define what should be used.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
12:52 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=all ]
Work on JBESB-719 started by Daniel Bevenius.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
2:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=comments#action_12383380 ]
Daniel Bevenius commented on JBESB-719:
---------------------------------------
Committed revision 15936.
This commit takes care of step 1, which is to add the ability to configure the acknowledge
mode for jms session.
Doing this in two commits after discussing this with Mark.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
2:37 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=comments#action_12383381 ]
Kevin Conner commented on JBESB-719:
------------------------------------
Daniel, please do not do part 2 without discussing with me. Using thread local variables
is likely to break the resource handling.
As for reliability, we now have transaction support for JMS.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
2:39 a.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=all ]
Work on JBESB-719 stopped by Daniel Bevenius.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
3:58 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=comments#action_12384505 ]
Kevin Conner commented on JBESB-719:
------------------------------------
I believe the second part of this is adequately covered by the JCA/JMS inflow. We should
close this now.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
9:31 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=all ]
Kevin Conner updated JBESB-719:
-------------------------------
Fix Version/s: 4.2.1 triage
(was: 4.2.1)
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1 triage
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
4:46 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-719) The messages can be lost in case of ESB termination
[ http://jira.jboss.com/jira/browse/JBESB-719?page=all ]
Mark Little closed JBESB-719.
-----------------------------
Resolution: Done
I agree with Kevin and am closing.
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Fix For: 4.2.1 CP1
Even if the ESB is using internally reliable JMS as a transport the messages can be lost
during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If
the allocated session is stored into ThreadLocal variable and returned by the subsequent
calls by the same thread and get commited on call JMSConnectionPool.closeSession() then
all internal message transfers via JMS will be done in transaction - one transfer/one
transaction.
--
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
6175
days inactive
6290
days old
10 comments
4 participants
participants (4)
-
Daniel Bevenius (JIRA) -
Jiri Pechanec (JIRA)
-
Kevin Conner (JIRA)
-
Mark Little (JIRA)