You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Brian Roach (JIRA)" <ji...@apache.org> on 2008/08/18 09:23:52 UTC
[jira] Created: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
---------------------------------------------------------------------------------------------------------------------------------------------------------
Key: AMQCPP-193
URL: https://issues.apache.org/activemq/browse/AMQCPP-193
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: Openwire
Affects Versions: 2.2, 2.3
Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
Reporter: Brian Roach
Assignee: Nathan Mittler
Fix For: 2.3, 2.2
Attachments: transactionTest.cpp
If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
The exception text is: No valid response received for command
The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
To summarize:
- Start sending messages with the session set to SESSION_TRANSACTED
- Fill ActiveMQ memory
- Receive exception
- The last message sent will be in the queue. All other messages will be rolled back.
Here's what the debug log looks like:
DEBUG Usage - Memory usage change. from: 2, to: 1
DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
DEBUG Usage - Memory usage change. from: 1, to: 0
DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
As you can see, it adds a message to the queue after the rollback and after stopping the connection.
Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
Posted by "Brian Roach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45020#action_45020 ]
Brian Roach commented on AMQCPP-193:
------------------------------------
One other thing - the behavior is slightly different with the current 2.3 trunk;
The trunk (2.3?) now blocks when the memory fill occurs. However, if you kill the client, the same problem occurs - the last message winds up in the queue outside of the transaction. And, unfortunately, wrapping the Producer::send() in an alarm and destroying the session on a timeout doesn't solve the problem - still get that last message sent.
> If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-193
> URL: https://issues.apache.org/activemq/browse/AMQCPP-193
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.2, 2.3
> Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
> Reporter: Brian Roach
> Assignee: Nathan Mittler
> Fix For: 2.2, 2.3
>
> Attachments: transactionTest.cpp
>
>
> If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
> The exception text is: No valid response received for command
> The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
> To summarize:
> - Start sending messages with the session set to SESSION_TRANSACTED
> - Fill ActiveMQ memory
> - Receive exception
> - The last message sent will be in the queue. All other messages will be rolled back.
> Here's what the debug log looks like:
> DEBUG Usage - Memory usage change. from: 2, to: 1
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
> DEBUG Usage - Memory usage change. from: 1, to: 0
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
> DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
> DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
> As you can see, it adds a message to the queue after the rollback and after stopping the connection.
> Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQCPP-193.
-------------------------------
Resolution: Cannot Reproduce
> If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-193
> URL: https://issues.apache.org/activemq/browse/AMQCPP-193
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.2, 2.3
> Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
> Reporter: Brian Roach
> Assignee: Timothy Bish
> Fix For: 2.3
>
> Attachments: transactionTest.cpp
>
>
> If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
> The exception text is: No valid response received for command
> The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
> To summarize:
> - Start sending messages with the session set to SESSION_TRANSACTED
> - Fill ActiveMQ memory
> - Receive exception
> - The last message sent will be in the queue. All other messages will be rolled back.
> Here's what the debug log looks like:
> DEBUG Usage - Memory usage change. from: 2, to: 1
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
> DEBUG Usage - Memory usage change. from: 1, to: 0
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
> DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
> DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
> As you can see, it adds a message to the queue after the rollback and after stopping the connection.
> Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-193:
--------------------------------
Fix Version/s: 2.3
(was: 2.2)
> If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-193
> URL: https://issues.apache.org/activemq/browse/AMQCPP-193
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.2, 2.3
> Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
> Reporter: Brian Roach
> Assignee: Nathan Mittler
> Fix For: 2.3
>
> Attachments: transactionTest.cpp
>
>
> If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
> The exception text is: No valid response received for command
> The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
> To summarize:
> - Start sending messages with the session set to SESSION_TRANSACTED
> - Fill ActiveMQ memory
> - Receive exception
> - The last message sent will be in the queue. All other messages will be rolled back.
> Here's what the debug log looks like:
> DEBUG Usage - Memory usage change. from: 2, to: 1
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
> DEBUG Usage - Memory usage change. from: 1, to: 0
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
> DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
> DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
> As you can see, it adds a message to the queue after the rollback and after stopping the connection.
> Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQCPP-193:
-----------------------------------
Assignee: Timothy Bish (was: Nathan Mittler)
> If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-193
> URL: https://issues.apache.org/activemq/browse/AMQCPP-193
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.2, 2.3
> Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
> Reporter: Brian Roach
> Assignee: Timothy Bish
> Fix For: 2.3
>
> Attachments: transactionTest.cpp
>
>
> If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
> The exception text is: No valid response received for command
> The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
> To summarize:
> - Start sending messages with the session set to SESSION_TRANSACTED
> - Fill ActiveMQ memory
> - Receive exception
> - The last message sent will be in the queue. All other messages will be rolled back.
> Here's what the debug log looks like:
> DEBUG Usage - Memory usage change. from: 2, to: 1
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
> DEBUG Usage - Memory usage change. from: 1, to: 0
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
> DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
> DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
> As you can see, it adds a message to the queue after the rollback and after stopping the connection.
> Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-193:
--------------------------------
Fix Version/s: (was: 2.3)
> If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-193
> URL: https://issues.apache.org/activemq/browse/AMQCPP-193
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.2, 2.3
> Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
> Reporter: Brian Roach
> Assignee: Nathan Mittler
> Fix For: 2.3
>
> Attachments: transactionTest.cpp
>
>
> If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
> The exception text is: No valid response received for command
> The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
> To summarize:
> - Start sending messages with the session set to SESSION_TRANSACTED
> - Fill ActiveMQ memory
> - Receive exception
> - The last message sent will be in the queue. All other messages will be rolled back.
> Here's what the debug log looks like:
> DEBUG Usage - Memory usage change. from: 2, to: 1
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
> DEBUG Usage - Memory usage change. from: 1, to: 0
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
> DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
> DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
> As you can see, it adds a message to the queue after the rollback and after stopping the connection.
> Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-193) If activeMQ blocks due to reaching
memory limit during a transaction, the last message sent is posted to the
queue after the rollback occurs and persists
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48481#action_48481 ]
Timothy Bish commented on AMQCPP-193:
-------------------------------------
I have not been able to reproduce this on a 5.2 broker
> If activeMQ blocks due to reaching memory limit during a transaction, the last message sent is posted to the queue after the rollback occurs and persists
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-193
> URL: https://issues.apache.org/activemq/browse/AMQCPP-193
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.2, 2.3
> Environment: Solaris x86, Solaris Sparc (UltraSPARC-T1)
> Reporter: Brian Roach
> Assignee: Timothy Bish
> Fix For: 2.3
>
> Attachments: transactionTest.cpp
>
>
> If you send a large number of messages inside a transaction, and ActiveMQ runs out of memory, cms::MessageProducer::send() throws an exception (as it should).
> The exception text is: No valid response received for command
> The problem is ... the last message sent (the one that caused the exception to be thrown) gets added to the queue while the others are rolled back. This is a large problem, as the whole point of transactions is to avoid this sort of thing.
> To summarize:
> - Start sending messages with the session set to SESSION_TRANSACTED
> - Fill ActiveMQ memory
> - Receive exception
> - The last message sent will be in the queue. All other messages will be rolled back.
> Here's what the debug log looks like:
> DEBUG Usage - Memory usage change. from: 2, to: 1
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:109, at: offset = 4527877, file = 6, size = 47444, type = 1
> DEBUG Usage - Memory usage change. from: 1, to: 0
> DEBUG AMQMessageStore - Transacted message add rollback for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:110, at: offset = 4575321, file = 6, size = 47439, type = 1
> DEBUG TransportConnection - Connection Stopped: /127.0.0.1:44382
> DEBUG AMQMessageStore - Journalled message add for: 68445488-66bc-c258-0d30-4a1faede93a5:0:1:111, at: offset = 4622760, file = 6, size = 47442, type = 1
> As you can see, it adds a message to the queue after the rollback and after stopping the connection.
> Attached is C++ that will demonstrate the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.