October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1119) Assign an unique NodeID automatically

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-1119?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-1119: ------------------------------------- For me, the user should be forced to do this because it carries risk. > Assign an unique NodeID automatically > ------------------------------------- > > Key: WFLY-1119 > URL: https://issues.jboss.org/browse/WFLY-1119 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Clebert Suconic > Priority: Optional > > It shouldn't be needed to assign the node-id manually IMO. > You could store the node-id on a file and recover it for subsequent starts. > On hornetQ for instance, we look for the nodeID on a file, if the file doesn't exist we assign a UUID and write to the file. > In our previous experience UUID would be a best fit to assign the nodes since that was the only way we could guarantee unique IDs between the nodes. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7334) Elytron kerberos implementation ignore java.security.krb5.* system properties

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7334?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7334: ---------------------------------- [~mchoma] Sorry, I has mistaken, the correct krb5.conf works correctly even without *refreshKrb5Config* option - no need to set it. > Elytron kerberos implementation ignore java.security.krb5.* system properties > ----------------------------------------------------------------------------- > > Key: WFLY-7334 > URL: https://issues.jboss.org/browse/WFLY-7334 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > Attachments: standalone-elytron.xml > > > I don't see any behavior change, when I set standard java.security.krb5.* system properties. Trying to set properties in both ways: > * command line > {code} > -Djava.security.krb5.conf=/unreal/path -Djava.security.krb5.debug=true -Djava.security.krb5.kdc=wrong.kdc -Djava.security.krb5.realm=REDHAT.COM > {code} > * standalone.xml > {code} > <property name="java.security.krb5.conf" value="/etc/krb5.confBUG"/> > <property name="java.security.krb5.kdc" value="localhost.localhostBUG"/> > <property name="java.security.krb5.realm" value="JBOSS.ORGBUG"/> > <property name="java.security.krb5.debug" value="true"/> > {code} > Biggest problem as I see is user is unable to change {{krb5.conf}} location. In legacy security solution it was possible. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1901) Fail in finally block overrides the fail in catch block

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1901?page=com.atlassian.jira.plugi... ] Jean-Francois Denise reassigned WFCORE-1901: -------------------------------------------- Assignee: Jean-Francois Denise > Fail in finally block overrides the fail in catch block > ------------------------------------------------------- > > Key: WFCORE-1901 > URL: https://issues.jboss.org/browse/WFCORE-1901 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Information of the thrown exception is thrown. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1901) Fail in finally block overrides the fail in catch block

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-1901: -------------------------------------------- Summary: Fail in finally block overrides the fail in catch block Key: WFCORE-1901 URL: https://issues.jboss.org/browse/WFCORE-1901 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Jean-Francois Denise Information of the thrown exception is thrown. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1344) Add documentation for Aries-Blueprint integration

by Marek Czernek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1344?page=com.atlassian.jira.plugi... ] Marek Czernek commented on DROOLS-1344: --------------------------------------- [~kdwivedi], I have talked to Mario about this issue (docs jira linked). We do not have any Aries BP docs in our current guides (upstream nor downstream). If this issue blocks our release, as suggested by [~rsynek], this should be addressed (and incorporated in the downstream docs) by 6.4 release. I am not sure whether Mario has the time to finish this jira on time, maybe prioritization is in order? WDYT? > Add documentation for Aries-Blueprint integration > ------------------------------------------------- > > Key: DROOLS-1344 > URL: https://issues.jboss.org/browse/DROOLS-1344 > Project: Drools > Issue Type: Task > Components: docs > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1817) upgrade Xerces to 2.11.0.SP5

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1817?page=com.atlassian.jira.plugi... ] Carlo de Wolf commented on WFCORE-1817: --------------------------------------- https://github.com/jboss/xerces/tree/jboss-2.11.0.SP5 > upgrade Xerces to 2.11.0.SP5 > ---------------------------- > > Key: WFCORE-1817 > URL: https://issues.jboss.org/browse/WFCORE-1817 > Project: WildFly Core > Issue Type: Task > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 3.0.0.Alpha9, 2.2.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6271) SFSB methods can still be invoked after a calling transaction has rollbacked

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6271?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on WFLY-6271: ------------------------------------ [~swd847] I haven't been working on wildfly for a while now, so I'm not sure if this was resolved as part of your solution to WFLY-6215. I'm not currently able to dedicate any time to this issue, so I have unassigned myself. > SFSB methods can still be invoked after a calling transaction has rollbacked > ---------------------------------------------------------------------------- > > Key: WFLY-6271 > URL: https://issues.jboss.org/browse/WFLY-6271 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6271) SFSB methods can still be invoked after a calling transaction has rollbacked

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6271?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned WFLY-6271: ---------------------------------- Assignee: (was: Ryan Emerson) > SFSB methods can still be invoked after a calling transaction has rollbacked > ---------------------------------------------------------------------------- > > Key: WFLY-6271 > URL: https://issues.jboss.org/browse/WFLY-6271 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7208) Integration of Web-Services with transactions during the graceful shutdown

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-7208?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-7208: -------------------------------- Summary: Integration of Web-Services with transactions during the graceful shutdown (was: Integration with transactions during the graceful shutdown) > Integration of Web-Services with transactions during the graceful shutdown > -------------------------------------------------------------------------- > > Key: WFLY-7208 > URL: https://issues.jboss.org/browse/WFLY-7208 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Reporter: Gytis Trikleris > Assignee: Alessio Soldano > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > During the graceful shutdown Web Services subsystem should consult XTS subsystem whether the requests should be rejected or not. Transaction subsystem would check for availability of WS-AT or WS-BA transaction and return the outcome. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7207) Integration of EJB with transactions during the graceful shutdown

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-7207?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-7207: -------------------------------- Summary: Integration of EJB with transactions during the graceful shutdown (was: Integration with transactions during the graceful shutdown) > Integration of EJB with transactions during the graceful shutdown > ----------------------------------------------------------------- > > Key: WFLY-7207 > URL: https://issues.jboss.org/browse/WFLY-7207 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Gytis Trikleris > Assignee: David Lloyd > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > During the graceful shutdown EJB subsystem should consult Transactions subsystem whether the requests should be rejected or not. Transaction subsystem would check for availability of JTA or JTS transaction and return the outcome. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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