September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3777) Upgrade mod_cluster to 1.3.1.Alpha2

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3777?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3777: --------------------------------- Summary: Upgrade mod_cluster to 1.3.1.Alpha2 (was: Upgrade mod_cluster to 1.3.1.Alpha1) > Upgrade mod_cluster to 1.3.1.Alpha2 > ----------------------------------- > > Key: WFLY-3777 > URL: https://issues.jboss.org/browse/WFLY-3777 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Alpha1 > > > We should get the upgrades going so that we integrate and find bugs quickly. > This will also need to integrate the last piece of WFLY-457. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-597) Dynamic salience does'nt work

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-597?page=com.atlassian.jira.plugin... ] Kris Verlaenen moved JBPM-4458 to DROOLS-597: --------------------------------------------- Project: Drools (was: jBPM) Key: DROOLS-597 (was: JBPM-4458) Workflow: GIT Pull Request workflow (was: classic default workflow) Affects Version/s: (was: jBPM 6.0.0.Final) Assignee: Mark Proctor (was: Maciej Swiderski) Component/s: (was: Runtime Engine) > Dynamic salience does'nt work > ----------------------------- > > Key: DROOLS-597 > URL: https://issues.jboss.org/browse/DROOLS-597 > Project: Drools > Issue Type: Bug > Environment: Eclipse/Windows 7 - 64 bits > Reporter: Yacine Jaber > Assignee: Mark Proctor > Attachments: WodSalienceImpl.java > > > I have implemented my own bean (Salience) that manage the dynamic salience for the rules. > After building the drl file i overlaod the salience of the rules with my dynamic salience WodSalienceImpl(Attached file). > However, the salience is not respected even if this bean was called (getValue) before the match creation. > N.B: I used MVELSalience by writing the dynamic salience into the rules(MEVL expression). The result was the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-96) OutboundSocketBinding always overrides source socket, unable to bind to wildcard address

by Radoslav Husar (JIRA)

