February 2012 - infinispan-issues

[JBoss JIRA] Created: (ISPN-556) house keeping of stale prepared transactions

by Mircea Markus (JIRA)

house keeping of stale prepared transactions -------------------------------------------- Key: ISPN-556 URL: https://jira.jboss.org/browse/ISPN-556 Project: Infinispan Issue Type: Feature Request Components: Transactions Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.0.Final We will need a background cleanup thread to clean up stale prepares and ongoing txs that have exceeded a timeout (in cases where there is no backend TM and hence no recovery) - Timeout could be set by user (cfg) - Or by TM (XAResource.setTimeout()) Should also be able to release locks in this case -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

6
12
0 / 0

[JBoss JIRA] (ISPN-1826) Hot Rod protocol fails to retrieve correct topology after node join

by Michal Linhard (JIRA)

Michal Linhard created ISPN-1826: ------------------------------------ Summary: Hot Rod protocol fails to retrieve correct topology after node join Key: ISPN-1826 URL: https://issues.jboss.org/browse/ISPN-1826 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.0.FINAL Reporter: Michal Linhard Assignee: Manik Surtani Another resilience test: 4 nodes node2 goes down and up again: http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/j... Test timeline goes like this: 2012-02-01 04:39:21,993: 20 hotrod clients started 2012-02-01 04:42:21,995: node02 killed 2012-02-01 04:45:27,950: node02 up again Endpoints: 172.18.1.1:11222 - node01 172.18.1.3:11222 - node02 172.18.1.5:11222 - node03 172.18.1.7:11222 - node04 in the client side log http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/j... http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/j... some warnings about connection refused and then node02 being removed from the pool by Timer thread: {code} 2012-02-01 04:43:15,608 254109 INFO [org.infinispan.client.hotrod.impl.protocol.Codec11] (Timer-1:) ISPN004006: New topology: [/172.18.1.1:11222, /172.18.1.7:11222, /172.18.1.5:11222] 2012-02-01 04:43:15,609 254110 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Timer-1:) ISPN004014: New server added(/172.18.1.1:11222), adding to the pool. 2012-02-01 04:43:15,610 254111 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Timer-1:) ISPN004014: New server added(/172.18.1.7:11222), adding to the pool. 2012-02-01 04:43:15,611 254112 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Timer-1:) ISPN004014: New server added(/172.18.1.5:11222), adding to the pool. 2012-02-01 04:43:15,612 254113 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Timer-1:) ISPN004016: Server not in cluster anymore(/172.18.1.3:11222), removing from the pool. {code} Log of Client-19 {code} 2012-02-01 04:39:20,962 19437 DEBUG [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) Statically configured servers: [/172.18.1.7:11222, /172.18.1.5:11222, /172.18.1.3:11222, /172.18.1.1:11222] 2012-02-01 04:39:20,962 19437 DEBUG [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) Load balancer class: org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy 2012-02-01 04:39:20,963 19438 DEBUG [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) Tcp no delay = true; client socket timeout = 120000 ms; connect timeout = 120000 ms 2012-02-01 04:39:20,996 19471 INFO [org.infinispan.client.hotrod.impl.protocol.Codec11] (Client-19:) ISPN004006: New topology: [/172.18.1.1:11222, /172.18.1.3:11222, /172.18.1.7:11222, /172.18.1.5:11222] 2012-02-01 04:39:20,997 19472 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.1:11222), adding to the pool. 2012-02-01 04:39:20,998 19473 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.3:11222), adding to the pool. 2012-02-01 04:39:20,999 19474 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.7:11222), adding to the pool. 2012-02-01 04:39:21,000 19475 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.5:11222), adding to the pool. 2012-02-01 04:45:26,202 384677 INFO [org.infinispan.client.hotrod.impl.protocol.Codec11] (Client-19:) ISPN004006: New topology: [/172.18.1.1:11222, /172.18.1.7:11222, /172.18.1.5:11222] 2012-02-01 04:45:26,206 384681 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.1:11222), adding to the pool. 2012-02-01 04:45:26,207 384682 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.7:11222), adding to the pool. 2012-02-01 04:45:26,208 384683 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (Client-19:) ISPN004014: New server added(/172.18.1.5:11222), adding to the pool. {code} it seems like they get new topology update but without newly started node02 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
9
0 / 0

[JBoss JIRA] (ISPN-1820) SearchMapping is not recognized

by Michael Wittig (JIRA)

