December 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7315) Use activations manager for cluster wide activations stats collection

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7315?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7315: ----------------------------------------- Assignee: Vladimir Blagojevic > Use activations manager for cluster wide activations stats collection > --------------------------------------------------------------------- > > Key: ISPN-7315 > URL: https://issues.jboss.org/browse/ISPN-7315 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta2 > > > In ClusterCacheStatsImpl.java we erroneously used passivation manager null check while accessing activation manager. This probably worked because these two were used in tandem but we should nonetheless use an appropriate null check. I ran into NPE when testing 9.0.0.Beta1 and testing off-heap memory -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7315) Use activations manager for cluster wide activations stats collection

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-7315: ----------------------------------------- Summary: Use activations manager for cluster wide activations stats collection Key: ISPN-7315 URL: https://issues.jboss.org/browse/ISPN-7315 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.Beta1 Reporter: Vladimir Blagojevic Fix For: 9.0.0.Beta2 In ClusterCacheStatsImpl.java we erroneously used passivation manager null check while accessing activation manager. This probably worked because these two were used in tandem but we should nonetheless use an appropriate null check. I ran into NPE when testing 9.0.0.Beta1 and testing off-heap memory -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7313) AbstractFileLookup.lookupFileStrict broken on Windows

by Stefan Engel (JIRA)

