April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6454) Schema cache should require a special role when authorization is enabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6454?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6454: ---------------------------------- Status: Open (was: New) > Schema cache should require a special role when authorization is enabled > ------------------------------------------------------------------------ > > Key: ISPN-6454 > URL: https://issues.jboss.org/browse/ISPN-6454 > Project: Infinispan > Issue Type: Task > Components: Remote Querying, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Similarly to what happens with the script cache, if authorization is enabled the protobuf schema cache should only be accessible when the user has a specific role. The proposed role name is '___schema_manager' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6454) Schema cache should require a special role when authorization is enabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6454?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6454: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4223 > Schema cache should require a special role when authorization is enabled > ------------------------------------------------------------------------ > > Key: ISPN-6454 > URL: https://issues.jboss.org/browse/ISPN-6454 > Project: Infinispan > Issue Type: Task > Components: Remote Querying, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Similarly to what happens with the script cache, if authorization is enabled the protobuf schema cache should only be accessible when the user has a specific role. The proposed role name is '___schema_manager' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-21) Testsuite fails on local OSX environment

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPRK-21: ------------------------------------- Summary: Testsuite fails on local OSX environment Key: ISPRK-21 URL: https://issues.jboss.org/browse/ISPRK-21 Project: Infinispan Spark Issue Type: Bug Reporter: Galder Zamarreño Errors and output: https://gist.github.com/galderz/0a35ae02b62f7c6747b3304ea9fc333f -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6474) Server should not start default cache

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6474?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-6474: --------------------------------------- It starts a (useless) cache which is not part of the configuration. This is also shown in the server logs. > Server should not start default cache > ------------------------------------- > > Key: ISPN-6474 > URL: https://issues.jboss.org/browse/ISPN-6474 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Server > Affects Versions: 8.1.3.Final, 8.2.1.Final > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Fix For: 8.1.4.Final, 8.2.2.Final, 9.0.0.Final > > > The AbstractProtocolServer class always starts the default cache, but this should not happen. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6438) A Hot Rod client should be able to configure the same properties with hotrod-client.properties file as the programatic API supports

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6438?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6438: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4222 > A Hot Rod client should be able to configure the same properties with hotrod-client.properties file as the programatic API supports > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6438 > URL: https://issues.jboss.org/browse/ISPN-6438 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 9.0.0.Final > > > If a HotRod client is initialized by a hotrod-client.properties file and the RemoteCacheManager() constructor it should be possible to all possible properties. > The properties for > - SSL > - FILE_STORE * > - TRUST_STORE * > are not available with this configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6476) Integration test modules shouldn't change the failsafe plugin's lifecycle

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6476: ---------------------------------- Summary: Integration test modules shouldn't change the failsafe plugin's lifecycle Key: ISPN-6476 URL: https://issues.jboss.org/browse/ISPN-6476 Project: Infinispan Issue Type: Bug Components: Build process Affects Versions: 8.2.1.Final Reporter: Dan Berindei Fix For: 9.0.0.Alpha1 Many of our integration tests modules run the {{integration-test}} and {{verify}} goals of {{maven-failsafe-plugin}} together, sometimes specifying a lifecycle phase, sometimes not. This shouldn't be necessary, because failsafe runs both goals, it just binds them to different phases. On the contrary, running both goals in the same phase can fail the build too early, skipping any executions bound to the {{post-integration-test}} phase. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6177) Add ability to pre-register protobuf schema definitions via config

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6177?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-6177: --------------------------------------- The DUP approach could also be used for deploying scripts. > Add ability to pre-register protobuf schema definitions via config > ------------------------------------------------------------------ > > Key: ISPN-6177 > URL: https://issues.jboss.org/browse/ISPN-6177 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > > The global config should name some *.proto files (from disk or CP resources) to be registered with the ProtobufMetadataManager on startup. > This could probably use org.jboss.as.server.deployment.DeploymentUnitProcessor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6475) Remove the async log4j2 appender in the test configurations

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6475?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6475: ------------------------------------ For now we've only noticed the OOMEs in the build with TRACE logging enabled, because there is another factor involved: {{UnitTestTestNGListener}} registers a {{UncaughtExceptionHandler}} that logs the stacks of all the threads when it handles an OOME. The ISPN-6364 fix removes this thread dump on OOME, so it should also fix this issue. But it's the async appender doesn't improve things that much, so we should still remove it for extra safety. > Remove the async log4j2 appender in the test configurations > ----------------------------------------------------------- > > Key: ISPN-6475 > URL: https://issues.jboss.org/browse/ISPN-6475 > Project: Infinispan > Issue Type: Task > Components: Build process, Test Suite - Server > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1 > > > {{ClientEventsOOMTest}} started generating {{OutOfMemoryError}} s again, and they are hanging the build because of LOG4J2-1361. > We should remove the async appender, at least until LOG4J2-1361 is fixed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6475) Remove the async log4j2 appender in the test configurations

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6475?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6475: ------------------------------- Description: {{ClientEventsOOMTest}} started generating {{OutOfMemoryError}} s again, and they are hanging the build because of LOG4J2-1361. We should remove the async appender, at least until LOG4J2-1361 is fixed. was: {{ClientEventsOOMTest}} started generating {{OutOfMemoryError}}s again, and they are hanging the build because of LOG4J2-1361. We should remove the async appender, at least until LOG4J2-1361 is fixed. > Remove the async log4j2 appender in the test configurations > ----------------------------------------------------------- > > Key: ISPN-6475 > URL: https://issues.jboss.org/browse/ISPN-6475 > Project: Infinispan > Issue Type: Task > Components: Build process, Test Suite - Server > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1 > > > {{ClientEventsOOMTest}} started generating {{OutOfMemoryError}} s again, and they are hanging the build because of LOG4J2-1361. > We should remove the async appender, at least until LOG4J2-1361 is fixed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6475) Remove the async log4j2 appender in the test configurations

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6475?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6475: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4221 > Remove the async log4j2 appender in the test configurations > ----------------------------------------------------------- > > Key: ISPN-6475 > URL: https://issues.jboss.org/browse/ISPN-6475 > Project: Infinispan > Issue Type: Task > Components: Build process, Test Suite - Server > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1 > > > {{ClientEventsOOMTest}} started generating {{OutOfMemoryError}}s again, and they are hanging the build because of LOG4J2-1361. > We should remove the async appender, at least until LOG4J2-1361 is fixed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 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