April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6120) Management console - there should be a warning about possible data loss when stopping the cluster

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6120?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6120: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Management console - there should be a warning about possible data loss when stopping the cluster > ------------------------------------------------------------------------------------------------- > > Key: ISPN-6120 > URL: https://issues.jboss.org/browse/ISPN-6120 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > > Clusters tab -> cluster -> actions -> stop > When stopping cluster/node, pop up should show warning, saying that caches without configured cache store will loose data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6298: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/78 > Network partition detection not working in mgmt console > ------------------------------------------------------- > > Key: ISPN-6298 > URL: https://issues.jboss.org/browse/ISPN-6298 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > > Page: Clusters -> select server group. > When I create a network partition and go to the page above, I still see the cluster status as "started". According to https://issues.jboss.org/browse/ISPN-5768 , there should be something as "Degraded" > I checked that the cluster is really partitioned. When I go to JConsole, I see in JGroups JChannel attributes, that the "view" is only partial. I also see in the server logs that servers correctly detected the split. > When I go to homepage (or the "Status event" tab), I see in the "Latest Grid Events:" that the split happened, hence the mgmt console is able to correctly detect it elsewhere. > Note that neither the status of a cache, which has configured partition handling to true, changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6298: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Network partition detection not working in mgmt console > ------------------------------------------------------- > > Key: ISPN-6298 > URL: https://issues.jboss.org/browse/ISPN-6298 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > > Page: Clusters -> select server group. > When I create a network partition and go to the page above, I still see the cluster status as "started". According to https://issues.jboss.org/browse/ISPN-5768 , there should be something as "Degraded" > I checked that the cluster is really partitioned. When I go to JConsole, I see in JGroups JChannel attributes, that the "view" is only partial. I also see in the server logs that servers correctly detected the split. > When I go to homepage (or the "Status event" tab), I see in the "Latest Grid Events:" that the split happened, hence the mgmt console is able to correctly detect it elsewhere. > Note that neither the status of a cache, which has configured partition handling to true, changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6540) Management console doesn't display cache containers correctly if there are two containers with the same name

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6540?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6540: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Management console doesn't display cache containers correctly if there are two containers with the same name > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-6540 > URL: https://issues.jboss.org/browse/ISPN-6540 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > Attachments: configs.zip, config_with_remoteSite.zip, Screenshot-containersWithSameName.png, Screenshot-detalPageForBothContainers.png > > > When we have two containers with the same name on different clusters some values are displayed correctly - #caches, name, clustering-info, but some are not - endpoints, sites. > Additionally, clicking on either of containers display the same information, even though containers are configured differently. > Please see the screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6575: -------------------------------- Status: Open (was: New) > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-6575: ----------------------------------- Assignee: William Burns > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6575: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4294 > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6575: -------------------------------- Fix Version/s: 9.0.0.Alpha2 8.2.2.Final > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6534) REST endpoint page doesn't work

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6534?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-6534: --------------------------------------- Caused by removing Undertow dependency from ISPN in [e81d358351d|https://github.com/infinispan/infinispan/commit/e81d358351d5a...] - not sure if it worth to implement http server for one single html page > REST endpoint page doesn't work > ------------------------------- > > Key: ISPN-6534 > URL: https://issues.jboss.org/browse/ISPN-6534 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final > Reporter: Roman Macor > > - start infinispan standalone server > - in web browser go to localhost:8080 > Result: > Nothing is displayed in the browser > Server log: > 12:58:55,882 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (nioEventLoopGroup-7-1) RESTEASY002010: Failed to execute: javax.ws.rs.NotFoundException: RESTEASY003210: Could not find resource for full path: http://localhost:8080/ > at org.jboss.resteasy.core.registry.ClassNode.match(ClassNode.java:75) > at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) > at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:445) > at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:257) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:194) > at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) > at org.jboss.resteasy.plugins.server.netty.RequestHandler.channelRead0(RequestHandler.java:53) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308) > at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32) > at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) > at java.lang.Thread.run(Thread.java:745) > Expected result: > Rest console should be displayed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6071: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NullPointerException when executing RemoveExpiredCommand > -------------------------------------------------------- > > Key: ISPN-6071 > URL: https://issues.jboss.org/browse/ISPN-6071 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Affects Versions: 8.0.2.Final > Reporter: Jason Hoetger > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.1.4.Final, 8.2.2.Final > > > I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace: > {noformat} > ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...] > ... > Caused by: java.lang.NullPointerException: null > at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142) > {noformat} > Here's RemoveExpiredCommand#setParameters(...): > {code} @Override > public void setParameters(int commandId, Object[] args) { > if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id"); > int i = 0; > commandInvocationId = (CommandInvocationId) args[i++]; > key = args[i++]; > value = args[i++]; > lifespan = (long) args[i++]; > }{code} > Line 142 is the cast of assignment of {{args\[3\]}} to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the {{perform()}} method seems to anticipate null lifespans at line 72: > {code} // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan > if (lifespan == null) {}{code} > Could this be fixed by simply changing the cast at line 142 from (long) to (Long)? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016