April 2016 - infinispan-issues - Jboss List Archives

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

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6475: ---------------------------------- Summary: 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 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: Open (was: New) > 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-6177) Add ability to pre-register protobuf schema definitions via config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6177?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6177: -------------------------------- Description: 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. was: The global config should name some *.proto files (from disk or CP resources) to be registered with the ProtobufMetadataManager on startup. > 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-6457) Servers should disallow access to internal user caches over the wire when authorization is disabled

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6457?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6457: ------------------------------------- I think the point of disabling authorization is to allow everything. So why disable access to these caches? > Servers should disallow access to internal user caches over the wire when authorization is disabled > --------------------------------------------------------------------------------------------------- > > Key: ISPN-6457 > URL: https://issues.jboss.org/browse/ISPN-6457 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > The server protocols currently allow access to internal user caches (such as the script and schema caches) if authorization is disabled. We should instead not allow access. -- 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 Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6474?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-6474: ---------------------------------------- What's the actual problem that this creates? > 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-5699) Simplify entry wrapping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5699?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5699: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1324030 Bugzilla Update: Perform > Simplify entry wrapping > ----------------------- > > Key: ISPN-5699 > URL: https://issues.jboss.org/browse/ISPN-5699 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The entry wrapping should be more or less the same for all write commands. > Currently we have some optimizations to skip wrapping in some cases, in the first phase we should probably keep them: > * Non-repeatable reads don't store anything in the context if the value is null > * Replace and remove store a null entry in the context > * PutForExternalRead doesn't store anything in the context if the value is non-null -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6412) RESTReplicationIT fails

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6412?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6412: ------------------------------------ [~sebastian.laskawiec] I see {{RESTReplicationIT.setUp()}} adds the servers to the static {{RESTHelper.servers}} list, but {{RESTHelper.tearDown()}} doesn't clear the list, and this pattern is repeated in almost all the REST integration tests (except for {{RESTBasicSecurityIT}} and {{RESTDigestSecurityIT}}, which are ignored). I'm not sure how many servers we use in the REST integration tests, but could it be that the test is sometimes using the wrong server? > RESTReplicationIT fails > ----------------------- > > Key: ISPN-6412 > URL: https://issues.jboss.org/browse/ISPN-6412 > Project: Infinispan > Issue Type: Bug > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > http://ci.infinispan.org/viewLog.html?buildId=37653&tab=buildResultsDiv&b... -- 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)

Tristan Tarrant created ISPN-6474: ------------------------------------- Summary: 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.2.1.Final, 8.1.3.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-6473) Implement integration test for SASL EXTERNAL mech

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6473?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6473: ---------------------------------- Status: Open (was: New) > Implement integration test for SASL EXTERNAL mech > ------------------------------------------------- > > Key: ISPN-6473 > URL: https://issues.jboss.org/browse/ISPN-6473 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Implement IT test for SASL EXTERNAL mech -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6473) Implement integration test for SASL EXTERNAL mech

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6473?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6473: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4220 > Implement integration test for SASL EXTERNAL mech > ------------------------------------------------- > > Key: ISPN-6473 > URL: https://issues.jboss.org/browse/ISPN-6473 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Implement IT test for SASL EXTERNAL mech -- 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