May 2014 - jboss-jira - Jboss List Archives

[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)

11 years, 11 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)

11 years, 11 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)

11 years, 11 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)

11 years, 11 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)

11 years, 11 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)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-104) MDC Logging not appearing in server.log

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-104?page=com.atlassian.jira.plu... ] James Perkins commented on JBLOGGING-104: ----------------------------------------- You would need to put a value of {{entry1}} and {{entry2}} into MDC in order for this to work. The pattern is {{%x{mdcKey}}} where mdcKey is the key for the MDC value you want to see. > MDC Logging not appearing in server.log > --------------------------------------- > > Key: JBLOGGING-104 > URL: https://issues.jboss.org/browse/JBLOGGING-104 > Project: JBoss Logging > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jboss-logging-logmanager, jboss-logging-spi > Affects Versions: 3.1.4.GA > Environment: Local > Reporter: ArunPrasath Rajmohan > Assignee: James Perkins > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > Hi > I am trying to log using org.jboss.logging.MDC but the log entry is not found in server.log > Steps followed: > 1.Maven Dependency Used: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>3.1.4.GA</version> > </dependency> > {code} > 2.Athe below code in the controller > org.jboss.logging.MDC.put("MDC Worked", new String("MDC Worked")); > 3.Placed the jboss-logging.xml inside META-INF folder of the web application. > The content of jboss-logging.xml is as follows: > {code:xml} > <periodic-rotating-file-handler > file-name="${jboss.server.log.dir}/server.log" > name="FILE" > autoflush="true" > append="true" > suffix=".yyyy-MM-dd"> > > <error-manager> > <only-once/> > </error-manager> > > <formatter> > <pattern-formatter pattern="%d %-5p [%c] (%t) [%X{entry1}, %X{entry2}] %s%E%n"/> > </formatter> > </periodic-rotating-file-handler> > {code} > Problem: > There are no errors but the log entry is not found in the server.log > Regards > Arun > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-104) MDC Logging not appearing in server.log

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-104?page=com.atlassian.jira.plu... ] James Perkins updated JBLOGGING-104: ------------------------------------ Description: Hi I am trying to log using org.jboss.logging.MDC but the log entry is not found in server.log Steps followed: 1.Maven Dependency Used: {code:xml} <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging</artifactId> <version>3.1.4.GA</version> </dependency> {code} 2.Athe below code in the controller org.jboss.logging.MDC.put("MDC Worked", new String("MDC Worked")); 3.Placed the jboss-logging.xml inside META-INF folder of the web application. The content of jboss-logging.xml is as follows: {code:xml} <periodic-rotating-file-handler file-name="${jboss.server.log.dir}/server.log" name="FILE" autoflush="true" append="true" suffix=".yyyy-MM-dd"> <error-manager> <only-once/> </error-manager> <formatter> <pattern-formatter pattern="%d %-5p [%c] (%t) [%X{entry1}, %X{entry2}] %s%E%n"/> </formatter> </periodic-rotating-file-handler> {code} Problem: There are no errors but the log entry is not found in the server.log Regards Arun was: Hi I am trying to log using org.jboss.logging.MDC but the log entry is not found in server.log Steps followed: 1.Maven Dependency Used: <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging</artifactId> <version>3.1.4.GA</version> </dependency> 2.Athe below code in the controller org.jboss.logging.MDC.put("MDC Worked", new String("MDC Worked")); 3.Placed the jboss-logging.xml inside META-INF folder of the web application. The content of jboss-logging.xml is as follows: <periodic-rotating-file-handler file-name="${jboss.server.log.dir}/server.log" name="FILE" autoflush="true" append="true" suffix=".yyyy-MM-dd"> <error-manager> <only-once/> </error-manager> <formatter> <pattern-formatter pattern="%d %-5p [%c] (%t) [%X{entry1}, %X{entry2}] %s%E%n"/> </formatter> </periodic-rotating-file-handler> Problem: There are no errors but the log entry is not found in the server.log Regards Arun > MDC Logging not appearing in server.log > --------------------------------------- > > Key: JBLOGGING-104 > URL: https://issues.jboss.org/browse/JBLOGGING-104 > Project: JBoss Logging > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jboss-logging-logmanager, jboss-logging-spi > Affects Versions: 3.1.4.GA > Environment: Local > Reporter: ArunPrasath Rajmohan > Assignee: James Perkins > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > Hi > I am trying to log using org.jboss.logging.MDC but the log entry is not found in server.log > Steps followed: > 1.Maven Dependency Used: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>3.1.4.GA</version> > </dependency> > {code} > 2.Athe below code in the controller > org.jboss.logging.MDC.put("MDC Worked", new String("MDC Worked")); > 3.Placed the jboss-logging.xml inside META-INF folder of the web application. > The content of jboss-logging.xml is as follows: > {code:xml} > <periodic-rotating-file-handler > file-name="${jboss.server.log.dir}/server.log" > name="FILE" > autoflush="true" > append="true" > suffix=".yyyy-MM-dd"> > > <error-manager> > <only-once/> > </error-manager> > > <formatter> > <pattern-formatter pattern="%d %-5p [%c] (%t) [%X{entry1}, %X{entry2}] %s%E%n"/> > </formatter> > </periodic-rotating-file-handler> > {code} > Problem: > There are no errors but the log entry is not found in the server.log > Regards > Arun > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-475) Drools condition part always use MVEL strict mode (extended classes doen't get properties of super class )

