June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8912) org/wildfly/iiop/openjdk/csiv2/ElytronSASClientInterceptor using API removed from Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8912?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved JBEAP-11437 to WFLY-8912: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8912 (was: JBEAP-11437) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: IIOP Security (was: IIOP) (was: Security) > org/wildfly/iiop/openjdk/csiv2/ElytronSASClientInterceptor using API removed from Elytron > ----------------------------------------------------------------------------------------- > > Key: WFLY-8912 > URL: https://issues.jboss.org/browse/WFLY-8912 > Project: WildFly > Issue Type: Bug > Components: IIOP, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8912) org/wildfly/iiop/openjdk/csiv2/ElytronSASClientInterceptor using API removed from Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8912?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8912: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > org/wildfly/iiop/openjdk/csiv2/ElytronSASClientInterceptor using API removed from Elytron > ----------------------------------------------------------------------------------------- > > Key: WFLY-8912 > URL: https://issues.jboss.org/browse/WFLY-8912 > Project: WildFly > Issue Type: Bug > Components: IIOP, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-154: -------------------------------------- I've changed the priority to critical as this seems to be an issue on Windows. > Log rotations should be more resilient to failed rotations > ---------------------------------------------------------- > > Key: LOGMGR-154 > URL: https://issues.jboss.org/browse/LOGMGR-154 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Priority: Critical > Fix For: 2.0.7.Final, 2.1.0.Alpha2 > > > If a failure occurs while rotating a file the file handler will stop working. The file handler should instead report the failed rotation, but keep allowing messages to be written. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-154: --------------------------------- Fix Version/s: 2.0.7.Final 2.1.0.Alpha2 > Log rotations should be more resilient to failed rotations > ---------------------------------------------------------- > > Key: LOGMGR-154 > URL: https://issues.jboss.org/browse/LOGMGR-154 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Fix For: 2.0.7.Final, 2.1.0.Alpha2 > > > If a failure occurs while rotating a file the file handler will stop working. The file handler should instead report the failed rotation, but keep allowing messages to be written. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-154: --------------------------------- Priority: Critical (was: Major) > Log rotations should be more resilient to failed rotations > ---------------------------------------------------------- > > Key: LOGMGR-154 > URL: https://issues.jboss.org/browse/LOGMGR-154 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Priority: Critical > Fix For: 2.0.7.Final, 2.1.0.Alpha2 > > > If a failure occurs while rotating a file the file handler will stop working. The file handler should instead report the failed rotation, but keep allowing messages to be written. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2939) Disabled deployments in server group enabled after WAR is updated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2939?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-2939 at 6/8/17 11:16 AM: ------------------------------------------------------------------- I think the WFCORE-446 work introduced this, by updating the CLI to always send the 'enabled' param to the full-replace-deployment management op. It should only send it if the user input specifically determines a value; otherwise it should leave it undefined. If undefined the existing settings on the server-group=x/deployment=y resources should remain in place. was (Author: brian.stansberry): I think the WFCORE-446 work introduced this, by updating the CLI to always send the 'enabled' param to the full-replace-deployment. It should only send it if the user input specifically determines a value; otherwise it should leave it undefined. If undefined the existing settings on the server-group=x/deployment=y resources should remain in place. > Disabled deployments in server group enabled after WAR is updated > ----------------------------------------------------------------- > > Key: WFCORE-2939 > URL: https://issues.jboss.org/browse/WFCORE-2939 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Environment: Centos 7 > OpenJDK > Reporter: Matthew Casperson > > Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-154: -------------------------------------- >From the forum post: {quote} 2017-05-29 11:01:48 Commons Daemon procrun stderr initialized LogManager error of type OPEN_FAILURE: Unable to rotate log file java.nio.file.FileSystemException: C:\wildfly-9.0.2.Final\standalone\log\server.log -> C:\wildfly-9.0.2.Final\standalone\log\server.log.1: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:387) at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287) at java.nio.file.Files.move(Files.java:1395) {quote} > Log rotations should be more resilient to failed rotations > ---------------------------------------------------------- > > Key: LOGMGR-154 > URL: https://issues.jboss.org/browse/LOGMGR-154 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > > If a failure occurs while rotating a file the file handler will stop working. The file handler should instead report the failed rotation, but keep allowing messages to be written. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2939) Disabled deployments in server group enabled after WAR is updated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2939?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2939: ------------------------------------------ I think the WFCORE-446 work introduced this, by updating the CLI to always send the 'enabled' param to the full-replace-deployment. It should only send it if the user input specifically determines a value; otherwise it should leave it undefined. If undefined the existing settings on the server-group=x/deployment=y resources should remain in place. > Disabled deployments in server group enabled after WAR is updated > ----------------------------------------------------------------- > > Key: WFCORE-2939 > URL: https://issues.jboss.org/browse/WFCORE-2939 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Environment: Centos 7 > OpenJDK > Reporter: Matthew Casperson > > Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2939) Disabled deployments in server group enabled after WAR is updated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2939?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2939: ------------------------------------- Component/s: CLI > Disabled deployments in server group enabled after WAR is updated > ----------------------------------------------------------------- > > Key: WFCORE-2939 > URL: https://issues.jboss.org/browse/WFCORE-2939 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Environment: Centos 7 > OpenJDK > Reporter: Matthew Casperson > > Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2940) Elytron: Update test to be agnostic of modifiable realm identity iteration

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2940?page=com.atlassian.jira.plugi... ] David Lloyd moved WFLY-8911 to WFCORE-2940: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2940 (was: WFLY-8911) Component/s: Security (was: Security) Fix Version/s: 3.0.0.Beta26 (was: 11.0.0.Beta1) > Elytron: Update test to be agnostic of modifiable realm identity iteration > -------------------------------------------------------------------------- > > Key: WFCORE-2940 > URL: https://issues.jboss.org/browse/WFCORE-2940 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta26 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017