May 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBWEB-300) High CPU in concurrent access to the JSSESupport keySizeCache map

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-300?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWEB-300: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1103018, https://bugzilla.redhat.com/show_bug.cgi?id=1103019 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1103018) > High CPU in concurrent access to the JSSESupport keySizeCache map > ----------------------------------------------------------------- > > Key: JBWEB-300 > URL: https://issues.jboss.org/browse/JBWEB-300 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.3.0.GA, JBossWeb-7.4.0.GA > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > The keySizeCache map in JSSESupport isn't protected from concurrent access and so can cause high CPU loops. The complete fix from the tomcat bug that had this map access synchronized wasn't used: > https://issues.apache.org/bugzilla/show_bug.cgi?id=47744 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-300) High CPU in concurrent access to the JSSESupport keySizeCache map

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-300?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWEB-300: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1103018 > High CPU in concurrent access to the JSSESupport keySizeCache map > ----------------------------------------------------------------- > > Key: JBWEB-300 > URL: https://issues.jboss.org/browse/JBWEB-300 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.3.0.GA, JBossWeb-7.4.0.GA > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > The keySizeCache map in JSSESupport isn't protected from concurrent access and so can cause high CPU loops. The complete fix from the tomcat bug that had this map access synchronized wasn't used: > https://issues.apache.org/bugzilla/show_bug.cgi?id=47744 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-300) High CPU in concurrent access to the JSSESupport keySizeCache map

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/JBWEB-300?page=com.atlassian.jira.plugin.... ] Aaron Ogburn commented on JBWEB-300: ------------------------------------ Synch added for thread safety: 7.3.x: r2431 7.4.x: r2432 > High CPU in concurrent access to the JSSESupport keySizeCache map > ----------------------------------------------------------------- > > Key: JBWEB-300 > URL: https://issues.jboss.org/browse/JBWEB-300 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.3.0.GA, JBossWeb-7.4.0.GA > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > The keySizeCache map in JSSESupport isn't protected from concurrent access and so can cause high CPU loops. The complete fix from the tomcat bug that had this map access synchronized wasn't used: > https://issues.apache.org/bugzilla/show_bug.cgi?id=47744 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-501) Propagation context is not set correctly when nodes are shared

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-501?page=com.atlassian.jira.plugin... ] Davide Sottara updated DROOLS-501: ---------------------------------- Summary: Propagation context is not set correctly when nodes are shared (was: jBPM Ruleflow groups ignore no-loops when nodes are shared) > Propagation context is not set correctly when nodes are shared > -------------------------------------------------------------- > > Key: DROOLS-501 > URL: https://issues.jboss.org/browse/DROOLS-501 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.CR1 > > > The following rules > {code} > package org.drools.compiler.loop > rule "Rule 1" > ruleflow-group "Start" > no-loop > when > $thing1 : String() > $thing2 : Integer() > then > System.out.println( 'At 1' ); > update( $thing2 ); > end > rule "Rule 2" > ruleflow-group "End" > no-loop > when > $thing1 : String() > $thing2 : Integer() > then > System.out.println( 'At 2' ); > update( $thing2 ); > end > {code} > cause an endless loop even if controlled by a jBPM process with two rule tasks -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-501) jBPM Ruleflow groups ignore no-loops when nodes are shared

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-501?page=com.atlassian.jira.plugin... ] Davide Sottara updated DROOLS-501: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > jBPM Ruleflow groups ignore no-loops when nodes are shared > ---------------------------------------------------------- > > Key: DROOLS-501 > URL: https://issues.jboss.org/browse/DROOLS-501 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.CR1 > > > The following rules > {code} > package org.drools.compiler.loop > rule "Rule 1" > ruleflow-group "Start" > no-loop > when > $thing1 : String() > $thing2 : Integer() > then > System.out.println( 'At 1' ); > update( $thing2 ); > end > rule "Rule 2" > ruleflow-group "End" > no-loop > when > $thing1 : String() > $thing2 : Integer() > then > System.out.println( 'At 2' ); > update( $thing2 ); > end > {code} > cause an endless loop even if controlled by a jBPM process with two rule tasks -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-300) High CPU in concurrent access to the JSSESupport keySizeCache map

by Aaron Ogburn (JIRA)

