[JBoss JIRA] (ISPN-4448) RHQ server plugin: synchronize data operation String casting to Byte array fails
by Tomas Sykora (JIRA)
[ https://issues.jboss.org/browse/ISPN-4448?page=com.atlassian.jira.plugin.... ]
Tomas Sykora commented on ISPN-4448:
------------------------------------
I made a little progress here:
I forgot to use --codec=hotrod during putting entries into OLD server. When I put entries using hotrod codec and then issue dumpkeys operation, then I am able to invoke Synchronize Data operation in RHQ and it returns Success.
The problem is that new cache contains NO migrated entries.
Continuing with investigation...
> RHQ server plugin: synchronize data operation String casting to Byte array fails
> --------------------------------------------------------------------------------
>
> Key: ISPN-4448
> URL: https://issues.jboss.org/browse/ISPN-4448
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX, reporting and management
> Affects Versions: 7.0.0.Alpha4
> Reporter: Tomas Sykora
> Assignee: William Burns
> Labels: rhq
>
> Invocation of rolling upgrades related operation -- Synchronize Data -- on a new node's cache fails with a following error:
> java.lang.Exception: JBAS011002: Failed to invoke operation: java.lang.String cannot be cast to [B, rolled-back=true
> at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Note, that there is also ISPN-4447 which says, that we can't record known global keyset using RHQ.
> In this issue, we proceed that operation using CLI interface console in order to create dumped keys. Then, we tried to synchronize data using RHQ cache operation and passing "hotrod" as a migrator. This was expected to work properly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (ISPN-4452) DummyInMemoryStore should respect fetch arguments on process method.
by William Burns (JIRA)
William Burns created ISPN-4452:
-----------------------------------
Summary: DummyInMemoryStore should respect fetch arguments on process method.
Key: ISPN-4452
URL: https://issues.jboss.org/browse/ISPN-4452
Project: Infinispan
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: William Burns
Assignee: Mircea Markus
The DummyInMemoryStore currently ignores the fetchValue and fetchMetadata keys. We should make this respect both independently so it can be easier to find if something is broken in a test. An example might be that someone passes fetchValue as false, but they really do require the value and DummyInMemorystore would return the value either way and the caller would still pass even though if they used a different store implementation it might fail.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (ISPN-4448) RHQ server plugin: synchronize data operation String casting to Byte array fails
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4448?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-4448:
-------------------------------------
I personally haven't used the ispn cli, so I couldn't comment [~NadirX] or [~pruivo] would know.
I attempted it using the jboss-cli.sh that is shipped with wildfly binary distribution.
> RHQ server plugin: synchronize data operation String casting to Byte array fails
> --------------------------------------------------------------------------------
>
> Key: ISPN-4448
> URL: https://issues.jboss.org/browse/ISPN-4448
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX, reporting and management
> Affects Versions: 7.0.0.Alpha4
> Reporter: Tomas Sykora
> Assignee: William Burns
> Labels: rhq
>
> Invocation of rolling upgrades related operation -- Synchronize Data -- on a new node's cache fails with a following error:
> java.lang.Exception: JBAS011002: Failed to invoke operation: java.lang.String cannot be cast to [B, rolled-back=true
> at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Note, that there is also ISPN-4447 which says, that we can't record known global keyset using RHQ.
> In this issue, we proceed that operation using CLI interface console in order to create dumped keys. Then, we tried to synchronize data using RHQ cache operation and passing "hotrod" as a migrator. This was expected to work properly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (ISPN-3959) JdbcBinaryStore's expiration locks buckets indefinitely
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3959?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3959:
-----------------------------------
Fix Version/s: 7.0.0.Final
> JdbcBinaryStore's expiration locks buckets indefinitely
> -------------------------------------------------------
>
> Key: ISPN-3959
> URL: https://issues.jboss.org/browse/ISPN-3959
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.2.Final, 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 7.0.0.Alpha5, 7.0.0.Final
>
>
> The buckets are locked in eviction thread (in the main purge method), while unlocked in BucketPurger.call() which is executed in persistence thread. The unlock fails and the buckets stay locked indefinitely.
> Another error is that the Bucket class is not serializable.
> This is also a bug in BaseStoreTest as this uses WithinThreadExecutor as the executor for purging while usually this is done in different thread. Moreover, as the purge method is actually not obliged to purge anything, the test does not test the purging itself, but rather a check for expired entry when it is loaded (contains operation). The purging should be enforced by purge listener (calling the purge method until all entries are purged).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (ISPN-3959) JdbcBinaryStore's expiration locks buckets indefinitely
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3959?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3959:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Alpha5
Resolution: Done
> JdbcBinaryStore's expiration locks buckets indefinitely
> -------------------------------------------------------
>
> Key: ISPN-3959
> URL: https://issues.jboss.org/browse/ISPN-3959
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.2.Final, 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 7.0.0.Alpha5
>
>
> The buckets are locked in eviction thread (in the main purge method), while unlocked in BucketPurger.call() which is executed in persistence thread. The unlock fails and the buckets stay locked indefinitely.
> Another error is that the Bucket class is not serializable.
> This is also a bug in BaseStoreTest as this uses WithinThreadExecutor as the executor for purging while usually this is done in different thread. Moreover, as the purge method is actually not obliged to purge anything, the test does not test the purging itself, but rather a check for expired entry when it is loaded (contains operation). The purging should be enforced by purge listener (calling the purge method until all entries are purged).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months