June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3015) Upgrade WildFly Elytron to 1.1.0.Beta55

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3015?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3015: ------------------------------------- Fix Version/s: 3.0.0.Beta28 > Upgrade WildFly Elytron to 1.1.0.Beta55 > --------------------------------------- > > Key: WFCORE-3015 > URL: https://issues.jboss.org/browse/WFCORE-3015 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Beta28 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2199) JDBC_PING cluster doesn't handle shutdown members

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2199?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2199: --------------------------- Fix Version/s: 4.0.5 > JDBC_PING cluster doesn't handle shutdown members > ------------------------------------------------- > > Key: JGRP-2199 > URL: https://issues.jboss.org/browse/JGRP-2199 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0 > Reporter: Douglas Adams > Assignee: Bela Ban > Fix For: 4.0.5 > > Attachments: file-ping.xml, jdbc-ping.xml, stuck_starting_up.log > > > FILE_PING and JDBC_PING have different behavior when a cluster's coordinator stops. > With FILE_PING the coordinator will delete the whole cluster's file on shutdown of the coordinator. > JDBC_PING does not do this and reveals a problematic flaw in how node's are handled on shutdown. > When I added my own logging to the source of these files I observed that they're both continuously writing to the database/file all of the members because {{write()}} is called very frequently. > --- > Current behavior: > GIVEN a cluster of JDBC_PING registered nodes > WHEN a node shuts down > THEN it removes itself from the database table AND the coordinator almost immediately re-adds the shut down member to the table because of the {{List<PingData>}} sent to write() > GIVEN a cluster of JDBC_PING registered nodes has only the coordinator left > WHEN the coordinator shuts down > THEN the coordinator removes itself from the database and because there's no coordinator left the database shows a list of only the 'members' with no coordinator > GIVEN a cluster of JDBC_PING registered nodes > WHEN the coordinator shuts down or crashes and does not have time to remove itself from the database > THEN the next node to start will never finish negotiating membership with the cluster because a phantom coordinator still exists (see attachement: stuck_starting_up.log) > --- > I expected the behavior between JDBC_PING and FILE_PING to remain consistent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1267) Release WildFly Elytron 1.1.0.Beta55

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1267: ------------------------------------- Summary: Release WildFly Elytron 1.1.0.Beta55 Key: ELY-1267 URL: https://issues.jboss.org/browse/ELY-1267 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta55 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1265) Update X500AttributePrincipalDecoder to support converting to X500Principal

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1265?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1265. ----------------------------------- Resolution: Done > Update X500AttributePrincipalDecoder to support converting to X500Principal > --------------------------------------------------------------------------- > > Key: ELY-1265 > URL: https://issues.jboss.org/browse/ELY-1265 > Project: WildFly Elytron > Issue Type: Bug > Components: X.500 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta55 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1266) Simple String in Elytron rotating-file-audit-log.suffix attribute causes wrong audit file name

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1266: --------------------------------- Summary: Simple String in Elytron rotating-file-audit-log.suffix attribute causes wrong audit file name Key: ELY-1266 URL: https://issues.jboss.org/browse/ELY-1266 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse {{suffix}} attribute of Elytron {{rotating-file-audit-log}} uses {{java.text.SimpleDateFormat}} format [1]. It means that {{'someText'}} can be used as value of {{suffix}} attribute. However in case when only this string (without any pattern letters) is used in {{suffix}}, then resulting audit file name includes suffix "null" instead of defined suffix "someText". In case when suffix includes also pattern letters (e.g. {{d'someText'}}) then it works correctly. [1] https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1266) Simple String in Elytron rotating-file-audit-log.suffix attribute causes wrong audit file name

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1266?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1266: ------------------------------ Affects Version/s: 1.1.0.Beta52 > Simple String in Elytron rotating-file-audit-log.suffix attribute causes wrong audit file name > ---------------------------------------------------------------------------------------------- > > Key: ELY-1266 > URL: https://issues.jboss.org/browse/ELY-1266 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta52 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > {{suffix}} attribute of Elytron {{rotating-file-audit-log}} uses {{java.text.SimpleDateFormat}} format [1]. It means that {{'someText'}} can be used as value of {{suffix}} attribute. However in case when only this string (without any pattern letters) is used in {{suffix}}, then resulting audit file name includes suffix "null" instead of defined suffix "someText". In case when suffix includes also pattern letters (e.g. {{d'someText'}}) then it works correctly. > [1] https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1266) Simple String in Elytron rotating-file-audit-log.suffix attribute causes wrong audit file name

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1266?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1266: ------------------------------ Component/s: Audit > Simple String in Elytron rotating-file-audit-log.suffix attribute causes wrong audit file name > ---------------------------------------------------------------------------------------------- > > Key: ELY-1266 > URL: https://issues.jboss.org/browse/ELY-1266 > Project: WildFly Elytron > Issue Type: Bug > Components: Audit > Affects Versions: 1.1.0.Beta52 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > {{suffix}} attribute of Elytron {{rotating-file-audit-log}} uses {{java.text.SimpleDateFormat}} format [1]. It means that {{'someText'}} can be used as value of {{suffix}} attribute. However in case when only this string (without any pattern letters) is used in {{suffix}}, then resulting audit file name includes suffix "null" instead of defined suffix "someText". In case when suffix includes also pattern letters (e.g. {{d'someText'}}) then it works correctly. > [1] https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7114) Upgrade JMS API 2.0.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7114?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-7114: ------------------------------ Summary: Upgrade JMS API 2.0.0 (was: Upgrade JMS API to 2.0.1) > Upgrade JMS API 2.0.0 > --------------------- > > Key: WFLY-7114 > URL: https://issues.jboss.org/browse/WFLY-7114 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > JMS 2.0.1 API has been released for the JMS 2.0 errata release as it introduced as a change to serialVersionUID introduced a new version API > see https://java.net/projects/jms-spec/pages/JMS20RevA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7114) Upgrade JMS API 2.0.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7114?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-7114: ------------------------------ Description: JMS 2.0.0 API has released an errata as it introduced as a change to serialVersionUID introduced a new version API see https://java.net/projects/jms-spec/pages/JMS20RevA was: JMS 2.0.1 API has been released for the JMS 2.0 errata release as it introduced as a change to serialVersionUID introduced a new version API see https://java.net/projects/jms-spec/pages/JMS20RevA > Upgrade JMS API 2.0.0 > --------------------- > > Key: WFLY-7114 > URL: https://issues.jboss.org/browse/WFLY-7114 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > JMS 2.0.0 API has released an errata as it introduced as a change to serialVersionUID introduced a new version API > see https://java.net/projects/jms-spec/pages/JMS20RevA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7114) Upgrade JMS API to 2.0.1

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7114?page=com.atlassian.jira.plugin.... ] Jeff Mesnil edited comment on WFLY-7114 at 6/27/17 4:34 AM: ------------------------------------------------------------ For reference the corresponding changes in the API RI: https://github.com/javaee/openmq/issues/359 was (Author: jmesnil): For reference the corresponding changes in the API RI: https://java.net/jira/browse/MQ-359 > Upgrade JMS API to 2.0.1 > ------------------------ > > Key: WFLY-7114 > URL: https://issues.jboss.org/browse/WFLY-7114 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > JMS 2.0.1 API has been released for the JMS 2.0 errata release as it introduced as a change to serialVersionUID introduced a new version API > see https://java.net/projects/jms-spec/pages/JMS20RevA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017