Radoslav Husar created WFCORE-96: ------------------------------------ Summary: OutboundSocketBinding always overrides source socket, unable to bind to wildcard address Key: WFCORE-96 URL: https://issues.jboss.org/browse/WFCORE-96 Project: WildFly Core Issue Type: Feature Request Affects Versions: 1.0.0.Alpha5 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 1.0.0.Alpha6 (17:58:26) rhusar: pferraro: OutboundSocketBinding https://github.com/wildfly/wildfly-core/blob/master/network/src/main/java... checks if the binding is null but since https://github.com/wildfly/wildfly-core/blob/master/network/src/main/java... it will never be null... (17:59:10) rhusar: pferraro: so we will be always binding connections to the proxy to the default interface -- i guess that's a correct behavior anyways... (18:47:35) pferraro: hmm (18:49:08) pferraro: rhusar: seems unintuitive though (18:50:02) pferraro: rhusar: so you can never specific a wildcard address? (18:59:53) rhusar: pferraro: right, as far as i understand it.. (19:01:06) rhusar: pferraro: maybe i could add method like getOptionalSourceAddress() that would return sourceNetworkInterface directly -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3492) JSSE configuration in security domain wrongly acceptes empty parameters

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3492?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky resolved WFLY-3492. ------------------------------------- Fix Version/s: 8.2.0.CR1 Resolution: Done > JSSE configuration in security domain wrongly acceptes empty parameters > ----------------------------------------------------------------------- > > Key: WFLY-3492 > URL: https://issues.jboss.org/browse/WFLY-3492 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.1.0.Final > Reporter: Chao Wang > Assignee: Alexey Loubyansky > Fix For: 8.2.0.CR1 > > > Description from https://bugzilla.redhat.com/show_bug.cgi?id=1080069: > {noformat} > When adding a jsse configuration in security domain through CLI, it's not persisted correctly. > Steps to reproduce: > * Run CLI (./jboss-cli.sh -c) and use this commands to configure new security domain: > /subsystem=security/security-domain=trust-domain:add > /subsystem=security/security-domain=trust-domain/jsse=classic:add(truststore=>{password=1234test,url=/home/jcacek/projects/ocsp-check/build/trusted-clients.jks}) > reload > * check standalone.xml, where should be sth. like > <security-domain name="trust-domain"> > <jsse truststore-password="1234test" truststore-url="/home/jcacek/projects/ocsp-check/build/trusted-clients.jks"/> > </security-domain> > But there is: > <security-domain name="trust-domain"> > <jsse/> > </security-domain> > {noformat} > {noformat} > I had a mistake in the second command, it should be: > /subsystem=security/security-domain=trust-domain/jsse=classic:add(truststore={password=>1234test,url=>/home/jcacek/projects/ocsp-check/build/trusted-clients.jks}) > Then it works. > Nevertheless it's probably still a bug, when the original command returns: > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3846) JMS resources allows duplicate JNDI entries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3846?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3846: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1140537 > JMS resources allows duplicate JNDI entries > ------------------------------------------- > > Key: WFLY-3846 > URL: https://issues.jboss.org/browse/WFLY-3846 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.Alpha1 > > > The JMS resources that can be stored in JNDI (connection-factory, pooled-connection-factory, jms-queue, jms-topic) does not check whether their list of JNDI entries contains duplicates. > At runtime, duplicates are eliminated but this introduces a difference between the resource model with duplicate entries and its runtime state (without duplicates). > The attribute definitions for their JNDI entries should validate at the MODEL stage that their value does not contain duplicate elements. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1865) Test FORK and RELAY2

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1865?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1865: -------------------------------- Possible cause: I think the issue is that messages forwarded by RELAY2 are copied, but we only copy headers with IDs >= 200. SOLUTION: assign an ID > 203 to FORK in {{jg-protocol-ids.xml}}. Paul verifies this. > Test FORK and RELAY2 > -------------------- > > Key: JGRP-1865 > URL: https://issues.jboss.org/browse/JGRP-1865 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5.1, 3.6 > > > Test whether RELAY2 still works OK when placed over FORK. This combo will be used in WildFly 9. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1865) Test FORK and RELAY2

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1865?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1865: --------------------------- Fix Version/s: 3.5.1 > Test FORK and RELAY2 > -------------------- > > Key: JGRP-1865 > URL: https://issues.jboss.org/browse/JGRP-1865 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5.1, 3.6 > > > Test whether RELAY2 still works OK when placed over FORK. This combo will be used in WildFly 9. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-95) PrimitiveListAttributeDefinition.Builder copy constructor does not copy the listValidator

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-95: --------------------------------- Summary: PrimitiveListAttributeDefinition.Builder copy constructor does not copy the listValidator Key: WFCORE-95 URL: https://issues.jboss.org/browse/WFCORE-95 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha5 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Minor Fix For: 1.0.0.Alpha6 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-859) Authentication failure due to a login module misconfiguration is not reported if principal is null

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-859?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-859: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=927064 > Authentication failure due to a login module misconfiguration is not reported if principal is null > -------------------------------------------------------------------------------------------------- > > Key: SECURITY-859 > URL: https://issues.jboss.org/browse/SECURITY-859 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Affects Versions: PicketBox_4_0_21.Beta2, PicketBox_4_0_19.SP5 > Reporter: Ivo Studensky > Assignee: Peter Skopek > > Any misconfiguration of a login module leading to authentication failure used to be reported at trace level for anonymous user (principal == null) until SECURITY-660. Right now it is reported at debug level, but only if principal != null. > I am going to propose a fix to report the cause of such a failure at debug level despite the principal value. So that customers can see for example "javax.security.auth.login.LoginException: unable to find LoginModule class: ..." in their logs instead of "PBOX000016: Access denied" only. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-859) Authentication failure due to a login module misconfiguration is not reported if principal is null

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-859?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-859: -------------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 927064|https://bugzilla.redhat.com/show_bug.cgi?id=927064] from NEW to ASSIGNED > Authentication failure due to a login module misconfiguration is not reported if principal is null > -------------------------------------------------------------------------------------------------- > > Key: SECURITY-859 > URL: https://issues.jboss.org/browse/SECURITY-859 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Affects Versions: PicketBox_4_0_21.Beta2, PicketBox_4_0_19.SP5 > Reporter: Ivo Studensky > Assignee: Peter Skopek > > Any misconfiguration of a login module leading to authentication failure used to be reported at trace level for anonymous user (principal == null) until SECURITY-660. Right now it is reported at debug level, but only if principal != null. > I am going to propose a fix to report the cause of such a failure at debug level despite the principal value. So that customers can see for example "javax.security.auth.login.LoginException: unable to find LoginModule class: ..." in their logs instead of "PBOX000016: Access denied" only. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014