January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5735) Remove references to PermGen setting in JVM configurations of tests, enlarge some heap sizes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5735?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5735: ----------------------------------------------- Vaclav Dedik <vdedik(a)redhat.com> changed the Status of [bug 1298379|https://bugzilla.redhat.com/show_bug.cgi?id=1298379] from MODIFIED to ON_QA > Remove references to PermGen setting in JVM configurations of tests, enlarge some heap sizes > -------------------------------------------------------------------------------------------- > > Key: ISPN-5735 > URL: https://issues.jboss.org/browse/ISPN-5735 > Project: Infinispan > Issue Type: Task > Components: Build process, Test Suite - Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 8.0.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6082) Management console - cluster view page doesn't count nodes that are offline in #nodes #hosts column

by Roman Macor (JIRA)

Roman Macor created ISPN-6082: --------------------------------- Summary: Management console - cluster view page doesn't count nodes that are offline in #nodes #hosts column Key: ISPN-6082 URL: https://issues.jboss.org/browse/ISPN-6082 Project: Infinispan Issue Type: Bug Components: Console Reporter: Roman Macor Assignee: Vladimir Blagojevic page: Clusters tab Count of nodes and hosts only counts nodes that are running. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6075) Created cache is immediately available

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6075?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-6075: -------------------------------- Description: Steps to reproduce: 1) Add new cache 2) Go to the cache detail page Issues: 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. 3) I'm able to create a RemoteCache and put/get entries - no exception thrown was: Steps to reproduce: 1) Add new cache 2) Go to the cache detail page Issues: 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. > Created cache is immediately available > -------------------------------------- > > Key: ISPN-6075 > URL: https://issues.jboss.org/browse/ISPN-6075 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > > Steps to reproduce: > 1) Add new cache > 2) Go to the cache detail page > Issues: > 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) > 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. > 3) I'm able to create a RemoteCache and put/get entries - no exception thrown -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6075) Created cache is immediately available

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6075?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-6075: -------------------------------- Summary: Created cache is immediately available (was: Created cache appears as available in UI) > Created cache is immediately available > -------------------------------------- > > Key: ISPN-6075 > URL: https://issues.jboss.org/browse/ISPN-6075 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > > Steps to reproduce: > 1) Add new cache > 2) Go to the cache detail page > Issues: > 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) > 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5727) Client Listener removal and shutdown problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5727?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5727: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1297930|https://bugzilla.redhat.com/show_bug.cgi?id=1297930] from POST to MODIFIED > Client Listener removal and shutdown problems > --------------------------------------------- > > Key: ISPN-5727 > URL: https://issues.jboss.org/browse/ISPN-5727 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final, 8.0.2.Final > > > There are a couple of problems related to client listener registration on the client: > 1. When shutting down a remote cache manager to which client listeners have been added, even if the user does not remove them individually, stopping the remote cache manager should shutdown all client-side client listener threads. This is not the case right now. > 2. When removing a client listener, the client listener thread needs to be stopped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1444) Infinispan fails to shutdown gracefully

by James Mackenzie (JIRA)

