April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-917) Remove setStatusCode call in NegotiationMechanism

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-917?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-917: -------------------------------------- Fix Version/s: Negotiation_3_0_3_CR1 (was: Negotiation_3_0_2_Final) > Remove setStatusCode call in NegotiationMechanism > ------------------------------------------------- > > Key: SECURITY-917 > URL: https://issues.jboss.org/browse/SECURITY-917 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_3_CR1 > > > Once UNDERTOW-548 is resolved we can remove manually setting the status code ourselves. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-915) Migrate MessageFactory discovery to use ServiceLoader

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-915?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-915: -------------------------------------- Fix Version/s: Negotiation_3_0_3_CR1 (was: Negotiation_3_0_2_Final) > Migrate MessageFactory discovery to use ServiceLoader > ----------------------------------------------------- > > Key: SECURITY-915 > URL: https://issues.jboss.org/browse/SECURITY-915 > Project: PicketBox > Issue Type: Feature Request > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_3_CR1 > > > At the moment we have statically defined class names and attempt to load them in turn to identify which ones are actually available - ServiceLoader based discovery would eliminate this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-940) Release JBoss Negotiation 3.0.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-940?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-940. --------------------------------------- Resolution: Done > Release JBoss Negotiation 3.0.2.Final > ------------------------------------- > > Key: SECURITY-940 > URL: https://issues.jboss.org/browse/SECURITY-940 > Project: PicketBox > Issue Type: Release > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_2_CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1025) NPE removing a rule that contains a subnetwork

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1025?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1025: ------------------------------------------------- Tibor Zimanyi <tzimanyi(a)redhat.com> changed the Status of [bug 1298579|https://bugzilla.redhat.com/show_bug.cgi?id=1298579] from ON_QA to VERIFIED > NPE removing a rule that contains a subnetwork > ---------------------------------------------- > > Key: DROOLS-1025 > URL: https://issues.jboss.org/browse/DROOLS-1025 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Removing a rule containing a subnetwork causes the following NPE: > {code} > java.lang.NullPointerException > at org.drools.core.phreak.AddRemoveRule.deletePeerLeftTuple(AddRemoveRule.java:777) > at org.drools.core.phreak.AddRemoveRule.followPeer(AddRemoveRule.java:749) > at org.drools.core.phreak.AddRemoveRule.processLeftTuples(AddRemoveRule.java:713) > at org.drools.core.phreak.AddRemoveRule.flushStagedTuples(AddRemoveRule.java:281) > at org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:153) > at org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:173) > at org.drools.core.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:163) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1635) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1626) > at org.drools.core.impl.KnowledgeBaseImpl.internalRemoveRule(KnowledgeBaseImpl.java:1610) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1581) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1089) Reentrant working memory actions aren't flushed immediately even when eager evaluation is forced

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1089?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1089: ------------------------------------------------- Tibor Zimanyi <tzimanyi(a)redhat.com> changed the Status of [bug 1316860|https://bugzilla.redhat.com/show_bug.cgi?id=1316860] from ON_QA to VERIFIED > Reentrant working memory actions aren't flushed immediately even when eager evaluation is forced > ------------------------------------------------------------------------------------------------ > > Key: DROOLS-1089 > URL: https://issues.jboss.org/browse/DROOLS-1089 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.0.CR2, 7.0.0.Final > > > jBPM requires Drools working memory actions to be immediately flushed and then uses Drools force eager activation option. However even when this option is enabled working memory actions that aren't created in a reentrant way (during a rule firing) are enqueued instead of being flushed as expected by jBPM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6449) Upgrade Narayana to 5.3.2.Final

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6449?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-6449: ---------------------------------- Fix Version/s: 11.0.0.Alpha1 > Upgrade Narayana to 5.3.2.Final > ------------------------------- > > Key: WFLY-6449 > URL: https://issues.jboss.org/browse/WFLY-6449 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-939) Contents of NegotiationContext getting cleared before challenge is sent to client.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-939?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-939. --------------------------------------- Resolution: Done > Contents of NegotiationContext getting cleared before challenge is sent to client. > ---------------------------------------------------------------------------------- > > Key: SECURITY-939 > URL: https://issues.jboss.org/browse/SECURITY-939 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_3_0_0_Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_2_CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6450) Old JGroups/Netty dependencies in wildfly-jms-client-bom

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6450?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-4035 to WFLY-6450: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6450 (was: JBEAP-4035) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.Final (was: 7.0.0.ER7) > Old JGroups/Netty dependencies in wildfly-jms-client-bom > -------------------------------------------------------- > > Key: WFLY-6450 > URL: https://issues.jboss.org/browse/WFLY-6450 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > > There is different JGroups and Netty version in EAP 7.0.0.ER7 zip and dependencies downloaded by wildfly-jms-client-bom: > {code} > <dependency> > <groupId>org.jboss.eap</groupId> > <artifactId>wildfly-jms-client-bom</artifactId> > <version>7.0.0.ER7-redhat-1</version> > <type>pom</type> > </dependency> > {code} > Actual state: > EAP 7.0.0.ER7 contains Netty 4.0.32 but bom 4.0.30 > EAP 7.0.0.ER7 contains JGroups 3.6.8 but bom 3.6.0 > Expected state: > Those versions should be in sync. > Customer impact: > No issue was found. > Priority can be increased if issue occurs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6449) Upgrade Narayana to 5.3.2.Final

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-6449: ------------------------------------- Summary: Upgrade Narayana to 5.3.2.Final Key: WFLY-6449 URL: https://issues.jboss.org/browse/WFLY-6449 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1110) Avoid acquiring a kbase readlock when performing a working memory action

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1110?page=com.atlassian.jira.plugi... ] Mario Fusco closed DROOLS-1110. ------------------------------- Fix Version/s: 6.4.0.Final 7.0.0.Final Resolution: Done Implemented by https://github.com/droolsjbpm/drools/commit/1e50f13e6 > Avoid acquiring a kbase readlock when performing a working memory action > ------------------------------------------------------------------------- > > Key: DROOLS-1110 > URL: https://issues.jboss.org/browse/DROOLS-1110 > Project: Drools > Issue Type: Enhancement > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.0.Final, 7.0.0.Final > > > At the moment all working memory actions (insert/update/delete) need to acquire a read lock on the kbase. This is avoidable making the kbase to deactivate (through their state machine) all the ksessions created from it before modifying the kbase itself. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 April 2016