August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10858) Agroal subsystem should provide configurable application type RBAC constraints

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10858?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10858: --------------------------------------- Assignee: Brian Stansberry (was: Jason Greene) I'll do initial work on this although I won't have time to write tests. > Agroal subsystem should provide configurable application type RBAC constraints > ------------------------------------------------------------------------------ > > Key: WFLY-10858 > URL: https://issues.jboss.org/browse/WFLY-10858 > Project: WildFly > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 14.0.0.CR1 > > > We need to add RBAC application type constraints for the agroal resources so admins in the Deployer RBAC role can be allowed to administer them. Now they cannot which is different from the IJ-based subsystem. See for example https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10858) Agroal subsystem should provide configurable application type RBAC constraints

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10858: --------------------------------------- Summary: Agroal subsystem should provide configurable application type RBAC constraints Key: WFLY-10858 URL: https://issues.jboss.org/browse/WFLY-10858 Project: WildFly Issue Type: Bug Reporter: Brian Stansberry Assignee: Jason Greene Priority: Blocker Fix For: 14.0.0.CR1 We need to add RBAC application type constraints for the agroal resources so admins in the Deployer RBAC role can be allowed to administer them. Now they cannot which is different from the IJ-based subsystem. See for example https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10857) Agroal subsystem should not expose runtime attributes and operations in profile resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10857?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10857: ------------------------------------ Priority: Blocker (was: Major) > Agroal subsystem should not expose runtime attributes and operations in profile resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-10857 > URL: https://issues.jboss.org/browse/WFLY-10857 > Project: WildFly > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 14.0.0.CR1 > > > Items 2, 3, 4 in https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10857) Agroal subsystem should not expose runtime attributes and operations in profile resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10857?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10857: ------------------------------------ Fix Version/s: 14.0.0.CR1 > Agroal subsystem should not expose runtime attributes and operations in profile resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-10857 > URL: https://issues.jboss.org/browse/WFLY-10857 > Project: WildFly > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 14.0.0.CR1 > > > Items 2, 3, 4 in https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10857) Agroal subsystem should not expose runtime attributes and operations in profile resources

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10857: --------------------------------------- Summary: Agroal subsystem should not expose runtime attributes and operations in profile resources Key: WFLY-10857 URL: https://issues.jboss.org/browse/WFLY-10857 Project: WildFly Issue Type: Bug Reporter: Brian Stansberry Assignee: Brian Stansberry Items 2, 3, 4 in https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3962: ------------------------------------------ [~jamezp] Right. One way or the other that's what we'd have to do in scripts as well. Or something imaginative that's probably just as complex. I'm not saying this is trivial. And domain servers add another scenario to the problem and thus add to scope. But it doesn't multiply scope or add some fundamentally different problem. > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Management, Modules, Scripts > Affects Versions: 6.0.0.Alpha3 > Reporter: Matej Novotny > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14 > > As per request, copying MODULES-372 to WFCORE as well. > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Clebert Suconic commented on WFWIP-90: -------------------------------------- [~mnovak] so, not a regression! We have to fix it.. but we can do it after migration! > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3962: --------------------------------------- [~brian.stansberry] Can't different JVM's be defined for servers? So the HC could be running on Java 8 while a server is running on Java 11. We'd have to execute a new process and gather server information from it some how when we generate the launch commands. > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Management, Modules, Scripts > Affects Versions: 6.0.0.Alpha3 > Reporter: Matej Novotny > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14 > > As per request, copying MODULES-372 to WFCORE as well. > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10845) WildFly13 Infinispan 9.2 Query

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10845?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10845: --------------------------------------- Component/s: Clustering Assignee: Paul Ferraro (was: Jason Greene) > WildFly13 Infinispan 9.2 Query > ------------------------------ > > Key: WFLY-10845 > URL: https://issues.jboss.org/browse/WFLY-10845 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Majid Mostafavi > Assignee: Paul Ferraro > > standalone.xml > {color:#14892c}<cache-container name="gridCache" default-cache="default" module="org.infinispan.query:ispn-9.2"> > <local-cache name="default"> > <locking isolation="REPEATABLE_READ"/> > <transaction locking="OPTIMISTIC" mode="FULL_XA"/> > <file-store passivation="true" purge="false"/> > </local-cache> > </cache-container>{color} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3962: ------------------------------------------ {quote} For domain it would be a manual process anyway. While we could detect Java 9+ for the HC and DC we can't for the servers. {quote} I think our ability to do detection for a domain server is superior to anything we could do in the scripts for the PC / HC. The Java code running in the HC can be more flexible and powerful and platform independent than script stuff. > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Management, Modules, Scripts > Affects Versions: 6.0.0.Alpha3 > Reporter: Matej Novotny > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14 > > As per request, copying MODULES-372 to WFCORE as well. > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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

2008

2007

2006

jboss-jira August 2018