January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4211) MBean implementation lifecycle methods in MSC threads

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4211?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4211: ------------------------------------- Affects Version/s: 9.0.0.Alpha1 > MBean implementation lifecycle methods in MSC threads > ----------------------------------------------------- > > Key: WFLY-4211 > URL: https://issues.jboss.org/browse/WFLY-4211 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 9.0.0.Alpha1 > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Beta1 > > > MBean lifecycle methods should not be invoked from MSC threads, the implementation of these may block the thread, for instance due to a JNDI bind. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4211) MBean implementation lifecycle methods in MSC threads

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4211?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4211: ------------------------------------- Fix Version/s: 9.0.0.Beta1 > MBean implementation lifecycle methods in MSC threads > ----------------------------------------------------- > > Key: WFLY-4211 > URL: https://issues.jboss.org/browse/WFLY-4211 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 9.0.0.Alpha1 > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Beta1 > > > MBean lifecycle methods should not be invoked from MSC threads, the implementation of these may block the thread, for instance due to a JNDI bind. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4216) when ever i deploy my ear file, i get this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4216?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on WFLY-4216: ------------------------------------------ Also this JIRA miss affected version. > when ever i deploy my ear file, i get this error > ------------------------------------------------ > > Key: WFLY-4216 > URL: https://issues.jboss.org/browse/WFLY-4216 > Project: WildFly > Issue Type: Bug > Reporter: oma sung > Assignee: Bartosz Baranowski > Priority: Optional > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4216) when ever i deploy my ear file, i get this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4216?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4216: ------------------------------------- Priority: Optional (was: Major) > when ever i deploy my ear file, i get this error > ------------------------------------------------ > > Key: WFLY-4216 > URL: https://issues.jboss.org/browse/WFLY-4216 > Project: WildFly > Issue Type: Bug > Reporter: oma sung > Assignee: Bartosz Baranowski > Priority: Optional > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4216) when ever i deploy my ear file, i get this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4216?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on WFLY-4216: ------------------------------------------ Altering Priority for the time being. > when ever i deploy my ear file, i get this error > ------------------------------------------------ > > Key: WFLY-4216 > URL: https://issues.jboss.org/browse/WFLY-4216 > Project: WildFly > Issue Type: Bug > Reporter: oma sung > Assignee: Bartosz Baranowski > Priority: Optional > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4216) when ever i deploy my ear file, i get this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4216?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on WFLY-4216: ------------------------------------------ [~omasung] - what error? Also, this JIRA has been set as as "Feature Request". Please provide error message and reproducer ear/project. > when ever i deploy my ear file, i get this error > ------------------------------------------------ > > Key: WFLY-4216 > URL: https://issues.jboss.org/browse/WFLY-4216 > Project: WildFly > Issue Type: Feature Request > Reporter: oma sung > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4216) when ever i deploy my ear file, i get this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4216?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4216: ------------------------------------- Issue Type: Bug (was: Feature Request) > when ever i deploy my ear file, i get this error > ------------------------------------------------ > > Key: WFLY-4216 > URL: https://issues.jboss.org/browse/WFLY-4216 > Project: WildFly > Issue Type: Bug > Reporter: oma sung > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4216) when ever i deploy my ear file, i get this error

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4216?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-4216: ---------------------------------------- Assignee: Bartosz Baranowski (was: Jason Greene) > when ever i deploy my ear file, i get this error > ------------------------------------------------ > > Key: WFLY-4216 > URL: https://issues.jboss.org/browse/WFLY-4216 > Project: WildFly > Issue Type: Feature Request > Reporter: oma sung > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-490) ModelControllerImpl uses SecureRandom per request

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/WFCORE-490?page=com.atlassian.jira.plugin... ] James Livingston edited comment on WFCORE-490 at 1/13/15 11:45 PM: ------------------------------------------------------------------- The second one (line 401) is per boot of the server, but the first (line 337) is per request in internalExecute(). It could occur more than once per request if the attempt at putting it in the activeOperations map fails due to there already being an operation with the same id. With JDK 7+, java.util.Random instances are guaranteed to be thread safe (albeit potentially slower under contention), so a single random instance could be shared between threads as long as the operation ID didn't have to be a secure random number. Any loss of performance from concurrent access would be outweighed by the fact it no longer has to gather entropy from the OS to initialise the SecureRandom object. was (Author: jameslivingston): The second one (line 401) is per boot of the server, but the first (line 337) is per request in internalExecute(). It could occur more than once per request if the attempt at putting it in the activeOperations map fails due to there already being an operation with the same id. > ModelControllerImpl uses SecureRandom per request > ------------------------------------------------- > > Key: WFCORE-490 > URL: https://issues.jboss.org/browse/WFCORE-490 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: James Livingston > Assignee: Brian Stansberry > > https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... and https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... create a new SecureRandom which is used to seed a normal Random, and that is thrown away after one use. That causes it to use entropy from the OS pool, which if done at a sufficiently high rate on servers can cause stalls. > I can't think of any reason why the operation ID would need to be a secure random number rather than a normal one, so unless there is one it may be better to use a normal Random and not drain the entropy pool. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-490) ModelControllerImpl uses SecureRandom per request

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/WFCORE-490?page=com.atlassian.jira.plugin... ] James Livingston commented on WFCORE-490: ----------------------------------------- The second one (line 401) is per boot of the server, but the first (line 337) is per request in internalExecute(). It could occur more than once per request if the attempt at putting it in the activeOperations map fails due to there already being an operation with the same id. > ModelControllerImpl uses SecureRandom per request > ------------------------------------------------- > > Key: WFCORE-490 > URL: https://issues.jboss.org/browse/WFCORE-490 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: James Livingston > Assignee: Brian Stansberry > > https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... and https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... create a new SecureRandom which is used to seed a normal Random, and that is thrown away after one use. That causes it to use entropy from the OS pool, which if done at a sufficiently high rate on servers can cause stalls. > I can't think of any reason why the operation ID would need to be a secure random number rather than a normal one, so unless there is one it may be better to use a normal Random and not drain the entropy pool. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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 January 2015