Aaron Ogburn created JBWEB-300: ---------------------------------- Summary: High CPU in concurrent access to the JSSESupport keySizeCache map Key: JBWEB-300 URL: https://issues.jboss.org/browse/JBWEB-300 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossWeb-7.3.0.GA, JBossWeb-7.4.0.GA Reporter: Aaron Ogburn Assignee: Remy Maucherat The keySizeCache map in JSSESupport isn't protected from concurrent access and so can cause high CPU loops. The complete fix from the tomcat bug that had this map access synchronized wasn't used: https://issues.apache.org/bugzilla/show_bug.cgi?id=47744 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-472) Drools Eclipse plugin can't recognize third party classes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-472?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-472: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Drools Eclipse plugin can't recognize third party classes > --------------------------------------------------------- > > Key: DROOLS-472 > URL: https://issues.jboss.org/browse/DROOLS-472 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: * OS: Mac OS X 10.9.2 > * Eclipse Kepler > * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final) > * Java SE 1.7 > * Drools Runtime 6.0.1 > Reporter: Jinghai Rao > Assignee: Mario Fusco > > Whenever I use classes from any third party jar files (not in JRE System Library and Drools Library), I got error messages in Eclipse IDE. > At the place where I import the class, the error message is "Only a type can be imported. ... resolves to a package". > At the place where I use the class, the error message is "... cannot be resolved to a type". > However, I have included the jar file in classpath. The project can also be executed successfully even with the error message in IDE. > Below is my development environment: > * OS: Mac OS X 10.9.2 > * Eclipse Kepler > * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final) > * Java SE 1.7 > * Drools Runtime 6.0.1 > !https://lh5.googleusercontent.com/-gltHnzUIUg4/U1qbEzVd_LI/AAAAAAAAEYw/mKxE2jv-VVc/w1796-h1168-no/Screen+Shot+2014-04-25+at+10.20.36+AM.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-472) Drools Eclipse plugin can't recognize third party classes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-472?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-472: ------------------------------------ Could be fixed by https://github.com/droolsjbpm/droolsjbpm-tools/pull/33 Need to be checked > Drools Eclipse plugin can't recognize third party classes > --------------------------------------------------------- > > Key: DROOLS-472 > URL: https://issues.jboss.org/browse/DROOLS-472 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: * OS: Mac OS X 10.9.2 > * Eclipse Kepler > * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final) > * Java SE 1.7 > * Drools Runtime 6.0.1 > Reporter: Jinghai Rao > Assignee: Mario Fusco > > Whenever I use classes from any third party jar files (not in JRE System Library and Drools Library), I got error messages in Eclipse IDE. > At the place where I import the class, the error message is "Only a type can be imported. ... resolves to a package". > At the place where I use the class, the error message is "... cannot be resolved to a type". > However, I have included the jar file in classpath. The project can also be executed successfully even with the error message in IDE. > Below is my development environment: > * OS: Mac OS X 10.9.2 > * Eclipse Kepler > * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final) > * Java SE 1.7 > * Drools Runtime 6.0.1 > !https://lh5.googleusercontent.com/-gltHnzUIUg4/U1qbEzVd_LI/AAAAAAAAEYw/mKxE2jv-VVc/w1796-h1168-no/Screen+Shot+2014-04-25+at+10.20.36+AM.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-107) Implement java.util.logging.LogManager.getLoggerNames()

by James Perkins (JIRA)

James Perkins created LOGMGR-107: ------------------------------------ Summary: Implement java.util.logging.LogManager.getLoggerNames() Key: LOGMGR-107 URL: https://issues.jboss.org/browse/LOGMGR-107 Project: JBoss Log Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 1.5.3.Final, 2.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3418) deployed applications are not distributed to host controller(s)

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/WFLY-3418?page=com.atlassian.jira.plugin.... ] Dennis Reed commented on WFLY-3418: ----------------------------------- This is useful for being able to promote an HC to a DC. However, just the opposite behavior is desirable in all other cases. In a large domain it's just a waste of resources (bandwidth and disk space on each HC) to copy deployments not used by that HC. > deployed applications are not distributed to host controller(s) > --------------------------------------------------------------- > > Key: WFLY-3418 > URL: https://issues.jboss.org/browse/WFLY-3418 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.1.0.CR2 > Environment: Wildfly 8.1.0 CR5 domain mode > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > > when a new HC is brought up into an existing DC/HC environment, it does not receive a copy of all deployed applications (e.g. the "content" folder) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2014