[JBoss JIRA] (ISPN-4137) Transaction executed multiple times due to forwarded CommitCommand
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4137?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-4137:
-----------------------------------
[~william.burns]: It seems that the condition for replaying the Prepare was modified in ISPN-3633
> Transaction executed multiple times due to forwarded CommitCommand
> ------------------------------------------------------------------
>
> Key: ISPN-4137
> URL: https://issues.jboss.org/browse/ISPN-4137
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer, Transactions
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
>
> When the {{StateTransferInterceptor}} forwards a CommitCommand for the new topology, multiple CommitCommands may be broadcast across the cluster. If the command (forwarded already from originator) times out, the transaction may be correctly finished by the first one and the application considers TX as succeeded (useSynchronizations=true), although one more Rollback is sent as well.
> Then, again in STI, when the CommitCommand arrives with higher topologyId than the one used for the first TX execution, another artificial Prepare (followed by the commit) is executed - see {{STI.visitCommitCommand}}.
> However, this execution may be delayed a lot and originator may have already executed another TX on the same entries. Then, this forwarded Commit will overwrite the already updated entries, causing inconsistency of data.
--
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
12 years
[JBoss JIRA] (ISPN-4137) Transaction executed multiple times due to forwarded CommitCommand
by Radim Vansa (JIRA)
Radim Vansa created ISPN-4137:
---------------------------------
Summary: Transaction executed multiple times due to forwarded CommitCommand
Key: ISPN-4137
URL: https://issues.jboss.org/browse/ISPN-4137
Project: Infinispan
Issue Type: Bug
Components: State Transfer, Transactions
Reporter: Radim Vansa
Assignee: Dan Berindei
Priority: Critical
When the {{StateTransferInterceptor}} forwards a CommitCommand for the new topology, multiple CommitCommands may be broadcast across the cluster. If the command (forwarded already from originator) times out, the transaction may be correctly finished by the first one and the application considers TX as succeeded (useSynchronizations=true), although one more Rollback is sent as well.
Then, again in STI, when the CommitCommand arrives with higher topologyId than the one used for the first TX execution, another artificial Prepare (followed by the commit) is executed - see {{STI.visitCommitCommand}}.
However, this execution may be delayed a lot and originator may have already executed another TX on the same entries. Then, this forwarded Commit will overwrite the already updated entries, causing inconsistency of data.
--
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
12 years
[JBoss JIRA] (ISPN-4104) Generic store cache child creation fails
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4104?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4104:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Alpha2
7.0.0.Final
Resolution: Done
> Generic store cache child creation fails
> ----------------------------------------
>
> Key: ISPN-4104
> URL: https://issues.jboss.org/browse/ISPN-4104
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: William Burns
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> This issue is similar to: https://issues.jboss.org/browse/ISPN-4103
> I can see this error during server restart:
> 10:38:01,682 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "clustered"),
> ("distributed-cache" => "namedCache")
> ]) - failure description: "JBAS010292: org.infinispan.persistence.file.SingleFileStore is not a valid cache store"
> After issuing of operation this configuration fragment is added into standalone.xml configuration file: <store name="genericStore" class="org.infinispan.persistence.file.SingleFileStore" preload="true" passivation="false" purge="false"/>
> Child creation using not generic, but pure File Cache Store option works OK. Store is configured and using this class: org.infinispan.persistence.file.SingleFileStore, however, when trying to do the same using generic store creation, it fails.
> See error in linked JIRA (for loader) as I suspect there is the same cause for this.
--
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
12 years
[JBoss JIRA] (ISPN-4103) Generic loader cache child creation fails
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4103?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4103:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Alpha2
7.0.0.Final
Resolution: Done
> Generic loader cache child creation fails
> -----------------------------------------
>
> Key: ISPN-4103
> URL: https://issues.jboss.org/browse/ISPN-4103
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: William Burns
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> Creation of cache child -- cluster loader is ok.
> However, when trying to create the same using generic loader child resource, it fails with following message [1].
> Server probably wasn't updated for latest persistence (loaders/stores) changes and only allows 5.2 based loaders/stores.
> Operation call from RHQ point of view looks to be clear and OK.
> [1]:
> 09:46:08,710 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "clustered"),
> ("distributed-cache" => "namedCache")
> ]): java.lang.IllegalArgumentException: JBAS011001: org.infinispan.persistence.cluster.ClusterLoader is not a valid cache loader
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.buildCacheLoader(CacheAdd.java:602)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.handleLoaderProperties(CacheAdd.java:548)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.processModelNode(CacheAdd.java:515)
> at org.jboss.as.clustering.infinispan.subsystem.ClusteredCacheAdd.processModelNode(ClusteredCacheAdd.java:70)
> at org.jboss.as.clustering.infinispan.subsystem.SharedStateCacheAdd.processModelNode(SharedStateCacheAdd.java:47)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheAdd.processModelNode(DistributedCacheAdd.java:86)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.installRuntimeServices(CacheAdd.java:223)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.performRuntime(CacheAdd.java:199)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:334) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
> Caused by: java.lang.ClassCastException: org.infinispan.persistence.cluster.ClusterLoader cannot be cast to org.infinispan.loaders.CacheLoader
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.buildCacheLoader(CacheAdd.java:597)
> ... 17 more
--
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
12 years
[JBoss JIRA] (ISPN-4104) Generic store cache child creation fails
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4104?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4104:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2452
> Generic store cache child creation fails
> ----------------------------------------
>
> Key: ISPN-4104
> URL: https://issues.jboss.org/browse/ISPN-4104
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: William Burns
>
> This issue is similar to: https://issues.jboss.org/browse/ISPN-4103
> I can see this error during server restart:
> 10:38:01,682 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "clustered"),
> ("distributed-cache" => "namedCache")
> ]) - failure description: "JBAS010292: org.infinispan.persistence.file.SingleFileStore is not a valid cache store"
> After issuing of operation this configuration fragment is added into standalone.xml configuration file: <store name="genericStore" class="org.infinispan.persistence.file.SingleFileStore" preload="true" passivation="false" purge="false"/>
> Child creation using not generic, but pure File Cache Store option works OK. Store is configured and using this class: org.infinispan.persistence.file.SingleFileStore, however, when trying to do the same using generic store creation, it fails.
> See error in linked JIRA (for loader) as I suspect there is the same cause for this.
--
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
12 years
[JBoss JIRA] (ISPN-4103) Generic loader cache child creation fails
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4103?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4103:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2452
> Generic loader cache child creation fails
> -----------------------------------------
>
> Key: ISPN-4103
> URL: https://issues.jboss.org/browse/ISPN-4103
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: William Burns
>
> Creation of cache child -- cluster loader is ok.
> However, when trying to create the same using generic loader child resource, it fails with following message [1].
> Server probably wasn't updated for latest persistence (loaders/stores) changes and only allows 5.2 based loaders/stores.
> Operation call from RHQ point of view looks to be clear and OK.
> [1]:
> 09:46:08,710 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "clustered"),
> ("distributed-cache" => "namedCache")
> ]): java.lang.IllegalArgumentException: JBAS011001: org.infinispan.persistence.cluster.ClusterLoader is not a valid cache loader
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.buildCacheLoader(CacheAdd.java:602)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.handleLoaderProperties(CacheAdd.java:548)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.processModelNode(CacheAdd.java:515)
> at org.jboss.as.clustering.infinispan.subsystem.ClusteredCacheAdd.processModelNode(ClusteredCacheAdd.java:70)
> at org.jboss.as.clustering.infinispan.subsystem.SharedStateCacheAdd.processModelNode(SharedStateCacheAdd.java:47)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheAdd.processModelNode(DistributedCacheAdd.java:86)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.installRuntimeServices(CacheAdd.java:223)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.performRuntime(CacheAdd.java:199)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:334) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
> Caused by: java.lang.ClassCastException: org.infinispan.persistence.cluster.ClusterLoader cannot be cast to org.infinispan.loaders.CacheLoader
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.buildCacheLoader(CacheAdd.java:597)
> ... 17 more
--
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
12 years
[JBoss JIRA] (ISPN-4125) ClassCastException if cache.keyset() is invoked for a string-keyed-jdbc-store in C/S mode
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-4125?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-4125:
-------------------------------------
[~wfink] I've created a test to reproduce this but I cannot make it fail. Any other details I might have missed?
> ClassCastException if cache.keyset() is invoked for a string-keyed-jdbc-store in C/S mode
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-4125
> URL: https://issues.jboss.org/browse/ISPN-4125
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 6.0.0.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Adrian Nistor
> Labels: 621, 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> If the cache is empty cache.keyset() invocation returns an empty set.
> If it is invoked after entities are added it failes with the Exception below.
> The same test work if a binary-keyed-jdbc-store is used!
> The HotRod client is based on the hot-rod C/S quickstart.
> The configuration is:
> <subsystem xmlns="urn:infinispan:server:core:6.0" default-cache-container="clustered">
> <cache-container name="clustered" default-cache="string" statistics="true">
> <transport executor="infinispan-transport" lock-timeout="60000"/>
> <replicated-cache name="string" mode="ASYNC" start="EAGER">
> <locking isolation="READ_COMMITTED" acquire-timeout="20000" concurrency-level="500" striping="false"/>
> <transaction mode="NONE"/>
> <string-keyed-jdbc-store datasource="java:jboss/datasources/JDGDatasource" passivation="false" preload="true" purge="false" shared="false">
> <!-- property name="databaseType">ORACLE</property -->
> <string-keyed-table prefix="qs">
> <id-column name="id" type="VARCHAR(255)"/>
> <data-column name="datum" type="BLOB(2000)"/>
> <timestamp-column name="version" type="BIGINT"/>
> </string-keyed-table>
> <write-behind modification-queue-size="1024" shutdown-timeout="25000" flush-lock-timeout="15000" thread-pool-size="5" />
> </string-keyed-jdbc-store>
> <expiration interval="10000" />
> </replicated-cache>
> ERROR [org.infinispan.server.hotrod.HotRodDecoder:76] (HotRodServerWorker-88) ISPN005009: Unexpected error before any request parameters read: java.lang.ClassCastException: java.lang.String cannot be cast to [B
> at org.infinispan.server.hotrod.AbstractEncoder1x$$anonfun$writeResponse$5.apply(AbstractEncoder1x.scala:113) [infinispan.jar:7.0.0-SNAPSHOT]
> at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> at org.infinispan.server.hotrod.AbstractEncoder1x.writeResponse(AbstractEncoder1x.scala:113) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.infinispan.server.hotrod.HotRodEncoder.encode(HotRodEncoder.scala:48) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.Channels.write(Channels.java:704) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.Channels.write(Channels.java:671) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) [netty-3.6.6.Final.jar:]
> at org.infinispan.server.core.AbstractProtocolDecoder.writeResponse(AbstractProtocolDecoder.scala:163) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.infinispan.server.hotrod.HotRodDecoder.customDecodeKey(HotRodDecoder.scala:138) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.infinispan.server.core.AbstractProtocolDecoder.decodeKey(AbstractProtocolDecoder.scala:105) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:53) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:29) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:500) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) [netty-3.6.6.Final.jar:]
> at org.infinispan.server.core.AbstractProtocolDecoder.messageReceived(AbstractProtocolDecoder.scala:377) [infinispan.jar:7.0.0-SNAPSHOT]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.6.Final.jar:]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.6.Final.jar:]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
--
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
12 years