[JBoss JIRA] (WFLY-10380) ThreadPoolExecutor leak under SM due to lack of privileged block
by David Lloyd (JIRA)
David Lloyd created WFLY-10380:
----------------------------------
Summary: ThreadPoolExecutor leak under SM due to lack of privileged block
Key: WFLY-10380
URL: https://issues.jboss.org/browse/WFLY-10380
Project: WildFly
Issue Type: Bug
Reporter: David Lloyd
Priority: Critical
Still researching the source of these leaks.
The way the leak happens is, a {{java.util.concurrent.ThreadPoolExecutor}} is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the {{modifyThread}} {{RuntimePermission}}, and the thread pool never shuts down.
We need to identify the points where TPEs are being constructed without controlled privileges.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10379) Simplify the build configuration of the release identifying info
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-10379:
---------------------------------------
Summary: Simplify the build configuration of the release identifying info
Key: WFLY-10379
URL: https://issues.jboss.org/browse/WFLY-10379
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The build currently produces 8 different installations, 2 x 2 x 2, with the factors being full vs servlet, fat vs skinny and legacy build vs galleon. Another factor also is WF vs EAP once the WF code is branched for EAP.
Currently there are some properties and logic related to "product identification" scattered around, which is a pretty unmanageable now. This task is to set the properties in the root pom (where they can easily be updated for later releases or EAP) and then references them elsewhere.
This task is really about a particular subset of things the relate to product.conf and the org.jboss.as.product:<productslot> module. I expect similar things can be done for other strings, but that's not in scope.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-1759) add-user.sh does not return the secret value in non-interactive mode.
by Petros Petrou (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1759?page=com.atlassian.jira.plugi... ]
Petros Petrou closed WFCORE-1759.
---------------------------------
Tested the issue in EAP 7.1
> add-user.sh does not return the secret value in non-interactive mode.
> ---------------------------------------------------------------------
>
> Key: WFCORE-1759
> URL: https://issues.jboss.org/browse/WFCORE-1759
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Petros Petrou
> Assignee: Ivo Hrádek
> Priority: Minor
> Fix For: 3.0.0.Alpha8
>
>
> Running add-user.sh in non-interactive mode does not return the secret value of the password. It would be a useful feature when automating user creation using platform build software.
> Non-Interactive Mode
> =============
> add-user.sh --user domainuser --password welcome1!
> Added user 'domainuser' to file '\opt\wildfly-10.0.0\standalone\configuration\mgmt-users.properties'
> Added user 'domainuser' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties'
> Press any key to continue . . .
> Interactive Mode
> =============
> What type of user do you wish to add?
> a) Management User (mgmt-users.properties)
> b) Application User (application-users.properties)
> (a): a
> Enter the details of the new user to add.
> Using realm 'ManagementRealm' as discovered from the existing property files.
> Username : ppetrou
> Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
> - The password should be different from the username
> - The password should not be one of the following restricted values {root, admin, administrator}
> - The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
> Password :
> Re-enter Password :
> What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]:
> About to add user 'ppetrou' for realm 'ManagementRealm'
> Is this correct yes/no? yes
> Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-users.properties'
> Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties'
> Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-groups.properties'
> Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-groups.properties'
> Is this new user going to be used for one AS process to connect to another AS process?
> e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
> yes/no? yes
> To represent the user add the following to the server-identities definition <secret value="d2VsY29tZTEh" />
> Press any key to continue . . .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10373) Standard undertow subsystem config should declare the default-[server|virtual-host|servlet-container|security-domain] attributes
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-10373?page=com.atlassian.jira.plugin... ]
Jan Stourac commented on WFLY-10373:
------------------------------------
I guess this is partly related also with WFLY-8538, correct? I'll add it to the 'related' jiras. Feel free to remove if that is not the case.
Also, I think this is a candidate for RFE?
> Standard undertow subsystem config should declare the default-[server|virtual-host|servlet-container|security-domain] attributes
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10373
> URL: https://issues.jboss.org/browse/WFLY-10373
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> The various default-xxx attributes on root undertow subsystem element if not set have default values that map to the standard child elements in the config. The problem with relying on those defaults and not specifying the values is their usage becomes "black magic" and the fact that things will fail if the child elements are removed or renamed is lost.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months