[JBoss JIRA] (ISPN-2788) NullPointerException appears in case passing null as an exclusion list to LuceneCacheLoader.loadAllKeys()
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2788?page=com.atlassian.jira.plugin.... ]
Adrian Nistor reopened ISPN-2788:
---------------------------------
Issue not fully fixed. New PR here:
https://github.com/infinispan/infinispan/pull/1656
> NullPointerException appears in case passing null as an exclusion list to LuceneCacheLoader.loadAllKeys()
> ---------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2788
> URL: https://issues.jboss.org/browse/ISPN-2788
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 5.2.0.Final
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
>
> NullPointerException is thrown in case of passing null as a keyExclusionList to LuceneCacheLoader.loadAllKeys() method.
> The log is:
> {code}
> java.lang.NullPointerException
> at org.infinispan.lucene.cachestore.DirectoryLoaderAdaptor.loadSomeKeys(DirectoryLoaderAdaptor.java:108)
> at org.infinispan.lucene.cachestore.DirectoryLoaderAdaptor.loadAllKeys(DirectoryLoaderAdaptor.java:174)
> at org.infinispan.lucene.cachestore.LuceneCacheLoader.loadAllKeys(LuceneCacheLoader.java:126)
> at org.infinispan.lucene.cacheloader.LuceneCacheLoaderTest.testLoadAllKeysWithNullExclusion(LuceneCacheLoaderTest.java:263)
> 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:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> 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)
> {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
13 years, 2 months
[JBoss JIRA] (ISPN-2788) NullPointerException appears in case passing null as an exclusion list to LuceneCacheLoader.loadAllKeys()
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2788?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-2788:
--------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1643, https://github.com/infinispan/infinispan/pull/1656 (was: https://github.com/infinispan/infinispan/pull/1643)
> NullPointerException appears in case passing null as an exclusion list to LuceneCacheLoader.loadAllKeys()
> ---------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2788
> URL: https://issues.jboss.org/browse/ISPN-2788
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 5.2.0.Final
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
>
> NullPointerException is thrown in case of passing null as a keyExclusionList to LuceneCacheLoader.loadAllKeys() method.
> The log is:
> {code}
> java.lang.NullPointerException
> at org.infinispan.lucene.cachestore.DirectoryLoaderAdaptor.loadSomeKeys(DirectoryLoaderAdaptor.java:108)
> at org.infinispan.lucene.cachestore.DirectoryLoaderAdaptor.loadAllKeys(DirectoryLoaderAdaptor.java:174)
> at org.infinispan.lucene.cachestore.LuceneCacheLoader.loadAllKeys(LuceneCacheLoader.java:126)
> at org.infinispan.lucene.cacheloader.LuceneCacheLoaderTest.testLoadAllKeysWithNullExclusion(LuceneCacheLoaderTest.java:263)
> 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:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> 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)
> {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
13 years, 2 months
[JBoss JIRA] (ISPN-2810) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0
by Dan Berindei (JIRA)
Dan Berindei created ISPN-2810:
----------------------------------
Summary: In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0
Key: ISPN-2810
URL: https://issues.jboss.org/browse/ISPN-2810
Project: Infinispan
Issue Type: Feature Request
Components: Remote protocols
Affects Versions: 5.2.0.Final
Reporter: Dan Berindei
Assignee: Galder Zamarreño
Fix For: 5.3.0.Alpha1
Contrary to what ISPN-732 says, timeToLiveSeconds=0 and maxIdleTimeSeconds=0 are now treated correctly by the server and the entry is stored in the cache with the default lifespan/maxIdle.
But if the user PUTs or POSTs an entry and doesn't specify timeToLiveSeconds=0 and maxIdleTimeSeconds=0 explicitly, the entries are stored with infinite lifespan/maxIdle.
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2770) Wrong format arguments in trace log message
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2770?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2770:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Thanks Adi, integrated on both 5.2.x and master.
> Wrong format arguments in trace log message
> -------------------------------------------
>
> Key: ISPN-2770
> URL: https://issues.jboss.org/browse/ISPN-2770
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.CR2
> Reporter: Michal Linhard
> Assignee: Adrian Nistor
> Fix For: 5.2.1, 5.3.0.Final
>
>
> https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
> {code}
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) java.util.logging.ErrorManager: 5: Formatting error
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) java.util.MissingFormatArgumentException: Format specifier 's'
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at java.util.Formatter.format(Formatter.java:2432)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at java.util.Formatter.format(Formatter.java:2367)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at java.lang.String.format(String.java:2769)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtLogRecord.formatRecord(ExtLogRecord.java:434)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtLogRecord.getFormattedMessage(ExtLogRecord.java:397)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.formatters.Formatters$10.renderRaw(Formatters.java:358)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:150)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86)
> node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:290)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.Logger.logRaw(Logger.java:721)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.Logger.log(Logger.java:672)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logging.Logger.logf(Logger.java:2126)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logging.DelegatingBasicLogger.tracef(DelegatingBasicLogger.java:134)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterCacheStatus.addMember(ClusterCacheStatus.java:106)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:460)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterTopologyManagerImpl.handleNewView(ClusterTopologyManagerImpl.java:231)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.handleViewChange(ClusterTopologyManagerImpl.java:597)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at java.lang.reflect.Method.invoke(Method.java:597)
> node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:212)
> node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at java.lang.Thread.run(Thread.java:662)
> {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
13 years, 2 months
[JBoss JIRA] (ISPN-2798) Test name differs from test class name
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2798?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2798:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
thanks - integrated on both 5.2.x and master.
> Test name differs from test class name
> --------------------------------------
>
> Key: ISPN-2798
> URL: https://issues.jboss.org/browse/ISPN-2798
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 5.2.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 5.2.1, 5.3.0.Alpha1
>
>
> The log from a recent test run on core contains these warnings.
> Some of them are actually superfluous because they refer to abstract classes. UnitTestTestNGListener should not print such a warning if the test class is abstract.
> {noformat}
> 2013-02-05 17:18:14,372 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name AsyncAPIAsyncReplTest for class AsyncAPITxAsyncReplTest
> 2013-02-05 17:18:14,373 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name AsyncAPISyncReplTest for class AsyncAPITxSyncReplTest
> 2013-02-05 17:18:14,376 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name SyncReplImplicitLockingTest for class SyncReplPessimisticLockingTest
> 2013-02-05 17:18:15,351 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name DldEagerLockingReplicationTest for class DldPessimisticLockingReplicationTest
> 2013-02-05 17:18:15,354 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name Command line test for class BaseDldPessimisticLockingTest
> 2013-02-05 17:18:15,355 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name DldEagerLockingDistributedTest for class DldPessimisticLockingDistributedTest
> 2013-02-05 17:18:19,641 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name TransactionReleaseWithAsync2ndPhaseRecoveryTest for class TransactionCleanupWithAsync2ndPhaseRecoveryTest
> 2013-02-05 17:18:19,930 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name ReplLockReorderingTest for class ReplicatedLockReorderingTest
> 2013-02-05 17:18:23,524 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name TransactionReleaseWithAsync2ndPhaseTest for class TransactionCleanupWithAsync2ndPhaseTest
> 2013-02-05 17:18:39,416 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name AsyncTest for class AsyncStoreEvictionTest
> 2013-02-05 17:18:39,472 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name RemovedEntryFoundAsyncStoreTest for class AsyncStoreFunctionalTest
> 2013-02-05 17:18:52,937 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name InitiatorCrasherBeforePrepareOptimisticTest for class InitiatorCrashOptimisticTest
> 2013-02-05 17:19:02,368 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name BasicSingleLockRepOptTest for class BasicSingleLockReplOptTest
> 2013-02-05 17:19:24,012 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name TopologyAwareConsistentHashFactoryTest for class TopologyAwareSyncConsistentHashFactoryTest
> 2013-02-05 17:19:34,681 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name AsyncAPISyncDistTest for class AsyncAPITxSyncDistTest
> 2013-02-05 17:19:35,098 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name AsyncAPIAsyncDistTest for class AsyncAPITxAsyncDistTest
> 2013-02-05 17:20:44,563 WARN [org.infinispan.test.fwk.UnitTestTestNGListener] (TestNG) Wrong test name TxAndAsyncOpsTest for class TxCacheAndAsyncOpsTest
> {noformat}
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2720) StateTransferPessimisticTest.testStateTransfer fails randomly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2720?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2720:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
integrated on 5.2.x and master.
> StateTransferPessimisticTest.testStateTransfer fails randomly
> -------------------------------------------------------------
>
> Key: ISPN-2720
> URL: https://issues.jboss.org/browse/ISPN-2720
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 5.2.0.CR1
> Reporter: Galder Zamarreño
> Assignee: Adrian Nistor
> Labels: testsuite_stability
> Fix For: 5.2.1, 5.3.0.Alpha1
>
> Attachments: testStateTransfer-6.tgz
>
>
> {code}testStateTransfer(org.infinispan.statetransfer.StateTransferPessimisticTest) Time elapsed: 0.174 sec <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<2>
> at org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.failNotEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:128)
> at org.junit.Assert.assertEquals(Assert.java:472)
> at org.junit.Assert.assertEquals(Assert.java:456)
> at org.infinispan.statetransfer.StateTransferPessimisticTest.testStateTransfer(StateTransferPessimisticTest.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680){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
13 years, 2 months
[JBoss JIRA] (ISPN-2730) Not possible to instantiate org.infinispan.cdi.InfinispanExtension during startup of appserver
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2730?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2730:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
integrated on 5.2.x and master.
> Not possible to instantiate 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.1, 5.3.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
13 years, 2 months