[jboss-jira] [JBoss JIRA] (WFLY-12081) (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain

Ondrej Kotek (Jira) issues at jboss.org
Wed May 15 08:24:00 EDT 2019


     [ https://issues.jboss.org/browse/WFLY-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Kotek updated WFLY-12081:
--------------------------------
    Description: 
After enabling JACC on {{undertow/application-security-domain=other}}, the server can get stuck when starting with Security Manager turned on. It stops responding and cannot be terminated by Ctrl-C.

After disabling JACC, or when starting without Security Manager, the server starts as expected.

This behaviour blocks customers that uses JACC with Security Manager.

  was:
After enabling JACC on {{undertow/application-security-domain=other}}, the server can get stuck when starting with Security Manager turned on.

After disabling JACC, or when starting without Security Manager, the server starts as expected.

This behaviour blocks customers that uses JACC with Security Manager.



> (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-12081
>                 URL: https://issues.jboss.org/browse/WFLY-12081
>             Project: WildFly
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 17.0.0.Beta1
>            Reporter: Ondrej Kotek
>            Assignee: Darran Lofthouse
>            Priority: Blocker
>
> After enabling JACC on {{undertow/application-security-domain=other}}, the server can get stuck when starting with Security Manager turned on. It stops responding and cannot be terminated by Ctrl-C.
> After disabling JACC, or when starting without Security Manager, the server starts as expected.
> This behaviour blocks customers that uses JACC with Security Manager.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list