Re: Getting javax.cache.CacheException after upgrading to Ignite 2.7 (IGNITE-10884 )
Hi Prasad,
The ticket is resolved with fix version 2.8, which was not released
yet. Unfortunately we overlooked to include it into 2.7.6 scope. Sorry
for that.
пт, 27 сент. 2019 г. в 16:49, Prasad Bhalerao :
>
> Hi,
>
> this issue still exists in ignite 2.7.6 version but the ticket is marked as
> Fixed. I am still able to reproduce the issue using following reproducer.
>
> Because this issue I am not able to upgrade to latest version from 2.6.0
> version.
>
> GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
>
> Please run IgniteTransactionTester class to check the issue.
>
> Thanks,
> Prasad
>
> On Thu, Jan 10, 2019 at 7:22 PM Ilya Kasnacheev
> wrote:
>>
>> Hello!
>>
>> I have filed a blocker ticket about it:
>> https://issues.apache.org/jira/browse/IGNITE-10884
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 9 янв. 2019 г. в 17:43, Prasad Bhalerao :
>>>
>>>
>>> Hi Ilya,
>>>
>>> I have created a reproducer for this issue and uploaded it to GitHub.
>>>
>>> GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
>>>
>>> Please run IgniteTransactionTester class to check the issue.
>>>
>>>
>>> Exception:
>>>
>>> Exception in thread "main" javax.cache.CacheException: Only pessimistic
>>> repeatable read transactions are supported at the moment.
>>> at
>>> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:697)
>>> at
>>> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
>>> at
>>> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
>>> at
>>> IgniteTransactionTester.testTransactionException(IgniteTransactionTester.java:53)
>>> at IgniteTransactionTester.main(IgniteTransactionTester.java:38)
>>> Caused by: class
>>> org.apache.ignite.internal.processors.query.IgniteSQLException: Only
>>> pessimistic repeatable read transactions are supported at the moment.
>>> at
>>> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.tx(MvccUtils.java:690)
>>> at
>>> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.tx(MvccUtils.java:671)
>>> at
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1793)
>>> at
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2610)
>>> at
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:2315)
>>> at
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2209)
>>> at
>>> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2135)
>>> at
>>> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2130)
>>> at
>>> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>>> at
>>> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2707)
>>> at
>>> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2144)
>>> at
>>> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:685)
>>>
>>> Thanks,
>>>
>>> Prasad
>>>
>>>
>>>
>>> On Wed, Jan 9, 2019 at 6:22 PM Ilya Kasnacheev
>>> wrote:
Hello!
It was discussed recently:
http://apache-ignite-users.70518.x6.nabble.com/Migrate-from-2-6-to-2-7-td25738.html
I don't think you will be able to use SQL from transactions in Ignite 2.7.
While this looks like a regression, you will have to work around it for
now.
Do you have a small reproducer for this issue? I could file a ticket if
you had. You can try to do it yourself, too.
Regards,
--
Ilya Kasnacheev
ср, 9 янв. 2019 г. в 15:33, Prasad Bhalerao :
>
> Hi,
>
> My cache configuration is as follows. I am using TRANSACTIONAL and not
> TRANSACTIONAL_SNAPSHOT.
>
>
>
> private CacheConfiguration ipContainerIPV4CacheCfg() {
>
> CacheConfiguration ipContainerIpV4CacheCfg = new
> CacheConfiguration<>(CacheName.IP_CONTAINER_IPV4_CACHE.name());
>
> ipContainerIpV4CacheCfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ipContainerIpV4CacheCfg.setWriteThrough(ENABLE_WRITE_THROUGH);
> ipContainerIpV4CacheCfg.setReadThrough(false);
> ipContainerIpV4CacheCfg.setRebalanceMode(CacheRebalanceMode.ASYNC);
>
> ipContainerIpV4CacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> ipContainerIpV4CacheCfg.setBackups(1);
> Factory storeFactory =
> FactoryBuilder.factoryOf(IpContainerIpV4CacheStore.class);
> ipContainerIpV4CacheCfg.setCacheStoreFactory(storeFactory);
>
Re: Getting javax.cache.CacheException after upgrading to Ignite 2.7 (IGNITE-10884 )
Hi,
this issue still exists in ignite 2.7.6 version but the ticket is marked as
Fixed. I am still able to reproduce the issue using following reproducer.
Because this issue I am not able to upgrade to latest version from 2.6.0
version.
GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
Please run IgniteTransactionTester class to check the issue.
Thanks,
Prasad
On Thu, Jan 10, 2019 at 7:22 PM Ilya Kasnacheev
wrote:
> Hello!
>
> I have filed a blocker ticket about it:
> https://issues.apache.org/jira/browse/IGNITE-10884
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 9 янв. 2019 г. в 17:43, Prasad Bhalerao >:
>
>>
>> Hi Ilya,
>>
>> I have created a reproducer for this issue and uploaded it to GitHub.
>>
>> GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
>>
>> Please run IgniteTransactionTester class to check the issue.
>>
>>
>> Exception:
>>
>> Exception in thread "main" javax.cache.CacheException: Only pessimistic
>> repeatable read transactions are supported at the moment.
>> at
>> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:697)
>> at
>> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
>> at
>> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
>> at
>> IgniteTransactionTester.testTransactionException(IgniteTransactionTester.java:53)
>> at IgniteTransactionTester.main(IgniteTransactionTester.java:38)
>> Caused by: class
>> org.apache.ignite.internal.processors.query.IgniteSQLException: Only
>> pessimistic repeatable read transactions are supported at the moment.
>> at
>> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.tx(MvccUtils.java:690)
>> at
>> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.tx(MvccUtils.java:671)
>> at
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1793)
>> at
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2610)
>> at
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:2315)
>> at
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2209)
>> at
>> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2135)
>> at
>> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2130)
>> at
>> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>> at
>> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2707)
>> at
>> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2144)
>> at
>> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:685)
>>
>> Thanks,
>>
>> Prasad
>>
>>
>>
>> On Wed, Jan 9, 2019 at 6:22 PM Ilya Kasnacheev
>> wrote:
>>
>>> Hello!
>>>
>>> It was discussed recently:
>>> http://apache-ignite-users.70518.x6.nabble.com/Migrate-from-2-6-to-2-7-td25738.html
>>>
>>> I don't think you will be able to use SQL from transactions in Ignite
>>> 2.7. While this looks like a regression, you will have to work around it
>>> for now.
>>>
>>> Do you have a small reproducer for this issue? I could file a ticket if
>>> you had. You can try to do it yourself, too.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 9 янв. 2019 г. в 15:33, Prasad Bhalerao <
>>> prasadbhalerao1...@gmail.com>:
>>>
Hi,
My cache configuration is as follows. I am using TRANSACTIONAL and not
TRANSACTIONAL_SNAPSHOT.
private CacheConfiguration ipContainerIPV4CacheCfg() {
CacheConfiguration ipContainerIpV4CacheCfg = new
CacheConfiguration<>(CacheName.IP_CONTAINER_IPV4_CACHE.name());
ipContainerIpV4CacheCfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
ipContainerIpV4CacheCfg.setWriteThrough(ENABLE_WRITE_THROUGH);
ipContainerIpV4CacheCfg.setReadThrough(false);
ipContainerIpV4CacheCfg.setRebalanceMode(CacheRebalanceMode.ASYNC);
ipContainerIpV4CacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
ipContainerIpV4CacheCfg.setBackups(1);
Factory storeFactory =
FactoryBuilder.factoryOf(IpContainerIpV4CacheStore.class);
ipContainerIpV4CacheCfg.setCacheStoreFactory(storeFactory);
ipContainerIpV4CacheCfg.setIndexedTypes(DefaultDataAffinityKey.class,
IpContainerIpV4Data.class);
ipContainerIpV4CacheCfg.setCacheStoreSessionListenerFactories(cacheStoreSessionListenerFactory());
ipContainerIpV4CacheCfg.setSqlIndexMaxInlineSize(84);
RendezvousAffinityFunction affinityFunction = new
