January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on WFLY-4171: ---------------------------------------- New repository that contains blank archetype and fixed HTML5 banner: https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4255) Allow Arquillian to specify a timeout value for the Wildfly clean shutdown mechanism when shutting down a server.

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/WFLY-4255?page=com.atlassian.jira.plugin.... ] Aslak Knutsen moved ARQ-1901 to WFLY-4255: ------------------------------------------ Project: WildFly (was: Arquillian) Key: WFLY-4255 (was: ARQ-1901) Component/s: Test Suite (was: JBoss AS Containers) > Allow Arquillian to specify a timeout value for the Wildfly clean shutdown mechanism when shutting down a server. > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4255 > URL: https://issues.jboss.org/browse/WFLY-4255 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Richard Achmatowicz > > Wildfly has a clean shutdown mechanism which can be used to shutdown a server from the command line so that requests active at the time of shutdown get a chance to complete: > {code} > [standalone@localhost:9990 /] :shutdown(timeout=5) > {"outcome" => "success"} > {code} > Provide access to this feature from an Arquillian test case so that test cases may test with or without clean shutdown enabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4255) Allow Arquillian to specify a timeout value for the Wildfly clean shutdown mechanism when shutting down a server.

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/WFLY-4255?page=com.atlassian.jira.plugin.... ] Aslak Knutsen reassigned WFLY-4255: ----------------------------------- Assignee: Radoslav Husar > Allow Arquillian to specify a timeout value for the Wildfly clean shutdown mechanism when shutting down a server. > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4255 > URL: https://issues.jboss.org/browse/WFLY-4255 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Richard Achmatowicz > Assignee: Radoslav Husar > > Wildfly has a clean shutdown mechanism which can be used to shutdown a server from the command line so that requests active at the time of shutdown get a chance to complete: > {code} > [standalone@localhost:9990 /] :shutdown(timeout=5) > {"outcome" => "success"} > {code} > Provide access to this feature from an Arquillian test case so that test cases may test with or without clean shutdown enabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] Tom Jenkinson edited comment on JBJCA-1244 at 1/15/15 12:33 PM: ---------------------------------------------------------------- I have produced a patch that can handle this case for all JDBC resource adapters that are compliant with the SQL States in the SQL specification: http://pubs.opengroup.org/onlinepubs/9695959099/toc.pdf: https://github.com/tomjenkinson/ironjacamar/compare/ironjacamar:1.0...tom... (EDIT removed reference to specific commit) was (Author: tomjenkinson): I have produced a patch that can handle this case for all JDBC resource adapters that are compliant with the SQL States in the SQL specification: http://pubs.opengroup.org/onlinepubs/9695959099/toc.pdf: https://github.com/tomjenkinson/ironjacamar/compare/ironjacamar:1.0...tom... Specifically it is commit: https://github.com/tomjenkinson/ironjacamar/commit/de0d740ad1aec305d97049... > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBJCA-1244: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1181132 > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated JBJCA-1244: --------------------------------- Forum Reference: https://developer.jboss.org/message/916075 > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBJCA-1244: ------------------------------------ Summary: LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification Key: JBJCA-1244 URL: https://issues.jboss.org/browse/JBJCA-1244 Project: IronJacamar Issue Type: Bug Affects Versions: 1.0.30.Final Reporter: Tom Jenkinson Assignee: Jesper Pedersen The XA specification states the following about the RBROLLBACK error code for xa_commit(): {quote} [XA_RB∗] The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: [XA_RBROLLBACK] The resource manager rolled back the transaction branch for an unspecified reason {quote} It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: {quote} [XAER_RMFAIL] An error occurred that makes the resource manager unavailable. {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on JBJCA-1244: -------------------------------------- Further information that is pertinent to the implementation of this defect is that after discussion with Jesper on the forum, the reason that LocalXAResourceImpl has difficulty in determining the underlying cause of the rollback exception is that the errorcode parameter in LocalTransactionException does not have a defined value to indicate communication issues so a way to formalise this code should be found: https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.0.30.Final/... > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on JBJCA-1244: -------------------------------------- Further information that is pertinent to the effect of this defect is if we consider the following pseudo code test case: 1. xar.start(xid) 2. conn.insert(foo) 3. xar.end(xid) 4. xar.commit(xid, true) If a communication failure pre-commit or post-commit on the remote resource manager occurs then LocalXAResourceImpl will return RBROLLBACK which contravenes XA. It should return RMFAIL here. If RBROLLBACK is returned this must evaluate to true but in the case of a comms issue on the return of the call then it would fail: assertTrue(conn2.query(foo == null)) In more concrete terms this results in a critical defect on the CMR functionality of EAP as the error code of the XAR is used to dictate the remaining XAResources. Although it is accepted that RMFAIL if the commit failed in comms precommit would result in the rest of the XAR committing even though the CMR did not, this is a known effect of XA and JTA and the recovery manager is designed to detect this scenario and alert the user to the now determined heuristic outcome of the transaction. > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on JBJCA-1244: -------------------------------------- I have produced a patch that can handle this case for all JDBC resource adapters that are compliant with the SQL States in the SQL specification: http://pubs.opengroup.org/onlinepubs/9695959099/toc.pdf: https://github.com/tomjenkinson/ironjacamar/compare/ironjacamar:1.0...tom... Specifically it is commit: https://github.com/tomjenkinson/ironjacamar/commit/de0d740ad1aec305d97049... > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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 January 2015