March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7337) Introduce an authorization SPI

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-7337?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on WFLY-7337: ---------------------------------------- [~dmlloyd] This list of requirements refer to state changes in a transactions and in resources. Please could provide more detail about why these are needed (preferably on an event by event basis). Also you say that the list is incomplete, do you have a view about which kind of future event may be of interest. > Introduce an authorization SPI > ------------------------------ > > Key: WFLY-7337 > URL: https://issues.jboss.org/browse/WFLY-7337 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: David Lloyd > Assignee: Amos Feng > > We need an SPI that can be invoked to authorize state changes in a transaction. The method(s) should make it clear in some way which operation is being authorized, and it must run from the same thread as the thread which instigates the state change. > It must be possible to register an implementation of the SPI when the container starts up or acquires the transaction manager. > The operations that should provide authorization checks include, but are not limited to: > * begin > * rollback > * prepare > * forget > * commit (one or two phase) > * recover > Thanks! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1341) Account for additional DB2 FATAL connection errors

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1341?page=com.atlassian.jira.plugin... ] Ingo Weiss updated JBJCA-1341: ------------------------------ Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/606, https://github.com/ironjacamar/ironjacamar/pull/607, https://github.com/ironjacamar/ironjacamar/pull/608 (was: https://github.com/ironjacamar/ironjacamar/pull/606, https://github.com/ironjacamar/ironjacamar/pull/607) > Account for additional DB2 FATAL connection errors > -------------------------------------------------- > > Key: JBJCA-1341 > URL: https://issues.jboss.org/browse/JBJCA-1341 > Project: IronJacamar > Issue Type: Enhancement > Components: Validator > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such. > One example would be the -99999 error that indicates "Connection is closed" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-148) Support suppressed exceptions in log formatting

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-148?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-148: --------------------------------- Description: In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. This JIRA was created to track a back port of the JDK 7 enhancement to support suppressed exceptions to the 1.5.x branch which requires JDK 6. This will introduce a new requirement that the 1.5 branch will require JDK 7 to compile, but will still work on JDK 6. was:In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. > Support suppressed exceptions in log formatting > ----------------------------------------------- > > Key: LOGMGR-148 > URL: https://issues.jboss.org/browse/LOGMGR-148 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 1.5.7.Final > > > In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. > This JIRA was created to track a back port of the JDK 7 enhancement to support suppressed exceptions to the 1.5.x branch which requires JDK 6. This will introduce a new requirement that the 1.5 branch will require JDK 7 to compile, but will still work on JDK 6. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-148) Support suppressed exceptions in log formatting

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-148?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-148: --------------------------------- Fix Version/s: 1.5.7.Final (was: 2.0.0.Final) > Support suppressed exceptions in log formatting > ----------------------------------------------- > > Key: LOGMGR-148 > URL: https://issues.jboss.org/browse/LOGMGR-148 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 1.5.7.Final > > > In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-148) Support suppressed exceptions in log formatting

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-148?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-148: --------------------------------- Git Pull Request: (was: https://github.com/jboss-logging/jboss-logmanager/pull/73) > Support suppressed exceptions in log formatting > ----------------------------------------------- > > Key: LOGMGR-148 > URL: https://issues.jboss.org/browse/LOGMGR-148 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 1.5.7.Final > > > In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-148) Support suppressed exceptions in log formatting

by James Perkins (JIRA)

James Perkins created LOGMGR-148: ------------------------------------ Summary: Support suppressed exceptions in log formatting Key: LOGMGR-148 URL: https://issues.jboss.org/browse/LOGMGR-148 Project: JBoss Log Manager Issue Type: Feature Request Components: core Reporter: David Lloyd Assignee: James Perkins Fix For: 2.0.0.Final In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-147) Create an option for the ExtHandler to not close children handlers

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-147?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-147: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/104, https://github.com/jboss-logging/jboss-logmanager/pull/105 (was: https://github.com/jboss-logging/jboss-logmanager/pull/104) > Create an option for the ExtHandler to not close children handlers > ------------------------------------------------------------------ > > Key: LOGMGR-147 > URL: https://issues.jboss.org/browse/LOGMGR-147 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.0.6.Final, 2.1.0.Beta1 > > > In some environments it may not be desirable for the child handlers to be closed when the parent handler is closed. As an example in WildFly if an {{AsyncHandler}} is added with child handlers, then removed those child handlers can no longer be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-147) Create an option for the ExtHandler to not close children handlers

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-147?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-147: --------------------------------- Fix Version/s: 2.0.6.Final 2.1.0.Beta1 > Create an option for the ExtHandler to not close children handlers > ------------------------------------------------------------------ > > Key: LOGMGR-147 > URL: https://issues.jboss.org/browse/LOGMGR-147 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.0.6.Final, 2.1.0.Beta1 > > > In some environments it may not be desirable for the child handlers to be closed when the parent handler is closed. As an example in WildFly if an {{AsyncHandler}} is added with child handlers, then removed those child handlers can no longer be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1341) Account for additional DB2 FATAL connection errors

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1341?page=com.atlassian.jira.plugin... ] Ingo Weiss updated JBJCA-1341: ------------------------------ Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/606, https://github.com/ironjacamar/ironjacamar/pull/607 (was: https://github.com/ironjacamar/ironjacamar/pull/606) > Account for additional DB2 FATAL connection errors > -------------------------------------------------- > > Key: JBJCA-1341 > URL: https://issues.jboss.org/browse/JBJCA-1341 > Project: IronJacamar > Issue Type: Enhancement > Components: Validator > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such. > One example would be the -99999 error that indicates "Connection is closed" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8339) Upgrade Narayana to 5.5.4.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-8339: ----------------------------------- Summary: Upgrade Narayana to 5.5.4.Final Key: WFLY-8339 URL: https://issues.jboss.org/browse/WFLY-8339 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson https://issues.jboss.org/projects/JBTM/versions/12333853 https://github.com/jbosstm/narayana/compare/5.5.3.Final...5.5.4.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017