Michael Wittig created ISPN-1820: ------------------------------------ Summary: SearchMapping is not recognized Key: ISPN-1820 URL: https://issues.jboss.org/browse/ISPN-1820 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.1.0.FINAL Environment: Windows XP, Java 1.6.0_26 Reporter: Michael Wittig Assignee: Sanne Grinovero SearchMapping is not recognized by Infinispan and therfore it is not possible to add Objects to cache where you can not add Annotations. (maybe you just have the class Files) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
8
0 / 0

[JBoss JIRA] (ISPN-1839) L1 invalidation fails when some of the requestors have left the cluster

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1839: ---------------------------------- Summary: L1 invalidation fails when some of the requestors have left the cluster Key: ISPN-1839 URL: https://issues.jboss.org/browse/ISPN-1839 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.1.0.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.1.1.FINAL When a node leaves the cluster, it remains in the list of requestors for all the entries that it retrieved from other nodes. When those entries are updated, their owners try to invalidate them on the leaver. The invalidation command fails because the target has left, and this causes the entire put operation to fail. This can be seen in some of the HotRod server tests, e.g. HotRodDistributionTest: {noformat} 2012-02-02 10:56:06,186 TRACE (CacheViewTrigger,HotRodDistributionTest-NodeA-37471) [org.infinispan.cacheviews.PendingCacheViewChanges] Previous members are [HotRodDistributionTest-NodeA-37471, HotRodDistributionTest-NodeB-63614, HotRodDistributionTest-NodeC-41658], joiners are [], leavers are [HotRodDistributionTest-NodeC-41658], recovered after merge = false 2012-02-02 10:56:06,296 TRACE (OOB-2,ISPN,HotRodDistributionTest-NodeB-63614) [org.infinispan.distribution.L1ManagerImpl] Keys [ByteArrayKey{data=ByteArray{size=39, hashCode=7ec14a15, array=0x6b2d746573744469..}}] needs invalidation on [HotRodDistributionTest-NodeC-41658] 2012-02-02 10:56:06,296 TRACE (OOB-2,ISPN,HotRodDistributionTest-NodeB-63614) [org.infinispan.remoting.rpc.RpcManagerImpl] HotRodDistributionTest-NodeB-63614 invoking in future call InvalidateL1Command{num keys=1, forRehash=false, origin=HotRodDistributionTest-NodeA-37471} to recipient list [HotRodDistributionTest-NodeC-41658] 2012-02-02 10:56:06,297 TRACE (transport-thread-64) [org.infinispan.remoting.rpc.RpcManagerImpl] HotRodDistributionTest-NodeB-63614 broadcasting call InvalidateL1Command{num keys=1, forRehash=false, origin=HotRodDistributionTest-NodeA-37471} to recipient list [HotRodDistributionTest-NodeC-41658] 2012-02-02 10:56:06,298 ERROR (OOB-2,ISPN,HotRodDistributionTest-NodeB-63614) [org.infinispan.interceptors.InvocationContextInterceptor] ISPN000136: Execution error java.util.concurrent.ExecutionException: org.infinispan.remoting.transport.jgroups.SuspectException: One or more nodes have left the cluster while replicating command SingleRpcCommand{cacheName='hotRodDistSync', command=InvalidateL1Command{num keys=1, forRehash=false, origin=HotRodDistributionTest-NodeA-37471}} {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1825) infinispan-5.1.xsd not in schema path and slow down bootstrap.

by Jeffrey Jia (JIRA)

Jeffrey Jia created ISPN-1825: --------------------------------- Summary: infinispan-5.1.xsd not in schema path and slow down bootstrap. Key: ISPN-1825 URL: https://issues.jboss.org/browse/ISPN-1825 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.FINAL Environment: infinispan 5.1.0.Final Reporter: Jeffrey Jia Assignee: Manik Surtani Priority: Minor Fix For: 5.1.1.FINAL org.infinispan.config.InfinispanConfiguration line:369 --376 {code} if (is != null) { log.debugf("Using schema %s", localPathToSchema); return is; } if (log.isDebugEnabled()) { log.debugf("Could not find schema on path %s, resolving %s to %s", localPathToSchema, SCHEMA_SYSTEM_PROPERTY, schemaPath()); } {code} the infinispan 4.2.x infinispan/core/pom.xml {code} <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.1</version> <executions> <execution> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> </execution> </executions> <configuration> <mainClass>org.infinispan.util.JaxbSchemaGenerator</mainClass> <arguments> <argument>${basedir}/src/main/resources/schema</argument> </arguments> </configuration> </plugin> {code} infinispan 5.1.x infinispan/core/pom.xml {code} <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <phase>process-resources</phase> <goals> <goal>java</goal> </goals> </execution> </executions> <configuration> <mainClass>net.sf.xframe.xsddoc.Main</mainClass> <arguments> <argument>-q</argument> <argument>-s</argument> <argument>-t</argument> <argument>"XML Schema for Infinispan"</argument> <argument>-o</argument> <argument>${project.build.directory}/xsd_doc</argument> <argument>${basedir}/src/main/resources/infinispan-5.1.xsd</argument> </arguments> </configuration> </plugin> {code} it always take 5s and my log is : {code} 2012-02-01 16:14:40,552 DEBUG [org.infinispan.config.InfinispanConfiguration] (main) Could not find schema on path schema/infinispan-config-5.1.xsd, resolving infinispan.config.schema to http://www.infinispan.org/schemas/infinispan-config-5.1.xsd 2012-02-01 16:15:45,115 WARN [org.infinispan.config.InfinispanConfiguration] (main) ISPN000139: Infinispan configuration schema could not be resolved locally nor fetched from URL. Local path=null, schema path=schema/infinispan-config-5.1.xsd, schema URL=http://www.infinispan.org/schemas/infinispan-config-5.1.xsd {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
8
0 / 0

