September 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3516) Remove deprecated API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3516?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3516: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/2073, https://github.com/infinispan/infinispan-server/pull/154 (was: https://github.com/infinispan/infinispan/pull/2073) > Remove deprecated API > --------------------- > > Key: ISPN-3516 > URL: https://issues.jboss.org/browse/ISPN-3516 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 6.0.0.Alpha4 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Beta1 > > > classes: > * org.infinispan.loaders.remote.wrapper.EntryWrapper > * org.infinispan.context.FlagContainer > methods: > * StreamingMarshaller.startObjectOutput > * AdvancedCache.getCacheEntry > * AtomicMapLookup.getAtomicMap > * DistributionManager.isLocal > * TxInterceptor.setStatisticsEnabled > * GridFile.delete > * ModuleLifecycle.cacheManagerStarting > * ModuleLifecycle.cacheStarting > * DeadlockDetectingLockManager.getLocallyInterruptedTransactions > packages: > * org.infinispan.config -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3522) Upgrade to c3p0 version 0.9.2.1

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3522: ---------------------------------- Summary: Upgrade to c3p0 version 0.9.2.1 Key: ISPN-3522 URL: https://issues.jboss.org/browse/ISPN-3522 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 6.0.0.Alpha4 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 6.0.0.Beta2 We are currently using c3p0 version 0.9.1.2, which is the last version with the {{c3p0}) group id. We should upgrade to the latest stable version, 0.9.2.1: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.mchange%22%20AND%2... AFAIK version 0.9.2.1 does not solve the concurrency issue in ISPN-3324, but it may solve other problems. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3457) Infinispan error running on IBM JDK

by Ivan Vasyliev (JIRA)

