[JBoss JIRA] (ISPN-3440) Update version.compiler.plugin and jboss.maven.plugin versions in the quickstart POM files
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/ISPN-3440?page=com.atlassian.jira.plugin.... ]
Sande Gilda updated ISPN-3440:
------------------------------
Description:
Update the following property versions in the quickstart POM files:
version.jboss.maven.plugin: from 7.3.Final to 7.4.Final
version.compiler.plugin: from 2.3.1 to 3.1
was:
Change the following property versions in the quickstarts as follows:
version.jboss.maven.plugin: from 7.3.Final to 7.4.Final
version.compiler.plugin: from 2.3.1 to 3.1
> Update version.compiler.plugin and jboss.maven.plugin versions in the quickstart POM files
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-3440
> URL: https://issues.jboss.org/browse/ISPN-3440
> Project: Infinispan
> Issue Type: Enhancement
> Components: Demos and Tutorials
> Reporter: Sande Gilda
> Assignee: Mircea Markus
>
> Update the following property versions in the quickstart POM files:
> version.jboss.maven.plugin: from 7.3.Final to 7.4.Final
> version.compiler.plugin: from 2.3.1 to 3.1
--
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
10 years, 8 months
[JBoss JIRA] (ISPN-3440) Update version.compiler.plugin and jboss.maven.plugin versions in the POM files
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/ISPN-3440?page=com.atlassian.jira.plugin.... ]
Sande Gilda updated ISPN-3440:
------------------------------
Description:
Change the following property versions in the quickstarts as follows:
version.jboss.maven.plugin: from 7.3.Final to 7.4.Final
version.compiler.plugin: from 2.3.1 to 3.1
was:
Change the following property versions:
version.jboss.maven.plugin: from 7.3.Final to 7.4.Final
version.compiler.plugin: from 2.3.1 to 3.1
> Update version.compiler.plugin and jboss.maven.plugin versions in the POM files
> -------------------------------------------------------------------------------
>
> Key: ISPN-3440
> URL: https://issues.jboss.org/browse/ISPN-3440
> Project: Infinispan
> Issue Type: Enhancement
> Components: Demos and Tutorials
> Reporter: Sande Gilda
> Assignee: Mircea Markus
>
> Change the following property versions in the quickstarts as follows:
> version.jboss.maven.plugin: from 7.3.Final to 7.4.Final
> version.compiler.plugin: from 2.3.1 to 3.1
--
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
10 years, 8 months
[JBoss JIRA] (ISPN-3405) Entries are passivated with wrong ID in DB
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-3405?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-3405:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Entries are passivated with wrong ID in DB
> ------------------------------------------
>
> Key: ISPN-3405
> URL: https://issues.jboss.org/browse/ISPN-3405
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.3.0.Final, 6.0.0.Alpha1
> Reporter: Vitalii Chepeliuk
> Assignee: Galder Zamarreño
> Fix For: 6.0.0.Beta1, 6.0.0.Final
>
>
> Entry passivation into DB, concretly this class LockSupportCacheStore and method store. Look at lines with "<<<" string for more info
> {code:title=LockSupportCacheStore.java|borderStyle=solid}
> @Override
> public final void store(InternalCacheEntry ed) throws CacheLoaderException {
> if (trace) {
> log.tracef("store(%s)", ed);
> }
> if (ed == null) {
> return;
> }
> if (ed.canExpire() && ed.isExpired(timeService.wallClockTime())) {
> if (containsKey(ed.getKey())) {
> if (trace) {
> log.tracef("Entry %s is expired! Removing!", ed);
> }
> remove(ed.getKey());
> } else {
> if (trace) {
> log.tracef("Entry %s is expired! Not doing anything.", ed);
> }
> }
> return;
> }
> L keyHashCode = getLockFromKey(ed.getKey()); <<< here key is generated like ed.getKey().hashCode() & 0xfffffc00;
> lockForWriting(keyHashCode);
> try {
> storeLockSafe(ed, keyHashCode); <<< here it should be stored into Bucket and then stored in DB
> } finally {
> unlock(keyHashCode);
> }
> if (trace) {
> log.tracef("exit store(%s)", ed);
> }
> }
> {code}
> When I use RemoteCacheManager and RemoteCache I am putting entries into cache
> {code:title=Test.java|borderStyle=solid}
> cache.put("key1", "v1");
> cache.put("key2", "v2");
> cache.put("key3", "v3");
> {code}
> Then 2 entries are passivated and stored in DB
> ||ID||DATA||TIMESTAMP||
> |183713792|0301fe032a01034c422b21033e286d7942657374506572736f6e616c4b657957686963684861734e657665724265656e426574746572420521033e02763203620003630000000000000002|-1|
> |23486464|0301fe032a01034c420721033e046b657931420521033e02763103620003630000000000000001|-1|
> IDs are generated from method above and
> {code:title=Test.java|borderStyle=solid}
> byte[] keyBytes = marshaller.objectToByteBuffer("key1"); <<< key is marshalled
> long keyID = ByteArrayEquivalence.INSTANCE.hashCode(keyBytes) & 0xfffffc00 //computation taken from BucketBasedCacheStore <<< this does not work for me
> {code}
> And next step I'd like to retrieve data from DB
> SELECT ID, DATA FROM JDBC_BINARY_DEFAULT WHERE ID=keyID
> But in method
> {code:title=BucketBasedCacheStore.java|borderStyle=solid}
> @Override
> public Integer getLockFromKey(Object key) {
> return key.hashCode() & 0xfffffc00; <<< here should be used Arrays.hashCode((byte[])key) & 0xfffffc00), if key is represented as byte array, or used ByteArrayEquivalence instead of simple byte array(byte[]) as argument
> }
> {code}
--
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
10 years, 8 months
[JBoss JIRA] (ISPN-3438) RHQ Plugin still needs additional work for caches, stores and endpoints
by William Burns (JIRA)
William Burns created ISPN-3438:
-----------------------------------
Summary: RHQ Plugin still needs additional work for caches, stores and endpoints
Key: ISPN-3438
URL: https://issues.jboss.org/browse/ISPN-3438
Project: Infinispan
Issue Type: Enhancement
Components: Server
Reporter: William Burns
Assignee: Tristan Tarrant
ISPN-3350 added support RHQ administration of adding/removing caches/stores/endpoints. There are still a few things missing:
# Remote store needs work for remote-servers still
# JDBC Stores are not supported due to pending changes - ISPN-3290
# Security domain value for REST endpoint can probably be a resource ref in rhq-plugin to limit choices
--
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
10 years, 8 months
[JBoss JIRA] (ISPN-3434) DistTotalOrderL1WriteSkewTest test doesn't run with L1 enabled
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-3434?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-3434:
------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2026
> DistTotalOrderL1WriteSkewTest test doesn't run with L1 enabled
> --------------------------------------------------------------
>
> Key: ISPN-3434
> URL: https://issues.jboss.org/browse/ISPN-3434
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Reporter: William Burns
> Assignee: Pedro Ruivo
>
> The decorate method doesn't invoke the super method, which causes the L1 to not be enabled. By invoking the super method and enabling L1, there are actually failing tests.
> Failed tests:
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testPutIgnoreReturnValueNonExistingKey:73->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeAY-38834. expected:<v1> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testPutIgnoreReturnValueNonExistingKeyOnNonOwner:77->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeBC-51791. expected:<v1> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testPutIgnoreReturnValueOnNonExistingKey:65->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeBF-6894. expected:<v1> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testPutIgnoreReturnValueOnNonExistingKeyOnNonOwner:69->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeBK-23011. expected:<v1> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testRemoveIgnoreReturnValueNonExistingKey:89->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeBO-8015. expected:<null> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testRemoveIgnoreReturnValueNonExistingKeyOnNonOwner:93->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeBS-18673. expected:<null> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey:81->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeBV-26641. expected:<null> but was:<v2>
> DistTotalOrderL1WriteSkewTest>AbstractClusteredWriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKeyOnNonOwner:85->AbstractClusteredWriteSkewTest.doIgnoreReturnValueTest:241 wrong final value for DistTotalOrderL1WriteSkewTest-NodeCA-47053. expected:<null> but was:<v2>
> DistTotalOrderL1WriteSkewTest>DistWriteSkewTest.testNullEntries:185 null
> DistTotalOrderL1WriteSkewTest>DistWriteSkewTest.testWriteSkew:48 null
> DistTotalOrderL1WriteSkewTest>DistWriteSkewTest.testWriteSkewMultiEntries:146 null
--
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
10 years, 8 months