[
https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5249:
------------------------------
Comment: was deleted
(was: GitHub user jkorab opened a pull request:
https://github.com/apache/activemq/pull/36
Fix for AMQ-5249
Approach to the change is described in
http://issues.apache.org/jira/browse/AMQ-5294?focusedCommentId=14077910&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14077910
For some reason there is also a commit in this pull request that was
already merged (Added close destroy-method...), apologies something messed up
in the workflow.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jkorab/activemq trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/36.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #36
----
commit a92027691a8de2482e43ab33ed4e9dd0f7a24377
Author: Jakub Korab <[email protected]>
Date: 2014-04-03T10:36:24Z
Added close destroy-method to Postgres data source. Example crashed and
burned on master-slave failover when master lost network connectivity - took
down VM.
commit 039750805eec66fad2c273e7db5c15912acb272c
Author: jkorab <[email protected]>
Date: 2014-07-25T11:23:11Z
Merge branch 'trunk' of https://github.com/apache/activemq into trunk
commit ecedea34faee1e8c56daa4a7a9c40261cdba91fe
Author: jkorab <[email protected]>
Date: 2014-07-29T16:25:09Z
Fix for AMQ-5294. Refactored tool to unify timing of the samplers and
client (producer/consumer), in such a way that the performance test no longer
sits waiting for sampler to complete, even though the run terminated much
earlier. Full description of approach in
http://issues.apache.org/jira/browse/AMQ-5294?focusedCommentId=14077910&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14077910
----
)
> "cursor got duplicate" error after upgrade
> ------------------------------------------
>
> Key: AMQ-5249
> URL: https://issues.apache.org/jira/browse/AMQ-5249
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.9.1, 5.10.0
> Reporter: Rural Hunter
>
> I was using 5.9.0 and meet one problem so I tried to upgrade activemq. I
> tried both 5.9.1 and 5.10.0 and encouterred a same problem. I saw messages
> filled DLQ very quickly. I checked the clients both producer and consumer but
> there was no error. I checked activemq log and found the log is full of these
> warnings:
> 2014-06-27 23:22:09,337 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.cyyun.webmon.spider.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:211.com-52399-1400732399425-1:1:235992:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,337 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.xxxx.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:nbzjjf22805-34129-1403880308671-1:1:28:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,338 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.xxxxx.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:jxncxnj2-48598-1403856107346-1:1:6007:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,338 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.xxxx.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:jxnc17-60227-1400730816361-1:1:149072:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,339 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.xxxx.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:cyyun-46954-1403800808565-1:1:9765:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,339 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.xxxx.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:ubuntu-55495-1403497638437-1:1:53086:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,340 | WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.xxxx.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
> - cursor got duplicate: ID:cyyun-39030-1403880008363-1:1:70:1:1, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> Broker[localhost] Scheduler
> The problem mostly happens right after activemq starts and sometimes happened
> after activemq worked normally for a while.
> For now I have to roll back to 5.9.0 and the problem doesn't occure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