[JBoss JIRA] (ISPN-1836) XSD contains wrong description for use1PcForAutoCommitTransactions attribute

by Martin Gencur (JIRA)

Martin Gencur created ISPN-1836: ----------------------------------- Summary: XSD contains wrong description for use1PcForAutoCommitTransactions attribute Key: ISPN-1836 URL: https://issues.jboss.org/browse/ISPN-1836 Project: Infinispan Issue Type: Task Affects Versions: 5.1.1.CR1 Reporter: Martin Gencur Assignee: Pete Muir Fix For: 5.1.1.FINAL https://github.com/infinispan/infinispan/blob/master/core/src/main/resour... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1832) Update JBoss TransactionManager to 4.16.2.Final

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1832: ------------------------------------- Summary: Update JBoss TransactionManager to 4.16.2.Final Key: ISPN-1832 URL: https://issues.jboss.org/browse/ISPN-1832 Project: Infinispan Issue Type: Component Upgrade Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.1.1.FINAL, 5.2.0.ALPHA1, 5.2.0.FINAL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1829) NPE when key 2 string transformer for lucene missing

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-1829: ---------------------------------- Summary: NPE when key 2 string transformer for lucene missing Key: ISPN-1829 URL: https://issues.jboss.org/browse/ISPN-1829 Project: Infinispan Issue Type: Enhancement Components: Lucene Directory Affects Versions: 5.1.0.FINAL Reporter: Thomas Fromm Assignee: Sanne Grinovero A speaking error message, maybe including the class name, for which a transformer is missing would be better. java.lang.NullPointerException at org.infinispan.query.backend.KeyTransformationHandler.getTransformerClassFromAnnotation(KeyTransformationHandler.java:204) at org.infinispan.query.backend.KeyTransformationHandler.getTransformerClass(KeyTransformationHandler.java:196) at org.infinispan.query.backend.KeyTransformationHandler.getTransformer(KeyTransformationHandler.java:189) at org.infinispan.query.backend.KeyTransformationHandler.keyToString(KeyTransformationHandler.java:154) at org.infinispan.query.backend.QueryInterceptor.keyToString(QueryInterceptor.java:310) at org.infinispan.query.backend.QueryInterceptor.addToIndexes(QueryInterceptor.java:220) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1835) ModuleCommandFactory hierachy should be cleaned up

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1835: -------------------------------------- Summary: ModuleCommandFactory hierachy should be cleaned up Key: ISPN-1835 URL: https://issues.jboss.org/browse/ISPN-1835 Project: Infinispan Issue Type: Enhancement Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 6.0.0.FINAL The distinction between ModuleCommandFactory and ExtendedModuleCommandFactory should go away, and they should be independent interfaces. The reason for this is cos ModuleCommandFactory is a global component and so should care about creating global commands, i.e. perform GC. On the other hand ExtendedModuleCommandFactory (which should be renamed) is a cache component and so cares about creating cache specific global components, i.e. invalidate a named region (or cache) in 2LC. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
2
0 / 0

[JBoss JIRA] (ISPN-1833) Add EmbeddedCacheManager.getGlobalComponentRegistry

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1833: -------------------------------------- Summary: Add EmbeddedCacheManager.getGlobalComponentRegistry Key: ISPN-1833 URL: https://issues.jboss.org/browse/ISPN-1833 Project: Infinispan Issue Type: Enhancement Components: Core API Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 6.0.0.FINAL You should be able to retrieve the global component registry out of the EmbeddedCacheManager. Rather that having to do: cache.getAdvancedCache().getComponentRegistry().getGlobalComponentRegistry() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2012