January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5689) EJB subsystem security domain mapping

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-5689?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-5689: ----------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly/pull/4, https://github.com/wildfly-security-incubator/wildfly/pull/9 (was: https://github.com/wildfly-security-incubator/wildfly/pull/4) > EJB subsystem security domain mapping > ------------------------------------- > > Key: WFLY-5689 > URL: https://issues.jboss.org/browse/WFLY-5689 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > Fix For: 11.0.0.Alpha1 > > > Allow the EJB subsystem to declare which Elytron security domains it uses. > Sample configuration: > {code:xml} > <security-domains default="ApplicationDomain"> > <security-domain name="ApplicationDomain" alias="MyDomain"/> > <security-domain name="ManagementDomain"/> > </security-domains> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5965) Incorporate JCA version that allows fairness configuration of semaphores for managed pools

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5965?page=com.atlassian.jira.plugin.... ] Jesper Pedersen commented on WFLY-5965: --------------------------------------- JBEAP-2418 -> JBEAP-2224 -> WFLY-5680 > Incorporate JCA version that allows fairness configuration of semaphores for managed pools > ------------------------------------------------------------------------------------------ > > Key: WFLY-5965 > URL: https://issues.jboss.org/browse/WFLY-5965 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > Allowing the configuration of the fairness of the semaphore used to manage the connection pools in JCA provides a performance benefit in some use cases where ordering of leasing connections is not a requirement. > Relevant JCA JIRA: https://issues.jboss.org/browse/JBJCA-1305 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5965) Incorporate JCA version that allows fairness configuration of semaphores for managed pools

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5965?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-5965: ------------------------------------- OK, then we need the link from WFLY-5860 to JBEAP-2418 so it can be tracked > Incorporate JCA version that allows fairness configuration of semaphores for managed pools > ------------------------------------------------------------------------------------------ > > Key: WFLY-5965 > URL: https://issues.jboss.org/browse/WFLY-5965 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > Allowing the configuration of the fairness of the semaphore used to manage the connection pools in JCA provides a performance benefit in some use cases where ordering of leasing connections is not a requirement. > Relevant JCA JIRA: https://issues.jboss.org/browse/JBJCA-1305 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5860) WildFly/IronJacamar 1.3.2.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5860?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-5860: ------------------------------------- Assignee: James Perkins (was: Stefano Maestri) > WildFly/IronJacamar 1.3.2.Final > ------------------------------- > > Key: WFLY-5860 > URL: https://issues.jboss.org/browse/WFLY-5860 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Jesper Pedersen > Assignee: James Perkins > Priority: Blocker > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5965) Incorporate JCA version that allows fairness configuration of semaphores for managed pools

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5965?page=com.atlassian.jira.plugin.... ] Jesper Pedersen closed WFLY-5965. --------------------------------- Resolution: Duplicate Issue WFLY-5860 > Incorporate JCA version that allows fairness configuration of semaphores for managed pools > ------------------------------------------------------------------------------------------ > > Key: WFLY-5965 > URL: https://issues.jboss.org/browse/WFLY-5965 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > Allowing the configuration of the fairness of the semaphore used to manage the connection pools in JCA provides a performance benefit in some use cases where ordering of leasing connections is not a requirement. > Relevant JCA JIRA: https://issues.jboss.org/browse/JBJCA-1305 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1284) jvmsType definition in management schema references incorrect type for the 'jvm' element

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1284?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-1284. -------------------------------------- Resolution: Rejected Actually not a problem. > jvmsType definition in management schema references incorrect type for the 'jvm' element > ---------------------------------------------------------------------------------------- > > Key: WFCORE-1284 > URL: https://issues.jboss.org/browse/WFCORE-1284 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.6.Final > > > Currently it is: - > {noformat} >  > <xs:complexType name="jvmsType"> > <xs:sequence> > <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/> > </xs:sequence> > </xs:complexType> > {noformat} > However the type should be 'jvm'Type' the 'namedJvmType' is for the referenced back. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1284) jvmsType definition in management schema references incorrect type for the 'jvm' element

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1284: ---------------------------------------- Summary: jvmsType definition in management schema references incorrect type for the 'jvm' element Key: WFCORE-1284 URL: https://issues.jboss.org/browse/WFCORE-1284 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.0.6.Final Currently it is: - {noformat}  <xs:complexType name="jvmsType"> <xs:sequence> <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> {noformat} However the type should be 'jvm'Type' the 'namedJvmType' is for the referenced back. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-634) Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads

by Mateusz Patelak (JIRA)