[ https://issues.jboss.org/browse/ISPN-3457?page=com.atlassian.jira.plugin.... ] Ivan Vasyliev updated ISPN-3457: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2077 > Infinispan error running on IBM JDK > ----------------------------------- > > Key: ISPN-3457 > URL: https://issues.jboss.org/browse/ISPN-3457 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.Alpha3 > Environment: WAS 8.0.0.6 JDK, Windows 7 Professional > Reporter: Luis Montoya > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha3 > > > I created a sample application using infinispan on standar JDK (Sun/Oracle). This app works fine using this JDK. > > I tried to run the app on IBM JDK (the needed for WAS), but I get the below error: > > org.infinispan.commons.CacheException: Unable to construct a GlobalComponentRegistry! > at org.infinispan.factories.GlobalComponentRegistry.<init>(GlobalComponentRegistry.java:129) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:276) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:246) > at org.infinispan.quickstart.clusteredcache.replication.AbstractNode.createCacheManagerProgramatically(AbstractNode.java:41) > at org.infinispan.quickstart.clusteredcache.replication.AbstractNode.<init>(AbstractNode.java:62) > at org.infinispan.quickstart.clusteredcache.replication.Node0.main(Node0.java:32) > Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.LocalTopologyManagerImpl.inject(org.infinispan.remoting.transport.Transport,java.util.concurrent.ExecutorService,org.infinispan.factories.GlobalComponentRegistry,org.infinispan.util.TimeService) on object of type LocalTopologyManagerImpl with parameters [org.infinispan.executors.LazyInitializingExecutorService@96d7b55b, org.infinispan.executors.LazyInitializingExecutorService@96d7b55b, org.infinispan.factories.GlobalComponentRegistry@9fd5a559, org.infinispan.util.DefaultTimeService@725adace] > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:188) > at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:229) > at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65) > at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797) > at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201) > at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156) > at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:277) > at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:253) > at org.infinispan.factories.GlobalComponentRegistry.<init>(GlobalComponentRegistry.java:125) > ... 5 more > Caused by: java.lang.IllegalArgumentException: discrepancia en el tipo de argumento > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:183) > ... 13 more > > > It seems that a method which is being invoked through reflection is receiving incorrectly the first parameter, which should be a org.infinispan.remoting.transport.Transport instance, but it is receiving a org.infinispan.executors.LazyInitializingExecutorService@96d7b55b instance > > The code which launch the error is the next: > > > new DefaultCacheManager( > GlobalConfigurationBuilder.defaultClusteredBuilder().globalJmxStatistics().allowDuplicateDomains(true) > .transport().addProperty("configurationFile", "jgroups.xml") > .build(), > new ConfigurationBuilder() > .clustering().cacheMode(CacheMode.REPL_SYNC) > .build() > ); > Making a review and debug of the code, the next behavior was seen which produce the error: > if a map called map contains something like this {1=some.class.type}, and you try to get a value using the 0 as the key ( map.get(0), it doens't return null rather it returns the value for the 1 key, it means, for map.get(0) it returns "some.class.type", as if map.get(1) was called) > Also, when the contains method of Map interface is called ( map.contains(0)), it returns true, which is incorrect because the map only has the 1 key > This behavior is happening on this class and method: > class: org.infinispan.factories.components.ComponentMetadata$InjectMetadata > methods: getParameterName, isParameterNameSet -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3519) Upgrade to JGroups 3.4.0.Beta1

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3519?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3519: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2075 > Upgrade to JGroups 3.4.0.Beta1 > ------------------------------ > > Key: ISPN-3519 > URL: https://issues.jboss.org/browse/ISPN-3519 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Beta1 > > > <email-from-bela> > I released 3.4.0.Beta1 yesterday. It contains delta views [1] and > compressed merge views [2]. Useful in large clusters, delta views > dramatically reduce the message size needed to install a new view, by > sending only the diff to the previous view. E.g. if we have > v5={A,B,C,D,E} and F joins, A will only send v6={v5 +F}, and everybody > will construct a new view v6={A,B,C,D,E,F}. > The message size of a new view is therefore only a function of the > number of members which joined or left, and not a function of the entire > cluster size. > Full views are only sent when the first view of a coordinator is sent, > e.g. if A crashes and B takes over, B would send the full view. > Delta views can be turned off by seting GMS.use_delta_views=false. > 3.4.0.Beta1 can be downloaded from SourceForge [3] or Nexus [4]. > 3.4.0.Beta1 should be the last (and only) beta, I intend to release > 3.4.0.Final in early October. > Cheers, > [1] https://issues.jboss.org/browse/JGRP-1354 > [2] https://issues.jboss.org/browse/JGRP-1391 > [3] https://sourceforge.net/projects/javagroups/files/JGroups/3.4.0.Beta1 > [4] > http://search.maven.org/remotecontent?filepath=org/jgroups/jgroups/3.4.0.... > </email-from-bela> -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3519) Upgrade to JGroups 3.4.0.Beta1

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3519?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3519: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to JGroups 3.4.0.Beta1 > ------------------------------ > > Key: ISPN-3519 > URL: https://issues.jboss.org/browse/ISPN-3519 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Beta1 > > > <email-from-bela> > I released 3.4.0.Beta1 yesterday. It contains delta views [1] and > compressed merge views [2]. Useful in large clusters, delta views > dramatically reduce the message size needed to install a new view, by > sending only the diff to the previous view. E.g. if we have > v5={A,B,C,D,E} and F joins, A will only send v6={v5 +F}, and everybody > will construct a new view v6={A,B,C,D,E,F}. > The message size of a new view is therefore only a function of the > number of members which joined or left, and not a function of the entire > cluster size. > Full views are only sent when the first view of a coordinator is sent, > e.g. if A crashes and B takes over, B would send the full view. > Delta views can be turned off by seting GMS.use_delta_views=false. > 3.4.0.Beta1 can be downloaded from SourceForge [3] or Nexus [4]. > 3.4.0.Beta1 should be the last (and only) beta, I intend to release > 3.4.0.Final in early October. > Cheers, > [1] https://issues.jboss.org/browse/JGRP-1354 > [2] https://issues.jboss.org/browse/JGRP-1391 > [3] https://sourceforge.net/projects/javagroups/files/JGroups/3.4.0.Beta1 > [4] > http://search.maven.org/remotecontent?filepath=org/jgroups/jgroups/3.4.0.... > </email-from-bela> -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1540) Refactor distribution interceptor

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1540?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1540: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Refactor distribution interceptor > --------------------------------- > > Key: ISPN-1540 > URL: https://issues.jboss.org/browse/ISPN-1540 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.1.0.BETA5 > Reporter: Mircea Markus > Assignee: William Burns > Fix For: 6.0.0.Beta1 > > > DistributionInterceptor, as it looks now is unnecessary complex. Before adding more functionality on top of it (i.e. ISPN-1539) it should be refactored: > - extract L1 logic into a different interceptor > - this would require moving the StateTransferLock logic into another interceptor as well > - now that we have separation between tx and non-tx caches, we can extract the remaining logic into TransactionalDistributionInterceptor and NonTransactional... -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2205) Design HotRod protocol version 1.2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2205?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2205: ------------------------------------- [~galderz] There's still one thing to be addressed: - the protocol defines the consistent hash (CH) in terms of wheels - the server has a routing table - we have some code on the server that builds/emulates the wheel in a way the client understands it This hack has some drawbacks: - in certain situations the primary owner computation on the client is not performed correctly (doesn't match the primary owner on the server) - it is not efficient We should improve the protocol to fix this. > Design HotRod protocol version 1.2 > ---------------------------------- > > Key: ISPN-2205 > URL: https://issues.jboss.org/browse/ISPN-2205 > Project: Infinispan > Issue Type: Task > Components: Remote protocols > Affects Versions: 5.2.0.ALPHA2 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: hotrod > > The consistent hash representation is changing in 5.2, and we need to modify the HotRod protocol to incorporate those changes. We preserved compatibility with 1.0/1.1 clients with a workaround on the server, but is not as efficient as it could be. > The new version could also incorporate fixes for older issues like ISPN-1293. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3521) Server security module uses outdated Infinispan API

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3521?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3521: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Server security module uses outdated Infinispan API > --------------------------------------------------- > > Key: ISPN-3521 > URL: https://issues.jboss.org/browse/ISPN-3521 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta1 > > > Fork the security subsystem so that it uses modern Infinispan APIs -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3521) Server security module uses outdated Infinispan API

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3521?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3521: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-server/pull/153 > Server security module uses outdated Infinispan API > --------------------------------------------------- > > Key: ISPN-3521 > URL: https://issues.jboss.org/browse/ISPN-3521 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta1 > > > Fork the security subsystem so that it uses modern Infinispan APIs -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2205) Design HotRod protocol version 1.2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2205?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2205: -------------------------------- Fix Version/s: (was: 5.2.0.Final) (was: 5.2.0.CR1) > Design HotRod protocol version 1.2 > ---------------------------------- > > Key: ISPN-2205 > URL: https://issues.jboss.org/browse/ISPN-2205 > Project: Infinispan > Issue Type: Task > Components: Remote protocols > Affects Versions: 5.2.0.ALPHA2 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: hotrod > > The consistent hash representation is changing in 5.2, and we need to modify the HotRod protocol to incorporate those changes. We preserved compatibility with 1.0/1.1 clients with a workaround on the server, but is not as efficient as it could be. > The new version could also incorporate fixes for older issues like ISPN-1293. -- 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

12 years, 7 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 September 2013