April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5529) Clustering Quickstarts Tracker

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5529?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5529: --------------------------------- Description: Tracker for clustering quickstarts. There are bunch of areas that could use a quickstart; intentionally no concrete Jiras for these yet: * Externalizers + General session replication/failover * CommandDispatcher * Cross-site replication * Group membership * JGroups channel injection (community-only) * Infinispan cache injection (community-only) was:Tracker for clustering quickstarts. > Clustering Quickstarts Tracker > ------------------------------ > > Key: WFLY-5529 > URL: https://issues.jboss.org/browse/WFLY-5529 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tracker for clustering quickstarts. > There are bunch of areas that could use a quickstart; intentionally no concrete Jiras for these yet: > * Externalizers + General session replication/failover > * CommandDispatcher > * Cross-site replication > * Group membership > * JGroups channel injection (community-only) > * Infinispan cache injection (community-only) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2643) Elytron Audit Logging does not support log file rotation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2643?page=com.atlassian.jira.plugi... ] Jan Kalina moved JBEAP-10219 to WFCORE-2643: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2643 (was: JBEAP-10219) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.DR14) > Elytron Audit Logging does not support log file rotation > -------------------------------------------------------- > > Key: WFCORE-2643 > URL: https://issues.jboss.org/browse/WFCORE-2643 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Labels: audit-logging, eap7.1-rfe-blocker, rotation > > It is not possible to rotate (= rename current log file and start logging into a new one) Elytron Audit log files. It cannot be set to use the log rotation neither based on the file size (e.g. once the file size outreaches 100 MB) nor based on a time period (e.g. rotate create a new file every Sunday at midnight). > Inability to set the log rotation could lead to huge log files. Then it would be really difficult to read such files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8541) Create SingletonService quickstart

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8541?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved JBEAP-10218 to WFLY-8541: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8541 (was: JBEAP-10218) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering Quickstarts (was: Clustering) (was: Quickstarts) > Create SingletonService quickstart > ---------------------------------- > > Key: WFLY-8541 > URL: https://issues.jboss.org/browse/WFLY-8541 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Create a useful quickstart that does something other than using EE lookup from MSC to demonstrate org.wildfly.clustering.singleton.SingletonService. See [1] for more info. > [1] https://issues.jboss.org/browse/JBEAP-4004?focusedCommentId=13184169&page... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2535) ModuleResourceRootPathsTestCase fails with security manager in WF core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2535?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2535: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2276 (was: https://github.com/wildfly/wildfly-core/pull/2283) > ModuleResourceRootPathsTestCase fails with security manager in WF core > ---------------------------------------------------------------------- > > Key: WFCORE-2535 > URL: https://issues.jboss.org/browse/WFCORE-2535 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Test Suite > Reporter: Jan Tymel > Assignee: ehsavoie Hugonnet > > *org.jboss.as.test.integration.management.cli.modules.ModuleResourceRootPathsTestCase#testModules* > {{cd testsuite/standalone/}} > {{mvn test -Dtest=ModuleResourceRootPathsTestCase -Dsecurity.manager -DtestLogToFile=false}} > {code} > 13:26:00,583 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."test-archive.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."test-archive.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "test-archive.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:785) > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "jboss.bind.address" "read")" in code source "(vfs:/content/test-archive.war <no signer certificates>)" of "ModuleClassLoader for Module "deployment.test-archive.war" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469) > at java.lang.System.getProperty(System.java:443) > at java.lang.System.getProperty(System.java:427) > at org.jboss.as.test.shared.TestSuiteEnvironment.getSystemProperty(TestSuiteEnvironment.java:50) > at org.jboss.as.test.shared.TestSuiteEnvironment.getHttpAddress(TestSuiteEnvironment.java:173) > at org.wildfly.test.undertow.UndertowServiceActivator.getAddress(UndertowServiceActivator.java:100) > at org.wildfly.test.undertow.UndertowServiceActivator.activate(UndertowServiceActivator.java:66) > at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:91) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2406) Credential store alias with upper-case letters can't be added when Java assertions are enabled

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2406?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-2406. -------------------------------------- Fix Version/s: 3.0.0.Beta14 Resolution: Done I think this is done; please reopen if I am wrong. > Credential store alias with upper-case letters can't be added when Java assertions are enabled > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-2406 > URL: https://issues.jboss.org/browse/WFCORE-2406 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: ehsavoie Hugonnet > Priority: Critical > Fix For: 3.0.0.Beta14 > > > When Java assertions are enable then adding credential store entry (alias) with upper case letters fails with assertion error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-105) Option to have LoggingToolsProcessor to not use javax.annotation.Generated

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-105?page=com.atlassian.jira.plugi... ] James Perkins commented on LOGTOOL-105: --------------------------------------- The original PR has a conflict and I went with a slightly different approach. The new PR, https://github.com/jboss-logging/jboss-logging-tools/pull/60, attempts to figure out which annotation it can use and if neither can be used then no annotation will be added to the generated source. > Option to have LoggingToolsProcessor to not use javax.annotation.Generated > -------------------------------------------------------------------------- > > Key: LOGTOOL-105 > URL: https://issues.jboss.org/browse/LOGTOOL-105 > Project: Log Tool > Issue Type: Feature Request > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 2.1.0.Alpha2 > > > To allow projects using the JBoss Logging annotation processor to test latest Java 9 Jigsaw builds, we need to be able to workaround issue > https://bugs.openjdk.java.net/browse/JDK-8152842 > I'm introducing an annotation processor option which will cause the generated source code to "forget" to mark the generated code with {{javax.annotation.Generated}}. > -{{AskipGeneratedAnnotation=true}} > The JMH annotation processor followed a similar path: > https://bugs.openjdk.java.net/browse/CODETOOLS-7901643 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-105) Option to have LoggingToolsProcessor to not use javax.annotation.Generated

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-105?page=com.atlassian.jira.plugi... ] James Perkins updated LOGTOOL-105: ---------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logging-tools/pull/47, https://github.com/jboss-logging/jboss-logging-tools/pull/60 (was: https://github.com/jboss-logging/jboss-logging-tools/pull/47) > Option to have LoggingToolsProcessor to not use javax.annotation.Generated > -------------------------------------------------------------------------- > > Key: LOGTOOL-105 > URL: https://issues.jboss.org/browse/LOGTOOL-105 > Project: Log Tool > Issue Type: Feature Request > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 2.1.0.Alpha2 > > > To allow projects using the JBoss Logging annotation processor to test latest Java 9 Jigsaw builds, we need to be able to workaround issue > https://bugs.openjdk.java.net/browse/JDK-8152842 > I'm introducing an annotation processor option which will cause the generated source code to "forget" to mark the generated code with {{javax.annotation.Generated}}. > -{{AskipGeneratedAnnotation=true}} > The JMH annotation processor followed a similar path: > https://bugs.openjdk.java.net/browse/CODETOOLS-7901643 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1067) Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1067: ------------------------------------- Summary: Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML Key: ELY-1067 URL: https://issues.jboss.org/browse/ELY-1067 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta36 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1067) Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1067?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1067: ---------------------------------- Priority: Blocker (was: Major) > Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML > -------------------------------------------------------------------------------------------------- > > Key: ELY-1067 > URL: https://issues.jboss.org/browse/ELY-1067 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta36 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1066) Add a GSSCredential CredentialSource

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1066: ------------------------------------- Summary: Add a GSSCredential CredentialSource Key: ELY-1066 URL: https://issues.jboss.org/browse/ELY-1066 Project: WildFly Elytron Issue Type: Enhancement Components: Credentials Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 1.1.0.Beta36 Initially this should be minimal / no configuration to make a GSSCrdential available if the local user has a Kerberos ticket - at a later point we can review adding additional config such as client keytabs etc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 April 2017