You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2012/08/10 15:46:28 UTC
[jira] [Created] (APLO-238) assertion failed in latest snapshot
under load
Lionel Cons created APLO-238:
--------------------------------
Summary: assertion failed in latest snapshot under load
Key: APLO-238
URL: https://issues.apache.org/jira/browse/APLO-238
Project: ActiveMQ Apollo
Issue Type: Bug
Environment: apollo-99-trunk-20120810.034513-80
Reporter: Lionel Cons
When running some stress tests against Apollo (latest snapshot) I saw several:
2012-08-10 14:04:08,468 | WARN | java.lang.AssertionError: assertion failed: The downstream sink violated it's contract, an offer was not accepted but it had told us it was not full | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-8
FWIW, the stress test was to have many producers sending messages to a topic with one consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-238) assertion failed in latest snapshot
under load
Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443963#comment-13443963 ]
Lionel Cons commented on APLO-238:
----------------------------------
FWIW, I've tried with shorter samples (sample_interval=500) and the problem is still present.
> assertion failed in latest snapshot under load
> ----------------------------------------------
>
> Key: APLO-238
> URL: https://issues.apache.org/jira/browse/APLO-238
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120810.034513-80
> Reporter: Lionel Cons
> Attachments: apollo.log, scenario.xml
>
>
> When running some stress tests against Apollo (latest snapshot) I saw several:
> 2012-08-10 14:04:08,468 | WARN | java.lang.AssertionError: assertion failed: The downstream sink violated it's contract, an offer was not accepted but it had told us it was not full | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-8
> FWIW, the stress test was to have many producers sending messages to a topic with one consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-238) assertion failed in latest snapshot
under load
Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443820#comment-13443820 ]
Lionel Cons commented on APLO-238:
----------------------------------
This has been reproduced with apollo-99-trunk-20120827.204756-104, using stomp-benchmark. See the attached scenario & log.
> assertion failed in latest snapshot under load
> ----------------------------------------------
>
> Key: APLO-238
> URL: https://issues.apache.org/jira/browse/APLO-238
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120810.034513-80
> Reporter: Lionel Cons
>
> When running some stress tests against Apollo (latest snapshot) I saw several:
> 2012-08-10 14:04:08,468 | WARN | java.lang.AssertionError: assertion failed: The downstream sink violated it's contract, an offer was not accepted but it had told us it was not full | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-8
> FWIW, the stress test was to have many producers sending messages to a topic with one consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-238) assertion failed in latest snapshot
under load
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433154#comment-13433154 ]
Hiram Chirino commented on APLO-238:
------------------------------------
Hi Lionel,
Have you figured out what's the best way to reproduce this?
> assertion failed in latest snapshot under load
> ----------------------------------------------
>
> Key: APLO-238
> URL: https://issues.apache.org/jira/browse/APLO-238
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120810.034513-80
> Reporter: Lionel Cons
>
> When running some stress tests against Apollo (latest snapshot) I saw several:
> 2012-08-10 14:04:08,468 | WARN | java.lang.AssertionError: assertion failed: The downstream sink violated it's contract, an offer was not accepted but it had told us it was not full | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-8
> FWIW, the stress test was to have many producers sending messages to a topic with one consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (APLO-238) assertion failed in latest snapshot
under load
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved APLO-238.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.5
Assignee: Hiram Chirino
Should be fixed now in the latest snapshot. Thanks for the scenario file!
> assertion failed in latest snapshot under load
> ----------------------------------------------
>
> Key: APLO-238
> URL: https://issues.apache.org/jira/browse/APLO-238
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120810.034513-80
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> Fix For: 1.5
>
> Attachments: apollo.log, scenario.xml
>
>
> When running some stress tests against Apollo (latest snapshot) I saw several:
> 2012-08-10 14:04:08,468 | WARN | java.lang.AssertionError: assertion failed: The downstream sink violated it's contract, an offer was not accepted but it had told us it was not full | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-8
> FWIW, the stress test was to have many producers sending messages to a topic with one consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-238) assertion failed in latest snapshot
under load
Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lionel Cons updated APLO-238:
-----------------------------
Attachment: scenario.xml
apollo.log
> assertion failed in latest snapshot under load
> ----------------------------------------------
>
> Key: APLO-238
> URL: https://issues.apache.org/jira/browse/APLO-238
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120810.034513-80
> Reporter: Lionel Cons
> Attachments: apollo.log, scenario.xml
>
>
> When running some stress tests against Apollo (latest snapshot) I saw several:
> 2012-08-10 14:04:08,468 | WARN | java.lang.AssertionError: assertion failed: The downstream sink violated it's contract, an offer was not accepted but it had told us it was not full | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-8
> FWIW, the stress test was to have many producers sending messages to a topic with one consumer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira