January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2730) Not possible to instanciate org.infinispan.cdi.InfinispanExtension during startup of appserver

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2730?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2730: ----------------------------------- Fix Version/s: 5.2.0.Final Assignee: Tristan Tarrant (was: Pete Muir) > Not possible to instanciate org.infinispan.cdi.InfinispanExtension during startup of appserver > ---------------------------------------------------------------------------------------------- > > Key: ISPN-2730 > URL: https://issues.jboss.org/browse/ISPN-2730 > Project: Infinispan > Issue Type: Bug > Components: CDI integration > Affects Versions: 5.2.0.CR1 > Environment: tested in openEJB > java version "1.6.0_33" > Java(TM) SE Runtime Environment (build 1.6.0_33-b03) > Oracle JRockit(R) (build R28.2.4-14-151097-1.6.0_33-20120618-1634-windows-x86_64, compiled mode) > Reporter: Michael Mellenthin > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.Final > > > I have infinispan-cdi library in my appserver to be able to use JSR-107. > During startup of application server it loads the InfinispanExtension because the service provider is declared in META-INF/services. > During startup I get the exception > {code} > Caused by: java.util.ServiceConfigurationError: javax.enterprise.inject.spi.Extension: Provider org.infinispan.cdi.InfinispanExtension could not be instantiated: java.lang.IllegalAccessException: Class java.util.ServiceLoader$LazyIterator can not access a member of class org.infinispan.cdi.InfinispanExtension with modifiers "" > at java.util.ServiceLoader.fail(ServiceLoader.java:207) > at java.util.ServiceLoader.access$100(ServiceLoader.java:164) > at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:353) > at java.util.ServiceLoader$1.next(ServiceLoader.java:421) > {code} > The reason is that the InfinispanExtension only provides a package scoped constructor. > For sure the documentation of java.util.ServiceLoader is not very clear here. It just says: > *"The only requirement enforced by this facility is that provider classes must have a zero-argument constructor so that they can be instantiated during loading"* > But the implementation fails if the constructor is not public. Hence, we need a public constructor for InfinispanExtension. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2729) [FineGrainedAtomicMap] Class Cast Exception in Clustered + Repeatable Read + Write Skew

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2729?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2729: ----------------------------------- Fix Version/s: 5.2.0.Final Assignee: Galder Zamarreño (was: Mircea Markus) Affects Version/s: (was: 5.2.0.CR1) > [FineGrainedAtomicMap] Class Cast Exception in Clustered + Repeatable Read + Write Skew > --------------------------------------------------------------------------------------- > > Key: ISPN-2729 > URL: https://issues.jboss.org/browse/ISPN-2729 > Project: Infinispan > Issue Type: Bug > Components: Core API, Fine-grained API, Locking and Concurrency > Environment: Mac OSx 10.5, Java 1.6 sun-jdk, maven 3.0.4 > Reporter: Pedro Ruivo > Assignee: Galder Zamarreño > Labels: atomic_map, clustered, write-skew > Fix For: 5.2.0.Final > > > Test case available in here [1] > When a transaction commits, the write skew check performs the validation by casting the cache entry to a ClusteredRepeatableReadEntry. However, the entry is a DeltaAwareCacheEntry. > This happens when you have operations over a map inside a transaction. > The tests failing are: > WriteSkewFineGrainedAtomicMapAPITest.testSizeOnCache() > WriteSkewFineGrainedAtomicMapAPITest.testCreateMapInTx() > [1]https://github.com/pruivo/infinispan/commits/t_atomic_map_issue -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2757) ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2757?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2757: -------------------------------- Fix Version/s: 5.2.1 (was: 5.2.0.Final) > ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing > --------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2757 > URL: https://issues.jboss.org/browse/ISPN-2757 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 5.2.1 > > > The local data container does not have the entry yet so the ReplaceCommand fails. See BaseReplStateTransferConsistencyTest.testReplace(). -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2727) Transactional put failed after master node with enabled InfinispanIndexManager is killed

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2727?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2727: ----------------------------------- Fix Version/s: 5.2.0.Final Assignee: Galder Zamarreño (was: Sanne Grinovero) > Transactional put failed after master node with enabled InfinispanIndexManager is killed > ----------------------------------------------------------------------------------------- > > Key: ISPN-2727 > URL: https://issues.jboss.org/browse/ISPN-2727 > Project: Infinispan > Issue Type: Bug > Components: Querying > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > Attachments: MultiNodeDistributedTest.java, MultiNodeLocalTest.java, MultiNodeLocalTxTest.java, MultiNodeReplicatedTest.java, MultiNodeReplicatedTxTest.java > > > I've added new test, which uses the following Infinispan configuration: REPL_SYNC clustering mode, with transaction enabled, as well as enabled indexing with InfinispanIndexManager. > The test adds several nodes with the described configuration, adds entries to different nodes, and checks that the query for the entries returns the same result for all nodes. > Then master node is killed, and then again new data is inserted and checked on all nodes. (Similiar test to https://github.com/infinispan/infinispan/blob/master/query/src/test/java/... but with enabled transaction). > When the test tries to insert new entry to one of the caches, after the master node kill, the following exception appears: > {code} > testIndexingWorkDistribution(org.infinispan.query.distributed.MultiNodeReplicatedTxTest) Time elapsed: 1.656 sec <<< FAILURE! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1177) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:117) > at org.infinispan.query.distributed.MultiNodeDistributedTest.storeOn(MultiNodeDistributedTest.java:78) > at org.infinispan.query.distributed.MultiNodeDistributedTest.testIndexingWorkDistribution(MultiNodeDistributedTest.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > 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) > Caused by: org.infinispan.CacheException: Could not prepare. > at org.infinispan.transaction.synchronization.SynchronizationAdapter.beforeCompletion(SynchronizationAdapter.java:70) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:273) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:93) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:164) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) > ... 24 more > Caused by: javax.transaction.xa.XAException > at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:161) > at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:123) > at org.infinispan.transaction.synchronization.SynchronizationAdapter.beforeCompletion(SynchronizationAdapter.java:68) > ... 29 more > {code} > You can find the test attached. The test which fails is MultiNodeReplicatedTxTest.java . The rest are the tests which are the parents and a bit modified compared to the version in infinispan repo. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2717) execute(Runnable) of DistributedExecutorService doesn't show exception message in case of failure of Runnable

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2717?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-2717: -------------------------------------- Assignee: Galder Zamarreño (was: Vladimir Blagojevic) > execute(Runnable) of DistributedExecutorService doesn't show exception message in case of failure of Runnable > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2717 > URL: https://issues.jboss.org/browse/ISPN-2717 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.CR2 > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > > Assume, that we have a runnable which run() method throws RuntimeException. > In case if the runnable is executed using void execute(Runnable command) for DistributedExecutorService, the execution of runnable fails - but there is no any stacktrace printed in the logs. > So it is really hard to find, what was wrong in your Runnable. > The sample test which does this is: > {code} > public void testRunnableExecution() throws InterruptedException { > //assuming cache initialization is done > DistributedExecutorService des = new DefaultExecutorService(cache); > SampleRunnable runnable = new SampleRunnable(); > des.execute(runnable); > } > static class SampleRunnable implements Runnable, Serializable { > public SampleRunnable() { > } > @Override > public void run() { > System.out.println("Running runnable"); > int i = 5 / 0; > } > } > {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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2726) Sporadic NPE in KeyAffinityServiceImpl

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2726?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2726: ----------------------------------- Fix Version/s: 5.2.0.Final > Sporadic NPE in KeyAffinityServiceImpl > -------------------------------------- > > Key: ISPN-2726 > URL: https://issues.jboss.org/browse/ISPN-2726 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Thomas Fromm > Assignee: Mircea Markus > Fix For: 5.2.0.Final > > > The NPE appears not often, unfortunality with enabled TRACE logging, it never appears :-( I'll keep trying to get TRACEs. > Exception in thread "pool-70-thread-1" java.lang.NullPointerException > at org.infinispan.affinity.KeyAffinityServiceImpl.getAddressForKey(KeyAffinityServiceImpl.java:347) > at org.infinispan.affinity.KeyAffinityServiceImpl.access$700(KeyAffinityServiceImpl.java:59) > at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.generateKeys(KeyAffinityServiceImpl.java:270) > at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.run(KeyAffinityServiceImpl.java:242) > 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) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2726) Sporadic NPE in KeyAffinityServiceImpl

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2726?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-2726: -------------------------------------- Assignee: Galder Zamarreño (was: Mircea Markus) > Sporadic NPE in KeyAffinityServiceImpl > -------------------------------------- > > Key: ISPN-2726 > URL: https://issues.jboss.org/browse/ISPN-2726 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Thomas Fromm > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > > The NPE appears not often, unfortunality with enabled TRACE logging, it never appears :-( I'll keep trying to get TRACEs. > Exception in thread "pool-70-thread-1" java.lang.NullPointerException > at org.infinispan.affinity.KeyAffinityServiceImpl.getAddressForKey(KeyAffinityServiceImpl.java:347) > at org.infinispan.affinity.KeyAffinityServiceImpl.access$700(KeyAffinityServiceImpl.java:59) > at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.generateKeys(KeyAffinityServiceImpl.java:270) > at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.run(KeyAffinityServiceImpl.java:242) > 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) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2717) execute(Runnable) of DistributedExecutorService doesn't show exception message in case of failure of Runnable

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2717?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2717: ----------------------------------- Fix Version/s: 5.2.0.Final > execute(Runnable) of DistributedExecutorService doesn't show exception message in case of failure of Runnable > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2717 > URL: https://issues.jboss.org/browse/ISPN-2717 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.CR2 > Reporter: Anna Manukyan > Assignee: Vladimir Blagojevic > Fix For: 5.2.0.Final > > > Assume, that we have a runnable which run() method throws RuntimeException. > In case if the runnable is executed using void execute(Runnable command) for DistributedExecutorService, the execution of runnable fails - but there is no any stacktrace printed in the logs. > So it is really hard to find, what was wrong in your Runnable. > The sample test which does this is: > {code} > public void testRunnableExecution() throws InterruptedException { > //assuming cache initialization is done > DistributedExecutorService des = new DefaultExecutorService(cache); > SampleRunnable runnable = new SampleRunnable(); > des.execute(runnable); > } > static class SampleRunnable implements Runnable, Serializable { > public SampleRunnable() { > } > @Override > public void run() { > System.out.println("Running runnable"); > int i = 5 / 0; > } > } > {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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2751) NPE after JBossMarshaller stops

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2751?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2751: ----------------------------------- Fix Version/s: 5.2.0.Final > NPE after JBossMarshaller stops > ------------------------------- > > Key: ISPN-2751 > URL: https://issues.jboss.org/browse/ISPN-2751 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Mircea Markus > Priority: Minor > Fix For: 5.2.0.Final > > > JBossMarshaller is used by JGroups even after it's stopped > which produces NPE on nonexistent externalizerTable: > https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2751) NPE after JBossMarshaller stops

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2751?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2751: ----------------------------------- Assignee: Galder Zamarreño (was: Mircea Markus) > NPE after JBossMarshaller stops > ------------------------------- > > Key: ISPN-2751 > URL: https://issues.jboss.org/browse/ISPN-2751 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 5.2.0.Final > > > JBossMarshaller is used by JGroups even after it's stopped > which produces NPE on nonexistent externalizerTable: > https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- 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

11 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013