March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6440) Unignore DenyUncoveredHttpMethodsTestCase#testTraceMethod

by Martin Simka (JIRA)

Martin Simka created WFLY-6440: ---------------------------------- Summary: Unignore DenyUncoveredHttpMethodsTestCase#testTraceMethod Key: WFLY-6440 URL: https://issues.jboss.org/browse/WFLY-6440 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Martin Simka Assignee: Martin Simka Priority: Minor DenyUncoveredHttpMethodsTestCase#testTraceMethod was ignored in https://github.com/wildfly/wildfly/pull/8647 PR says that test should be unignored once WFCORE-1347 is fixed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1454) Undertow 1.3.20.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1454?page=com.atlassian.jira.plugi... ] Stuart Douglas reassigned WFCORE-1454: -------------------------------------- Assignee: Stuart Douglas > Undertow 1.3.20.Final > --------------------- > > Key: WFCORE-1454 > URL: https://issues.jboss.org/browse/WFCORE-1454 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1454) Undertow 1.3.20.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-1454: -------------------------------------- Summary: Undertow 1.3.20.Final Key: WFCORE-1454 URL: https://issues.jboss.org/browse/WFCORE-1454 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1455) Undertow 1.3.20.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-1455: -------------------------------------- Summary: Undertow 1.3.20.Final Key: WFCORE-1455 URL: https://issues.jboss.org/browse/WFCORE-1455 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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: ------------------------------------------------- Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1298579|https://bugzilla.redhat.com/show_bug.cgi?id=1298579] from MODIFIED to ON_QA > 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)

10 years

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: ------------------------------------------------- Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1316860|https://bugzilla.redhat.com/show_bug.cgi?id=1316860] from MODIFIED to ON_QA > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6439) Undertow access_log prefix/suffix default values discrepancy

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6439?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-3988 to WFLY-6439: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6439 (was: JBEAP-3988) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Target Release: (was: 7.0.0.GA) Affects Version/s: (was: 7.0.0.ER7) > Undertow access_log prefix/suffix default values discrepancy > ------------------------------------------------------------ > > Key: WFLY-6439 > URL: https://issues.jboss.org/browse/WFLY-6439 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Schema definition of Undertow access log {{prefix}} and {{suffix}} attributes [in this file|https://github.com/jbossas/jboss-eap7/blob/EAP_7.0.0.ER7-dev/underto...] do not match what is [in access log definition|https://github.com/jbossas/jboss-eap7/blob/EAP_7.0.0.ER7-dev/u...] - see the difference in > {{access_log}} -> {{access_log.}} and {{.log}} -> {{log}} > There was a change [in this commit|https://github.com/jbossas/jboss-eap7/commit/f47aa52bf67f4d8a469ba...]. > Those values should match and according to mentioned commit I propose to edit schema definition to what is in access log definition file (therefore: prefix = "access_log." and suffix = "log"). > NOTE: I am setting target for GA as this is trivial change in schema definition and better to change it before GA as after this any change to schema definition is difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6438) Undertow listener max-header-size default value discrepancy

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6438?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-3987 to WFLY-6438: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6438 (was: JBEAP-3987) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Target Release: (was: 7.0.0.GA) Affects Version/s: (was: 7.0.0.ER7) > Undertow listener max-header-size default value discrepancy > ----------------------------------------------------------- > > Key: WFLY-6438 > URL: https://issues.jboss.org/browse/WFLY-6438 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > There is discrepancy in undertow schema definition of [listener attribute 'max-header-size' default value here|https://github.com/jbossas/jboss-eap7/blob/EAP_7.0.0.ER7-dev/underto...] and [ListenerResourceDefinition here|https://github.com/jbossas/jboss-eap7/blob/EAP_7.0.0.ER7-dev/underto...]. > Note: Default value in ListenerResourceDefinition java file was changed by [this commit|https://github.com/undertow-io/undertow/commit/9cfd0c7dca671bd0089...] > These two default values should be unified so they match. > NOTE: I set GA as a target release as this is probably trivial change in Undertow schema definition which is better to do before GA as after that any change into schema is difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1318: ------------------------------------------------ Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1320720|https://bugzilla.redhat.com/show_bug.cgi?id=1320720] from POST to MODIFIED > list driven ExceptionSorter, StaleConnectionChecker > --------------------------------------------------- > > Key: JBJCA-1318 > URL: https://issues.jboss.org/browse/JBJCA-1318 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Priority: Minor > Fix For: WildFly/IronJacamar 1.3.4.Final, 1.0.37.Final, 1.2.8.Final > > > Configuration defined ExceptionSorter, StaleConnectionChecker. > Using an externally (from the implementation) defined "," separated list. > Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files. > ie: > set via <config-property name="FatalExceptions">10099,10100,10101</> > set via <config-property name="StaleExceptions">10099,10100,10101</> > Documentation updated to reflect suggested error codes for vendor based upon the current implementations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-178) Domain to domain identity propagation

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-178?page=com.atlassian.jira.plugin.sy... ] Farah Juma reassigned ELY-178: ------------------------------ Assignee: Farah Juma (was: Darran Lofthouse) > Domain to domain identity propagation > ------------------------------------- > > Key: ELY-178 > URL: https://issues.jboss.org/browse/ELY-178 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: Darran Lofthouse > Assignee: Farah Juma > Fix For: 1.1.0.CR1 > > > At the lowest level a users identity is associated with a single SecurityRealm, two accounts that authenticated against different realms will never be considered equal. > However on top of this we have the security domains, a security domain amongst other things is an aggregation of realms. Incoming server connections and also applications can be associated with a security domain. However we still have the following two scenarios of a call to complete the consideration for: - > Connection -> Deployment > Deployment -> Deployment > In the first case the connection may be associated with a security domain with a large set of realms, however the deployment may be associated with a smaller set of realms. In the case that the realm is in both of these domains we need the identity to be able to automatically propagate. > Same for deployment to deployment calls, if there is a common realm the identity should propagate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016