November 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5917) Transactions rolled back early are never removed from the transaction table

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5917: ---------------------------------- Summary: Transactions rolled back early are never removed from the transaction table Key: ISPN-5917 URL: https://issues.jboss.org/browse/ISPN-5917 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.1.0.Alpha2, 8.0.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.1.0.Beta1, 8.1.0.Final When a transaction is rolled back before the first cache operation, the transaction is registered in the TransactionTable and is never removed. That happens because {{TxInterceptor}} sees the transaction is marked for rollback and immediately throws an exception. This can be seen in {{MarkAsRollbackTest}}, which blocks for 30 seconds during teardown because there's still a transaction in the transaction table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[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: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1175272|https://bugzilla.redhat.com/show_bug.cgi?id=1175272] from POST to MODIFIED > 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)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5903) Spring package split

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5903?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5903: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1266831|https://bugzilla.redhat.com/show_bug.cgi?id=1266831] from POST to MODIFIED > Spring package split > -------------------- > > Key: ISPN-5903 > URL: https://issues.jboss.org/browse/ISPN-5903 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > Into: > * remote > * embedded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5900) Cleanup uberjar packaging (ideal solution)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5900: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1266832|https://bugzilla.redhat.com/show_bug.cgi?id=1266832] from POST to MODIFIED > Cleanup uberjar packaging (ideal solution) > ------------------------------------------ > > Key: ISPN-5900 > URL: https://issues.jboss.org/browse/ISPN-5900 > Project: Infinispan > Issue Type: Feature Request > Components: Build process > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: jdg7 > > ISPN-5838 provides a backwards compatible solution whereas an ideal solution involves also changing packages (which will fix Weld/OSGi errors) into: > * org.infinispan.cdi.common > * org.infinispan.cdi.remote > * org.infinispan.cdi.embedded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5838) Cleanup uberjar packaging

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5838?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5838: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1266832|https://bugzilla.redhat.com/show_bug.cgi?id=1266832] from POST to MODIFIED > Cleanup uberjar packaging > ------------------------- > > Key: ISPN-5838 > URL: https://issues.jboss.org/browse/ISPN-5838 > Project: Infinispan > Issue Type: Feature Request > Components: Build process > Reporter: Pedro Zapata > Assignee: Sebastian Łaskawiec > Labels: jdg7 > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Need to minimize shipping non-required or provided dependencies in the uberjar. > Some ideas that need to be further refined: > * Split CDI into cdi-embedded and cdi-remote > * Add only cdi-embedded to infinispan-embedded (and cdi-remote to infinispan-remote) > * Add infinispan-client-hotrod to infinispan-embedded ? Used for RemoteCacheStore (which is an embedded use-case) > * infinispan-embedded has a compulsory dependency on javax.transaction api. We cannot change this in Infinispan <= 8.2 for backwards compatibility, but we can change it in 8.3 > * -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5916) Filtering by cache status in management console doesn't work

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-5916: --------------------------------- Summary: Filtering by cache status in management console doesn't work Key: ISPN-5916 URL: https://issues.jboss.org/browse/ISPN-5916 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.1.0.Alpha2 Reporter: Jiří Holuša Page: "Caches" tab -> click on certain cache container: list of caches in that container is shown. On the left side, these are options how to filter the shown caches and you can also filter by cache status - Indexing, Offline, Rebalancing, Split. When I click any of them, nothing happens, it looks like they do nothing since I definitely don't have any cache rebalancing or indexed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5915) Displaying caches in management console doesn't detect non-TX cache correctly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5915?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-5915: ------------------------------------- Assignee: Vladimir Blagojevic > Displaying caches in management console doesn't detect non-TX cache correctly > ----------------------------------------------------------------------------- > > Key: ISPN-5915 > URL: https://issues.jboss.org/browse/ISPN-5915 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Alpha2 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > > Page "Caches" tab -> click on certain cache container: list of caches in that container is shown. > Having cache configured e.g. like this: > {code} > <local-cache name="localCache" start="EAGER"> > <transaction mode="NONE"/> > </local-cache> > {code} > However, in the UI, the cache is still marked as transactional. There is the "transactional" icon in the cache card and also when I click to the filter to show only TX caches, the cache is still displayed. > It seems to me that the code only checks for presence of <transaction> element, but not it's "mode" attribute. If I set the cache without the <transaction> element, it's correctly recognized as non-TX cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5915) Displaying caches in management console doesn't detect non-TX cache correctly

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-5915: --------------------------------- Summary: Displaying caches in management console doesn't detect non-TX cache correctly Key: ISPN-5915 URL: https://issues.jboss.org/browse/ISPN-5915 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.1.0.Alpha2 Reporter: Jiří Holuša Page "Caches" tab -> click on certain cache container: list of caches in that container is shown. Having cache configured e.g. like this: {code} <local-cache name="localCache" start="EAGER"> <transaction mode="NONE"/> </local-cache> {code} However, in the UI, the cache is still marked as transactional. There is the "transactional" icon in the cache card and also when I click to the filter to show only TX caches, the cache is still displayed. It seems to me that the code only checks for presence of <transaction> element, but not it's "mode" attribute. If I set the cache without the <transaction> element, it's correctly recognized as non-TX cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5914) Unauthenticated connections should be closed immediately for mechs which specify NOANONYMOUS policy

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5914: ------------------------------------- Summary: Unauthenticated connections should be closed immediately for mechs which specify NOANONYMOUS policy Key: ISPN-5914 URL: https://issues.jboss.org/browse/ISPN-5914 Project: Infinispan Issue Type: Bug Components: Security, Server Affects Versions: 8.1.0.Alpha2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 8.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5914) Unauthenticated connections should be closed immediately for mechs which specify NOANONYMOUS policy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5914?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5914: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1243985 Bugzilla Update: Perform > Unauthenticated connections should be closed immediately for mechs which specify NOANONYMOUS policy > --------------------------------------------------------------------------------------------------- > > Key: ISPN-5914 > URL: https://issues.jboss.org/browse/ISPN-5914 > Project: Infinispan > Issue Type: Bug > Components: Security, Server > Affects Versions: 8.1.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2015