[ https://issues.jboss.org/browse/ISPN-1444?page=com.atlassian.jira.plugin.... ] James Mackenzie commented on ISPN-1444: --------------------------------------- I had the same issue and came across this page on a Google Search. The fix for any others that stumble across this: * If you unregister the shutdown hooks via DONT_REGISTER, you're responsible for stopping Infinispan caches yourself * If you don't, and you're using a Clustered Configuration, your Application Server process never gracefully terminate due to non-daemon JGroups theads (like those above) still running * You need to call CacheManager.stop() yourself (perhaps via a ServletContextListener) If you'd like more details, I wrote up the fix over here: http://www.jamesfmackenzie.com/2016/01/18/infinispan-shutdown-fix/ Thanks! Jimmy > Infinispan fails to shutdown gracefully > --------------------------------------- > > Key: ISPN-1444 > URL: https://issues.jboss.org/browse/ISPN-1444 > Project: Infinispan > Issue Type: Bug > Affects Versions: 4.2.1.FINAL, 5.0.1.FINAL > Reporter: Luc Boudreau > Assignee: Manik Surtani > Priority: Blocker > > We have embeded Infinispan into our project, but when used, we cannot gracefully shutdown the JVM anymore. > There are a few exceptions thrown by late-access to the classloader from log4j, but these errors are easy to work around. Tomcat blocks any class loading after an application has been marked as shutting down. I can load them in the classloader in my application at runtime and circumvent those issues. > The main problem is the fact that the threads are just hanging there. They are not marked as daemon threads, so the JVM doesn't shut them off automatically, if required. The culprit threads are: > - OOB-1 > - OOB-2 > - multicast receiver > - unicast-receiver > - TransferQueueBuilder > Some of these threads might be related to JGroups. Please advise, and I will create a separate ticket in their bug tracker if needed. > I know Infinispan registers a shutdown hook in order to cleanly shut down, but it looks quite unreliable and causes a lot of problems for us. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5727) Client Listener removal and shutdown problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5727?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5727: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1297930|https://bugzilla.redhat.com/show_bug.cgi?id=1297930] from MODIFIED to POST > Client Listener removal and shutdown problems > --------------------------------------------- > > Key: ISPN-5727 > URL: https://issues.jboss.org/browse/ISPN-5727 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final, 8.0.2.Final > > > There are a couple of problems related to client listener registration on the client: > 1. When shutting down a remote cache manager to which client listeners have been added, even if the user does not remove them individually, stopping the remote cache manager should shutdown all client-side client listener threads. This is not the case right now. > 2. When removing a client listener, the client listener thread needs to be stopped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6054) Docker image cannot build website

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/ISPN-6054?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on ISPN-6054: ----------------------------------------- Right, for app development (which is really the case here), the Gemfile.lock should be checked in. Is the lock file which ensures that everyone uses the same dependencies. This is a good read in this regards - https://viget.com/extend/bundler-best-practices > Docker image cannot build website > --------------------------------- > > Key: ISPN-6054 > URL: https://issues.jboss.org/browse/ISPN-6054 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Reporter: Emmanuel Bernard > > There are several issues with the Docker image: > 1. it uses Ruby 2.2 which apparently make Awestruct 0.5.7.RC2 + Guard fail > 2. the Gemfile.lock conflicts > For 1. the error is as followed https://gist.github.com/emmanuelbernard/0524a56f2f859569c634 > The best is for Awestruct to fix the issue (assuming the analysis is correct). The alternative is to install rvm inside the docker image to controll the ruby version used. It requires a few experimentations (probably 2 to 4 hours of work) > For 2. the problem is as followed: > - docker build installs and create a Gemfile.lock with specific versions > - the host might already have a Gemfile.lock or worse, does not have one > - when running docker, we do bind the host directory on top of the docker directory > - so the host Gemfile.lock is used (different from Docker's gemfile.lock) and this will look for potentially incorrect dependencies and fail > The solutions to 2 are: > - create a build_docker.sh which will build the docker image, remove Gemfile.lock from the host and rerun the rake setup step to rebuild the Gemfile.lock to the right value ; since the host dir will be mapped, the Gemfile.lock will survive a docker image restart > - change the scripts to store the Gemfile.lock somewhere in a non mapped directory of the docker image and use an environment variable set in Dockerfile to influence our Rakefile (we do that already with the env variable BIND) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6079) Searching nodes in management console by IP address doesn't work

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6079?page=com.atlassian.jira.plugin.... ] Roman Macor reassigned ISPN-6079: --------------------------------- Assignee: Vladimir Blagojevic > Searching nodes in management console by IP address doesn't work > ---------------------------------------------------------------- > > Key: ISPN-6079 > URL: https://issues.jboss.org/browse/ISPN-6079 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Searching nodes by IP address doesn't work. e.g. 127.0.0.1 > Result: No nodes are matched. > Note: searching by part of address - "127.0" works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6080) Management console - cluster view page displays offline nodes from other clusters

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6080?page=com.atlassian.jira.plugin.... ] Roman Macor reassigned ISPN-6080: --------------------------------- Assignee: Vladimir Blagojevic > Management console - cluster view page displays offline nodes from other clusters > --------------------------------------------------------------------------------- > > Key: ISPN-6080 > URL: https://issues.jboss.org/browse/ISPN-6080 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Go to Clusters -> Make sure one cluster is stopped, the other is started -> go to started cluster > Result: Nodes from started cluster are displayed as well as nodes from stopped cluster. > Expected result: Only nodes from started cluster should be displayed in "started" cluster page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016