July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3311) org.infinispan.lifecycle.ModuleLifecycle service definitions missing from Lucene Directory jar

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3311: ----------------------------------- Assignee: Sanne Grinovero (was: Galder Zamarreño) > org.infinispan.lifecycle.ModuleLifecycle service definitions missing from Lucene Directory jar > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Sanne Grinovero > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) org.infinispan.lifecycle.ModuleLifecycle service definitions missing from Lucene Directory jar

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3311: ----------------------------------- Priority: Critical (was: Major) > org.infinispan.lifecycle.ModuleLifecycle service definitions missing from Lucene Directory jar > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) Unmarshalling error switching from 5.2 to 5.3

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-3311: ---------------------------------------- @Sanne, what if when the merge was done, the META-INF/services files were not included? > Unmarshalling error switching from 5.2 to 5.3 > --------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3332) ReadableGridFileChannel#read doesn't return -1 on EOS

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3332?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3332. --------------------------------- Fix Version/s: 6.0.0.Final Resolution: Done > ReadableGridFileChannel#read doesn't return -1 on EOS > ----------------------------------------------------- > > Key: ISPN-3332 > URL: https://issues.jboss.org/browse/ISPN-3332 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.3.0.Final, 6.0.0.Alpha1 > Reporter: Ales Justin > Assignee: Ales Justin > Fix For: 5.3.1.Final, 6.0.0.Alpha2, 6.0.0.Final > > > ReadableGridFileChannel#read must return -1 on EOS. > Atm it returns 0, which can cause infinite loop on read. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2771) WriteSkewTest.testWriteSkewWithOnlyPut fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2771?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2771: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > WriteSkewTest.testWriteSkewWithOnlyPut fails randomly > ----------------------------------------------------- > > Key: ISPN-2771 > URL: https://issues.jboss.org/browse/ISPN-2771 > Project: Infinispan > Issue Type: Bug > Components: Test Suite, Transactions > Affects Versions: 5.2.0.CR3 > Reporter: Adrian Nistor > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > Attachments: WriteSkewTest.zip > > > {noformat} > org.infinispan.api.mvcc.repeatable_read.WriteSkewTest:testWriteSkewWithOnlyPut > org.infinispan.transaction.WriteSkewException: Detected write skew. > java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.infinispan.api.mvcc.repeatable_read.WriteSkewTest.testWriteSkewWithOnlyPut(WriteSkewTest.java:315) > 22 lines not shown > Caused by Detected write skew. > org.infinispan.container.entries.RepeatableReadEntry.performLocalWriteSkewCheck(RepeatableReadEntry.java:68) > at org.infinispan.container.entries.RepeatableReadEntry.copyForUpdate(RepeatableReadEntry.java:52) > at org.infinispan.container.EntryFactoryImpl.wrapEntryForPut(EntryFactoryImpl.java:170) > at org.infinispan.interceptors.EntryWrappingInterceptor.visitPutKeyValueCommand(EntryWrappingInterceptor.java:164) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPutKeyValueCommand(OptimisticLockingInterceptor.java:142) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:132) > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:62) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:251) > at org.infinispan.interceptors.TxInterceptor.visitPutKeyValueCommand(TxInterceptor.java:191) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:128) > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:92) > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:62) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:343) > at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1162) > at org.infinispan.CacheImpl.putInternal(CacheImpl.java:760) > at org.infinispan.CacheImpl.put(CacheImpl.java:754) > at org.infinispan.CacheImpl.put(CacheImpl.java:748) > at org.infinispan.CacheSupport.put(CacheSupport.java:53) > at org.infinispan.api.mvcc.repeatable_read.WriteSkewTest$EntryWriter.call(WriteSkewTest.java:433) > at org.infinispan.api.mvcc.repeatable_read.WriteSkewTest$EntryWriter.call(WriteSkewTest.java:418) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > 1 lines not shown > {noformat} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3340) WebSocket server should use jackson mapper instead of json.org

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3340: ------------------------------------- Summary: WebSocket server should use jackson mapper instead of json.org Key: ISPN-3340 URL: https://issues.jboss.org/browse/ISPN-3340 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Tristan Tarrant -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3339) Jon plugin, two deprecated ops are failing. [RpcManager] [Transaction]

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-3339: ---------------------------------- Summary: Jon plugin, two deprecated ops are failing. [RpcManager] [Transaction] Key: ISPN-3339 URL: https://issues.jboss.org/browse/ISPN-3339 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Environment: Local machine, Fedora16 Reporter: Tomas Sykora Assignee: Mircea Markus These 2 operations are failing using infinispan-rhq-plugin: [Transactions] Enable/disable statistics. Deprecated, use the statisticsEnabled attribute instead. [RpcManager] Enable/disable statistics. Deprecated, use the statisticsEnabled attribute instead. While this is deprecated, should we remove it from plugin? Should we replace it by different operation? Typical error stack trace: org.mc4j.ems.connection.EmsInvocationException: Exception on invocation of [setStatisticsEnabled]javax.management.MBeanException at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:126) at org.infinispan.rhq.CacheComponent.invokeOperation(CacheComponent.java:192) at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: javax.management.MBeanException at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:271) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:273) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:251) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:160) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1017) at sun.reflect.GeneratedMethodAccessor131.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.mc4j.ems.impl.jmx.connection.support.providers.proxy.JMXRemotingMBeanServerProxy.invoke(JMXRemotingMBeanServerProxy.java:59) at $Proxy110.invoke(Unknown Source) at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:110) ... 10 more Caused by: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:269) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3338) DistributionManager operations Locate key & Is key local are not working properly

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-3338: ---------------------------------- Summary: DistributionManager operations Locate key & Is key local are not working properly Key: ISPN-3338 URL: https://issues.jboss.org/browse/ISPN-3338 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Environment: Tested localy Fedora16 Reporter: Tomas Sykora Assignee: Mircea Markus Testing infinispan-rhq-plugin (for InVM). DistributionManager operations Locate key & Is key local seem not to working properly. For a nonsense key Locate key operation is returning success with result of a label for cache "home node". Is key local operation for nonsense key is returning TRUE which is obviously wrong. This happens even on totally clear, entry-free, cache. Operation Could key be affected by a rehash is returning operation success with result false. This is questionable whether it should return failure or not. Again, for nonsense key. Please can anyone look at it? I don't think this is directly jon/plugin related. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) Unmarshalling error switching from 5.2 to 5.3

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-3311: ---------------------------------------- Yeah, the class is still there in 5.3.x version. Very odd why it's not loaded though. We need to find out what's wrong with it to be able to understand what's causing it. I'll keep you posted. > Unmarshalling error switching from 5.2 to 5.3 > --------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) Unmarshalling error switching from 5.2 to 5.3

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3311: --------------------------------------- Hi Galder, the {{lucene-v3}} vs. {{lucene}} split in Maven is only a source-level split. The assembled jar contains compiled classes from both v3 and v4 modules: we had to use a Maven hack to support both versions of Lucene and still be backwards compatible in terms of module definition. Nothing too magic, we just merge the two built modules and then generate the OSGi stuff as last step. If this just affects the entries stored via the Lucene Directory then it's definitely less critical: indexes can be rebuilt from the data; if it's a {{LifecycleCallbacks}} issue I guess that could even be compensated for by registering them explicitly? > Unmarshalling error switching from 5.2 to 5.3 > --------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Sanne Grinovero > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- 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, 8 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 July 2013