October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7320) LDAP referrals does not work for Elytron dir-context since value of dir-context.referral-mode is always ignored

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7320?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7320: ----------------------------- Component/s: Security > LDAP referrals does not work for Elytron dir-context since value of dir-context.referral-mode is always ignored > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7320 > URL: https://issues.jboss.org/browse/WFLY-7320 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > Elytron dir-context is not able to follow/throw referrals in LDAP search. Value set in Elytron {{dir-context.referral-mode}} is ignored by Elytron. > InitialLdapContext {{java.naming.referral}} parameter is internally always set to value {{ignore}}. It is caused by ignoring {{ReferralMode}} parameter in {{obtainDirContext}} of {{org.wildfly.security.auth.realm.ldap.SimpleDirContextFactoryBuilder$SimpleDirContextFactory}} [1]. > We request blocker flag since this issue causes that referrals cannot be used for LDAP search with Elytron. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1326: ------------------------------------------ That went into a different path, and a apparently this is a rare bug, so it didn't reproduce there. The first solver should have a CH stepCountLimit termination of 403 steps. The second solver should run the rest of the CH entirely and have an LS stepCountLimit termination of 1233 steps. The third solver should just run. At each point confirm that the score is the same as in the original log. There's still an edge case that that doesn't reproduce it - if the the last step of the first solver's CH saw only half the moves and picked a less optimal one - but let's worry about that if we see that. Let's talk on Monday if you can use more info. > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1323) DefaultAgenda.immediateHalt takes up 20% of performance in statefull cases: investigate why

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1323?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1323: ------------------------------------- Priority: Minor (was: Major) > DefaultAgenda.immediateHalt takes up 20% of performance in statefull cases: investigate why > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1323 > URL: https://issues.jboss.org/browse/DROOLS-1323 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Minor > Attachments: Selection_240.png, Selection_241.png, Selection_245.png, Selection_246.png, Selection_247.png, Selection_249.png > > > Mario and Geoffrey will investigate, but here's the profiler reports to prove it. > to reproduce: OptaPlannerExamplesApp -> cloud balancing use case -> load dataset with 1600computer + turn off refresh checkbox -> start cpu profiling -> button solve -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2391) Wildfly caches content in exploded mode, breaking developer productivity

by Radomír Vach (JIRA)

[ https://issues.jboss.org/browse/WFLY-2391?page=com.atlassian.jira.plugin.... ] Radomír Vach commented on WFLY-2391: ------------------------------------ Hi, I have the same problem with exploded files. After some time wildfly start to cache XHTML file and provide me old files. I have Wildfly 10.1 > Wildfly caches content in exploded mode, breaking developer productivity > ------------------------------------------------------------------------ > > Key: WFLY-2391 > URL: https://issues.jboss.org/browse/WFLY-2391 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Environment: MacOSX with JBossTools 4.1.1.Beta1 > Reporter: Xavier Coulon > Assignee: Stuart Douglas > Priority: Critical > Fix For: 8.0.0.CR1 > > Attachments: jboss-as-kitchensink-html5-mobile.war.zip > > > While I was building a sample application with JBoss Tools 4.1.1.beta1 on WildFly 8.0.Beta1, I noticed that after a few minutes (or a few browser requests), the content of my index.html file seemed to be cached by the server, although I used the "exploded content" deployment mode (since I published the content using the WildFly Server Adapter in JBoss Tools). > > I checked the actual content of the index.html in the deployments folder and it contained the latest changes, which means that the JBoss Tools Server Adapter is doing its job well ;-) > I also tried to edit the index.html file directly in the deployments folder, and once again, I got no update in both Chrome and Firefox browsers. > > I checked in the "Network" tab of the browsers and could see that the server response for the index.html page had a "200 OK" status, which means that there's no browser caching involved. > I tried to get the index.html page with cUrl and got the same old version, which definitely excludes a browser caching issue. > At the end of the dat, this means that after a few changes, my browsers keep getting an old version of the deployed resources, which in turns means that I have to stop and restart the server to get the new content, and this is pretty bad in term of dev productivity. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7286) Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7286?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7286: ----------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Elytron - inconsistency between DMR and XSD representation of mechanism-provider-filtering-sasl-server-factory > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7286 > URL: https://issues.jboss.org/browse/WFLY-7286 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > > There is an inconsistency between DMR and XSD representation of {{mechanism-provider-filtering-sasl-server-factory}}. > According to XSD [1] {{filters}} may not occur in {{mechanism-provider-filtering-sasl-server-factory}}. According to DMR {{filters}} is {{"nillable" => false}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7285) Elytron - inconsistency between DMR and XSD representation of simple-permission-mapper

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7285?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7285: ----------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Elytron - inconsistency between DMR and XSD representation of simple-permission-mapper > -------------------------------------------------------------------------------------- > > Key: WFLY-7285 > URL: https://issues.jboss.org/browse/WFLY-7285 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > > There are inconsistencies between DMR and XSD representation of {{simple-permission-mapper}}. > According to XSD both {{permission-mapping}} [1] and its inner {{permission}} [2] must occur at least one times in {{simple-permission-mapper}}. According to DMR they are {{"nillable" => true}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [2] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7284) group-properties can be added without path in Elytron properties-realm which results to invalid server configuration

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7284?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned WFLY-7284: ----------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > group-properties can be added without path in Elytron properties-realm which results to invalid server configuration > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7284 > URL: https://issues.jboss.org/browse/WFLY-7284 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > > Adding {{groups-properties}} without {{path}} through CLI is allowed by Elytron subsystem which results to XMLStreamException after server is reloaded/restarted. > Exception in server log after reload/restart: > {code} > ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) > at org.jboss.as.server.ServerService.boot(ServerService.java:355) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[345,21] > Message: WFLYCTL0133: Missing required attribute(s): path > at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:180) > at org.wildfly.extension.elytron.RealmParser.readFileAttributes(RealmParser.java:522) > at org.wildfly.extension.elytron.RealmParser.readPropertiesRealm(RealmParser.java:337) > at org.wildfly.extension.elytron.RealmParser.readRealms(RealmParser.java:118) > at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:114) > at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:72) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) > at org.jboss.as.server.parsing.StandaloneXml_5.parseServerProfile(StandaloneXml_5.java:591) > at org.jboss.as.server.parsing.StandaloneXml_5.readServerElement(StandaloneXml_5.java:245) > at org.jboss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:144) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) > ... 3 more > FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-665) Ensure that the "index" attribute in AttributeMapper is greater than 1.

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-665: --------------------------------- Summary: Ensure that the "index" attribute in AttributeMapper is greater than 1. Key: ELY-665 URL: https://issues.jboss.org/browse/ELY-665 Project: WildFly Elytron Issue Type: Bug Components: Realms Affects Versions: 1.1.0.Beta10 Reporter: Ilia Vassilev Assignee: Ilia Vassilev -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-664) Ensure that the "index" attribute in AttributeMapper is greater than 1.

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-664: --------------------------------- Summary: Ensure that the "index" attribute in AttributeMapper is greater than 1. Key: ELY-664 URL: https://issues.jboss.org/browse/ELY-664 Project: WildFly Elytron Issue Type: Bug Components: Realms Affects Versions: 1.1.0.Beta10 Reporter: Ilia Vassilev Assignee: Darran Lofthouse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-664) Ensure that the "index" attribute in AttributeMapper is greater than 1.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-664?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-664: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Ensure that the "index" attribute in AttributeMapper is greater than 1. > ------------------------------------------------------------------------ > > Key: ELY-664 > URL: https://issues.jboss.org/browse/ELY-664 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta10 > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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