January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated ISPN-3942: ----------------------------------- Component/s: Remote Protocols > HotRod client keep trying recover a connection to a cluster member after shutdown > --------------------------------------------------------------------------------- > > Key: ISPN-3942 > URL: https://issues.jboss.org/browse/ISPN-3942 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Infinispan server with HotRod client in server-client mode and replicated caches. > Reporter: Wolf-Dieter Fink > Assignee: Mircea Markus > Labels: clustered, hotrod, hotrod-java-client > Attachments: hotrod-client.log > > > If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed. > There is only a replicated cache configured. > From the server-logfile the new cluster view is established > 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered] > There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server. > This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created ISPN-3942: -------------------------------------- Summary: HotRod client keep trying recover a connection to a cluster member after shutdown Key: ISPN-3942 URL: https://issues.jboss.org/browse/ISPN-3942 Project: Infinispan Issue Type: Bug Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 Environment: Infinispan server with HotRod client in server-client mode and replicated caches. Reporter: Wolf-Dieter Fink Assignee: Mircea Markus If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed. There is only a replicated cache configured. >From the server-logfile the new cluster view is established 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered] There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server. This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3941) Add pre-release stable version check for maven dependencies

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3941?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3941: -------------------------------- Description: We need to enhance our maven build to perform the following dependecy checks before doing a release: 1. no SNAPSHOT dependencies are used 2. all dependencies are Final if the current build is a Final Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might want to do this check only for org.jboss, org.infinispan artifact groups. was: We need to enhance our maven build to perform the following dependecy checks before doing a release: 1. no SNAPSHOT dependencies are used 2. all dependencies are Final if the current build is a Final Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might whant to do this check only for org.jboss.*, org.infinispan.* artifact groups. > Add pre-release stable version check for maven dependencies > ----------------------------------------------------------- > > Key: ISPN-3941 > URL: https://issues.jboss.org/browse/ISPN-3941 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha1 > > > We need to enhance our maven build to perform the following dependecy checks before doing a release: > 1. no SNAPSHOT dependencies are used > 2. all dependencies are Final if the current build is a Final > Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might want to do this check only for org.jboss, org.infinispan artifact groups. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3941) Add pre-release stable version check for maven dependencies

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-3941: ----------------------------------- Summary: Add pre-release stable version check for maven dependencies Key: ISPN-3941 URL: https://issues.jboss.org/browse/ISPN-3941 Project: Infinispan Issue Type: Enhancement Components: Build process Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Alpha1 We need to enhance our maven build to perform the following dependecy checks before doing a release: 1. no SNAPSHOT dependencies are used 2. all dependencies are Final if the current build is a Final Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might whant to do this check only for org.jboss.*, org.infinispan.* artifact groups. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3911) Integrate endpoint security with server security subsystem

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3911?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3911: ---------------------------------- Component/s: Security > Integrate endpoint security with server security subsystem > ---------------------------------------------------------- > > Key: ISPN-3911 > URL: https://issues.jboss.org/browse/ISPN-3911 > Project: Infinispan > Issue Type: Sub-task > Components: Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3940) Fine-grained authorization interceptor

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3940?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3940: ---------------------------------- Component/s: Security > Fine-grained authorization interceptor > -------------------------------------- > > Key: ISPN-3940 > URL: https://issues.jboss.org/browse/ISPN-3940 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > > Introduce an AuthorizationInterceptor which can allow/deny operations based on the the current AccessControlContext -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3908) Security (Authentication, Authorization, Encryption)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3908?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3908: ---------------------------------- Component/s: Security > Security (Authentication, Authorization, Encryption) > ---------------------------------------------------- > > Key: ISPN-3908 > URL: https://issues.jboss.org/browse/ISPN-3908 > Project: Infinispan > Issue Type: Task > Components: Core, Remote Protocols, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 7.0.0.Final > > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3910) HotRod authentication

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3910?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3910: ---------------------------------- Component/s: Security > HotRod authentication > --------------------- > > Key: ISPN-3910 > URL: https://issues.jboss.org/browse/ISPN-3910 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Protocols, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3909) Authorization for Cache and CacheManager access

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3909?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3909: ---------------------------------- Component/s: Security > Authorization for Cache and CacheManager access > ----------------------------------------------- > > Key: ISPN-3909 > URL: https://issues.jboss.org/browse/ISPN-3909 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3931) Test Infinispan within a SecurityManager and provide a security policy

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3931?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3931: ---------------------------------- Component/s: Security > Test Infinispan within a SecurityManager and provide a security policy > ---------------------------------------------------------------------- > > Key: ISPN-3931 > URL: https://issues.jboss.org/browse/ISPN-3931 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Remote Protocols, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- 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

11 years, 11 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 January 2014