December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2025) NPE in Externalizer on shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2025?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2025: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug 818092|https://bugzilla.redhat.com/show_bug.cgi?id=818092] For JDG 6.0.0.ER7 I wasn't able to reproduce this (tried cca 10 times) In JDG 6.1.0.ER5 it didn't appear either (tried 3 times) > NPE in Externalizer on shutdown > ------------------------------- > > Key: ISPN-2025 > URL: https://issues.jboss.org/browse/ISPN-2025 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 5.1.4.FINAL > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.1.5.FINAL, 5.2.0.ALPHA1, 5.2.0.Final > > > This is what I get when I'm shutting down one of the clustered nodes (default config standalone-ha.xml) of JDG 6.0.0.ER7 > {code} > 09:50:25,505 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] Problems unmarshalling remote command from byte buffer: java.lang.NullPointerException > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.13.GA-redhat-1.jar:1.3.13.GA-redhat-1] > at org.infinispan.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:154) > at org.infinispan.marshall.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:114) > at org.infinispan.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:85) > at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectFromBuffer(MarshallerAdapter.java:50) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:200) > at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:456) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:363) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:238) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:543) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.JChannel.up(JChannel.java:716) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.RSVP.up(RSVP.java:179) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.pbcast.GMS.up(GMS.java:889) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:793) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:365) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:602) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:177) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.Discovery.up(Discovery.java:359) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.stack.Protocol.up(Protocol.java:363) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.TP.passMessageUp(TP.java:1180) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1728) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1710) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-1.jar:2.0.0.GA-redhat-1] > {code} > I've ran the instances out of the box by this commands, binding them to virtual ips on my laptop: > {code} > server1/bin/standalone.sh -b 192.168.11.101 -c standalone-ha.xml -Djboss.bind.address.management=192.168.11.101 -Djboss.node.name=node1 > server2/bin/standalone.sh -b 192.168.11.102 -c standalone-ha.xml -Djboss.bind.address.management=192.168.11.102 -Djboss.node.name=node2 > {code} > shutdown was a graceful shutdown by Ctrl+C from console -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2576) API documentation navigation bar is broken

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2576?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2576: ---------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Rejected The maven javadoc plugin is not at fault. The regression was caused by using a 1.7 JDK to build the release. Building with 1.6 against the new plugin produces correct results > API documentation navigation bar is broken > ------------------------------------------ > > Key: ISPN-2576 > URL: https://issues.jboss.org/browse/ISPN-2576 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.Beta5 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > > This is probably related to the plugin updates we made recently: the javadocs navigation bar now appears as a plain list of links. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2599) The ping command in the CLI should be hidden

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2599: ------------------------------------- Summary: The ping command in the CLI should be hidden Key: ISPN-2599 URL: https://issues.jboss.org/browse/ISPN-2599 Project: Infinispan Issue Type: Feature Request Components: CLI Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 5.2.0.Beta6 ping is an internal command and should not appear -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2594) CLI should prompt for password when connection requires it

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2594?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2594: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1515 > CLI should prompt for password when connection requires it > ---------------------------------------------------------- > > Key: ISPN-2594 > URL: https://issues.jboss.org/browse/ISPN-2594 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.2.0.Beta6 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2548) JDBCCacheStore doesn't work propertly with MSSql

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2548?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2548: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 879635|https://bugzilla.redhat.com/show_bug.cgi?id=879635] from ON_QA to VERIFIED > JDBCCacheStore doesn't work propertly with MSSql > ------------------------------------------------- > > Key: ISPN-2548 > URL: https://issues.jboss.org/browse/ISPN-2548 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.0.Beta4 > Reporter: Anna Manukyan > Assignee: Mircea Markus > Fix For: 5.2.0.Beta5, 5.2.0.Final > > > The functional tests for JDBCCacheStore using MSSQL2008 R2 as a store, are failing. > In case if the configuration is set with properties: > .addProperty("dropTableOnExit", "false") > .addProperty("createTableOnStart", "true") > The following exception arrise: > {code} > org.infinispan.loaders.CacheLoaderException: com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'edg_bin____defaultcache' in the database. > at org.infinispan.loaders.jdbc.TableManipulation.executeUpdateSql(TableManipulation.java:187) > at org.infinispan.loaders.jdbc.TableManipulation.createTable(TableManipulation.java:160) > at org.infinispan.loaders.jdbc.TableManipulation.start(TableManipulation.java:262) > at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.doConnectionFactoryInitialization(JdbcBinaryCacheStore.java:514) > at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.start(JdbcBinaryCacheStore.java:102) > at org.infinispan.loaders.CacheLoaderManagerImpl.start(CacheLoaderManagerImpl.java:159) > ... 104 more > {code} > Please note, that MSSql database is clean before the test run, this means that the table is not there. But the exception is in place anyway. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2558) Fix CLI help messages

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2558?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2558: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> made a comment on [bug 879177|https://bugzilla.redhat.com/show_bug.cgi?id=879177] All issues mentioned in this BZ were addressed. > Fix CLI help messages > --------------------- > > Key: ISPN-2558 > URL: https://issues.jboss.org/browse/ISPN-2558 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.0.Beta4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.2.0.Beta5 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2558) Fix CLI help messages

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2558?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2558: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 879177|https://bugzilla.redhat.com/show_bug.cgi?id=879177] from ON_QA to VERIFIED > Fix CLI help messages > --------------------- > > Key: ISPN-2558 > URL: https://issues.jboss.org/browse/ISPN-2558 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.0.Beta4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.2.0.Beta5 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2598) NullPointerException in case of passing customized FetchOptions to ClusteredQuery iterator() method

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2598?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2598: -------------------------------- Attachment: ClusteredQueryTest.java > NullPointerException in case of passing customized FetchOptions to ClusteredQuery iterator() method > --------------------------------------------------------------------------------------------------- > > Key: ISPN-2598 > URL: https://issues.jboss.org/browse/ISPN-2598 > Project: Infinispan > Issue Type: Bug > Components: Querying > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Attachments: ClusteredQueryTest.java > > > While running tests for query module, I've found the following thing. I'm not sure whether this is a bug, but the same flow for CacheQueryImpl works in different way rather than for ClusteredCacheQueryImpl. > I'm running the following command on already created ClusteredQuery: > {code} > ResultIterator iterator = cacheQuery.iterator(new FetchOptions() { > public FetchOptions fetchMode(FetchMode fetchMode) { > return null; > } > }); > {code} > This code throws NullPointerException, as the check of FetchMode is done in switch/case statement. > The same code for CacheQuery throws IllegalArgumentException, as the check is done with if/else statement. > Please find the test attached. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2598) NullPointerException in case of passing customized FetchOptions to ClusteredQuery iterator() method

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-2598: ----------------------------------- Summary: NullPointerException in case of passing customized FetchOptions to ClusteredQuery iterator() method Key: ISPN-2598 URL: https://issues.jboss.org/browse/ISPN-2598 Project: Infinispan Issue Type: Bug Components: Querying Reporter: Anna Manukyan Assignee: Sanne Grinovero While running tests for query module, I've found the following thing. I'm not sure whether this is a bug, but the same flow for CacheQueryImpl works in different way rather than for ClusteredCacheQueryImpl. I'm running the following command on already created ClusteredQuery: {code} ResultIterator iterator = cacheQuery.iterator(new FetchOptions() { public FetchOptions fetchMode(FetchMode fetchMode) { return null; } }); {code} This code throws NullPointerException, as the check of FetchMode is done in switch/case statement. The same code for CacheQuery throws IllegalArgumentException, as the check is done with if/else statement. Please find the test attached. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2597) HBase cache store testsuite should stop blocking CI jobs

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2597: -------------------------------------- Summary: HBase cache store testsuite should stop blocking CI jobs Key: ISPN-2597 URL: https://issues.jboss.org/browse/ISPN-2597 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.Beta6 i.e. https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/941/co... The "ERROR: Maven JVM terminated unexpectedly with exit code 137" error is normally associated with JVM running of memory. HBase has 'perftest' forkMode which means that it creates a new JVM per test. This is way too over the top for what it needs. Trying to run it with forkMode=none and paralell testsuite logs these errors: https://gist.github.com/4224569 This cache store shouldn't be blocking things, so disabling the cache store for the moment to be able to get on with other things. Anyone with Hadoop knowledge? -- 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

13 years, 4 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 2012