[JBoss JIRA] (ISPN-5092) CDI fails when both remote and embedded uber-jar are present
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5092?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5092:
-----------------------------------------------
Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1175272|https://bugzilla.redhat.com/show_bug.cgi?id=1175272] from MODIFIED to ON_QA
> CDI fails when both remote and embedded uber-jar are present
> ------------------------------------------------------------
>
> Key: ISPN-5092
> URL: https://issues.jboss.org/browse/ISPN-5092
> Project: Infinispan
> Issue Type: Bug
> Components: Build process, CDI Integration
> Reporter: Vojtech Juranek
> Fix For: 7.2.0.CR1
>
>
> When both uber-jars {{infinispan-remote}} and {{infinispan-embedded}} (e.g. for {{RemoteCacheStore}}), CDI fails with
> {noformat}
> org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.NullPointerException
> at org.infinispan.cdi.util.defaultbean.DefaultBeanExtension.afterBeanDiscovery(DefaultBeanExtension.java:345)
> 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:606)
> at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:42)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:359)
> at org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.deployBeans(ForwardingBootstrap.java:70)
> at org.jboss.weld.environment.se.Weld.initialize(Weld.java:133)
> at org.infinispan.all.remote.RemoteCDIDefaultCacheTest.loadBean(RemoteCDIDefaultCacheTest.java:26)
> {noformat}
> It's prpbably because CDI stuff is included in both jar and {{exclude}} in {{pom.xml}} doesn't work for uber-jars
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5893) ClusteredCacheConfigurationIT.testQueueFlushIntervalMemcached always fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5893?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5893:
-----------------------------------------------
Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1279369|https://bugzilla.redhat.com/show_bug.cgi?id=1279369] from MODIFIED to ON_QA
> ClusteredCacheConfigurationIT.testQueueFlushIntervalMemcached always fails
> --------------------------------------------------------------------------
>
> Key: ISPN-5893
> URL: https://issues.jboss.org/browse/ISPN-5893
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 8.1.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 8.1.0.Beta1
>
>
> Since the ISPN-5857 fix, ClusteredCacheConfigurationIT.testQueueFlushIntervalMemcached always fails.
> The problem is that the "k1" key no longer has node 1 as the primary owner. Because replication between the primary (node 2) and the backup (node 1) is asynchronous, a get after a put on node 1 almost never finds the value.
> The simple fix would be to swap the roles of node 1 and node 2 in the test.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5939) RemoteListenerWithDslFilterTest.testEventFilter and NonIndexedCacheRemoteListenerWithDslFilterTest.testEventFilter fail randomly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5939?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5939:
-----------------------------------------------
Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1279877|https://bugzilla.redhat.com/show_bug.cgi?id=1279877] from MODIFIED to ON_QA
> RemoteListenerWithDslFilterTest.testEventFilter and NonIndexedCacheRemoteListenerWithDslFilterTest.testEventFilter fail randomly
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-5939
> URL: https://issues.jboss.org/browse/ISPN-5939
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Reporter: Roman Macor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta2, 8.0.2.Final
>
>
> RemoteListenerWithDslFilterTest.testEventFilter and NonIndexedCacheRemoteListenerWithDslFilterTest.testEventFilter fail randomly with:
> Error Message
> expected:<2> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.client.hotrod.event.RemoteListenerWithDslFilterTest.testEventFilter(RemoteListenerWithDslFilterTest.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5965) Add a new mode (READ ONLY) for Partition Handling
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-5965:
--------------------------------------
Summary: Add a new mode (READ ONLY) for Partition Handling
Key: ISPN-5965
URL: https://issues.jboss.org/browse/ISPN-5965
Project: Infinispan
Issue Type: Feature Request
Components: Core
Reporter: Wolf-Dieter Fink
Without any PartitionHandling it is not possible to ensure the consistency of the cache.
With PH enabled it depends whether the remaining partition has the majority or at least all owners for a particular key to be able to access the key.
In some cases the prefered behaviour is to keep every entry readable but prevent from any change to keep consistency.
So there should be a configuration option for the partition handling to switch all instances to READ_ONLY instead of AVAILABLE/DEGRADED.
In this case each get will return the current value but each put will be rejected with a AvailabilityException
This prevents from any rebalancing if one partition contains a majority and stay available.
But in case of a real instance crash it might need a human interaction to set the state back to AVAILABLE as the node will never come back to the cluster.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months