July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9945) ServerNG: Test Suite

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9945?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9945: ---------------------------------- Status: Open (was: New) > ServerNG: Test Suite > -------------------- > > Key: ISPN-9945 > URL: https://issues.jboss.org/browse/ISPN-9945 > Project: Infinispan > Issue Type: Sub-task > Components: Server, Test Suite - Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > Implement a test harness with the following objectives: > * minimize server start/stops by reusing the same servers multiple times > * simplify development and execution of the tests without requiring complex setups -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10416) ServerNG: KeyCloak authentication/authorization

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10416?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10416: ----------------------------------- Status: Open (was: New) > ServerNG: KeyCloak authentication/authorization > ----------------------------------------------- > > Key: ISPN-10416 > URL: https://issues.jboss.org/browse/ISPN-10416 > Project: Infinispan > Issue Type: Sub-task > Components: Security, Server > Affects Versions: 10.0.0.Beta4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5, 10.0.0.Final > > > Use the Elytron trust realm and the oauth2 introspection to support OAUTHBEARER in Hot Rod and BEARER in REST -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10416) ServerNG: KeyCloak authentication/authorization

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10416: -------------------------------------- Summary: ServerNG: KeyCloak authentication/authorization Key: ISPN-10416 URL: https://issues.jboss.org/browse/ISPN-10416 Project: Infinispan Issue Type: Sub-task Components: Security, Server Affects Versions: 10.0.0.Beta4 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Beta5, 10.0.0.Final Use the Elytron trust realm and the oauth2 introspection to support OAUTHBEARER in Hot Rod and BEARER in REST -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10415) Remove standalone-ha.xml references

by Gustavo Lira e Silva (Jira)