[ https://issues.jboss.org/browse/DROOLS-634?page=com.atlassian.jira.plugin... ] Mateusz Patelak commented on DROOLS-634: ---------------------------------------- There is nothing more I can share, unfortunately. > Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-634 > URL: https://issues.jboss.org/browse/DROOLS-634 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR1 > Reporter: Anantjot Anand > Assignee: Mario Fusco > > Caused by: java.lang.NullPointerException > at org.drools.core.reteoo.RuleTerminalNodeLeftTuple.getDeclarationIds(RuleTerminalNodeLeftTuple.java:394) > at org.drools.core.audit.WorkingMemoryLogger.extractDeclarations(WorkingMemoryLogger.java:325) > at org.drools.core.audit.WorkingMemoryLogger.matchCreated(WorkingMemoryLogger.java:269) > at org.drools.core.event.AgendaEventSupport.fireActivationCreated(AgendaEventSupport.java:58) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftTupleInsert(PhreakRuleTerminalNode.java:95) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftInserts(PhreakRuleTerminalNode.java:69) > at org.drools.core.phreak.PhreakRuleTerminalNode.doNode(PhreakRuleTerminalNode.java:42) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:316) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:225) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:98) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:988) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1274) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1254) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1273) Can not add property after change of class in custom log formatter.

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1273?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-1273: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: James Perkins) > Can not add property after change of class in custom log formatter. > ------------------------------------------------------------------- > > Key: WFCORE-1273 > URL: https://issues.jboss.org/browse/WFCORE-1273 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Running unsecured EAP 7.0. DR9 version in standalone mode with standalone-full-ha profile > Reporter: James Perkins > Assignee: ehsavoie Hugonnet > > When you create custom formater - XMLFormatter {{/subsystem=logging/custom-formatter=XMLFormatter:add(class=java.util.logging.XMLFormatter, module=org.jboss.logmanager)}} and then in web console edit class of formatter to *org.jboss.logmanager.formatters.PatternFormatter* then save and try to add properties - *pattern=%s%E%n*. Property is not saved. > When you create new formatter with *org.jboss.logmanager.formatters.PatternFormatter* class and then try to add same property, saving is successful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-634) Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads

by Anantjot Anand (JIRA)

[ https://issues.jboss.org/browse/DROOLS-634?page=com.atlassian.jira.plugin... ] Anantjot Anand commented on DROOLS-634: --------------------------------------- It happens that I am again dealing with this exception currently in 6.3.0.Final as well. However for me it happen for fisrt evaluation only and if i re-submit the same request no exception happen. Very wierd behavior. I plan to set null pointer check and see if it resolves it or move the exception somewhere else. Caused by: java.lang.NullPointerException at org.drools.core.reteoo.RuleTerminalNodeLeftTuple.getDeclarationIds(RuleTerminalNodeLeftTuple.java:394) at org.drools.core.audit.WorkingMemoryLogger.extractDeclarations(WorkingMemoryLogger.java:329) at org.drools.core.audit.WorkingMemoryLogger.matchCreated(WorkingMemoryLogger.java:273) at org.drools.core.event.AgendaEventSupport.fireActivationCreated(AgendaEventSupport.java:58) at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftTupleInsert(PhreakRuleTerminalNode.java:110) at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftInserts(PhreakRuleTerminalNode.java:84) at org.drools.core.phreak.PhreakRuleTerminalNode.doNode(PhreakRuleTerminalNode.java:57) at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:318) at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:166) at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:123) at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73) at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:979) at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1293) at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260) at com.wellsfargo.ARGenT.Execution.RuleBase.processDataWithRules(RuleBase.java:1529) ... 10 more</stackTrace> > Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-634 > URL: https://issues.jboss.org/browse/DROOLS-634 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR1 > Reporter: Anantjot Anand > Assignee: Mario Fusco > > Caused by: java.lang.NullPointerException > at org.drools.core.reteoo.RuleTerminalNodeLeftTuple.getDeclarationIds(RuleTerminalNodeLeftTuple.java:394) > at org.drools.core.audit.WorkingMemoryLogger.extractDeclarations(WorkingMemoryLogger.java:325) > at org.drools.core.audit.WorkingMemoryLogger.matchCreated(WorkingMemoryLogger.java:269) > at org.drools.core.event.AgendaEventSupport.fireActivationCreated(AgendaEventSupport.java:58) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftTupleInsert(PhreakRuleTerminalNode.java:95) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftInserts(PhreakRuleTerminalNode.java:69) > at org.drools.core.phreak.PhreakRuleTerminalNode.doNode(PhreakRuleTerminalNode.java:42) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:316) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:225) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:98) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:988) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1274) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1254) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 2016