You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/10/28 12:29:27 UTC
[jira] [Commented] (AMQ-6025) Activemq ACTIVEMQ_ACKS table gets
double updates
[ https://issues.apache.org/jira/browse/AMQ-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978265#comment-14978265 ]
Jean-Baptiste Onofré commented on AMQ-6025:
-------------------------------------------
Let me take a look on that.
> Activemq ACTIVEMQ_ACKS table gets double updates
> ------------------------------------------------
>
> Key: AMQ-6025
> URL: https://issues.apache.org/jira/browse/AMQ-6025
> Project: ActiveMQ
> Issue Type: Bug
> Components: OSGi/Karaf
> Affects Versions: 5.10.1
> Reporter: Krishnan
>
> Customer feedback:
> Issue's on ActiveMQ 5.10
> We have 290 offline durable clients in Active MQ broker and which have 50 pending messages for each offline durable client. When the messages exceeds their TTL time for those messages, LAST_ACK_ID will be updated twice for each subscriber(e.g.: again 290 set of updates it is firing). why is the updates being duplicated and Is there any possibility to tune or remove second set of transactions.
> Following configuration made in activemq.xml file for this.
> cleanupPeriod:
> <persistenceAdapter>
> <jdbcPersistenceAdapter dataSource="#mysql-ds" cleanupPeriod="300000"/>
> </persistenceAdapter>
> expireMessagesPeriod
> <policyEntry topic="<<topic name>>" expireMessagesPeriod=" 86400000 ">
> And also attached the general Db log for the updates.
> Support Note: Checked Customer log 215MB . And there's lots of updates on the ACK table. Just a snippet of the logs..
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378703, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT149' AND SUB_NAME='300SUBS149'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378703, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT142' AND SUB_NAME='300SUBS142'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378703, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT141' AND SUB_NAME='300SUBS141'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT140' AND SUB_NAME='300SUBS140'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT14' AND SUB_NAME='300SUBS14'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT146' AND SUB_NAME='300SUBS146'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT147' AND SUB_NAME='300SUBS147'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT145' AND SUB_NAME='300SUBS145'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT148' AND SUB_NAME='300SUBS148'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT143' AND SUB_NAME='300SUBS143'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT144' AND SUB_NAME='300SUBS144'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT149' AND SUB_NAME='300SUBS149'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT142' AND SUB_NAME='300SUBS142'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378704, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT141' AND SUB_NAME='300SUBS141'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378705, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT140' AND SUB_NAME='300SUBS140'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378705, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT14' AND SUB_NAME='300SUBS14'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378705, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT146' AND SUB_NAME='300SUBS146'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378705, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT147' AND SUB_NAME='300SUBS147'
> 4171969 Query
> UPDATE ACTIVEMQ_ACKS SET LAST_ACKED_ID=378705, XID = NULL WHERE CONTAINER='topic://bmrsTopic' AND CLIENT_ID='300CLNT145' AND SUB_NAME='300SUBS145'
> There is also similar forum discussion on the same
> http://activemq.2283324.n4.nabble.com/Too-many-updates-in-MySQL-td4700512.html
> A related TalendESB Ticket is available at
> https://jira.talendforge.org/browse/TESB-16693
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)