[ https://issues.jboss.org/browse/ISPN-10415?page=com.atlassian.jira.plugin... ] Gustavo Lira e Silva updated ISPN-10415: ---------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7158, https://github.com/infinispan/infinispan/pull/7159 > Remove standalone-ha.xml references > ----------------------------------- > > Key: ISPN-10415 > URL: https://issues.jboss.org/browse/ISPN-10415 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > > standalone-ha.xml was renamed in a less EAP-centric manner, now clustered.xml is being used. > All references for standalone-ha.xml should be update to standalone.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10415) Remove standalone-ha.xml references

by Gustavo Lira e Silva (Jira)

Gustavo Lira e Silva created ISPN-10415: ------------------------------------------- Summary: Remove standalone-ha.xml references Key: ISPN-10415 URL: https://issues.jboss.org/browse/ISPN-10415 Project: Infinispan Issue Type: Bug Components: Documentation-Core Reporter: Gustavo Lira e Silva Assignee: Gustavo Lira e Silva standalone-ha.xml was renamed in a less EAP-centric manner, now clustered.xml is being used. All references for standalone-ha.xml should be update to standalone.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10352) Externalize all code and config samples in docs

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10352?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10352: ------------------------------- Affects Version/s: (was: 10.0.0.Beta4) > Externalize all code and config samples in docs > ----------------------------------------------- > > Key: ISPN-10352 > URL: https://issues.jboss.org/browse/ISPN-10352 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Optional > > All code samples in docs should be run and tested at build time. Externalize all code samples to a separate directory and include them. Do the same for all config samples in any format, yaml, xml, and so on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10411) Domain controller console shows blank page

by Juan Antonio Farré Basurte (Jira)

[ https://issues.jboss.org/browse/ISPN-10411?page=com.atlassian.jira.plugin... ] Juan Antonio Farré Basurte commented on ISPN-10411: --------------------------------------------------- I think I found the problem. When I specify jboss.node.name, in some calls, its value is used both for the host and for the server names. For example, suppose I have: <host ... name="myHost"> <server name="myServer"> <property name="jboss.node.name" value="myNode"/> The failing request specifies host: myNode and server: myNode. If I remove the property jboss.node.name, then the request is host: myHost and server: myServer and it works just fine. This seems to me a bug using jboss.node.name where it shouldn't. This happens in Infinispan 9.4.15, but not, for example in Keycloak 6.0.1. Anyway, it would be nice to get the console rendered with a suitable error, so I won't close this, just lower the priority. > Domain controller console shows blank page > ------------------------------------------ > > Key: ISPN-10411 > URL: https://issues.jboss.org/browse/ISPN-10411 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 9.4.15.Final > Environment: CentOs 7.6.1810 (Core) X86_64 > OpenJDK 1.8.0.212.b04 > Reporter: Juan Antonio Farré Basurte > Priority: Major > Labels: console, infinispan, web-console, wildfly > Attachments: infinispan.PNG, infinispan.PNG > > > I have a regular installation of Infinispan in domain mode, with a master node and a slave node in a separate machine. > When I connect through my browser to WildFly console at http://myHost:9990/console I am asked to log in. > After succesful login, I get redirected to: > http://localhost:9990/console/index.html#/containers > and nothing is rendered at all. The page is totally blank. > With the browser developer tools, I can see many POSTs succeeding, but later some of them fail with error 500 and the following failure description in the payload: > {code:json} > { > "outcome" : "failed", > "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"infinispan-HS2-1\"),\n (\"server\" => \"infinispan-HS2-1\"),\n (\"subsystem\" => \"datagrid-infinispan\"),\n (\"cache-container\" => \"clustered\")\n]", > "rolled-back" : true > } > {code} > This is with Firefox 68.0, Chrome 75.0 and IE 11, so it does not seem to be browser related. > > More information: > I don't see any error message in the logs. > Appart of this, the infinispan server is working correctly. > I also have a very similar installation of Keycloak 6.0.1 and WildFly console works perfectly. > Keycloak packages WildFly 16 and Infinispan, WildFly 14. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10411) Domain controller console shows blank page

by Juan Antonio Farré Basurte (Jira)

[ https://issues.jboss.org/browse/ISPN-10411?page=com.atlassian.jira.plugin... ] Juan Antonio Farré Basurte updated ISPN-10411: ---------------------------------------------- Priority: Minor (was: Major) > Domain controller console shows blank page > ------------------------------------------ > > Key: ISPN-10411 > URL: https://issues.jboss.org/browse/ISPN-10411 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 9.4.15.Final > Environment: CentOs 7.6.1810 (Core) X86_64 > OpenJDK 1.8.0.212.b04 > Reporter: Juan Antonio Farré Basurte > Priority: Minor > Labels: console, infinispan, web-console, wildfly > Attachments: infinispan.PNG, infinispan.PNG > > > I have a regular installation of Infinispan in domain mode, with a master node and a slave node in a separate machine. > When I connect through my browser to WildFly console at http://myHost:9990/console I am asked to log in. > After succesful login, I get redirected to: > http://localhost:9990/console/index.html#/containers > and nothing is rendered at all. The page is totally blank. > With the browser developer tools, I can see many POSTs succeeding, but later some of them fail with error 500 and the following failure description in the payload: > {code:json} > { > "outcome" : "failed", > "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"infinispan-HS2-1\"),\n (\"server\" => \"infinispan-HS2-1\"),\n (\"subsystem\" => \"datagrid-infinispan\"),\n (\"cache-container\" => \"clustered\")\n]", > "rolled-back" : true > } > {code} > This is with Firefox 68.0, Chrome 75.0 and IE 11, so it does not seem to be browser related. > > More information: > I don't see any error message in the logs. > Appart of this, the infinispan server is working correctly. > I also have a very similar installation of Keycloak 6.0.1 and WildFly console works perfectly. > Keycloak packages WildFly 16 and Infinispan, WildFly 14. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10413) os-maven-plugin not setting `os.detected.classifier` property on partial maven builds

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10413?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10413: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > os-maven-plugin not setting `os.detected.classifier` property on partial maven builds > ------------------------------------------------------------------------------------- > > Key: ISPN-10413 > URL: https://issues.jboss.org/browse/ISPN-10413 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.0.0.Beta4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta5 > > > When executing {{mvn clean install -am -pl core}} the commons module will fail because the property {{os.detected.classifier}} is not set by the {{os-maven-plugin}} resulting in a NPE being thrown by the {{proto-schema-compatibility}} maven plugin. > {code:java} > [ERROR] Failed to execute goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check (default) on project infinispan-commons: Execution default of goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check failed.: NullPointerException -> [Help 1] > {code} > The solution is to add the following to the parent pom: > {code:java} > <extensions> > <extension> > <groupId>kr.motd.maven</groupId> > <artifactId>os-maven-plugin</artifactId> > </extension> > </extensions> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10404) XStream 1.4.11.1

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10404?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10404: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > XStream 1.4.11.1 > ---------------- > > Key: ISPN-10404 > URL: https://issues.jboss.org/browse/ISPN-10404 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Affects Versions: 10.0.0.Beta4, 9.4.15.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5, 9.4.16.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2019