by Shailesh T (JIRA)

[ https://issues.jboss.org/browse/DROOLS-475?page=com.atlassian.jira.plugin... ] Shailesh T closed DROOLS-475. ----------------------------- Thanks for immediate fix. Verified with 'drools-distribution-6.1.0.Beta4', This is working. > Drools condition part always use MVEL strict mode (extended classes doen't get properties of super class ) > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-475 > URL: https://issues.jboss.org/browse/DROOLS-475 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: JDK 6, MVEL as default, with strict-mode set to false with file META-INF/drools.default.packagebuilder.conf with following entries > drools.dialect.default = mvel > drools.dialect.java = org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration > drools.dialect.java.compiler = ECLIPSE > drools.dialect.mvel = org.drools.compiler.rule.builder.dialect.mvel.MVELDialectConfiguration > drools.dialect.mvel.strict = false > Reporter: Shailesh T > Assignee: Mario Fusco > Priority: Critical > Labels: drools, mvel, strict-mode > Fix For: 6.1.0.Beta4 > > Attachments: BasicInclude.drl > > > Even after setting MVEL strict mode to false, condition part of drools works using strict mode and can't work with Inherited getters of HashMap (Breaks lot of working rules from 5.4) > Error: [Error: unable to resolve method using strict-mode: defaultpkg.Test.Price()] > [Near : {... Price < 100 ....}] > ... > t: HashMap( > Price < 11 > ) > .. > Does work but > import java.util.HashMap; > declare HashMap > end > declare Test extends HashMap > end > t: Test( > Price<100 > ) > doesn't work (please see full rules in steps to reproduce) > Even condition > this["OtherPrices"]["OldPrice"] < 9 > does work for Map but not for inherited Test class > (applicable but not included in sample code to reproduce issue, added drl for this as attachment) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SASL-49) Custom Property to Prefer JDK Mechanisms

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/SASL-49?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on SASL-49: --------------------------------- As an alternative you could use {{Security.getProviders()}} with an appropriate filter and filter the list that way, which wouldn't require any nonstandard behavior at all. > Custom Property to Prefer JDK Mechanisms > ---------------------------------------- > > Key: SASL-49 > URL: https://issues.jboss.org/browse/SASL-49 > Project: JBoss SASL Provider > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > This is primarily for testing although it could be used for other purposes, a new custom property should be added to JBoss SASL which will cause mechanisms that duplicate JDK supplied mechanisms to avoid being used themselves. > i.e. Even though JBoss SASL could supply an implementation for that mechanisms it will let the JDK supplied version win through. > For testing this will enable interoperability testing between our mechanisms and the JDK mechanisms, for end users they could use JBoss SASL for the new mechanisms we supply whilst still using the JDK for the mechanisms it supplied. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 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 May 2014