activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe Leuba (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APLO-384) Error with messages having an expiration
Date Tue, 28 Jul 2015 09:21:04 GMT

     [ https://issues.apache.org/jira/browse/APLO-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philippe Leuba updated APLO-384:
--------------------------------
    Attachment: activemq-broker-test.cpp

Sample test application to reproduce the problem, execute it as: activemq-broker-test 25000'
on the same machine as the broker

> Error with messages having an expiration
> ----------------------------------------
>
>                 Key: APLO-384
>                 URL: https://issues.apache.org/jira/browse/APLO-384
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.6, 1.7.1
>            Reporter: Philippe Leuba
>         Attachments: activemq-broker-test.cpp
>
>
> When sending a large number of messages (25000) to a queue, being a mix of messages with
and without expiration from a c++ application using activemq-cpp 3.8.2 and stomp connector
on localhost (tcp://localhost:61613?wireFormat=stomp), we encounter an error in the log:
> {code}
> 09:37:54,943 INFO  [queue.EmbeddedBroker] The broker has now started.
> 09:38:15,328 INFO  [log.connection] connected: local:/127.0.0.1:61613, remote:/127.0.0.1:53399
> 09:38:52,195 WARN  [broker.QueueEntry] Retrying 1 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:52,393 WARN  [broker.QueueEntry] Retrying 2 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:52,510 WARN  [broker.QueueEntry] Retrying 3 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:52,611 WARN  [broker.QueueEntry] Retrying 4 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:52,705 WARN  [broker.QueueEntry] Retrying 5 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:52,803 WARN  [broker.QueueEntry] Retrying 6 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:52,907 WARN  [broker.QueueEntry] Retrying 7 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:53,006 WARN  [broker.QueueEntry] Retrying 8 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:53,110 WARN  [broker.QueueEntry] Retrying 9 load do to Queue 'outbound-control'
detected store change in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:53,204 WARN  [broker.QueueEntry] Queue 'outbound-control' detected store change
in range [10002:20001]. -1 message(s) and -1067 bytes
> 09:38:55,857 INFO  [log.connection] disconnected: local:/127.0.0.1:61613, remote:/127.0.0.1:53399
> {code}
> Following this error, we can be blocked on send or receive calls and the console can
show negative numbers of messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message