[ https://issues.jboss.org/browse/ISPN-7313?page=com.atlassian.jira.plugin.... ] Stefan Engel commented on ISPN-7313: ------------------------------------ Possible fix is to use an {{URLConnection}} instead of {{ClassLoader.getResourceAsStream()}}. This is a 'works for me' solution. Proper handling should then either wrap the exceptions in {{FileNotFoundException}} or change exception handling in {{AbstractFileLookup.getConfiguratuonBuilderHolder()}}. {code} public InputStream lookupFileStrict(URI uri, ClassLoader cl) throws FileNotFoundException { InputStream stream = null; try { URL url = new URL(uri.toString()); URLConnection connection = url.openConnection(); if (!(connection instanceof HttpURLConnection)) { stream = connection.getInputStream(); } else { throw new IllegalArgumentException("URL of type 'http' not supported"); } } catch (IOException e) { throw new IllegalStateException("Something went wrong", e); } return stream; } {code} > AbstractFileLookup.lookupFileStrict broken on Windows > ----------------------------------------------------- > > Key: ISPN-7313 > URL: https://issues.jboss.org/browse/ISPN-7313 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha4, 9.0.0.Beta1, 8.2.5.Final > Environment: Using Infinispan as JCache provider in Spring Boot (v1.3.5) application on Windows (either IDE (Eclipse) or fat jar). > Reporter: Stefan Engel > > The fix in ISPN-5949 breaks Windows compatibility. > infinispan.xml is configured in application.properties > {noformat} > spring.cache.jcache.config=classpath:spring/infinispan.xml > {noformat} > When using Infinispan in a Spring Boot application (fat jar or Eclipse IDE) the following exception is thrown: > {noformat} > Caused by: org.infinispan.commons.CacheConfigurationException: > com.ctc.wstx.exc.WstxIOException: Stream closed > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:119) > at org.infinispan.jcache.embedded.JCacheManager.getConfigurationBuilderHolder(JCacheManager.java:100) > at org.infinispan.jcache.embedded.JCacheManager.<init>(JCacheManager.java:56) > at org.infinispan.jcache.embedded.JCachingProvider.createCacheManager(JCachingProvider.java:46) > at org.infinispan.jcache.AbstractJCachingProvider.getCacheManager(AbstractJCachingProvider.java:67) > at org.springframework.boot.autoconfigure.cache.JCacheCacheConfiguration.createCacheManager(JCacheCacheConfiguration.java:101) > ... > {noformat} > When {{AbstractFileLookup.lookupFileStrict()}} is called in {{JCacheManager.getConfigurationHolder()}} the URI used for infinispan.xml looks something like this: > * fat jar > {noformat} > jar:file:/C:/projects/myapp/myservice-0.0.1.jar!/spring/infinispan.xml > {noformat} > * running app from within IDE > {noformat} > file:/C:/projects/workspace/myservice/target/classes/spring/infinispan.xml > {noformat} > The problem ist now twofold: > # First this nasty 'C:' in the Windows path breaks the parsing code in {{AbstractFileLookup.lookupFileStrict()}}, as {{lastIndexOf(':')}} cuts the drive letter from the path and not just 'jar:file:' as intended. The resulting {{fileName}} cannot be resolved and {{cl.getResourceAsStream(fileName)}} returns {{null}}. > {code} > public InputStream lookupFileStrict(URI uri, ClassLoader cl) throws FileNotFoundException { > //in case we don't have only file schema, but {{jar:file}} schema too, we have to get rid of all schemas > int startIndex = uri.toString().lastIndexOf(':'); > String fileName = uri.toString().substring(startIndex + 1); > return cl.getResourceAsStream(fileName); > } > {code} > # This method gets called too when running from within an IDE (at least Eclipse with Maven integration). But in this case Spring JCacheCacheConfiguration magic (createCachemanager() - configLocation.getURI()) resolves this path to a full path as seen above (not a classpath relative to {{/target/classes}}). As this path ist not on the classpath, {{cl.getResourceAsStream(fileName)}} returns {{null}}. > In both cases {{lookupFileStrict}} returns {{null}} as {{InputStream}} which in turn leads to the exception mentioned above. > The old code of {{lookupFileStrict()}} > {code} > return new FileInputStream(new File(uri)); > {code} > works fine from within the IDE, but is broken for a fat jar (ISPN-5949). > I am currently trying to find a workaround for this. But as far as I can see, the current behaviour (fix or no fix) is going to a problem when developing/running Infinispan enabled applications on Windows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7160: -------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4679, https://github.com/infinispan/infinispan/pull/4726 (was: https://github.com/infinispan/infinispan/pull/4679) > RemoteSpringSessionTest random failures > --------------------------------------- > > Key: ISPN-7160 > URL: https://issues.jboss.org/browse/ISPN-7160 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta2 > > > {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager: > {noformat} > org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53) > at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79) > at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37) > at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147) > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29) > {noformat} > If the cache manager was not created, teardown also fails with a NPE: > {noformat} > java.lang.NullPointerException > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41) > {noformat} > The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reopened ISPN-7160: --------------------------------------- > RemoteSpringSessionTest random failures > --------------------------------------- > > Key: ISPN-7160 > URL: https://issues.jboss.org/browse/ISPN-7160 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta2 > > > {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager: > {noformat} > org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53) > at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79) > at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37) > at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147) > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29) > {noformat} > If the cache manager was not created, teardown also fails with a NPE: > {noformat} > java.lang.NullPointerException > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41) > {noformat} > The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7314) Remove duplication code in AbstractListenerImpl and CacheNotifierImpl

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7314: -------------------------------------- Summary: Remove duplication code in AbstractListenerImpl and CacheNotifierImpl Key: ISPN-7314 URL: https://issues.jboss.org/browse/ISPN-7314 Project: Infinispan Issue Type: Enhancement Affects Versions: 9.0.0.Beta2 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 9.0.0.Final To speed up introduction of addFilteredListener, some code was duplicated in AbstractListenerImpl and CacheNotifierImpl. Refactor/deduplicate code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7242) Administration console does not work on IE

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7242?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7242: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/167 > Administration console does not work on IE > ------------------------------------------ > > Key: ISPN-7242 > URL: https://issues.jboss.org/browse/ISPN-7242 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Blocker > Fix For: 9.0.0.Beta2 > > Attachments: IE_Screenshot_Debug.png, Screenshot from 2016-11-28.png > > > I can't get pass log in screen in IE 11. > Steps to reproduce: enter username and password. > Result: nothing happens, IE web console show error message > Tested on Windows 7 machine, Firefox and Chrome work fine on the same machine. > IE web console: > Error: A security problem occurred. > at urlResolve (http://localhost:9990/console/scripts/management-console.min.js:43601:11) > at urlIsSameOrigin (http://localhost:9990/console/scripts/management-console.min.js:43627:9) > at sendReq (http://localhost:9990/console/scripts/management-console.min.js:35843:15) > at serverRequest (http://localhost:9990/console/scripts/management-console.min.js:35657:15) > at processQueue (http://localhost:9990/console/scripts/management-console.min.js:40325:17) > at Anonymous function (http://localhost:9990/console/scripts/management-console.min.js:40342:13) > at Scope.prototype.$eval (http://localhost:9990/console/scripts/management-console.min.js:41590:15) > at Scope.prototype.$digest (http://localhost:9990/console/scripts/management-console.min.js:41412:21) > at Scope.prototype.$apply (http://localhost:9990/console/scripts/management-console.min.js:41698:19) > at Anonymous function (http://localhost:9990/console/scripts/management-console.min.js:49690:21) > undefined > An unspecified error has been received from the server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7242) Administration console does not work on IE

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7242?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7242: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta2 Resolution: Done > Administration console does not work on IE > ------------------------------------------ > > Key: ISPN-7242 > URL: https://issues.jboss.org/browse/ISPN-7242 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Blocker > Fix For: 9.0.0.Beta2 > > Attachments: IE_Screenshot_Debug.png, Screenshot from 2016-11-28.png > > > I can't get pass log in screen in IE 11. > Steps to reproduce: enter username and password. > Result: nothing happens, IE web console show error message > Tested on Windows 7 machine, Firefox and Chrome work fine on the same machine. > IE web console: > Error: A security problem occurred. > at urlResolve (http://localhost:9990/console/scripts/management-console.min.js:43601:11) > at urlIsSameOrigin (http://localhost:9990/console/scripts/management-console.min.js:43627:9) > at sendReq (http://localhost:9990/console/scripts/management-console.min.js:35843:15) > at serverRequest (http://localhost:9990/console/scripts/management-console.min.js:35657:15) > at processQueue (http://localhost:9990/console/scripts/management-console.min.js:40325:17) > at Anonymous function (http://localhost:9990/console/scripts/management-console.min.js:40342:13) > at Scope.prototype.$eval (http://localhost:9990/console/scripts/management-console.min.js:41590:15) > at Scope.prototype.$digest (http://localhost:9990/console/scripts/management-console.min.js:41412:21) > at Scope.prototype.$apply (http://localhost:9990/console/scripts/management-console.min.js:41698:19) > at Anonymous function (http://localhost:9990/console/scripts/management-console.min.js:49690:21) > undefined > An unspecified error has been received from the server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7242) Administration console does not work on IE

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7242?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7242: -------------------------------------- Status: Open (was: New) > Administration console does not work on IE > ------------------------------------------ > > Key: ISPN-7242 > URL: https://issues.jboss.org/browse/ISPN-7242 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Blocker > Attachments: IE_Screenshot_Debug.png, Screenshot from 2016-11-28.png > > > I can't get pass log in screen in IE 11. > Steps to reproduce: enter username and password. > Result: nothing happens, IE web console show error message > Tested on Windows 7 machine, Firefox and Chrome work fine on the same machine. > IE web console: > Error: A security problem occurred. > at urlResolve (http://localhost:9990/console/scripts/management-console.min.js:43601:11) > at urlIsSameOrigin (http://localhost:9990/console/scripts/management-console.min.js:43627:9) > at sendReq (http://localhost:9990/console/scripts/management-console.min.js:35843:15) > at serverRequest (http://localhost:9990/console/scripts/management-console.min.js:35657:15) > at processQueue (http://localhost:9990/console/scripts/management-console.min.js:40325:17) > at Anonymous function (http://localhost:9990/console/scripts/management-console.min.js:40342:13) > at Scope.prototype.$eval (http://localhost:9990/console/scripts/management-console.min.js:41590:15) > at Scope.prototype.$digest (http://localhost:9990/console/scripts/management-console.min.js:41412:21) > at Scope.prototype.$apply (http://localhost:9990/console/scripts/management-console.min.js:41698:19) > at Anonymous function (http://localhost:9990/console/scripts/management-console.min.js:49690:21) > undefined > An unspecified error has been received from the server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7283) Make remote event supporting cluster listener more fine grained

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7283?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-7283: ------------------------------------- 8.2.x has been integrated. > Make remote event supporting cluster listener more fine grained > --------------------------------------------------------------- > > Key: ISPN-7283 > URL: https://issues.jboss.org/browse/ISPN-7283 > Project: Infinispan > Issue Type: Bug > Components: Listeners, Remote Protocols > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Beta2, 8.2.6.Final > > > Make server side cluster listener used for supporting remote events more fine grained. Right now if a client registers for created events, server side all nodes push all currently supported events over to the node where the remote listener is located: created, modified, removed and expired. Having all these events being passed around the cluster creates unnecessary load which can create problems in other nodes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2016