[JBoss JIRA] (WFLY-8760) get method of ModuleClassLoaderLocator requires createClassLoader permission
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-8760?page=com.atlassian.jira.plugin.... ]
Lin Gao reassigned WFLY-8760:
-----------------------------
Assignee: Lin Gao (was: Darran Lofthouse)
> get method of ModuleClassLoaderLocator requires createClassLoader permission
> ----------------------------------------------------------------------------
>
> Key: WFLY-8760
> URL: https://issues.jboss.org/browse/WFLY-8760
> Project: WildFly
…
[View More]> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Lin Gao
> Priority: Critical
>
> There is missing doPriviliged block in ModuleClassLoaderLocator. Fix of WFLY-7412 for ModuleClassLoaderLocator introduces new CombinedClassLoader innner class which extends SecureClassLoader. Initialization of this class needs to createClassLoader RuntimePermission.
> That means:
> * All deployment which uses API which internally uses ModuleClassLoaderLocator needs createClassLoader RuntimePermission (which is new in EAP 7.1, the same deployments in EAP 7.0 does not need this permission)
> ** i.e. getMappingContext(String mappingType) in org.jboss.security.plugins.mapping.JBossMappingManager works internally with ModuleClassLoaderLocator.
> * setting createClassLoader RuntimePermission for deployment can be dangerous and it should probably use own permission
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[View Less]
7 years, 10 months
[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late
by John Ament (JIRA)
[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ]
John Ament commented on WFLY-8488:
----------------------------------
[~rhusar] ping? :-)
> Usage of JGroups JDBC_PING attempts to delete row too late
> ----------------------------------------------------------
>
> Key: WFLY-8488
> URL: https://issues.jboss.org/browse/WFLY-8488
> Project: WildFly
> Issue Type: Bug
> …
[View More]Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: John Ament
> Assignee: Paul Ferraro
>
> I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down.
> In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[View Less]
7 years, 10 months
[JBoss JIRA] (WFCORE-2895) Save memory in RuntimeCapability ServiceName creation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2895:
-------------------------------------
Summary: Save memory in RuntimeCapability ServiceName creation (was: Save memory in dynamic RuntimeCapability ServiceName creation)
> Save memory in RuntimeCapability ServiceName creation
> -----------------------------------------------------
>
> Key: WFCORE-2895
> URL: https://issues.…
[View More]jboss.org/browse/WFCORE-2895
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates its ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
> Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[View Less]
7 years, 10 months
[JBoss JIRA] (WFCORE-2895) Save memory in dynamic RuntimeCapability ServiceName creation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2895:
-------------------------------------
Description:
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates its ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
Also RuntimeCapability should not create a ServiceName if the cap has …
[View More]no serviceValueType.
was:
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType.
> Save memory in dynamic RuntimeCapability ServiceName creation
> -------------------------------------------------------------
>
> Key: WFCORE-2895
> URL: https://issues.jboss.org/browse/WFCORE-2895
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates its ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
> Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[View Less]
7 years, 10 months
[JBoss JIRA] (WFCORE-2895) Save memory in dynamic RuntimeCapability ServiceName creation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2895:
-------------------------------------
Description:
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
Also RuntimeCapability should not create a ServiceName if the cap has …
[View More]no serviceValueType.
was:
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
Also RuntimeCapability should not create a ServiceName even if the cap has no serviceValueType.
> Save memory in dynamic RuntimeCapability ServiceName creation
> -------------------------------------------------------------
>
> Key: WFCORE-2895
> URL: https://issues.jboss.org/browse/WFCORE-2895
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated.
> Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[View Less]
7 years, 10 months