From issues at jboss.org Mon Nov 3 09:15:40 2014 From: issues at jboss.org (Jesper Pedersen (JIRA)) Date: Mon, 3 Nov 2014 09:15:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: Jesper Pedersen created JBTM-2282: ------------------------------------- Summary: IllegalStateException from periodic recovery Key: JBTM-2282 URL: https://issues.jboss.org/browse/JBTM-2282 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.0.3 Reporter: Jesper Pedersen Assignee: Michael Musgrove Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 09:15:41 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Nov 2014 09:15:41 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2282: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1032641 > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 09:16:35 2014 From: issues at jboss.org (SBS JIRA Integration (JIRA)) Date: Mon, 3 Nov 2014 09:16:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated JBTM-2282: --------------------------------------- Forum Reference: https://developer.jboss.org/message/908887#908887 > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 09:52:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Nov 2014 09:52:36 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016807#comment-13016807 ] RH Bugzilla Integration commented on JBTM-2282: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1032641|https://bugzilla.redhat.com/show_bug.cgi?id=1032641] from ASSIGNED to VERIFIED > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 09:55:35 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 3 Nov 2014 09:55:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016808#comment-13016808 ] Michael Musgrove commented on JBTM-2282: ---------------------------------------- Whilst fixing the related JIRA I did notice a locking issue which I fixed at the time. The fix went into release 4.17.23 and am awaiting a retest. > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 09:58:36 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Nov 2014 09:58:36 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016810#comment-13016810 ] Tom Jenkinson commented on JBTM-2282: ------------------------------------- Hi Jesper, I am not saying its not an issue but the ISE is coming out of IJ/connector isn't it? Caused by: java.lang.IllegalStateException at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.driverClassLoader(AbstractDataSourceService.java:246) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.access$200(AbstractDataSourceService.java:93) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer$1.getClassLoader(AbstractDataSourceService.java:396) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:634) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:497) Tom > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 10:00:36 2014 From: issues at jboss.org (Jesper Pedersen (JIRA)) Date: Mon, 3 Nov 2014 10:00:36 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016813#comment-13016813 ] Jesper Pedersen commented on JBTM-2282: --------------------------------------- Yes, because the datasource is inactive, but recovery is still running > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 10:05:38 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 3 Nov 2014 10:05:38 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2282) IllegalStateException from periodic recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2282. ------------------------------------ Resolution: Duplicate Issue Issue fixed in JBTM-2242 > IllegalStateException from periodic recovery > -------------------------------------------- > > Key: JBTM-2282 > URL: https://issues.jboss.org/browse/JBTM-2282 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.0.3 > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 18:20:35 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 3 Nov 2014 18:20:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2283: -------------------------------------- Summary: Tooling no longer exposes JTS record types Key: JBTM-2283 URL: https://issues.jboss.org/browse/JBTM-2283 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.0.3, 4.17.23 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.24, 5.0.4 Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 18:25:35 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 3 Nov 2014 18:25:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2283: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/756 > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 18:26:35 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Nov 2014 18:26:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2283: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1151071 > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 05:59:35 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Nov 2014 05:59:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017069#comment-13017069 ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- Gytis Trikleris changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from NEW to ASSIGNED > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 06:09:36 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Nov 2014 06:09:36 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2280) alternative to JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2280. --------------------------------- Resolution: Rejected Rejecting as the direct recoverable connection should work. If not, please raise a Jira/discussion against that feature. > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 06:42:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Nov 2014 06:42:37 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017098#comment-13017098 ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- Michael changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from NEW to ASSIGNED > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 12:44:35 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 4 Nov 2014 12:44:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2283: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/756, https://github.com/jbosstm/narayana/pull/757 (was: https://github.com/jbosstm/narayana/pull/756) > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Nov 5 06:59:35 2014 From: issues at jboss.org (SBS JIRA Integration (JIRA)) Date: Wed, 5 Nov 2014 06:59:35 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2280) alternative to JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated JBTM-2280: --------------------------------------- Forum Reference: https://developer.jboss.org/message/909177#909177 > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Nov 5 16:22:30 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 5 Nov 2014 16:22:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017647#comment-13017647 ] Mark Little commented on JBTM-2283: ----------------------------------- Can you expand on this JIRA to say why they're no longer exposed ;-) ? > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 05:17:29 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 6 Nov 2014 05:17:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017737#comment-13017737 ] Michael Musgrove commented on JBTM-2283: ---------------------------------------- The tooling maintained a map between record types and type names. Then, for each record type there is a bean that is responsible for exposing info about an instance of that record type (another map). To simplify things I condensed the two maps to a collection of tuples (record type, bean type, typename). When I did the refactor I lost the typename for JTS record types. I fixed that and added a test to catch any further oversights. > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 10:31:30 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 6 Nov 2014 10:31:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017957#comment-13017957 ] Mark Little commented on JBTM-2283: ----------------------------------- Thanks. That's a much better description and makes it easier for people in the future to understand what you were doing. Unless a JIRA title is really self explanatory (this one isn't) let's keep the Description field as informative as possible (this one wasn't). > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 05:00:30 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Nov 2014 05:00:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018179#comment-13018179 ] Michael Musgrove commented on JBTM-2283: ---------------------------------------- I normally do do good descriptions but in this case the bugzilla said it all. But I hear what you are saying and a precis of the linked bugzilla would have helped here to keep the JIRA self contained. Mike -- Michael Musgrove Transactions Team e: mmusgrov at redhat.com t: +44 191 243 0870 Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland) > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 05:03:30 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Nov 2014 05:03:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018179#comment-13018179 ] Michael Musgrove edited comment on JBTM-2283 at 11/7/14 5:02 AM: ----------------------------------------------------------------- I normally do do good descriptions but in this case the bugzilla said it all. But I hear what you are saying and a precis of the linked bugzilla would have helped here to keep the JIRA self contained. was (Author: mmusgrov): I normally do do good descriptions but in this case the bugzilla said it all. But I hear what you are saying and a precis of the linked bugzilla would have helped here to keep the JIRA self contained. Mike -- Michael Musgrove Transactions Team e: mmusgrov at redhat.com t: +44 191 243 0870 Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland) > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 09:04:30 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 7 Nov 2014 09:04:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2238) Tooling does not expose CMR records In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018292#comment-13018292 ] RH Bugzilla Integration commented on JBTM-2238: ----------------------------------------------- Hayk Hovsepyan changed the Status of [bug 1113225|https://bugzilla.redhat.com/show_bug.cgi?id=1113225] from POST to VERIFIED > Tooling does not expose CMR records > ----------------------------------- > > Key: JBTM-2238 > URL: https://issues.jboss.org/browse/JBTM-2238 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > CMR resources are not being exposed as MBeans via the (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser) tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 10 08:18:30 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 10 Nov 2014 08:18:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2110: ----------------------------------- Fix Version/s: 6.0.0 (was: 5.0.4) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 10 09:21:29 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 10 Nov 2014 09:21:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2250: ----------------------------------- Attachment: 2235.jstack soatest (Nov 10th) > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:24 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Nov 2014 09:33:24 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018645#comment-13018645 ] Michael Musgrove edited comment on JBTM-2250 at 11/10/14 9:28 AM: ------------------------------------------------------------------ console output (Nov 10th) from job http://172.17.130.106:8080/job/narayana/PROFILE=MAIN,jdk=jdk7.latest,label=mac/3/consoleFull was (Author: mmusgrov): soatest (Nov 10th) > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:48 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Nov 2014 09:33:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) Soatest node runs out of memory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018682#comment-13018682 ] Tom Jenkinson commented on JBTM-2277: ------------------------------------- You can disable the warning by putting this:-XX:-UseGCOverheadLimit however when you do this the build hangs. If you jstack it you get: {quote} [tom at TOM-PC narayana](Bash-fu)(13:37:11) $ jstack 8396 2014-11-10 14:55:54 Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode): "Service Thread" daemon prio=6 tid=0x000000000a758000 nid=0x20c4 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "C2 CompilerThread1" daemon prio=10 tid=0x00000000098cd800 nid=0xff8 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "C2 CompilerThread0" daemon prio=10 tid=0x00000000098c8000 nid=0x7f4 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Attach Listener" daemon prio=10 tid=0x00000000098c7800 nid=0x2018 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" daemon prio=10 tid=0x00000000098c6800 nid=0x1e34 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Finalizer" daemon prio=8 tid=0x000000000261a000 nid=0xbc8 in Object.wait() [0x000000000bc6e000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000d3c9b8e0> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) - locked <0x00000000d3c9b8e0> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) "Reference Handler" daemon prio=10 tid=0x0000000002619000 nid=0x1b7c runnable [0x000000000ba6f000] java.lang.Thread.State: RUNNABLE at java.lang.Object.notifyAll(Native Method) at java.lang.ref.ReferenceQueue.enqueue(ReferenceQueue.java:68) - locked <0x00000000d3c9b8e0> (a java.lang.ref.ReferenceQueue$Lock) - locked <0x00000000dbef56e0> (a java.lang.ref.Finalizer) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:146) "main" prio=6 tid=0x0000000002588000 nid=0x1550 runnable [0x000000000294d000] java.lang.Thread.State: RUNNABLE at org.apache.maven.model.Dependency.getManagementKey(Dependency.java:605) at org.apache.maven.model.merge.MavenModelMerger.getDependencyKey(MavenModelMerger.java:631) at org.apache.maven.model.management.DefaultDependencyManagementInjector$ManagementModelMerger.mergeManagedDependencies(DefaultDependencyManagementInjector.java:73) at org.apache.maven.model.management.DefaultDependencyManagementInjector.injectManagement(DefaultDependencyManagementInjector.java:50) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:429) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:398) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:389) at org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1106) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:427) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:398) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:389) at org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1106) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:427) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:398) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:389) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:159) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:118) at org.apache.maven.project.DefaultProjectBuilder.initProject(DefaultProjectBuilder.java:672) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:174) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) at org.codehaus.mojo.license.api.DefaultDependenciesTool.loadProjectDependencies(DefaultDependenciesTool.java:206) at org.codehaus.mojo.license.DownloadLicensesMojo.execute(DownloadLicensesMojo.java:256) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) "VM Thread" prio=10 tid=0x000000000a703800 nid=0x1bc4 runnable "GC task thread#0 (ParallelGC)" prio=6 tid=0x000000000259e800 nid=0x15e4 runnable "GC task thread#1 (ParallelGC)" prio=6 tid=0x00000000025a0800 nid=0xf68 runnable "GC task thread#2 (ParallelGC)" prio=6 tid=0x00000000025a2000 nid=0x1b0c runnable "GC task thread#3 (ParallelGC)" prio=6 tid=0x00000000025a3800 nid=0x21c4 runnable "GC task thread#4 (ParallelGC)" prio=6 tid=0x00000000025a7000 nid=0x236c runnable "GC task thread#5 (ParallelGC)" prio=6 tid=0x00000000025a8800 nid=0x1cd4 runnable "GC task thread#6 (ParallelGC)" prio=6 tid=0x00000000025a9800 nid=0x2004 runnable "GC task thread#7 (ParallelGC)" prio=6 tid=0x00000000025ab000 nid=0x15fc runnable "VM Periodic Task Thread" prio=10 tid=0x000000000a771000 nid=0x844 waiting on condition JNI global references: 251 {quote} > Soatest node runs out of memory > ------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:48 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Nov 2014 09:33:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2277: -------------------------------- Summary: GC Overhead issue when building WildFly Full Feature Pack (was: Soatest node runs out of memory) > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:49 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Nov 2014 09:33:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018683#comment-13018683 ] Tom Jenkinson commented on JBTM-2277: ------------------------------------- Interestingly it won't hang when you call: ./build.sh clean install -rf :wildfly-feature-pack -DskipTests > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:54 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Nov 2014 09:33:54 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018690#comment-13018690 ] Tom Jenkinson commented on JBTM-2277: ------------------------------------- Dies during: {code} [INFO] [INFO] --- maven-assembly-plugin:2.4.1:single (assemble) @ wildfly-feature-pack --- [INFO] Reading assembly descriptor: assembly.xml [INFO] Building zip: /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/feature-pack/target/wildfly-9.0.0.Alpha2-SNAPSHOT.zip [INFO] [INFO] --- license-maven-plugin:1.7:download-licenses (default) @ wildfly-feature-pack --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] {code} Hangs during: at org.codehaus.mojo.license.DownloadLicensesMojo.execute(DownloadLicensesMojo.java:256) Coincidence - I don't think so... > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:59 2014 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Tue, 11 Nov 2014 09:33:59 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018707#comment-13018707 ] Ond?ej Chaloupka commented on JBTM-2277: ---------------------------------------- >From what I can see the problem is caused by license plugin but I don't understand what is the cause. Adding "-Drelease=false -P!release" helped to me as skipping that phase. > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:33:59 2014 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Tue, 11 Nov 2014 09:33:59 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018707#comment-13018707 ] Ond?ej Chaloupka edited comment on JBTM-2277 at 11/10/14 10:42 AM: ------------------------------------------------------------------- Agree, from what I can see the problem is caused by license plugin but I don't understand what is the cause. Adding "-Drelease=false -P!release" helped to me as skipping that phase. was (Author: ochaloup): >From what I can see the problem is caused by license plugin but I don't understand what is the cause. Adding "-Drelease=false -P!release" helped to me as skipping that phase. > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:07 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Nov 2014 09:34:07 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2277: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/jboss-as/pull/35 The PR disables licence download - it should work for us but wouldn't get merged upstream :) > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:14 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Nov 2014 09:34:14 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2277: -------------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:14 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Nov 2014 09:34:14 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018727#comment-13018727 ] Michael Musgrove commented on JBTM-2277: ---------------------------------------- The oracle tuning guide (http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html) says: {quote} The parallel collector will throw an OutOfMemoryError if too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown {/quote} and then goes on to discuss the parallel garbage collector. Adding the following setting to the build resolves the issue: MAVEN_OPTS="-XX:+UseConcMarkSweepGC" > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:28 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Nov 2014 09:34:28 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2277: ----------------------------------- Git Pull Request: https://github.com/jbosstm/jboss-as/pull/35, https://github.com/jbosstm/narayana/pull/760 (was: https://github.com/jbosstm/jboss-as/pull/35) > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:01 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Nov 2014 09:36:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2279: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:22 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 11 Nov 2014 09:36:22 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018910#comment-13018910 ] Mark Little commented on JBTM-2279: ----------------------------------- Wouldn't it have been easier/better/less invasive to have hidden this within the call to getCheckedAction? _checkedAction = _checkedActionFactory.getCheckedAction(get_uid(), type()); + _checkedAction = allowCheckedActionFactoryToBeOverriden ? arjPropertyManager + .getCoordinatorEnvironmentBean().getCheckedActionFactory() + .getCheckedAction(get_uid(), type()) + : defaultCheckedActionFactory.getCheckedAction(get_uid(), + type()); > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:23 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 11 Nov 2014 09:36:23 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018910#comment-13018910 ] Mark Little edited comment on JBTM-2279 at 11/11/14 8:14 AM: ------------------------------------------------------------- Wouldn't it have been easier/better/less invasive to have hidden this within a call to something like getCheckedActionFactory()? _checkedAction = _checkedActionFactory.getCheckedAction(get_uid(), type()); + _checkedAction = allowCheckedActionFactoryToBeOverriden ? arjPropertyManager + .getCoordinatorEnvironmentBean().getCheckedActionFactory() + .getCheckedAction(get_uid(), type()) + : defaultCheckedActionFactory.getCheckedAction(get_uid(), + type()); was (Author: marklittle): Wouldn't it have been easier/better/less invasive to have hidden this within the call to getCheckedAction? _checkedAction = _checkedActionFactory.getCheckedAction(get_uid(), type()); + _checkedAction = allowCheckedActionFactoryToBeOverriden ? arjPropertyManager + .getCoordinatorEnvironmentBean().getCheckedActionFactory() + .getCheckedAction(get_uid(), type()) + : defaultCheckedActionFactory.getCheckedAction(get_uid(), + type()); > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:51 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Nov 2014 09:36:51 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2277) GC Overhead issue when building WildFly Full Feature Pack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2277: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > GC Overhead issue when building WildFly Full Feature Pack > --------------------------------------------------------- > > Key: JBTM-2277 > URL: https://issues.jboss.org/browse/JBTM-2277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-AS800/628/ > {code} > [ERROR] GC overhead limit exceeded -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 04:28:29 2014 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Wed, 12 Nov 2014 04:28:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array In-Reply-To: References: Message-ID: Christian von Kutzleben created JBTM-2284: --------------------------------------------- Summary: XID.toString broken: indexing mistake in array Key: JBTM-2284 URL: https://issues.jboss.org/browse/JBTM-2284 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 4.17.15 Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 Reporter: Christian von Kutzleben Assignee: Tom Jenkinson com.arjuna.ats.internal.jta.xa.XID public String toString () { //... stringBuilder.append(", "); for (int i = 0; i < bqual_length; i++) { stringBuilder.append(gtrid_length+data[i]); } //... } correct: stringBuilder.append(data[i+gtrid_length]); The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 05:03:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Nov 2014 05:03:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019252#comment-13019252 ] Tom Jenkinson commented on JBTM-2284: ------------------------------------- My apologies, it looks like we forgot to backport the fix for this useful bugfix. I have done that now. Fix on master: https://github.com/jbosstm/narayana/commit/6e8435a3175f6bc583b3af71c58def4f5f6b99b3 Fix on 4.17: https://github.com/jbosstm/narayana/commit/23a72786efacd3ee0a5889c7f25f51b1128ec952 > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 05:03:30 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Nov 2014 05:03:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2284: -------------------------------- Fix Version/s: 4.17.24 > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 05:04:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Nov 2014 05:04:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2284. --------------------------------- Resolution: Done > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 06:27:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Nov 2014 06:27:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2264) Error enlisting second xa resource on the same oracle instance but other schema In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2264: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I have merged this into master now. Thanks for the report! > Error enlisting second xa resource on the same oracle instance but other schema > ------------------------------------------------------------------------------- > > Key: JBTM-2264 > URL: https://issues.jboss.org/browse/JBTM-2264 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.0.3 > Reporter: Evgeniy Smelik > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > Attachments: sscce.zip, sscce.zip, test.log > > > I've got an exception {{java.sql.SQLException: ConnectionImple.registerDatabase - ARJUNA017017: enlist of resource failed}} while preparing statement in the second connection within the same oracle instance but other schema. > Whole stack trace: > {noformat} > oracle.jdbc.xa.OracleXAException > at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110) > at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:741) > at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:983) > at com.arjuna.ats.internal.jdbc.ConnectionImple.prepareStatement(ConnectionImple.java:179) > at SimpleJdbcTest.insert(SimpleJdbcTest.java:46) > at SimpleJdbcTest.main(SimpleJdbcTest.java:36) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) > java.sql.SQLException: ConnectionImple.registerDatabase - ARJUNA017017: enlist of resource failed > at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:1003) > at com.arjuna.ats.internal.jdbc.ConnectionImple.prepareStatement(ConnectionImple.java:179) > at SimpleJdbcTest.insert(SimpleJdbcTest.java:46) > at SimpleJdbcTest.main(SimpleJdbcTest.java:36) > {noformat} > (Detail log and SSCCE are attached). > I use jboss transaction manager in standaloine application just to test jboss JTA implementation. The same code works well if one and second data sources use own (different) database instances. > I note that atomikos and bitronix JTA implementation works correctly in the same environment irrespectively single oracle instance is used or not. > I found similar problem [here|http://stackoverflow.com/questions/23617179/jboss-6-1-unable-to-get-connection-from-pool]. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 06:29:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Nov 2014 06:29:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2278) Allow the transaction manager suspend operation to succeed for JTS mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2278: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Allow the transaction manager suspend operation to succeed for JTS mode > ----------------------------------------------------------------------- > > Key: JBTM-2278 > URL: https://issues.jboss.org/browse/JBTM-2278 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > It is not possible to perform TransactionManager::suspend operation during an afterCompletion call when the server is configured for JTS and has JacORB configured with interposition interceptors. This is because the transaction has not been used on the thread yet and when OTSManager.current() operation finds the PropagationContext in PICurrent to tries to recreate the hierarchy and ArjunaTransactionImple register_resource detects the transaction is no longer active so throws an Inactive exception causing suspend to fail. > SystemException is a valid response code from suspend but it would be desirable to try to avoid this when the transaction is local to the Synchronization. > Allowing suspend means this code would work: > public afterCompletion(status) { > tm.suspend() > tm.begin() > tm.commit() > } -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:05:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:05:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2285: ------------------------------------- Summary: Missing specs upload to the web page Key: JBTM-2285 URL: https://issues.jboss.org/browse/JBTM-2285 Project: JBoss Transaction Manager Issue Type: Task Components: Documentation Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.4 Attachments: IntegrationGuide.odt, IntegrationGuide.pdf -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:05:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:05:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2285: ---------------------------------- Description: Upload the attached files somewhere, so that they could be accesses from our web page > Missing specs upload to the web page > ------------------------------------ > > Key: JBTM-2285 > URL: https://issues.jboss.org/browse/JBTM-2285 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > Attachments: IntegrationGuide.odt, IntegrationGuide.pdf > > > Upload the attached files somewhere, so that they could be accesses from our web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:05:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:05:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2285: ---------------------------------- Attachment: IntegrationGuide.odt IntegrationGuide.pdf > Missing specs upload to the web page > ------------------------------------ > > Key: JBTM-2285 > URL: https://issues.jboss.org/browse/JBTM-2285 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > Attachments: IntegrationGuide.odt, IntegrationGuide.pdf > > > Upload the attached files somewhere, so that they could be accesses from our web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:07:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:07:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2285: ---------------------------------- Attachment: REST-Atomic_v2_draft_8_comments_sept_4.pdf RESTAT-v2-latest.pdf > Missing specs upload to the web page > ------------------------------------ > > Key: JBTM-2285 > URL: https://issues.jboss.org/browse/JBTM-2285 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > Attachments: IntegrationGuide.odt, IntegrationGuide.pdf, REST-Atomic_v2_draft_8_comments_sept_4.pdf, RESTAT-v2-latest.pdf > > > Upload the attached files somewhere, so that they could be accesses from our web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:08:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:08:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019396#comment-13019396 ] Gytis Trikleris commented on JBTM-2285: --------------------------------------- GitHub should be ok for storing them > Missing specs upload to the web page > ------------------------------------ > > Key: JBTM-2285 > URL: https://issues.jboss.org/browse/JBTM-2285 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > Attachments: BAFrameworkUpdated.odt, IntegrationGuide.odt, IntegrationGuide.pdf, REST-Atomic_v2_draft_8_comments_sept_4.pdf, RESTAT-v2-latest.pdf > > > Upload the attached files somewhere, so that they could be accesses from our web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:08:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:08:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2285: ---------------------------------- Attachment: BAFrameworkUpdated.odt > Missing specs upload to the web page > ------------------------------------ > > Key: JBTM-2285 > URL: https://issues.jboss.org/browse/JBTM-2285 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > Attachments: BAFrameworkUpdated.odt, IntegrationGuide.odt, IntegrationGuide.pdf, REST-Atomic_v2_draft_8_comments_sept_4.pdf, RESTAT-v2-latest.pdf > > > Upload the attached files somewhere, so that they could be accesses from our web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 09:34:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 09:34:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2285) Missing specs upload to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris deleted JBTM-2285: ---------------------------------- > Missing specs upload to the web page > ------------------------------------ > > Key: JBTM-2285 > URL: https://issues.jboss.org/browse/JBTM-2285 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Upload the attached files somewhere, so that they could be accesses from our web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 11:08:29 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Nov 2014 11:08:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Merge javadocs In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2286: ------------------------------------- Summary: Merge javadocs Key: JBTM-2286 URL: https://issues.jboss.org/browse/JBTM-2286 Project: JBoss Transaction Manager Issue Type: Task Components: Documentation Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.4 Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 12:25:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Nov 2014 12:25:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Merge javadocs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2286: -------------------------------- Description: Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. was:Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. > Merge javadocs > -------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 12:28:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 12 Nov 2014 12:28:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2188) Some code that writes to the file store is missing PrivilidgedAction blocks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019499#comment-13019499 ] RH Bugzilla Integration commented on JBTM-2188: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1162882|https://bugzilla.redhat.com/show_bug.cgi?id=1162882] from NEW to ASSIGNED > Some code that writes to the file store is missing PrivilidgedAction blocks > --------------------------------------------------------------------------- > > Key: JBTM-2188 > URL: https://issues.jboss.org/browse/JBTM-2188 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.0.3 > > > This means the code can fail when a security manager is present, as if deployment code is on the call stack it will not be able to write or read from the files. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 14:18:29 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 12 Nov 2014 14:18:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Merge javadocs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019524#comment-13019524 ] Mark Little commented on JBTM-2286: ----------------------------------- Two questions: 1) is this being driven by any customer/community request? 2) presumably the javadocs generated will always depend upon the build you perform, e.g., JTS doesn't get covered if I'm only building core? > Merge javadocs > -------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 04:31:31 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Nov 2014 04:31:31 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2286: -------------------------------- Summary: Create a zip with all javadocs included (was: Merge javadocs) > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 04:32:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Nov 2014 04:32:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2286: -------------------------------- Description: Currently javadocs are split by component. It would be more convenient to produce a single bundle of javadocs of all project as well. What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. was: Currently javadocs are split by component. It would be more convenient to have one bundle of javadocs of all project. What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be more convenient to produce a single bundle of javadocs of all project as well. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 04:33:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Nov 2014 04:33:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019622#comment-13019622 ] Tom Jenkinson commented on JBTM-2286: ------------------------------------- Hi Mark, I clarified the description a bit. Its an addition, not a replacement of the existing standalone set. Its for ease of publishing on the site. Hope you agree it would be beneficial for that. Thanks, Tom > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be more convenient to produce a single bundle of javadocs of all project as well. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 06:34:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Nov 2014 06:34:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2286: -------------------------------- Description: Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. was: Currently javadocs are split by component. It would be more convenient to produce a single bundle of javadocs of all project as well. What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 08:26:29 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 13 Nov 2014 08:26:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2283: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 09:12:29 2014 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Thu, 13 Nov 2014 09:12:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: Christian von Kutzleben created JBTM-2287: --------------------------------------------- Summary: JTS recovery module forgets about transaction -> transaction never recovered Key: JBTM-2287 URL: https://issues.jboss.org/browse/JBTM-2287 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 4.17.15 Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 Reporter: Christian von Kutzleben Assignee: Tom Jenkinson The scenario is as follows (and works fine with JTA, see below): Two XAResources in the same transaction, with xid1 and xid2, respectively. (For better readability, log file excerpts are referenced and provided at the end of the description.) start xid1 start xid2 end xid1, tmsuccess prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case end xid1, tmfail -> against XA protocol, however silently ignored by us [error1 printed in log file] end xid2, tmfail rollback xid2 [error2 printed in log file] [JTS: periodic, but fruitless recovery attempts] as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction with JTA the call sequence is as follows: start xid1 start xid2 end xid1, tmsuccess prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case rollback xid1 //this races with recovery module, but in any case, will be rolled back end xid2, tmfail rollback xid2 [JTA: periodic, successfull recovery] With JTA, rollback might even be triggered twice (second invocation ignored by us) here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) [JTA: periodic, successfull recovery] 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > [JTS: periodic, but fruitless recovery attempts] 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 [error1] 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] [error2] 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 10:30:31 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 13 Nov 2014 10:30:31 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019798#comment-13019798 ] Mark Little commented on JBTM-2286: ----------------------------------- ok > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 10:41:31 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 13 Nov 2014 10:41:31 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019805#comment-13019805 ] Mark Little commented on JBTM-2287: ----------------------------------- Yes, we should set the _prepared to true in jts.XAResourceRecord.prepare - we skip it because it happens in createState and we don't create any state (log) in this case, but we still need to remember we've been through this method. That will also stop the second call to end and then the subsequent call to rollback should work. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 04:27:29 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 14 Nov 2014 04:27:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019969#comment-13019969 ] Michael Musgrove commented on JBTM-2287: ---------------------------------------- Marks fix should trigger the rollback but I would still like to understand why xid1 isn't being picked up by our "orphan detection" filters: the standard XA recovery module has asked com.versant.odbms.XARecoveryResource for the pending xid and when we find it's one of ours and that we don't have a log for then we run it through registered "orphan filters" which should result in a roll back. Would it be possible for you to provide more information about what's happening in the logs (at trace level) around about one of our calls to your recovery resource: {quote} 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. {quote} > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 04:45:30 2014 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 14 Nov 2014 04:45:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019980#comment-13019980 ] Christian von Kutzleben commented on JBTM-2287: ----------------------------------------------- @Michael: here is the entire log file output (it's not that long), from the bean invocation which (artificially) kills the database, after prepare, before returning the result; up to a successful bean invocation after the database has been restarted automatically after the crash and after that the recovery attempts. Let me know, if you need more information. Note, that Xids logged by us in this output use a different toString() because of JBTM-2284 09:59:45,005 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 4) start flags=TMNOFLAGS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:45,006 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 4) start created Versant TxnId 5641.0.4109 for Xid 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:45,012 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 4) start flags=TMNOFLAGS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.76.0.0.0.0.0.0.0.0 09:59:45,012 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 4) start created Versant TxnId 5642.0.4106 for Xid 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.76.0.0.0.0.0.0.0.0 09:59:45,044 INFO [stdout] (EJB default - 4) About to terminate db server 0 09:59:45,047 INFO [stdout] (EJB default - 4) Crashhook set. 09:59:45,054 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) end flags=TMSUCCESS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:45,055 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) prepare xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:46,890 WARN [com.arjuna.ats.jtax] (RequestProcessor-5) ARJUNA024015: XAResource prepare failed on resource com.versant.odbms.XAResourceImpl at 2eed27ad for transaction < 131072, 29, 36, 0000000000-1-1101065041-50-615010084100114-110007049, 292929292929292929292828391357970-21-327912911312914318292929997829292929292929 > with: XAException.XAER_RMFAIL: com.versant.odbms.VersantXAException: Prepare error: Network error on database [jpadb1 at localhost]. at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:650) at com.versant.odbms.XAResourceImpl.prepare(XAResourceImpl.java:409) at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.prepare(XAResourceRecord.java:234) [jbossjts-jacorb-4.17.15.Final-redhat-5.jar:4.17.15.Final-redhat-5] at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:81) [jbossjts-jacorb-4.17.15.Final-redhat-5.jar:4.17.15.Final-redhat-5] at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] Caused by: com.versant.odbms.DatastoreException: Network error on database [jpadb1 at localhost]. at com.versant.odbms.Connection$30.getOrThrow(Connection.java:597) at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:623) ... 6 more Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) [rt.jar:1.7.0_25] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) [rt.jar:1.7.0_25] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225) [rt.jar:1.7.0_25] at sun.nio.ch.IOUtil.read(IOUtil.java:193) [rt.jar:1.7.0_25] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:375) [rt.jar:1.7.0_25] at com.versant.odbms.net.RPC.readAll(RPC.java:759) at com.versant.odbms.net.StreamedRPC.read(StreamedRPC.java:125) at com.versant.odbms.net.StreamedRPC.receive(StreamedRPC.java:114) at com.versant.odbms.SimpleConnection.doReceive(SimpleConnection.java:704) at com.versant.odbms.Connection$30.getOrThrow(Connection.java:593) ... 7 more 09:59:46,900 WARN [com.arjuna.ats.arjuna] (EJB default - 4) ARJUNA012073: BasicAction.End() - prepare phase of action-id 0:ffff0a6a3229:-313ccd9c:546472f5:46 failed. 09:59:46,900 WARN [com.arjuna.ats.arjuna] (EJB default - 4) ARJUNA012075: Action Aborting 09:59:46,901 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) end flags=TMFAIL xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:339) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:238) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:329) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] at org.jboss.threads.JBossThread.run(JBossThread.java:122) 09:59:46,910 WARN [jacorb.poa.controller] (RequestController-1) rid: 200 opname: _get_type_id cannot process request, because object doesn't exist 09:59:46,911 WARN [jacorb.poa.controller] (RequestController-1) rid: 200 opname: _get_type_id request rejected with exception: null 09:59:46,911 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022228: ExtendedResourceRecord.typeIs failed. Returning default value: 151 09:59:46,912 WARN [com.arjuna.ats.arjuna] (EJB default - 4) ARJUNA012091: Top-level abort of action 0:ffff0a6a3229:-313ccd9c:546472f5:46 received TwoPhaseOutcome.FINISH_ERROR from com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord 09:59:46,914 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) end flags=TMFAIL xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.76.0.0.0.0.0.0.0.0 09:59:46,914 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) rollback xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.76.0.0.0.0.0.0.0.0 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276) 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:339) 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:238) 09:59:46,965 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,965 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) 09:59:46,965 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,965 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) 09:59:46,966 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,966 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) 09:59:46,966 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,966 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) 09:59:46,967 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,967 ERROR [stderr] (EJB default - 4) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) 09:59:46,967 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,968 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) 09:59:46,968 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,968 ERROR [stderr] (EJB default - 4) at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) 09:59:46,968 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 09:59:46,969 ERROR [stderr] (EJB default - 4) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) 09:59:46,969 ERROR [stderr] (EJB default - 4) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) 09:59:46,969 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:329) 09:59:46,969 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) 09:59:46,969 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) 09:59:46,970 ERROR [stderr] (EJB default - 4) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 09:59:46,970 ERROR [stderr] (EJB default - 4) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 09:59:46,970 ERROR [stderr] (EJB default - 4) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 09:59:46,970 ERROR [stderr] (EJB default - 4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 09:59:46,970 ERROR [stderr] (EJB default - 4) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 09:59:46,970 ERROR [stderr] (EJB default - 4) at java.lang.Thread.run(Thread.java:724) 09:59:46,971 ERROR [stderr] (EJB default - 4) at org.jboss.threads.JBossThread.run(JBossThread.java:122) 09:59:46,971 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 4) JBAS014134: EJB Invocation failed on component ReconnectTestBean for method public abstract long[] com.versant.jpa.j2ee.jboss.beans.ReconnectTestBeanRemote.modifyAndStopDbBeforeCommit(com.versant.jpa.j2ee.jboss.entities.J2EEBook[],com.versant.jpa.foundation.Option,int): javax.ejb.EJBTransactionRolledbackException: Transaction rolled back at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:138) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:118) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:339) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:238) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:329) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: javax.transaction.RollbackException: org.omg.CORBA.TRANSACTION_ROLLEDBACK at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1324) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] ... 30 more 09:59:48,516 INFO [stdout] (EJB default - 5) * ADD: begin J2EEBook[0 / Programming In Scala] 09:59:48,593 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 5) start flags=TMNOFLAGS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.84.0.0.0.0.0.0.0.0 09:59:48,593 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 5) start created Versant TxnId 5641.0.19463 for Xid 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.84.0.0.0.0.0.0.0.0 09:59:48,601 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 5) start flags=TMNOFLAGS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.88.0.0.0.0.0.0.0.0 09:59:48,601 FINER [com.versant.odbms.XAResourceImpl] (EJB default - 5) start created Versant TxnId 5642.0.4108 for Xid 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.88.0.0.0.0.0.0.0.0 09:59:48,619 INFO [stdout] (EJB default - 5) * ADD: finish J2EEBook[1587800343624829960 / Programming In Scala] 09:59:48,624 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) end flags=TMSUCCESS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.84.0.0.0.0.0.0.0.0 09:59:48,625 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) prepare xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.84.0.0.0.0.0.0.0.0 09:59:48,744 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) end flags=TMSUCCESS xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.88.0.0.0.0.0.0.0.0 09:59:48,745 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) prepare xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.88.0.0.0.0.0.0.0.0 09:59:48,998 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) commit onePhase=false xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.84.0.0.0.0.0.0.0.0 09:59:49,097 FINER [com.versant.odbms.XAResourceImpl] (RequestProcessor-5) commit onePhase=false xid=131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.82.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.88.0.0.0.0.0.0.0.0 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 06:50:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 14 Nov 2014 06:50:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020009#comment-13020009 ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- Martin Simka changed the Status of [bug 1097166|https://bugzilla.redhat.com/show_bug.cgi?id=1097166] from CLOSED to NEW > Add a jdbc object store implementation for later revisions of MySQL driver > -------------------------------------------------------------------------- > > Key: JBTM-2121 > URL: https://issues.jboss.org/browse/JBTM-2121 > Project: JBoss Transaction Manager > Issue Type: Task > Affects Versions: 4.17.17, 5.0.1 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > commit 44553931 updated the MySQl driver to 5.1.28. > In this revision of the driver, it is reporting as mysql, not mysql_ab. It should be possible to duplicate our mysql_ab_driver to mysql_driver in order to catch both cases. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 07:04:30 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 14 Nov 2014 07:04:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020017#comment-13020017 ] Mark Little commented on JBTM-2287: ----------------------------------- Mike, we fail in prepare to there's no log. However, you're right in so much that recovery should eventually check the db and get the xid for the prepared resource. Since we don't have a log entry we should fall to presumed abort and roll it back. I'd like to know why JTA works and JTS doesn't. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 07:04:30 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 14 Nov 2014 07:04:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020017#comment-13020017 ] Mark Little edited comment on JBTM-2287 at 11/14/14 7:04 AM: ------------------------------------------------------------- Mike, we fail in prepare to there's no log. However, you're right in so much that recovery should eventually check the db and get the xid for the prepared resource. Since we don't have a log entry we should fall to presumed abort and roll it back. So you are correct in wondering why it doesn't kick in. I'd like to know why JTA works and JTS doesn't. was (Author: marklittle): Mike, we fail in prepare to there's no log. However, you're right in so much that recovery should eventually check the db and get the xid for the prepared resource. Since we don't have a log entry we should fall to presumed abort and roll it back. I'd like to know why JTA works and JTS doesn't. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 07:05:30 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Nov 2014 07:05:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020019#comment-13020019 ] Tom Jenkinson commented on JBTM-2287: ------------------------------------- I have written a test that even without Marks fix seems to work for a DummyXAResource: https://github.com/tomjenkinson/narayana/compare/jbosstm:master...tomjenkinson:JBTM2287?expand=1 Can you give a few more details of what you are expecting? Do all calls on this XAResource after the prepare failure fail until periodic recovery kicks in and uses a new XAResource instance which does have a connection to the database or is it really just the one call to prepare that is meant to be failing? > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 07:54:29 2014 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 14 Nov 2014 07:54:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020040#comment-13020040 ] Christian von Kutzleben commented on JBTM-2287: ----------------------------------------------- Tom, the XAResource itself remains functional, but all(*) subsequent calls will fail until the database has restarted and a connection can be reestablished, after that all calls should succeed again. (*) our provoked database crash/shutdown is not really atomic and with JTA we see that a rollback succeeds right after the failed prepare, and then the database is really shutdown I'm using 4.17.15 and I don't see a rollback invocation with JTS on our XAResource; even if rollback were called -- like in the JTA case --; rollback might report success, but the database might shut down right after that and upon restart, the transaction was revived by the database recovery system and waits for a decision by the TM. So what we expect from the fix is, that our recovery XAResource is advised to rollback this transaction. Specifically, even if you change something, so that now information is kept about this transactions outcome, it's hard for you to know, when you can drop this information, because a rollback might have been successfully issued to all XAResources, but because rollbacks are not f-synced in the database log and immediate crashing afterwards might revive these transactions as dead to-be-recovered transactions. Which means, if you don't keep information for this transaction for forever, then you should -- as Mike suggested -- presume abort. What we don't expect - but it would not harm either - is that rollback is called by the regular commit code. What we also don't expect - but it would be nice to have - is preventing the double end invocation. Btw. we have seen double-ends before, even with JTA, e.g. if the first end(tmsuccess) raises an XAException, then a second end(tmfail) is issued. Since we've found that out, we have a workaround in place to ignore double end invocations. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:03:29 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 14 Nov 2014 08:03:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2273) Admin CLI build failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng resolved JBTM-2273. ----------------------------- Resolution: Done > Admin CLI build failed > ---------------------- > > Key: JBTM-2273 > URL: https://issues.jboss.org/browse/JBTM-2273 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-quickstarts/112/ > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Building BlackTie Admin CLI Tool 5.0.4.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ btadmin --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ btadmin --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ btadmin --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ btadmin --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ btadmin --- > [INFO] > [INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-test-dependencies) @ btadmin --- > [INFO] Unpacking /home/hudson/.m2/repository/apache-log4cxx/contrib/log4cxx/902683/log4cxx-902683-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/junit/junit/4.11/junit-4.11.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/apr-1/contrib/apr-1/1.3.3/apr-1-1.3.3-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/codec/target/blacktie-codec-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/core/target/blacktie-core-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/tx/target/blacktie-tx-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/transport/target/blacktie-transport-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/xatmi/target/blacktie-xatmi-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/xsd/target/blacktie-xsd-5.0.4.Final-SNAPSHOT.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/hybrid/target/blacktie-hybrid-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] > [INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-dependencies) @ btadmin --- > [INFO] Copying protoc-2.4.1.3-centos54x64.zip to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/dependencies/protoc-2.4.1.3-centos54x64.zip > [INFO] Copying xercesc-3.0.1-centos54x64.zip to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/dependencies/xercesc-3.0.1-centos54x64.zip > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (unzip) @ btadmin --- > [WARNING] Parameter tasks is deprecated, use target instead > [INFO] Executing tasks > main: > [echo] unzip dependencies to test > [INFO] Executed tasks > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ btadmin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ btadmin --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 18 source files to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/classes > [WARNING] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/main/java/org/jboss/narayana/blacktie/btadmin/commands/Help.java:[129,50] decode(java.lang.String) in java.net.URLDecoder has been deprecated > [WARNING] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/main/java/org/jboss/narayana/blacktie/btadmin/commands/Shutdown.java: Some input files use unchecked or unsafe operations. > [WARNING] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/main/java/org/jboss/narayana/blacktie/btadmin/commands/Shutdown.java: Recompile with -Xlint:unchecked for details. > [INFO] > [INFO] --- blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:process-classes (process-classes) @ btadmin --- > copy-check: > init: > package: > [mkdir] Created dir: /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/classes/lib > [mkdir] Created dir: /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/classes/include > copy-idl: > copy-includes: > copy-libs: > process-classes: > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ btadmin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ btadmin --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/test-classes > [INFO] > [INFO] --- blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:test-compile (test-compile) @ btadmin --- > init: > fileset.test.check: > [echo] src/test/cpp **/*.c* > gen-test-runner1: > gen-test-runner2: > gen-test-runner: > package: > test-compile: > [INFO] > [INFO] --- blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:generate-exe (generate-exe) @ btadmin --- > init: > init-cpp-test: > [mkdir] Created dir: /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cpp-test-classes > [copy] Copying 3 files to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cpp-test-classes > generate-exe: > libnames not specified or empty. > libnames not specified or empty. > [cc] 1 total files to be compiled. > [cc] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/test/cpp/cs.cxx: In function ?int main(int, char**)?: > [cc] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/test/cpp/cs.cxx:31:39: warning: deprecated conversion from string constant to ?char*? [-Wwrite-strings] > [cc] putenv("BLACKTIE_CONFIGURATION=linux"); > [cc] ^ > [cc] Starting link > [cc] /lib64/libaprutil-1.so.0: undefined reference to `apr_pool_pre_cleanup_register' > [cc] collect2: error: ld returned 1 exit status > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Blacktie C++ Plugin ............................... SUCCESS [8.183s] > [INFO] BlackTie all files ................................ SUCCESS [0.626s] > [INFO] Blacktie Defaults and Dependencies ................ SUCCESS [0.032s] > [INFO] Blacktie C Defaults and Dependencies .............. SUCCESS [21.098s] > [INFO] Blacktie Java JNI Tests ........................... SUCCESS [1.017s] > [INFO] Blacktie Schemas .................................. SUCCESS [0.252s] > [INFO] Blacktie CORBA Transport .......................... SUCCESS [0.018s] > [INFO] Blacktie CORBA Transport Java Bindings ............ SUCCESS [1.057s] > [INFO] BlackTie Messaging (via JMS) ...................... SUCCESS [10.750s] > [INFO] Blacktie Java XATMI Implementation ................ SUCCESS [5.635s] > [INFO] Blacktie Java NBF Implementation .................. SUCCESS [0.228s] > [INFO] Blacktie Administration Services .................. SUCCESS [1:22.245s] > [INFO] Blacktie Administration Services EAR .............. SUCCESS [2.325s] > [INFO] Blacktie Core C++ Implementation .................. SUCCESS [13.134s] > [INFO] Blacktie Codec C++ Implementation ................. SUCCESS [16.424s] > [INFO] Blacktie C++ REST Transport ....................... SUCCESS [5.257s] > [INFO] Blacktie Utilities ................................ SUCCESS [3.695s] > [INFO] Blacktie C++ TX Client Library .................... SUCCESS [8.486s] > [INFO] Blacktie C++ Hybrid Transport ..................... SUCCESS [6.268s] > [INFO] Blacktie C++ XATMI Implementation ................. SUCCESS [7.711s] > [INFO] Blacktie C++ Queue Client ......................... SUCCESS [4.280s] > [INFO] Blacktie NBF ...................................... SUCCESS [5.005s] > [INFO] BlackTie Admin CLI Tool ........................... FAILURE [1.831s] > [INFO] Blacktie Server Code Generation ................... SKIPPED > [INFO] Blacktie Java/C C/Java XATMI Tests ................ SKIPPED > [INFO] Blacktie Distribution ............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 3:26.487s > [INFO] Finished at: Sat Oct 18 01:28:34 BST 2014 > [INFO] Final Memory: 65M/431M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.jboss.narayana.blacktie.plugins:blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:generate-exe (generate-exe) on project btadmin: Failed to execute: Executing Ant script: /btcpp.build.xml [generate-exe]: Failed to execute. gcc failed with return code 1 -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn -rf :btadmin > UID PID PPID C STIME TTY TIME CMD > hudson 2525 2522 0 Oct10 ? 00:08:00 sshd: hudson at notty > hudson 2568 2525 0 Oct10 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar > hudson 2575 2568 0 Oct10 ? 01:36:55 java -jar slave.jar > hudson 3261 32389 0 01:28 ? 00:00:00 ps -f > hudson 32369 2575 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > hudson 32389 32369 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > pkill: killing pid 2468 failed: Operation not permitted > pkill: killing pid 298 failed: Operation not permitted > pkill: killing pid 299 failed: Operation not permitted > pkill: killing pid 300 failed: Operation not permitted > pkill: killing pid 301 failed: Operation not permitted > pkill: killing pid 302 failed: Operation not permitted > pkill: killing pid 303 failed: Operation not permitted > pkill: killing pid 304 failed: Operation not permitted > pkill: killing pid 305 failed: Operation not permitted > pkill: killing pid 306 failed: Operation not permitted > pkill: killing pid 307 failed: Operation not permitted > pkill: killing pid 308 failed: Operation not permitted > pkill: killing pid 309 failed: Operation not permitted > pkill: killing pid 310 failed: Operation not permitted > pkill: killing pid 311 failed: Operation not permitted > pkill: killing pid 312 failed: Operation not permitted > pkill: killing pid 313 failed: Operation not permitted > pkill: killing pid 314 failed: Operation not permitted > pkill: killing pid 323 failed: Operation not permitted > pkill: killing pid 324 failed: Operation not permitted > pkill: killing pid 327 failed: Operation not permitted > pkill: killing pid 328 failed: Operation not permitted > pkill: killing pid 331 failed: Operation not permitted > pkill: killing pid 332 failed: Operation not permitted > pkill: killing pid 333 failed: Operation not permitted > UID PID PPID C STIME TTY TIME CMD > hudson 2525 2522 0 Oct10 ? 00:08:00 sshd: hudson at notty > hudson 2568 2525 0 Oct10 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar > hudson 2575 2568 0 Oct10 ? 01:36:55 java -jar slave.jar > hudson 3272 32389 0 01:28 ? 00:00:00 ps -f > hudson 32369 2575 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > hudson 32389 32369 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > Some tests failed: http://172.17.131.2/job/narayana-quickstarts/112/ > Build step 'Execute shell' marked build as failure > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:46:30 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 14 Nov 2014 08:46:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020050#comment-13020050 ] Mark Little edited comment on JBTM-2287 at 11/14/14 8:45 AM: ------------------------------------------------------------- We cannot store information about aborts. That defeats the point of the presumed-abort optimisation. We should call rollback during the normal termination of the transaction. If that fails (e.g., we crash before doing so), then the XAResource recovery should also roll back the db eventually. The double end issue should be an easy fix. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 11:03:31 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Nov 2014 11:03:31 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020162#comment-13020162 ] Tom Jenkinson commented on JBTM-2124: ------------------------------------- Historically, the reason this is a problem is if you have two recovery managers querying the same resource manager for Xids (but because the transaction flowed from a remote server, neither of these hosted the top level coordinator) then you would not be able to apply a filter that ensured only the recovery manager where the resource manager was originally enlisted at performs a rollback as its nodeId was not in the Xid. Now, when we developed the integration code for the EJB remoting transport as used in WidFly we had a similar issue and we developed a system whereby we can encode the subordinates node id into the bqual of the Xid. It is possible that we could use that technique when generating the Xid to enlisting XAR for JTS branches too. Pertinent code is available over here: https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/jta/xa/XATxConverter.java#L171 This is where it is called from: https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/jca/SubordinateAtomicAction.java#L107 > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 11:07:30 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Nov 2014 11:07:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020166#comment-13020166 ] Tom Jenkinson commented on JBTM-2124: ------------------------------------- The current approach to resolve this edge case is a combination of our tooling which will show you the transactions that are currently in flight in combination with performing manual resolution of the branch using the tools provided by your resource manager. > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 11:12:30 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Nov 2014 11:12:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020175#comment-13020175 ] Tom Jenkinson commented on JBTM-2287: ------------------------------------- Hi, The issue about periodic recovery not performing orphan detection for resource managers enlisted in a JTS transaction has already been raised as a feature request over here: JBTM-2124. There is a workaround described in the comments of the issue which boils down to a manual process. I will tackle the double end XA compliance issue with this Jira as you are right, in the situation where prepare fails it is possible for us to re-execute the end and this could be the reason your resource manager does not have the rollback called on it during our rollback method. In fact I can see an UNKNOWN getting thrown in our code if you return an error out of end that we don't expect and us not perfoming the initial rollback call: https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/resources/jts/orbspecific/XAResourceRecord.java#L368 Hope this helps, Tom > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 11:26:30 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 14 Nov 2014 11:26:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2286: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/763 > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 11:44:29 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Nov 2014 11:44:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2287: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/762/ [~marklittle], I produced a patch (link https://github.com/jbosstm/narayana/pull/762/) which does what you suggested (avoids the second xa_end) but in a slightly different way. I realise that the local JTA version sets _prepared in prepare as soon as end is called (probably for a similar reason) and that will prevent the end in rollback. What I found is that _prepared is used in the JTS variant of XAResourceRecord to determine when to write logs etc. The least invasive approach I could see was to keep track of when end itself was called and only allow a single call to end from the XARR class. I managed to reuse the endAssociation() method but to move its state to class level rather than method level. If you have any objections I can go back to investigating using _prepared but as I say it appears as though it could be more invasive because of the way it affects what gets written and potentially attempted to be deleted. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 16 23:32:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Sun, 16 Nov 2014 23:32:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2187) Timer error on startup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2187: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/764 > Timer error on startup > ---------------------- > > Key: JBTM-2187 > URL: https://issues.jboss.org/browse/JBTM-2187 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.4 > > > A community user has the following issue on startup: > {quote} > 2014-06-04 09:43:03,710 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final > 2014-06-04 09:43:06,889 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final > 2014-06-04 09:43:06,971 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Final "WildFly" starting > 2014-06-04 09:43:07,001 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties: > awt.toolkit = sun.awt.windows.WToolkit > file.encoding = Cp1252 > file.encoding.pkg = sun.io > file.separator = \ > java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment > java.awt.printerjob = sun.awt.windows.WPrinterJob > java.class.path = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\jboss-modules.jar > java.class.version = 51.0 > java.endorsed.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\endorsed > java.ext.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\ext;C:\Windows\Sun\Java\lib\ext > java.home = C:\Program Files\Java\jdk1.7.0\jre > java.io.tmpdir = C:\Users\EPETRE~2\AppData\Local\Temp\ > java.library.path = C:\Program Files\Java\jdk1.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\XEClient\bin;D:\app\epetremann\product\11.2.0\client_1\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Java\jdk1.6.0_30\bin;D:\Outils\instantclient_11_2;C:\Program Files\Common Files\SYSTEM\MSMAPI\1036;C:\Program Files\TortoiseSVN\bin;C:\XEClient\bin;D:\app\epetremann\product\11.2.0\client_1\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Java\jdk1.6.0_30\bin;D:\Outils\instantclient_11_2;C:\Program Files\Common Files\SYSTEM\MSMAPI\1036;C:\Program Files\TortoiseSVN\bin;D:\Outils\apache-maven-2.2.1\bin;C:\NatStar\BIN;C:\NatStar\PRIV\TEST\DLL;C:\NatStar\GLOB\CLASSES\DLL;C:\Perl64\bin;D:\Projets\FUI\ressources\ide\grails-2.2.4\bin;. > java.net.preferIPv4Stack = true > java.runtime.name = Java(TM) SE Runtime Environment > java.runtime.version = 1.7.0-b147 > java.specification.name = Java Platform API Specification > java.specification.vendor = Oracle Corporation > java.specification.version = 1.7 > java.util.logging.manager = org.jboss.logmanager.LogManager > java.vendor = Oracle Corporation > java.vendor.url = http://java.oracle.com/ > java.vendor.url.bug = http://bugreport.sun.com/bugreport/ > java.version = 1.7.0 > java.vm.info = mixed mode > java.vm.name = Java HotSpot(TM) 64-Bit Server VM > java.vm.specification.name = Java Virtual Machine Specification > java.vm.specification.vendor = Oracle Corporation > java.vm.specification.version = 1.7 > java.vm.vendor = Oracle Corporation > java.vm.version = 21.0-b17 > javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder > javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory > javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory > javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory > javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory > javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory > javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory > javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory > javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory > javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory > jboss.bind.address = 127.0.0.1 > jboss.bind.address.unsecure = 127.0.0.1 > jboss.home.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final > jboss.host.name = lt-petremann > jboss.modules.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\modules > jboss.modules.system.pkgs = org.jboss.byteman > jboss.node.name = lt-petremann > jboss.qualified.host.name = lt-petremann > jboss.server.base.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone > jboss.server.config.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\configuration > jboss.server.data.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data > jboss.server.deploy.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\content > jboss.server.log.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\log > jboss.server.name = lt-petremann > jboss.server.persist.config = true > jboss.server.temp.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\tmp > line.separator = > logging.configuration = file:D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\configuration/logging.properties > module.path = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\modules > org.jboss.boot.log.file = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\log\server.log > org.jboss.resolver.warning = true > org.xml.sax.driver = __redirected.__XMLReaderFactory > os.arch = amd64 > os.name = Windows 7 > os.version = 6.1 > path.separator = ; > program.name = standalone.bat > sun.arch.data.model = 64 > sun.boot.class.path = C:\Program Files\Java\jdk1.7.0\jre\lib\resources.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\rt.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jce.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.7.0\jre\classes > sun.boot.library.path = C:\Program Files\Java\jdk1.7.0\jre\bin > sun.cpu.endian = little > sun.cpu.isalist = amd64 > sun.desktop = windows > sun.io.unicode.encoding = UnicodeLittle > sun.java.command = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\jboss-modules.jar -mp D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\modules org.jboss.as.standalone -Djboss.home.dir=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final -Djboss.bind.address=127.0.0.1 -Djboss.bind.address.unsecure=127.0.0.1 > sun.java.launcher = SUN_STANDARD > sun.jnu.encoding = Cp1252 > sun.management.compiler = HotSpot 64-Bit Tiered Compilers > sun.os.patch.level = Service Pack 1 > user.country = FR > user.dir = D:\Projets\_RD\BlackTieCobolIT\bin > user.home = C:\Users\epetremann > user.language = fr > user.name = epetremann > user.script = > user.timezone = Europe/Paris > user.variant = > 2014-06-04 09:43:07,003 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\log\server.log -Dlogging.configuration=file:D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\configuration/logging.properties > 2014-06-04 09:43:16,246 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 2014-06-04 09:43:16,273 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.2.0.Final > 2014-06-04 09:43:16,281 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.2.0.Final > 2014-06-04 09:43:16,341 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. > 2014-06-04 09:43:16,342 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem > 2014-06-04 09:43:16,348 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem > 2014-06-04 09:43:16,350 INFO [org.wildfly.extension.blacktie] (ServerService Thread Pool -- 59) Starting Blacktie Susbsystem > 2014-06-04 09:43:16,351 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem > 2014-06-04 09:43:16,363 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension > 2014-06-04 09:43:16,365 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.20.Final > 2014-06-04 09:43:16,390 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] > 2014-06-04 09:43:16,397 INFO [org.jboss.as.connector.logging] (MSC service thread 1-11) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final) > 2014-06-04 09:43:16,454 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service > 2014-06-04 09:43:16,458 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/mail/Default] > 2014-06-04 09:43:16,666 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 2014-06-04 09:43:16,669 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2 > 2014-06-04 09:43:16,796 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017502: Undertow 1.0.0.Final starting > 2014-06-04 09:43:16,800 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Final starting > 2014-06-04 09:43:16,853 INFO [org.wildfly.extension.blacktie] (MSC service thread 1-2) Starting StompConnect tcp://127.0.0.1:61613 > 2014-06-04 09:43:16,875 INFO [org.codehaus.stomp.tcp.TcpTransportServer] (MSC service thread 1-2) Listening for connections at: tcp://127.0.0.1:61613 > 2014-06-04 09:43:16,876 INFO [org.wildfly.extension.blacktie] (MSC service thread 1-2) Started StompConnect tcp://127.0.0.1:61613 > 2014-06-04 09:43:16,909 WARN [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal > 2014-06-04 09:43:16,973 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messagingjournal,bindingsDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messagingbindings,largeMessagesDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messaginglargemessages,pagingDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messagingpaging) > 2014-06-04 09:43:16,977 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221006: Waiting to obtain live lock > 2014-06-04 09:43:16,980 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.0.Final > 2014-06-04 09:43:17,005 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221013: Using NIO Journal > 2014-06-04 09:43:17,061 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017527: Creating file handler for path D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final/welcome-content > 2014-06-04 09:43:17,064 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 60) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. > 2014-06-04 09:43:17,071 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017525: Started server default-server. > 2014-06-04 09:43:17,076 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) JBAS017531: Host default-host starting > 2014-06-04 09:43:17,085 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 2014-06-04 09:43:17,106 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017519: Undertow HTTP listener default listening on 127.0.0.1/127.0.0.1:8080 > 2014-06-04 09:43:17,108 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support CORE > 2014-06-04 09:43:17,157 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-12) JBAS015012: Started FileSystemDeploymentService for directory D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\deployments > 2014-06-04 09:43:17,162 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "blacktie-admin-services-ear-5.0.0.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.0.0.Final.ear") > 2014-06-04 09:43:17,196 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:9999 > 2014-06-04 09:43:17,319 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,320 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,326 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,384 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support AMQP > 2014-06-04 09:43:17,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,389 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support STOMP > 2014-06-04 09:43:17,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,393 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,395 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,397 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,396 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,400 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,399 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,404 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,402 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,406 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,404 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,409 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,408 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,407 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,413 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,411 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,416 WARN [jacorb.codeset] (MSC service thread 1-9) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1 > 2014-06-04 09:43:17,414 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,417 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,417 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,421 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,419 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,424 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,423 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,426 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,424 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,430 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,428 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,432 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221034: Waiting to obtain live lock > 2014-06-04 09:43:17,432 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,430 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,434 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,433 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221035: Live Server Obtained live lock > 2014-06-04 09:43:17,433 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,436 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,435 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,439 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,439 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,441 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,440 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,443 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,442 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,444 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,446 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,446 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,448 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,447 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,450 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,450 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,452 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,451 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,454 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,453 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,456 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,455 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,457 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,461 INFO [org.jboss.as.jacorb] (MSC service thread 1-9) JBAS016330: CORBA ORB Service started > 2014-06-04 09:43:17,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,463 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,462 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,466 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,466 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,467 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,470 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,471 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,472 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,473 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,475 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,475 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,477 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,476 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,478 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,488 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,489 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,490 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,492 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,493 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,495 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,496 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,497 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,498 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,500 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,501 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,502 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,503 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,504 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,638 INFO [org.jboss.as.jacorb] (MSC service thread 1-13) JBAS016328: CORBA Naming Service started > 2014-06-04 09:43:17,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /rest-at-coordinator > 2014-06-04 09:43:17,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: rest-at-participant > 2014-06-04 09:43:17,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) JBAS017534: Registered web context: volatile-rest-at-participant > 2014-06-04 09:43:18,284 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221020: Started Netty Acceptor version unknown 127.0.0.1:5445 > 2014-06-04 09:43:18,329 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221020: Started Netty Acceptor version unknown 127.0.0.1:5455 > 2014-06-04 09:43:18,331 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221007: Server is now live > 2014-06-04 09:43:18,332 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [5de4de80-e671-11e3-bd9e-7d17f38f2f22] > 2014-06-04 09:43:18,354 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 2014-06-04 09:43:18,357 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 2014-06-04 09:43:18,428 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-13) JBAS010406: Registered connection factory java:/JmsXA > 2014-06-04 09:43:18,538 INFO [org.hornetq.ra] (MSC service thread 1-13) HornetQ resource adaptor started > 2014-06-04 09:43:18,539 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-13) IJ020002: Deployed: file://RaActivatorhornetq-ra > 2014-06-04 09:43:18,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-9) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > 2014-06-04 09:43:18,543 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 2014-06-04 09:43:18,665 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final > 2014-06-04 09:43:19,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb-api.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,738 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb-impl.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,739 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jsr173_1.0_api.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,740 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,749 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015876: Starting deployment of "null" (runtime-name: "blacktie-admin-services-5.0.0.Final.jar") > 2014-06-04 09:43:20,108 WARN [org.jboss.as.dependency.private] (MSC service thread 1-10) JBAS018567: Deployment "deployment.blacktie-admin-services-ear-5.0.0.Final.ear.blacktie-admin-services-5.0.0.Final.jar" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 2014-06-04 09:43:20,111 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) JBAS018567: Deployment "deployment.blacktie-admin-services-ear-5.0.0.Final.ear" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 2014-06-04 09:43:20,125 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment blacktie-admin-services-ear-5.0.0.Final.ear > 2014-06-04 09:43:20,756 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.0.3.Final > 2014-06-04 09:43:20,931 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment blacktie-admin-services-5.0.0.Final.jar > 2014-06-04 09:43:20,937 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named QueueReaperBean in deployment unit subdeployment "blacktie-admin-services-5.0.0.Final.jar" of deployment "blacktie-admin-services-ear-5.0.0.Final.ear" are as follows: > java:global/blacktie-admin-services-ear-5.0.0.Final/blacktie-admin-services-5.0.0.Final/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean > java:app/blacktie-admin-services-5.0.0.Final/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean > java:module/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean > java:global/blacktie-admin-services-ear-5.0.0.Final/blacktie-admin-services-5.0.0.Final/QueueReaperBean > java:app/blacktie-admin-services-5.0.0.Final/QueueReaperBean > java:module/QueueReaperBean > 2014-06-04 09:43:20,981 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016005: Starting Services for CDI deployment: blacktie-admin-services-ear-5.0.0.Final.ear > 2014-06-04 09:43:21,039 INFO [org.jboss.weld.Version] (MSC service thread 1-11) WELD-000900: 2.1.2 (Final) > 2014-06-04 09:43:21,052 INFO [org.jboss.weld.deployer] (MSC service thread 1-13) JBAS016008: Starting weld service for deployment blacktie-admin-services-ear-5.0.0.Final.ear > 2014-06-04 09:43:21,186 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.BTR_BTDomainAdmin > 2014-06-04 09:43:21,211 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name /queue/BTR_BTDomainAdmin > 2014-06-04 09:43:21,212 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.BTR_BTStompAdmin > 2014-06-04 09:43:21,216 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name /queue/BTR_BTStompAdmin > 2014-06-04 09:43:21,225 INFO [org.jboss.as.ejb3] (MSC service thread 1-9) JBAS014142: Started message driven bean 'BlacktieStompAdministrationService' with 'hornetq-ra.rar' resource adapter > 2014-06-04 09:43:21,226 INFO [org.jboss.as.ejb3] (MSC service thread 1-15) JBAS014142: Started message driven bean 'BlacktieAdminServiceXATMI' with 'hornetq-ra.rar' resource adapter > 2014-06-04 09:43:21,267 INFO [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (MSC service thread 1-15) onConstruct load btconfig.xml > 2014-06-04 09:43:21,582 INFO [org.jboss.narayana.blacktie.administration.BlacktieAdminService] (MSC service thread 1-15) Admin Server Started > 2014-06-04 09:43:21,608 WARN [org.jboss.weld.Validator] (MSC service thread 1-8) WELD-001471: Interceptor method start defined on class org.jboss.narayana.blacktie.administration.QueueReaperBean is not defined according to the specification. It should not throw java.lang.Exception, which is a checked exception. > 2014-06-04 09:43:21,766 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) QueueReaper Started > 2014-06-04 09:43:21,797 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) QeueueReaper cancel a timer > 2014-06-04 09:43:21,799 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) QueueReaper create timer with 30000ms > 2014-06-04 09:43:21,813 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014120: Error invoking timeout for timer: [id=29b5597e-d94e-410a-b641-464046270eed timedObjectId=blacktie-admin-services-ear-5.0.0.Final.blacktie-admin-services-5.0.0.Final.QueueReaperBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 40976d9a initialExpiration=Wed Jun 04 09:43:09 CEST 2014 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=queue reaper: javax.ejb.NoSuchObjectLocalException: JBAS014469: Timer was canceled > at org.jboss.as.ejb3.timerservice.TimerImpl.assertTimerState(TimerImpl.java:462) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.TimerImpl.getInfo(TimerImpl.java:237) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.narayana.blacktie.administration.QueueReaperBean.run(QueueReaperBean.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0] > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:95) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:104) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:55) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:52) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:340) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) [wildfly-security-manager-1.0.0.Final.jar:1.0.0.Final] > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:104) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > 2014-06-04 09:43:21,900 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014121: Timer: [id=29b5597e-d94e-410a-b641-464046270eed timedObjectId=blacktie-admin-services-ear-5.0.0.Final.blacktie-admin-services-5.0.0.Final.QueueReaperBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 40976d9a initialExpiration=Wed Jun 04 09:43:09 CEST 2014 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=queue reaper will be retried > 2014-06-04 09:43:21,901 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014124: Timer is not active, skipping retry of timer: [id=29b5597e-d94e-410a-b641-464046270eed timedObjectId=blacktie-admin-services-ear-5.0.0.Final.blacktie-admin-services-5.0.0.Final.QueueReaperBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 40976d9a initialExpiration=Wed Jun 04 09:43:09 CEST 2014 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=queue reaper > 2014-06-04 09:43:21,902 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "blacktie-admin-services-ear-5.0.0.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.0.0.Final.ear") > 2014-06-04 09:43:21,922 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 2014-06-04 09:43:21,923 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 2014-06-04 09:43:21,924 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final "WildFly" started in 20202ms - Started 403 of 462 services (107 services are lazy, passive or on-demand) > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 02:45:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 17 Nov 2014 02:45:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2288) Deploy/Undeploy BlacktieAdminService MBean throws javax.naming.NameNotFoundException: java:comp/BeanManager In-Reply-To: References: Message-ID: Amos Feng created JBTM-2288: ------------------------------- Summary: Deploy/Undeploy BlacktieAdminService MBean throws javax.naming.NameNotFoundException: java:comp/BeanManager Key: JBTM-2288 URL: https://issues.jboss.org/browse/JBTM-2288 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration, BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.4 When deploy the balcktie admin ear, the wildfly throws NameNotFound Exception when deploying the BlacktiAdminService MBean {code} 11:39:30,059 INFO [org.jboss.narayana.blacktie.administration.BlacktieAdminService] (MSC service thread 1-8) Admin Server Started 11:39:30,060 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT] at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21] at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21] at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108) at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService.java:77) [wildfly-sar-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT] at org.jboss.as.service.StartStopService.start(StartStopService.java:57) [wildfly-sar-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] 11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21] at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21] at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108) at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 05:50:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 17 Nov 2014 05:50:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2289) All QA_JTA tests fail on Oracle In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2289: ------------------------------------- Summary: All QA_JTA tests fail on Oracle Key: JBTM-2289 URL: https://issues.jboss.org/browse/JBTM-2289 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA, Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Blocker Fix For: 5.0.4 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/685/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/ {code} BUILD FAILED /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml:111: some tests failed Total time: 148 minutes 16 seconds Test Failures: jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test019 Fail (2m52.176s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test020 Fail (1m48.440s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test021 Fail (2m51.868s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test022 Fail (1m48.429s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test029 Fail (2m56.246s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test030 Fail (1m48.966s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test031 Fail (2m56.454s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test032 Fail (1m49.092s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test008 Fail (2m47.491s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (1m48.420s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (2m45.377s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test011 Fail (1m49.096s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test012 Fail (2m48.005s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test013 Fail (1m48.328s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test019 Fail (2m51.740s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test020 Fail (1m48.531s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test021 Fail (2m51.655s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test022 Fail (1m48.485s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test029 Fail (2m56.792s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test030 Fail (1m48.883s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test031 Fail (2m56.524s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test032 Fail (1m48.943s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test008 Fail (2m45.500s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (1m48.318s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (2m47.985s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test011 Fail (1m48.492s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test012 Fail (2m45.681s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test013 Fail (1m48.303s) Buildfile: /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 05:58:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 17 Nov 2014 05:58:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2273) Admin CLI build failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020408#comment-13020408 ] Gytis Trikleris commented on JBTM-2273: --------------------------------------- Thanks, [~zhfeng], it works now. > Admin CLI build failed > ---------------------- > > Key: JBTM-2273 > URL: https://issues.jboss.org/browse/JBTM-2273 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-quickstarts/112/ > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Building BlackTie Admin CLI Tool 5.0.4.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ btadmin --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ btadmin --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ btadmin --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ btadmin --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ btadmin --- > [INFO] > [INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-test-dependencies) @ btadmin --- > [INFO] Unpacking /home/hudson/.m2/repository/apache-log4cxx/contrib/log4cxx/902683/log4cxx-902683-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/junit/junit/4.11/junit-4.11.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/apr-1/contrib/apr-1/1.3.3/apr-1-1.3.3-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/codec/target/blacktie-codec-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/core/target/blacktie-core-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/tx/target/blacktie-tx-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/transport/target/blacktie-transport-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/xatmi/target/blacktie-xatmi-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/xsd/target/blacktie-xsd-5.0.4.Final-SNAPSHOT.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] Unpacking /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/hybrid/target/blacktie-hybrid-5.0.4.Final-SNAPSHOT-centos54x64.jar to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cxx/test with includes "**/*" and excludes "" > [INFO] > [INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-dependencies) @ btadmin --- > [INFO] Copying protoc-2.4.1.3-centos54x64.zip to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/dependencies/protoc-2.4.1.3-centos54x64.zip > [INFO] Copying xercesc-3.0.1-centos54x64.zip to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/dependencies/xercesc-3.0.1-centos54x64.zip > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (unzip) @ btadmin --- > [WARNING] Parameter tasks is deprecated, use target instead > [INFO] Executing tasks > main: > [echo] unzip dependencies to test > [INFO] Executed tasks > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ btadmin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ btadmin --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 18 source files to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/classes > [WARNING] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/main/java/org/jboss/narayana/blacktie/btadmin/commands/Help.java:[129,50] decode(java.lang.String) in java.net.URLDecoder has been deprecated > [WARNING] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/main/java/org/jboss/narayana/blacktie/btadmin/commands/Shutdown.java: Some input files use unchecked or unsafe operations. > [WARNING] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/main/java/org/jboss/narayana/blacktie/btadmin/commands/Shutdown.java: Recompile with -Xlint:unchecked for details. > [INFO] > [INFO] --- blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:process-classes (process-classes) @ btadmin --- > copy-check: > init: > package: > [mkdir] Created dir: /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/classes/lib > [mkdir] Created dir: /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/classes/include > copy-idl: > copy-includes: > copy-libs: > process-classes: > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ btadmin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ btadmin --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/test-classes > [INFO] > [INFO] --- blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:test-compile (test-compile) @ btadmin --- > init: > fileset.test.check: > [echo] src/test/cpp **/*.c* > gen-test-runner1: > gen-test-runner2: > gen-test-runner: > package: > test-compile: > [INFO] > [INFO] --- blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:generate-exe (generate-exe) @ btadmin --- > init: > init-cpp-test: > [mkdir] Created dir: /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cpp-test-classes > [copy] Copying 3 files to /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/target/cpp-test-classes > generate-exe: > libnames not specified or empty. > libnames not specified or empty. > [cc] 1 total files to be compiled. > [cc] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/test/cpp/cs.cxx: In function ?int main(int, char**)?: > [cc] /home/hudson/workspace/narayana-quickstarts/narayana/blacktie/btadmin/src/test/cpp/cs.cxx:31:39: warning: deprecated conversion from string constant to ?char*? [-Wwrite-strings] > [cc] putenv("BLACKTIE_CONFIGURATION=linux"); > [cc] ^ > [cc] Starting link > [cc] /lib64/libaprutil-1.so.0: undefined reference to `apr_pool_pre_cleanup_register' > [cc] collect2: error: ld returned 1 exit status > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Blacktie C++ Plugin ............................... SUCCESS [8.183s] > [INFO] BlackTie all files ................................ SUCCESS [0.626s] > [INFO] Blacktie Defaults and Dependencies ................ SUCCESS [0.032s] > [INFO] Blacktie C Defaults and Dependencies .............. SUCCESS [21.098s] > [INFO] Blacktie Java JNI Tests ........................... SUCCESS [1.017s] > [INFO] Blacktie Schemas .................................. SUCCESS [0.252s] > [INFO] Blacktie CORBA Transport .......................... SUCCESS [0.018s] > [INFO] Blacktie CORBA Transport Java Bindings ............ SUCCESS [1.057s] > [INFO] BlackTie Messaging (via JMS) ...................... SUCCESS [10.750s] > [INFO] Blacktie Java XATMI Implementation ................ SUCCESS [5.635s] > [INFO] Blacktie Java NBF Implementation .................. SUCCESS [0.228s] > [INFO] Blacktie Administration Services .................. SUCCESS [1:22.245s] > [INFO] Blacktie Administration Services EAR .............. SUCCESS [2.325s] > [INFO] Blacktie Core C++ Implementation .................. SUCCESS [13.134s] > [INFO] Blacktie Codec C++ Implementation ................. SUCCESS [16.424s] > [INFO] Blacktie C++ REST Transport ....................... SUCCESS [5.257s] > [INFO] Blacktie Utilities ................................ SUCCESS [3.695s] > [INFO] Blacktie C++ TX Client Library .................... SUCCESS [8.486s] > [INFO] Blacktie C++ Hybrid Transport ..................... SUCCESS [6.268s] > [INFO] Blacktie C++ XATMI Implementation ................. SUCCESS [7.711s] > [INFO] Blacktie C++ Queue Client ......................... SUCCESS [4.280s] > [INFO] Blacktie NBF ...................................... SUCCESS [5.005s] > [INFO] BlackTie Admin CLI Tool ........................... FAILURE [1.831s] > [INFO] Blacktie Server Code Generation ................... SKIPPED > [INFO] Blacktie Java/C C/Java XATMI Tests ................ SKIPPED > [INFO] Blacktie Distribution ............................. SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 3:26.487s > [INFO] Finished at: Sat Oct 18 01:28:34 BST 2014 > [INFO] Final Memory: 65M/431M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.jboss.narayana.blacktie.plugins:blacktie-cpp-plugin:5.0.4.Final-SNAPSHOT:generate-exe (generate-exe) on project btadmin: Failed to execute: Executing Ant script: /btcpp.build.xml [generate-exe]: Failed to execute. gcc failed with return code 1 -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn -rf :btadmin > UID PID PPID C STIME TTY TIME CMD > hudson 2525 2522 0 Oct10 ? 00:08:00 sshd: hudson at notty > hudson 2568 2525 0 Oct10 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar > hudson 2575 2568 0 Oct10 ? 01:36:55 java -jar slave.jar > hudson 3261 32389 0 01:28 ? 00:00:00 ps -f > hudson 32369 2575 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > hudson 32389 32369 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > pkill: killing pid 2468 failed: Operation not permitted > pkill: killing pid 298 failed: Operation not permitted > pkill: killing pid 299 failed: Operation not permitted > pkill: killing pid 300 failed: Operation not permitted > pkill: killing pid 301 failed: Operation not permitted > pkill: killing pid 302 failed: Operation not permitted > pkill: killing pid 303 failed: Operation not permitted > pkill: killing pid 304 failed: Operation not permitted > pkill: killing pid 305 failed: Operation not permitted > pkill: killing pid 306 failed: Operation not permitted > pkill: killing pid 307 failed: Operation not permitted > pkill: killing pid 308 failed: Operation not permitted > pkill: killing pid 309 failed: Operation not permitted > pkill: killing pid 310 failed: Operation not permitted > pkill: killing pid 311 failed: Operation not permitted > pkill: killing pid 312 failed: Operation not permitted > pkill: killing pid 313 failed: Operation not permitted > pkill: killing pid 314 failed: Operation not permitted > pkill: killing pid 323 failed: Operation not permitted > pkill: killing pid 324 failed: Operation not permitted > pkill: killing pid 327 failed: Operation not permitted > pkill: killing pid 328 failed: Operation not permitted > pkill: killing pid 331 failed: Operation not permitted > pkill: killing pid 332 failed: Operation not permitted > pkill: killing pid 333 failed: Operation not permitted > UID PID PPID C STIME TTY TIME CMD > hudson 2525 2522 0 Oct10 ? 00:08:00 sshd: hudson at notty > hudson 2568 2525 0 Oct10 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar > hudson 2575 2568 0 Oct10 ? 01:36:55 java -jar slave.jar > hudson 3272 32389 0 01:28 ? 00:00:00 ps -f > hudson 32369 2575 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > hudson 32389 32369 0 01:07 ? 00:00:00 /bin/bash -xe /tmp/hudson884782302161251351.sh > Some tests failed: http://172.17.131.2/job/narayana-quickstarts/112/ > Build step 'Execute shell' marked build as failure > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 06:04:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 17 Nov 2014 06:04:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk is not installed on Catelyn In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2290: ------------------------------------- Summary: Gawk is not installed on Catelyn Key: JBTM-2290 URL: https://issues.jboss.org/browse/JBTM-2290 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Blocker Fix For: 5.0.4 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ {code} >From https://github.com/wildfly/wildfly * branch master -> FETCH_HEAD * [new branch] master -> upstream/master First, rewinding head to replay your work on top of it... Auto-merging pom.xml [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT Author: Tom Jenkinson 1 file changed, 1 insertion(+), 1 deletion(-) Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT All done. 'gawk' is not recognized as an internal or external command, operable program or batch file. "AS version is " Build step 'Execute Windows batch command' marked build as failure Archiving artifacts Sending e-mails to: gtrikler at redhat.com Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: FAILURE {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 06:12:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Nov 2014 06:12:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk is not installed on Catelyn In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2290: -------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > Gawk is not installed on Catelyn > -------------------------------- > > Key: JBTM-2290 > URL: https://issues.jboss.org/browse/JBTM-2290 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ > {code} > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > * [new branch] master -> upstream/master > First, rewinding head to replay your work on top of it... > Auto-merging pom.xml > [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT > Author: Tom Jenkinson > 1 file changed, 1 insertion(+), 1 deletion(-) > Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT > All done. > 'gawk' is not recognized as an internal or external command, > operable program or batch file. > "AS version is " > Build step 'Execute Windows batch command' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler at redhat.com > Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 06:15:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Nov 2014 06:15:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2289) All QA_JTA tests fail on Oracle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2289: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > All QA_JTA tests fail on Oracle > ------------------------------- > > Key: JBTM-2289 > URL: https://issues.jboss.org/browse/JBTM-2289 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/685/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/ > {code} > BUILD FAILED > /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml:111: some tests failed > Total time: 148 minutes 16 seconds > Test Failures: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test019 Fail (2m52.176s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test020 Fail (1m48.440s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test021 Fail (2m51.868s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test022 Fail (1m48.429s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test029 Fail (2m56.246s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test030 Fail (1m48.966s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test031 Fail (2m56.454s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test032 Fail (1m49.092s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test008 Fail (2m47.491s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (1m48.420s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (2m45.377s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test011 Fail (1m49.096s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test012 Fail (2m48.005s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test013 Fail (1m48.328s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test019 Fail (2m51.740s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test020 Fail (1m48.531s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test021 Fail (2m51.655s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test022 Fail (1m48.485s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test029 Fail (2m56.792s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test030 Fail (1m48.883s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test031 Fail (2m56.524s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test032 Fail (1m48.943s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test008 Fail (2m45.500s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (1m48.318s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (2m47.985s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test011 Fail (1m48.492s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test012 Fail (2m45.681s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test013 Fail (1m48.303s) > Buildfile: /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 06:16:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 17 Nov 2014 06:16:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk and wget are not installed on Catelyn In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2290: ---------------------------------- Summary: Gawk and wget are not installed on Catelyn (was: Gawk is not installed on Catelyn) > Gawk and wget are not installed on Catelyn > ------------------------------------------ > > Key: JBTM-2290 > URL: https://issues.jboss.org/browse/JBTM-2290 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ > {code} > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > * [new branch] master -> upstream/master > First, rewinding head to replay your work on top of it... > Auto-merging pom.xml > [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT > Author: Tom Jenkinson > 1 file changed, 1 insertion(+), 1 deletion(-) > Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT > All done. > 'gawk' is not recognized as an internal or external command, > operable program or batch file. > "AS version is " > Build step 'Execute Windows batch command' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler at redhat.com > Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 06:17:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 17 Nov 2014 06:17:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk and wget are not installed on Catelyn In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020418#comment-13020418 ] Gytis Trikleris commented on JBTM-2290: --------------------------------------- Quickstarts configuration uses wget, which is also missing on Catelyn: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstarts-windows2008-catelyn/691/ > Gawk and wget are not installed on Catelyn > ------------------------------------------ > > Key: JBTM-2290 > URL: https://issues.jboss.org/browse/JBTM-2290 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ > {code} > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > * [new branch] master -> upstream/master > First, rewinding head to replay your work on top of it... > Auto-merging pom.xml > [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT > Author: Tom Jenkinson > 1 file changed, 1 insertion(+), 1 deletion(-) > Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT > All done. > 'gawk' is not recognized as an internal or external command, > operable program or batch file. > "AS version is " > Build step 'Execute Windows batch command' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler at redhat.com > Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 07:56:40 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 17 Nov 2014 07:56:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020441#comment-13020441 ] Mark Little commented on JBTM-2287: ----------------------------------- Looks fine to me. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 08:16:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Nov 2014 08:16:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020444#comment-13020444 ] Tom Jenkinson commented on JBTM-2287: ------------------------------------- Thanks Mark, CI passed too so will get this merged. > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 08:59:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 17 Nov 2014 08:59:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk and wget are not installed on Catelyn In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020450#comment-13020450 ] Amos Feng commented on JBTM-2290: --------------------------------- It should also need the grep and curl > Gawk and wget are not installed on Catelyn > ------------------------------------------ > > Key: JBTM-2290 > URL: https://issues.jboss.org/browse/JBTM-2290 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ > {code} > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > * [new branch] master -> upstream/master > First, rewinding head to replay your work on top of it... > Auto-merging pom.xml > [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT > Author: Tom Jenkinson > 1 file changed, 1 insertion(+), 1 deletion(-) > Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT > All done. > 'gawk' is not recognized as an internal or external command, > operable program or batch file. > "AS version is " > Build step 'Execute Windows batch command' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler at redhat.com > Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 12:34:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 17 Nov 2014 12:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020532#comment-13020532 ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- Michael changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from NEW to ASSIGNED > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 04:57:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 04:57:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2289) All QA_JTA tests fail on Oracle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2289: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/765 > All QA_JTA tests fail on Oracle > ------------------------------- > > Key: JBTM-2289 > URL: https://issues.jboss.org/browse/JBTM-2289 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/685/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/ > {code} > BUILD FAILED > /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml:111: some tests failed > Total time: 148 minutes 16 seconds > Test Failures: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test019 Fail (2m52.176s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test020 Fail (1m48.440s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test021 Fail (2m51.868s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test022 Fail (1m48.429s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test029 Fail (2m56.246s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test030 Fail (1m48.966s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test031 Fail (2m56.454s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test032 Fail (1m49.092s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test008 Fail (2m47.491s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (1m48.420s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (2m45.377s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test011 Fail (1m49.096s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test012 Fail (2m48.005s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test013 Fail (1m48.328s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test019 Fail (2m51.740s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test020 Fail (1m48.531s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test021 Fail (2m51.655s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test022 Fail (1m48.485s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test029 Fail (2m56.792s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test030 Fail (1m48.883s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test031 Fail (2m56.524s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test032 Fail (1m48.943s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test008 Fail (2m45.500s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (1m48.318s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (2m47.985s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test011 Fail (1m48.492s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test012 Fail (2m45.681s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test013 Fail (1m48.303s) > Buildfile: /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 04:57:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 04:57:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2289) TransactionalDriver QA_JTA tests fail on Oracle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2289: -------------------------------- Summary: TransactionalDriver QA_JTA tests fail on Oracle (was: All QA_JTA tests fail on Oracle) > TransactionalDriver QA_JTA tests fail on Oracle > ----------------------------------------------- > > Key: JBTM-2289 > URL: https://issues.jboss.org/browse/JBTM-2289 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/685/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/ > {code} > BUILD FAILED > /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml:111: some tests failed > Total time: 148 minutes 16 seconds > Test Failures: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test019 Fail (2m52.176s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test020 Fail (1m48.440s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test021 Fail (2m51.868s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test022 Fail (1m48.429s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test029 Fail (2m56.246s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test030 Fail (1m48.966s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test031 Fail (2m56.454s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test032 Fail (1m49.092s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test008 Fail (2m47.491s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (1m48.420s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (2m45.377s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test011 Fail (1m49.096s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test012 Fail (2m48.005s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test013 Fail (1m48.328s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test019 Fail (2m51.740s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test020 Fail (1m48.531s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test021 Fail (2m51.655s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test022 Fail (1m48.485s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test029 Fail (2m56.792s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test030 Fail (1m48.883s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test031 Fail (2m56.524s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test032 Fail (1m48.943s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test008 Fail (2m45.500s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (1m48.318s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (2m47.985s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test011 Fail (1m48.492s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test012 Fail (2m45.681s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test013 Fail (1m48.303s) > Buildfile: /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 04:57:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 04:57:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2289) TransactionalDriver QA_JTA tests fail on Oracle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2289: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TransactionalDriver QA_JTA tests fail on Oracle > ----------------------------------------------- > > Key: JBTM-2289 > URL: https://issues.jboss.org/browse/JBTM-2289 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/685/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/ > {code} > BUILD FAILED > /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml:111: some tests failed > Total time: 148 minutes 16 seconds > Test Failures: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test019 Fail (2m52.176s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test020 Fail (1m48.440s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test021 Fail (2m51.868s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test022 Fail (1m48.429s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test029 Fail (2m56.246s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test030 Fail (1m48.966s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test031 Fail (2m56.454s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test032 Fail (1m49.092s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test008 Fail (2m47.491s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (1m48.420s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (2m45.377s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test011 Fail (1m49.096s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test012 Fail (2m48.005s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test013 Fail (1m48.328s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test019 Fail (2m51.740s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test020 Fail (1m48.531s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test021 Fail (2m51.655s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test022 Fail (1m48.485s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test029 Fail (2m56.792s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test030 Fail (1m48.883s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test031 Fail (2m56.524s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test032 Fail (1m48.943s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test008 Fail (2m45.500s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (1m48.318s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (2m47.985s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test011 Fail (1m48.492s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test012 Fail (2m45.681s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test013 Fail (1m48.303s) > Buildfile: /home/hudson/workspace/narayana/PROFILE/QA_JTA/jdk/jdk7.latest/label/linux/qa/run-tests.xml > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 05:02:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 05:02:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2287: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Double end fixed in linked PR > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 05:34:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 05:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1588) Support build on AIX In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1588. ------------------------------- Resolution: Deferred This can be reopened if the community requires it > Support build on AIX > -------------------- > > Key: JBTM-1588 > URL: https://issues.jboss.org/browse/JBTM-1588 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Build System > Reporter: Tom Jenkinson > > AIX build and instructions -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 05:39:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 05:39:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1147) Refactor ParticipantCompletion recovery tests to remove duplicate rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-1147. --------------------------------- Fix Version/s: (was: 6.0.0) Resolution: Deferred As the issue is stalled and there is no direct benefit to this beyond general maintenance I am deferring this. It can be reopened should our community be interested in the code challenge of byteman gymnastics. > Refactor ParticipantCompletion recovery tests to remove duplicate rules > ----------------------------------------------------------------------- > > Key: JBTM-1147 > URL: https://issues.jboss.org/browse/JBTM-1147 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.16.4, 4.17.0.M1/5.0.0.M1 > Reporter: Paul Robinson > Priority: Minor > > The Byteman rules for the participant completion XTS recovery tests have many rules that are almost duplicates of each other. For example: > The following rules in BACrashDuringCommit could be refactored into a single rule > {code} > ##################################################################### > # Setup counter MultiParticipantParticipantCompletionParticipantCloseTest > # > RULE setup counter MultiParticipantParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > ##################################################################### > # Setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest > # > RULE setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > ##################################################################### > # Setup counter MultiServiceParticipantCompletionParticipantCloseTest > # > RULE setup counter MultiServiceParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > ##################################################################### > # Setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest > # > RULE setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > {code} > These can be re-factored in to a rule like this: > {code} > RULE setup counter > INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest > METHOD run() > AT ENTRY > IF $0.getClass().getName().contains("ParticipantCompletionParticipant") > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > {code} > This assumes that we have the same numbers for each use of: > {code} > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > {code} > Which is *usually* the case: > {code} > grep -r createCounter\(\"closes\" . > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1), > ./src/test/resources/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1), > ./target/test-classes/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3), > {code} > Maybe we just override the rule for the one exception. Ideas for what to do here are to be investigated. > Also, the following similar rules are also present in this file: > {code} > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest > # > RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiParticipantParticipantCompletionParticipantCloseAndExitTest > # > RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseAndExitTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest > # > RULE wait for closes MultiServiceParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseAndExitTest > # > RULE wait for closes MultiServiceParticipantCompletionParticipantCloseAndExitTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > {code} > Which could be replaced with something like this: > {code} > RULE wait for closes > INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF $0.getClass().getName().contains("ParticipantCompletionParticipant") > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > {code} > We could also re-factor these two rules out into a separate Byteman script and add it to all tests that need it. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 05:42:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 05:42:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1586) reloadDomain reloadServer: reload configuration server operation (compatable with svn update) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1586. ------------------------------- Resolution: Won't Fix Will focus community effort on the java container linked > reloadDomain reloadServer: reload configuration server operation (compatable with svn update) > --------------------------------------------------------------------------------------------- > > Key: JBTM-1586 > URL: https://issues.jboss.org/browse/JBTM-1586 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie > Reporter: Tom Jenkinson > Original Estimate: 1 week > Remaining Estimate: 1 week > > reloadDomain: This method is available from the "control" tab of a domain and operates on all servers > reloadServer: > it would be useful to have a reload server configuration operation. > this will require an external shell script to repeatedly start server.exe processes dependent upon exit status of server.exe > the serverdone operation can then be altered to return a specific return code dependent upon whether shutdown/reload configuration was issued. > The use of this method is if the environment.xml file has changed the server can be rebooted with the new configuration file > the shell script would look like (we would need one for windows and one for linux): > int startServer = 1; > while (startServer) > int exitStatus = server.exe(); > if (exitStatus == reloadConfiguration) { > startServer = 1; > svn update configuration; > } else { > startServer = 0; > } > NOTE: This method does not take an id parameter as all servers must be reloaded -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 05:43:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 05:43:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2069) Review BlackTie docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2069: -------------------------------- Fix Version/s: 5.0.4 (was: 6.0.0) > Review BlackTie docs > -------------------- > > Key: JBTM-2069 > URL: https://issues.jboss.org/browse/JBTM-2069 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.4 > > > Ensure no erroneous information > Update AS7 references to WildFly > For example: > run.sh -> standalone.sh (changed parameters too) > JBossAS->WildFly > paths, are they up-to-date (for example what apps should be deployed and where) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 05:44:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 05:44:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie CI test hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2265: -------------------------------- Fix Version/s: 5.0.4 > BlackTie CI test hang > --------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.0.4 > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 06:20:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 18 Nov 2014 06:20:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1453: ----------------------------------- Fix Version/s: 6.0.0 (was: 5.0.4) > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.0.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 06:21:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 18 Nov 2014 06:21:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020734#comment-13020734 ] Michael Musgrove commented on JBTM-1453: ---------------------------------------- I have moved this out to 6.0 since it is ongoing work - a subset of the tests have already been migrated. > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.0.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 06:50:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 06:50:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-919) Convert tests to work on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-919: ------------------------------- Fix Version/s: 5.0.4 > Convert tests to work on Windows > -------------------------------- > > Key: JBTM-919 > URL: https://issues.jboss.org/browse/JBTM-919 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Priority: Minor > Fix For: 5.0.4 > > > Some of the tests cannot be ran on Windows which reduces our scope for testing and also leaves some hudson nodes idle. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 09:29:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 09:29:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2287: -------------------------------- Fix Version/s: 5.0.4 > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 09:33:40 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 18 Nov 2014 09:33:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2272) ISE failure in CDI transactional observer methods with remote EJB call using JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng reopened JBTM-2272: ----------------------------- It needs to add the codes to make the getContextClassLoader work on the security manager. > ISE failure in CDI transactional observer methods with remote EJB call using JTS > -------------------------------------------------------------------------------- > > Key: JBTM-2272 > URL: https://issues.jboss.org/browse/JBTM-2272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 4.17.23, 5.0.3 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 4.17.24, 5.0.4 > > > See the reproduce steps in https://bugzilla.redhat.com/show_bug.cgi?id=1098127 > and the description in https://issues.jboss.org/browse/WFLY-3548 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 10:38:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 18 Nov 2014 10:38:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2272) ISE failure in CDI transactional observer methods with remote EJB call using JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2272: ---------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/746, https://github.com/jbosstm/narayana/pull/747, https://github.com/jbosstm/narayana/pull/766, https://github.com/jbosstm/narayana/pull/767 (was: https://github.com/jbosstm/narayana/pull/746, https://github.com/jbosstm/narayana/pull/747) > ISE failure in CDI transactional observer methods with remote EJB call using JTS > -------------------------------------------------------------------------------- > > Key: JBTM-2272 > URL: https://issues.jboss.org/browse/JBTM-2272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 4.17.23, 5.0.3 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 4.17.24, 5.0.4 > > > See the reproduce steps in https://bugzilla.redhat.com/show_bug.cgi?id=1098127 > and the description in https://issues.jboss.org/browse/WFLY-3548 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 12:26:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 12:26:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2291) ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2291: ----------------------------------- Summary: ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity Key: JBTM-2291 URL: https://issues.jboss.org/browse/JBTM-2291 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.4 ObjStoreBrowser::probe uses System.currentTimeMillis to determine whether its list of allUids contains stale date during updateMBeans call. Now if you imagine a clock which never moved on (low fidelity) then this would mean that a Uid was never eligible to be reaper from this list. Or imagine a machine that is very fast (my laptop for example) and it is possible that probe, remove entry, probe can all be called in the same millisecond. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 12:28:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 12:28:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-919) Convert tests to work on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-919: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/768 > Convert tests to work on Windows > -------------------------------- > > Key: JBTM-919 > URL: https://issues.jboss.org/browse/JBTM-919 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Priority: Minor > Fix For: 5.0.4 > > > Some of the tests cannot be ran on Windows which reduces our scope for testing and also leaves some hudson nodes idle. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 12:28:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 12:28:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2291) ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2291: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/768 > ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity > --------------------------------------------------------------------------------------------------------- > > Key: JBTM-2291 > URL: https://issues.jboss.org/browse/JBTM-2291 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > ObjStoreBrowser::probe uses System.currentTimeMillis to determine whether its list of allUids contains stale date during updateMBeans call. > Now if you imagine a clock which never moved on (low fidelity) then this would mean that a Uid was never eligible to be reaper from this list. > Or imagine a machine that is very fast (my laptop for example) and it is possible that probe, remove entry, probe can all be called in the same millisecond. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 12:41:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Nov 2014 12:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020885#comment-13020885 ] Tom Jenkinson commented on JBTM-2250: ------------------------------------- Strange output in the console: /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined. I guess that this could be a misconfig that byteman can't cope with. You might be interested to know when I run the build on Windows byteman nukes any other Java process I have running e.g. elluminate/eclipse - it has form :) > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 13:36:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 18 Nov 2014 13:36:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020913#comment-13020913 ] Michael Musgrove commented on JBTM-2250: ---------------------------------------- Yes, I noticed this too and checked with adinn. He suggested that they should be the same so it wouldn't matter which one was chosen but I can't remember the details of why he said the warning cropped up - I will prod him again and record the result of the conversation. > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 05:23:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Nov 2014 05:23:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021061#comment-13021061 ] Michael Musgrove commented on JBTM-2250: ---------------------------------------- Its an oracle JVM bug: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8021205 Fixed in 7u60 (b01) > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 05:25:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 05:25:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021062#comment-13021062 ] Tom Jenkinson commented on JBTM-2250: ------------------------------------- Great, so should we update soatest with that JVM and close this? > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 06:34:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Nov 2014 06:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2250. ------------------------------------ Resolution: Done I cannot be certain the failure only ever happened on soatest so we cannot say whether the hang and JVM bug are related. However I upgraded the JDK to1.7.0_71-b14 and resolved it - we can always reopen it if required. > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 07:52:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 07:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2291) ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2291: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done As this is usually done in real time I have opted to implement this with nano time. If the clock never moves on for example it would still mean a probe,del,probe sequence may return stale values but as this is not likely in normal operation and data integrity is not affected I have resolved the issue. It may be beneficial to attempt to alter the code to not use the time at all but this would be a low priority issue as it should really only affect test verification steps on very fast machines now. > ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity > --------------------------------------------------------------------------------------------------------- > > Key: JBTM-2291 > URL: https://issues.jboss.org/browse/JBTM-2291 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > ObjStoreBrowser::probe uses System.currentTimeMillis to determine whether its list of allUids contains stale date during updateMBeans call. > Now if you imagine a clock which never moved on (low fidelity) then this would mean that a Uid was never eligible to be reaper from this list. > Or imagine a machine that is very fast (my laptop for example) and it is possible that probe, remove entry, probe can all be called in the same millisecond. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 07:52:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 07:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-919) Convert tests to work on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-919: ------------------------------- Comment: was deleted (was: Hi Amos, please feel free to keep moving this out, but I recommend you create a branch and incrementally ensure the tests work ok on a Windows VM.) > Convert tests to work on Windows > -------------------------------- > > Key: JBTM-919 > URL: https://issues.jboss.org/browse/JBTM-919 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Priority: Minor > Fix For: 5.0.4 > > > Some of the tests cannot be ran on Windows which reduces our scope for testing and also leaves some hudson nodes idle. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 07:52:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 07:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2291) ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2291: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > ObjStoreBrowser can return stale Uid if the machine is very fast or the machines clock has a low fidelity > --------------------------------------------------------------------------------------------------------- > > Key: JBTM-2291 > URL: https://issues.jboss.org/browse/JBTM-2291 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > ObjStoreBrowser::probe uses System.currentTimeMillis to determine whether its list of allUids contains stale date during updateMBeans call. > Now if you imagine a clock which never moved on (low fidelity) then this would mean that a Uid was never eligible to be reaper from this list. > Or imagine a machine that is very fast (my laptop for example) and it is possible that probe, remove entry, probe can all be called in the same millisecond. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 07:52:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 07:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-919) Convert tests to work on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-919: ---------------------------------- Assignee: Tom Jenkinson > Convert tests to work on Windows > -------------------------------- > > Key: JBTM-919 > URL: https://issues.jboss.org/browse/JBTM-919 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.4 > > > Some of the tests cannot be ran on Windows which reduces our scope for testing and also leaves some hudson nodes idle. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 07:53:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 07:53:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-919) Convert tests to work on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-919: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I haven't tested QA or XTS test suites but the main tests work just fine now on windows or linux > Convert tests to work on Windows > -------------------------------- > > Key: JBTM-919 > URL: https://issues.jboss.org/browse/JBTM-919 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.4 > > > Some of the tests cannot be ran on Windows which reduces our scope for testing and also leaves some hudson nodes idle. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 08:02:40 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 19 Nov 2014 08:02:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2286: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/769 (was: https://github.com/jbosstm/narayana/pull/763) > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 08:27:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Nov 2014 08:27:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2187) Timer error on startup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2187: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Timer error on startup > ---------------------- > > Key: JBTM-2187 > URL: https://issues.jboss.org/browse/JBTM-2187 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.4 > > > A community user has the following issue on startup: > {quote} > 2014-06-04 09:43:03,710 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final > 2014-06-04 09:43:06,889 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final > 2014-06-04 09:43:06,971 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Final "WildFly" starting > 2014-06-04 09:43:07,001 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties: > awt.toolkit = sun.awt.windows.WToolkit > file.encoding = Cp1252 > file.encoding.pkg = sun.io > file.separator = \ > java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment > java.awt.printerjob = sun.awt.windows.WPrinterJob > java.class.path = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\jboss-modules.jar > java.class.version = 51.0 > java.endorsed.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\endorsed > java.ext.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\ext;C:\Windows\Sun\Java\lib\ext > java.home = C:\Program Files\Java\jdk1.7.0\jre > java.io.tmpdir = C:\Users\EPETRE~2\AppData\Local\Temp\ > java.library.path = C:\Program Files\Java\jdk1.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\XEClient\bin;D:\app\epetremann\product\11.2.0\client_1\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Java\jdk1.6.0_30\bin;D:\Outils\instantclient_11_2;C:\Program Files\Common Files\SYSTEM\MSMAPI\1036;C:\Program Files\TortoiseSVN\bin;C:\XEClient\bin;D:\app\epetremann\product\11.2.0\client_1\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Java\jdk1.6.0_30\bin;D:\Outils\instantclient_11_2;C:\Program Files\Common Files\SYSTEM\MSMAPI\1036;C:\Program Files\TortoiseSVN\bin;D:\Outils\apache-maven-2.2.1\bin;C:\NatStar\BIN;C:\NatStar\PRIV\TEST\DLL;C:\NatStar\GLOB\CLASSES\DLL;C:\Perl64\bin;D:\Projets\FUI\ressources\ide\grails-2.2.4\bin;. > java.net.preferIPv4Stack = true > java.runtime.name = Java(TM) SE Runtime Environment > java.runtime.version = 1.7.0-b147 > java.specification.name = Java Platform API Specification > java.specification.vendor = Oracle Corporation > java.specification.version = 1.7 > java.util.logging.manager = org.jboss.logmanager.LogManager > java.vendor = Oracle Corporation > java.vendor.url = http://java.oracle.com/ > java.vendor.url.bug = http://bugreport.sun.com/bugreport/ > java.version = 1.7.0 > java.vm.info = mixed mode > java.vm.name = Java HotSpot(TM) 64-Bit Server VM > java.vm.specification.name = Java Virtual Machine Specification > java.vm.specification.vendor = Oracle Corporation > java.vm.specification.version = 1.7 > java.vm.vendor = Oracle Corporation > java.vm.version = 21.0-b17 > javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder > javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory > javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory > javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory > javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory > javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory > javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory > javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory > javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory > javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory > jboss.bind.address = 127.0.0.1 > jboss.bind.address.unsecure = 127.0.0.1 > jboss.home.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final > jboss.host.name = lt-petremann > jboss.modules.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\modules > jboss.modules.system.pkgs = org.jboss.byteman > jboss.node.name = lt-petremann > jboss.qualified.host.name = lt-petremann > jboss.server.base.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone > jboss.server.config.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\configuration > jboss.server.data.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data > jboss.server.deploy.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\content > jboss.server.log.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\log > jboss.server.name = lt-petremann > jboss.server.persist.config = true > jboss.server.temp.dir = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\tmp > line.separator = > logging.configuration = file:D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\configuration/logging.properties > module.path = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\modules > org.jboss.boot.log.file = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\log\server.log > org.jboss.resolver.warning = true > org.xml.sax.driver = __redirected.__XMLReaderFactory > os.arch = amd64 > os.name = Windows 7 > os.version = 6.1 > path.separator = ; > program.name = standalone.bat > sun.arch.data.model = 64 > sun.boot.class.path = C:\Program Files\Java\jdk1.7.0\jre\lib\resources.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\rt.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jce.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.7.0\jre\classes > sun.boot.library.path = C:\Program Files\Java\jdk1.7.0\jre\bin > sun.cpu.endian = little > sun.cpu.isalist = amd64 > sun.desktop = windows > sun.io.unicode.encoding = UnicodeLittle > sun.java.command = D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\jboss-modules.jar -mp D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\modules org.jboss.as.standalone -Djboss.home.dir=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final -Djboss.bind.address=127.0.0.1 -Djboss.bind.address.unsecure=127.0.0.1 > sun.java.launcher = SUN_STANDARD > sun.jnu.encoding = Cp1252 > sun.management.compiler = HotSpot 64-Bit Tiered Compilers > sun.os.patch.level = Service Pack 1 > user.country = FR > user.dir = D:\Projets\_RD\BlackTieCobolIT\bin > user.home = C:\Users\epetremann > user.language = fr > user.name = epetremann > user.script = > user.timezone = Europe/Paris > user.variant = > 2014-06-04 09:43:07,003 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\log\server.log -Dlogging.configuration=file:D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\configuration/logging.properties > 2014-06-04 09:43:16,246 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 2014-06-04 09:43:16,273 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.2.0.Final > 2014-06-04 09:43:16,281 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.2.0.Final > 2014-06-04 09:43:16,341 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. > 2014-06-04 09:43:16,342 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem > 2014-06-04 09:43:16,348 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem > 2014-06-04 09:43:16,350 INFO [org.wildfly.extension.blacktie] (ServerService Thread Pool -- 59) Starting Blacktie Susbsystem > 2014-06-04 09:43:16,351 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem > 2014-06-04 09:43:16,363 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension > 2014-06-04 09:43:16,365 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.20.Final > 2014-06-04 09:43:16,390 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] > 2014-06-04 09:43:16,397 INFO [org.jboss.as.connector.logging] (MSC service thread 1-11) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final) > 2014-06-04 09:43:16,454 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service > 2014-06-04 09:43:16,458 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/mail/Default] > 2014-06-04 09:43:16,666 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 2014-06-04 09:43:16,669 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2 > 2014-06-04 09:43:16,796 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017502: Undertow 1.0.0.Final starting > 2014-06-04 09:43:16,800 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Final starting > 2014-06-04 09:43:16,853 INFO [org.wildfly.extension.blacktie] (MSC service thread 1-2) Starting StompConnect tcp://127.0.0.1:61613 > 2014-06-04 09:43:16,875 INFO [org.codehaus.stomp.tcp.TcpTransportServer] (MSC service thread 1-2) Listening for connections at: tcp://127.0.0.1:61613 > 2014-06-04 09:43:16,876 INFO [org.wildfly.extension.blacktie] (MSC service thread 1-2) Started StompConnect tcp://127.0.0.1:61613 > 2014-06-04 09:43:16,909 WARN [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal > 2014-06-04 09:43:16,973 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messagingjournal,bindingsDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messagingbindings,largeMessagesDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messaginglargemessages,pagingDirectory=D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\data\messagingpaging) > 2014-06-04 09:43:16,977 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221006: Waiting to obtain live lock > 2014-06-04 09:43:16,980 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.0.Final > 2014-06-04 09:43:17,005 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221013: Using NIO Journal > 2014-06-04 09:43:17,061 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017527: Creating file handler for path D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final/welcome-content > 2014-06-04 09:43:17,064 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 60) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. > 2014-06-04 09:43:17,071 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017525: Started server default-server. > 2014-06-04 09:43:17,076 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) JBAS017531: Host default-host starting > 2014-06-04 09:43:17,085 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 2014-06-04 09:43:17,106 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017519: Undertow HTTP listener default listening on 127.0.0.1/127.0.0.1:8080 > 2014-06-04 09:43:17,108 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support CORE > 2014-06-04 09:43:17,157 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-12) JBAS015012: Started FileSystemDeploymentService for directory D:\Projets\_RD\BlackTieCobolIT\bin\wildfly-8.0.0.Final\standalone\deployments > 2014-06-04 09:43:17,162 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "blacktie-admin-services-ear-5.0.0.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.0.0.Final.ear") > 2014-06-04 09:43:17,196 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:9999 > 2014-06-04 09:43:17,319 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,320 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,326 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,384 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support AMQP > 2014-06-04 09:43:17,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,389 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support STOMP > 2014-06-04 09:43:17,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,393 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,395 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,397 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,396 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,400 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,399 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,404 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,402 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,406 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,404 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,409 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,408 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,407 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,413 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,411 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,416 WARN [jacorb.codeset] (MSC service thread 1-9) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1 > 2014-06-04 09:43:17,414 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,417 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,417 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,421 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,419 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,424 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,423 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,426 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,424 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,430 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,428 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,432 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221034: Waiting to obtain live lock > 2014-06-04 09:43:17,432 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,430 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,434 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,433 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221035: Live Server Obtained live lock > 2014-06-04 09:43:17,433 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,436 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,435 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,439 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,439 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,441 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,440 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,443 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,442 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,444 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,446 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,446 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,448 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,447 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,450 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,450 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,452 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,451 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,454 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,453 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,456 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,455 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,457 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,461 INFO [org.jboss.as.jacorb] (MSC service thread 1-9) JBAS016330: CORBA ORB Service started > 2014-06-04 09:43:17,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,463 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,462 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,466 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,466 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,467 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,470 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,471 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,472 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,473 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,475 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,475 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,477 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,476 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,478 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 2014-06-04 09:43:17,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,488 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,489 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,490 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 2014-06-04 09:43:17,492 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,493 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,495 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,496 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,497 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,498 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,500 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,501 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,502 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,503 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,504 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-4) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 2014-06-04 09:43:17,638 INFO [org.jboss.as.jacorb] (MSC service thread 1-13) JBAS016328: CORBA Naming Service started > 2014-06-04 09:43:17,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /rest-at-coordinator > 2014-06-04 09:43:17,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: rest-at-participant > 2014-06-04 09:43:17,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) JBAS017534: Registered web context: volatile-rest-at-participant > 2014-06-04 09:43:18,284 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221020: Started Netty Acceptor version unknown 127.0.0.1:5445 > 2014-06-04 09:43:18,329 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221020: Started Netty Acceptor version unknown 127.0.0.1:5455 > 2014-06-04 09:43:18,331 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221007: Server is now live > 2014-06-04 09:43:18,332 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [5de4de80-e671-11e3-bd9e-7d17f38f2f22] > 2014-06-04 09:43:18,354 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 2014-06-04 09:43:18,357 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 2014-06-04 09:43:18,428 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-13) JBAS010406: Registered connection factory java:/JmsXA > 2014-06-04 09:43:18,538 INFO [org.hornetq.ra] (MSC service thread 1-13) HornetQ resource adaptor started > 2014-06-04 09:43:18,539 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-13) IJ020002: Deployed: file://RaActivatorhornetq-ra > 2014-06-04 09:43:18,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-9) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > 2014-06-04 09:43:18,543 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 2014-06-04 09:43:18,665 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final > 2014-06-04 09:43:19,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb-api.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,738 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb-impl.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,739 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jsr173_1.0_api.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,740 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /D:/Projets/_RD/BlackTieCobolIT/bin/content/blacktie-admin-services-ear-5.0.0.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 2014-06-04 09:43:19,749 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015876: Starting deployment of "null" (runtime-name: "blacktie-admin-services-5.0.0.Final.jar") > 2014-06-04 09:43:20,108 WARN [org.jboss.as.dependency.private] (MSC service thread 1-10) JBAS018567: Deployment "deployment.blacktie-admin-services-ear-5.0.0.Final.ear.blacktie-admin-services-5.0.0.Final.jar" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 2014-06-04 09:43:20,111 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) JBAS018567: Deployment "deployment.blacktie-admin-services-ear-5.0.0.Final.ear" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 2014-06-04 09:43:20,125 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment blacktie-admin-services-ear-5.0.0.Final.ear > 2014-06-04 09:43:20,756 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.0.3.Final > 2014-06-04 09:43:20,931 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment blacktie-admin-services-5.0.0.Final.jar > 2014-06-04 09:43:20,937 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named QueueReaperBean in deployment unit subdeployment "blacktie-admin-services-5.0.0.Final.jar" of deployment "blacktie-admin-services-ear-5.0.0.Final.ear" are as follows: > java:global/blacktie-admin-services-ear-5.0.0.Final/blacktie-admin-services-5.0.0.Final/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean > java:app/blacktie-admin-services-5.0.0.Final/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean > java:module/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean > java:global/blacktie-admin-services-ear-5.0.0.Final/blacktie-admin-services-5.0.0.Final/QueueReaperBean > java:app/blacktie-admin-services-5.0.0.Final/QueueReaperBean > java:module/QueueReaperBean > 2014-06-04 09:43:20,981 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016005: Starting Services for CDI deployment: blacktie-admin-services-ear-5.0.0.Final.ear > 2014-06-04 09:43:21,039 INFO [org.jboss.weld.Version] (MSC service thread 1-11) WELD-000900: 2.1.2 (Final) > 2014-06-04 09:43:21,052 INFO [org.jboss.weld.deployer] (MSC service thread 1-13) JBAS016008: Starting weld service for deployment blacktie-admin-services-ear-5.0.0.Final.ear > 2014-06-04 09:43:21,186 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.BTR_BTDomainAdmin > 2014-06-04 09:43:21,211 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name /queue/BTR_BTDomainAdmin > 2014-06-04 09:43:21,212 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.BTR_BTStompAdmin > 2014-06-04 09:43:21,216 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name /queue/BTR_BTStompAdmin > 2014-06-04 09:43:21,225 INFO [org.jboss.as.ejb3] (MSC service thread 1-9) JBAS014142: Started message driven bean 'BlacktieStompAdministrationService' with 'hornetq-ra.rar' resource adapter > 2014-06-04 09:43:21,226 INFO [org.jboss.as.ejb3] (MSC service thread 1-15) JBAS014142: Started message driven bean 'BlacktieAdminServiceXATMI' with 'hornetq-ra.rar' resource adapter > 2014-06-04 09:43:21,267 INFO [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (MSC service thread 1-15) onConstruct load btconfig.xml > 2014-06-04 09:43:21,582 INFO [org.jboss.narayana.blacktie.administration.BlacktieAdminService] (MSC service thread 1-15) Admin Server Started > 2014-06-04 09:43:21,608 WARN [org.jboss.weld.Validator] (MSC service thread 1-8) WELD-001471: Interceptor method start defined on class org.jboss.narayana.blacktie.administration.QueueReaperBean is not defined according to the specification. It should not throw java.lang.Exception, which is a checked exception. > 2014-06-04 09:43:21,766 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) QueueReaper Started > 2014-06-04 09:43:21,797 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) QeueueReaper cancel a timer > 2014-06-04 09:43:21,799 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) QueueReaper create timer with 30000ms > 2014-06-04 09:43:21,813 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014120: Error invoking timeout for timer: [id=29b5597e-d94e-410a-b641-464046270eed timedObjectId=blacktie-admin-services-ear-5.0.0.Final.blacktie-admin-services-5.0.0.Final.QueueReaperBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 40976d9a initialExpiration=Wed Jun 04 09:43:09 CEST 2014 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=queue reaper: javax.ejb.NoSuchObjectLocalException: JBAS014469: Timer was canceled > at org.jboss.as.ejb3.timerservice.TimerImpl.assertTimerState(TimerImpl.java:462) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.TimerImpl.getInfo(TimerImpl.java:237) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.narayana.blacktie.administration.QueueReaperBean.run(QueueReaperBean.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0] > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:95) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:104) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:55) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:52) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:340) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [wildfly-ee-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) [wildfly-security-manager-1.0.0.Final.jar:1.0.0.Final] > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.1.Final.jar:1.2.1.Final] > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:104) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > 2014-06-04 09:43:21,900 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014121: Timer: [id=29b5597e-d94e-410a-b641-464046270eed timedObjectId=blacktie-admin-services-ear-5.0.0.Final.blacktie-admin-services-5.0.0.Final.QueueReaperBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 40976d9a initialExpiration=Wed Jun 04 09:43:09 CEST 2014 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=queue reaper will be retried > 2014-06-04 09:43:21,901 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014124: Timer is not active, skipping retry of timer: [id=29b5597e-d94e-410a-b641-464046270eed timedObjectId=blacktie-admin-services-ear-5.0.0.Final.blacktie-admin-services-5.0.0.Final.QueueReaperBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 40976d9a initialExpiration=Wed Jun 04 09:43:09 CEST 2014 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=queue reaper > 2014-06-04 09:43:21,902 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "blacktie-admin-services-ear-5.0.0.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.0.0.Final.ear") > 2014-06-04 09:43:21,922 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 2014-06-04 09:43:21,923 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 2014-06-04 09:43:21,924 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final "WildFly" started in 20202ms - Started 403 of 462 services (107 services are lazy, passive or on-demand) > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 08:27:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Nov 2014 08:27:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2272) ISE failure in CDI transactional observer methods with remote EJB call using JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2272: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ISE failure in CDI transactional observer methods with remote EJB call using JTS > -------------------------------------------------------------------------------- > > Key: JBTM-2272 > URL: https://issues.jboss.org/browse/JBTM-2272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 4.17.23, 5.0.3 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 4.17.24, 5.0.4 > > > See the reproduce steps in https://bugzilla.redhat.com/show_bug.cgi?id=1098127 > and the description in https://issues.jboss.org/browse/WFLY-3548 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 08:37:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 08:37:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2279: --------------------------------- > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 08:40:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Nov 2014 08:40:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2279: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/755, https://github.com/jbosstm/narayana/pull/770 (was: https://github.com/jbosstm/narayana/pull/755) I agree Mark. The way I had it was more like the ability to set a default and switch on whether it can be overridden. I think it is much clearer to just allow/suppress setting the single reference of a CAF via that property. I have sent a new PR so when that passes I will merge it in. > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 09:16:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 19 Nov 2014 09:16:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2286: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 09:22:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 19 Nov 2014 09:22:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2292) Update Narayana release script In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2292: ------------------------------------- Summary: Update Narayana release script Key: JBTM-2292 URL: https://issues.jboss.org/browse/JBTM-2292 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.4 Following changes are needed for Narayana release script: * Documentation was completely changed by JBTM-2281, thus links have to be changed * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives * Upload download links to the new web page via github * Replace extracted versions of documentations on the web page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 09:25:40 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 19 Nov 2014 09:25:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2292) Update Narayana release script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2292: ---------------------------------- Description: Following changes are needed for Narayana release script: * Documentation was completely changed by JBTM-2281, thus links have to be changed * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives * Upload download links to the new web page via github * Replace extracted versions of documentations on the web page * Update narayana release process doc * Update webpage update readme was: Following changes are needed for Narayana release script: * Documentation was completely changed by JBTM-2281, thus links have to be changed * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives * Upload download links to the new web page via github * Replace extracted versions of documentations on the web page > Update Narayana release script > ------------------------------ > > Key: JBTM-2292 > URL: https://issues.jboss.org/browse/JBTM-2292 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Following changes are needed for Narayana release script: > * Documentation was completely changed by JBTM-2281, thus links have to be changed > * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives > * Upload download links to the new web page via github > * Replace extracted versions of documentations on the web page > * Update narayana release process doc > * Update webpage update readme -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 10:10:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 19 Nov 2014 10:10:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2281) Merge the documentation manuals together In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2281: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/documentation/pull/28 > Merge the documentation manuals together > ---------------------------------------- > > Key: JBTM-2281 > URL: https://issues.jboss.org/browse/JBTM-2281 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > The documentation for our project is available here: > Narayana Documentation 5.0.2.Final - JBoss Community > > As you can see it consists of several downloads including multiple books, links to various JavaDocs and some IDL files. Personally I think it might be easier to locate documentation entries if there is a single document to consult and a single JavaDoc link. I consulted our users whether anyone would object to us producing a single document and single JavaDoc set and received no objection. I am also thinking of no longer publishing the IDL as separate files as these are always tagged and available in our repo. > One way or another we need to make it clear in the docs what is in product and what is in project. Its not quite so important for our community users to know this but when translating docs into product manuals it is crucial. Currently this is done because everything under https://github.com/jbosstm/documentation/tree/master/docs is product related and things one level up are various community projects. An obvious way to merge the docs is merge everything under docs and then everything under ../* except docs - i.e. 2 manuals -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 10:10:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 19 Nov 2014 10:10:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2281) Merge the documentation manuals together In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2281: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Merge the documentation manuals together > ---------------------------------------- > > Key: JBTM-2281 > URL: https://issues.jboss.org/browse/JBTM-2281 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > The documentation for our project is available here: > Narayana Documentation 5.0.2.Final - JBoss Community > > As you can see it consists of several downloads including multiple books, links to various JavaDocs and some IDL files. Personally I think it might be easier to locate documentation entries if there is a single document to consult and a single JavaDoc link. I consulted our users whether anyone would object to us producing a single document and single JavaDoc set and received no objection. I am also thinking of no longer publishing the IDL as separate files as these are always tagged and available in our repo. > One way or another we need to make it clear in the docs what is in product and what is in project. Its not quite so important for our community users to know this but when translating docs into product manuals it is crucial. Currently this is done because everything under https://github.com/jbosstm/documentation/tree/master/docs is product related and things one level up are various community projects. An obvious way to merge the docs is merge everything under docs and then everything under ../* except docs - i.e. 2 manuals -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:17:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 11:17:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021244#comment-13021244 ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from ASSIGNED to POST > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:17:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 11:17:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021245#comment-13021245 ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from ASSIGNED to POST > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:18:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 11:18:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021246#comment-13021246 ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from ASSIGNED to POST > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:18:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 11:18:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2188) Some code that writes to the file store is missing PrivilidgedAction blocks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021247#comment-13021247 ] RH Bugzilla Integration commented on JBTM-2188: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1162882|https://bugzilla.redhat.com/show_bug.cgi?id=1162882] from ASSIGNED to POST > Some code that writes to the file store is missing PrivilidgedAction blocks > --------------------------------------------------------------------------- > > Key: JBTM-2188 > URL: https://issues.jboss.org/browse/JBTM-2188 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.0.3 > > > This means the code can fail when a security manager is present, as if deployment code is on the call stack it will not be able to write or read from the files. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:31:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Nov 2014 11:31:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk and wget are not installed on Catelyn In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2290: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/771 > Gawk and wget are not installed on Catelyn > ------------------------------------------ > > Key: JBTM-2290 > URL: https://issues.jboss.org/browse/JBTM-2290 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ > {code} > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > * [new branch] master -> upstream/master > First, rewinding head to replay your work on top of it... > Auto-merging pom.xml > [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT > Author: Tom Jenkinson > 1 file changed, 1 insertion(+), 1 deletion(-) > Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT > All done. > 'gawk' is not recognized as an internal or external command, > operable program or batch file. > "AS version is " > Build step 'Execute Windows batch command' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler at redhat.com > Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:49:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 19 Nov 2014 15:49:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021334#comment-13021334 ] Mark Little commented on JBTM-2279: ----------------------------------- Nice. Thanks Tom. > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 17:40:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 17:40:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021361#comment-13021361 ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- Kabir Khan changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from POST to MODIFIED > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 17:41:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 17:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021362#comment-13021362 ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- Kabir Khan changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from POST to MODIFIED > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 17:41:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 17:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021363#comment-13021363 ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- Kabir Khan changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from POST to MODIFIED > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 17:41:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Nov 2014 17:41:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2188) Some code that writes to the file store is missing PrivilidgedAction blocks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021364#comment-13021364 ] RH Bugzilla Integration commented on JBTM-2188: ----------------------------------------------- Kabir Khan changed the Status of [bug 1162882|https://bugzilla.redhat.com/show_bug.cgi?id=1162882] from POST to MODIFIED > Some code that writes to the file store is missing PrivilidgedAction blocks > --------------------------------------------------------------------------- > > Key: JBTM-2188 > URL: https://issues.jboss.org/browse/JBTM-2188 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.0.3 > > > This means the code can fail when a security manager is present, as if deployment code is on the call stack it will not be able to write or read from the files. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 07:28:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 20 Nov 2014 07:28:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2292) Update Narayana release script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2292: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/772 > Update Narayana release script > ------------------------------ > > Key: JBTM-2292 > URL: https://issues.jboss.org/browse/JBTM-2292 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Following changes are needed for Narayana release script: > * Documentation was completely changed by JBTM-2281, thus links have to be changed > * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives > * Upload download links to the new web page via github > * Replace extracted versions of documentations on the web page > * Update narayana release process doc > * Update webpage update readme -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 08:03:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 20 Nov 2014 08:03:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2293) Create a docker file to make web page update easier In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2293: ------------------------------------- Summary: Create a docker file to make web page update easier Key: JBTM-2293 URL: https://issues.jboss.org/browse/JBTM-2293 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.4 Awestruct recuires quite a few dependencies to build a web page. Although it is not hard to install them manually, it is time consuming. It would be much easier to use docker for this. This docker file is a good start: https://github.com/goldmann/dockerfiles/tree/master/awestruct -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 21:32:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 20 Nov 2014 21:32:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2290) Gawk and wget are not installed on Catelyn In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2290: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Gawk and wget are not installed on Catelyn > ------------------------------------------ > > Key: JBTM-2290 > URL: https://issues.jboss.org/browse/JBTM-2290 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/776/ > {code} > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > * [new branch] master -> upstream/master > First, rewinding head to replay your work on top of it... > Auto-merging pom.xml > [detached HEAD a40514f] Upgrade Narayana to 5.0.4.Final-SNAPSHOT > Author: Tom Jenkinson > 1 file changed, 1 insertion(+), 1 deletion(-) > Committed: 0001 Upgrade Narayana to 5.0.4.Final-SNAPSHOT > All done. > 'gawk' is not recognized as an internal or external command, > operable program or batch file. > "AS version is " > Build step 'Execute Windows batch command' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler at redhat.com > Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 21:37:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 20 Nov 2014 21:37:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2294) There is missing catelyn configuration in the btconfig.xml In-Reply-To: References: Message-ID: Amos Feng created JBTM-2294: ------------------------------- Summary: There is missing catelyn configuration in the btconfig.xml Key: JBTM-2294 URL: https://issues.jboss.org/browse/JBTM-2294 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.4 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 21:49:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 20 Nov 2014 21:49:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2294) There is missing catelyn configuration in the btconfig.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2294: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/773 > There is missing catelyn configuration in the btconfig.xml > ---------------------------------------------------------- > > Key: JBTM-2294 > URL: https://issues.jboss.org/browse/JBTM-2294 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 03:42:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 21 Nov 2014 03:42:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2294) There is missing catelyn configuration in the btconfig.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2294: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > There is missing catelyn configuration in the btconfig.xml > ---------------------------------------------------------- > > Key: JBTM-2294 > URL: https://issues.jboss.org/browse/JBTM-2294 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:34:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 21 Nov 2014 10:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-1683: --------------------------------- > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:34:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 21 Nov 2014 10:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1683: -------------------------------- Fix Version/s: 5.0.4 (was: 5.0.0) > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:34:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 21 Nov 2014 10:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1683: -------------------------------- Affects Version/s: 5.0.0 > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:36:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 21 Nov 2014 10:36:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021979#comment-13021979 ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-windows2008-catelyn/783/ > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:46:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 21 Nov 2014 10:46:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021982#comment-13021982 ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- >From http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-windows2008-catelyn/783/artifact/blacktie/btadmin/target/test-classes/blacktie-C.log {quote} 2014-11-21 10:37:47,584 [0x00000f80] DEBUG (HybridSocketEndpointQueue:221 ) - waiting message with time 50 2014-11-21 10:37:47,584 [0x00000474] DEBUG (SocketServer :274 ) - connection from 127.0.0.1:60866 2014-11-21 10:37:47,577 [0x000007e0] TRACE (TxXAResourceManagerFactory:111 ) - ENTER 2014-11-21 10:37:47,584 [0x000007e0] TRACE (TxXAResourceManagerFactory:126 ) - ENTER 2014-11-21 10:37:47,585 [0x000007e0] TRACE (TxXARecoveryLog :120 ) - destructor 2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :101 ) - Releasing mutex: 008667A0 2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :103 ) - released mutex: 008667A0 2014-11-21 10:37:47,585 [0x000007e0] TRACE (TxManagerc :35 ) - < 2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 1005FE1C 2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :58 ) - acquired: 1005FE1C 2014-11-21 10:37:47,585 [0x000007e0] TRACE (AtmiBrokerEnv :92 ) - Reference count: 3 2014-11-21 10:37:47,585 [0x000007e0] TRACE (SynchronizableObject :101 ) - Releasing mutex: 1005FE1C 2014-11-21 10:37:47,586 [0x000007e0] TRACE (SynchronizableObject :103 ) - released mutex: 1005FE1C 2014-11-21 10:37:47,586 [0x000007e0] DEBUG (AtmiBrokerServer :630 ) - deleted services 2014-11-21 10:37:47,586 [0x000007e0] TRACE (ConnectionManager :53 ) - closeConnections {quote} Tallies up with albanys: /home/hudson/jobs/narayana-windows2008-catelyn/builds/783/archive/blacktie/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log/server.log {quote} 2014-11-21 10:37:47,735 WARN [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketSenderImpl] (Thread-25 (HornetQ-client-global-threads-27681350)) socket send with java.net.SocketException: Connection reset by peer: socket write error {quote} Why are we closing the connection on the client side? > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 11:11:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 21 Nov 2014 11:11:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2216) Extraneous warning message observed in XARecoveryModule.xaRecoverySecondPass if the first pass has already failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2216: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166754 > Extraneous warning message observed in XARecoveryModule.xaRecoverySecondPass if the first pass has already failed > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2216 > URL: https://issues.jboss.org/browse/JBTM-2216 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.20, 4.17.21, 5.0.2 > Environment: JBoss EAP 6.3 > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 4.17.23, 5.0.4 > > > When using AMQ failover protocol, the Narayana recovery process generates the following exception: > {noformat} > 10:19:36,053 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://ragga:61616?trace=true > 10:21:46,139 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://ragga:61616?trace=true > 10:21:46,139 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: Failover transport not connected: unconnected > at org.apache.activemq.TransactionContext.recover(TransactionContext.java:656) > at org.apache.activemq.ra.LocalAndXATransaction.recover(LocalAndXATransaction.java:135) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.recover(XAResourceWrapperImpl.java:177) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:548) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:187) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > 10:21:56,165 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:619) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.21.Final-redhat-1.jar:4.17.21.Final-redhat-1] > {noformat} > Although the first message may be expected if the resource manager throws an exception in XAResource::recover(), the second message does not add any further assistance in resolving the issue and should be removed as noise. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 11:12:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 21 Nov 2014 11:12:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2284: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166754 > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 11:45:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 21 Nov 2014 11:45:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS recovery module forgets about transaction -> transaction never recovered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2287: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166754 > JTS recovery module forgets about transaction -> transaction never recovered > ---------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 11:56:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 21 Nov 2014 11:56:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2287) JTS mode sends an erroneous xa_end to resource manager if prepare() returns RMFAIL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2287: -------------------------------- Summary: JTS mode sends an erroneous xa_end to resource manager if prepare() returns RMFAIL (was: JTS recovery module forgets about transaction -> transaction never recovered) > JTS mode sends an erroneous xa_end to resource manager if prepare() returns RMFAIL > ---------------------------------------------------------------------------------- > > Key: JBTM-2287 > URL: https://issues.jboss.org/browse/JBTM-2287 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss Transactions 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The scenario is as follows (and works fine with JTA, see below): > Two XAResources in the same transaction, with xid1 and xid2, respectively. > (For better readability, log file excerpts are referenced and provided at the end of the description.) > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > end xid1, tmfail -> against XA protocol, however silently ignored by us > [error1 printed in log file] > end xid2, tmfail > rollback xid2 > [error2 printed in log file] > [JTS: periodic, but fruitless recovery attempts] > as an effect, the transaction branch is never recovered and the dead transaction hangs around forever in the database; it looks like, as if the JTS recovery component forgot to early about that transaction, so does not do any rollback/commit decision for the reported to-be-recovered transaction > with JTA the call sequence is as follows: > start xid1 > start xid2 > end xid1, tmsuccess > prepare xid1 -> XAException.XAER_RMFAIL; provoked, txn is indeed prepared in our test case > rollback xid1 //this races with recovery module, but in any case, will be rolled back > end xid2, tmfail > rollback xid2 > [JTA: periodic, successfull recovery] > With JTA, rollback might even be triggered twice (second invocation ignored by us) > here the log file excerpts, Xids printed with own toString() impl, because of JBTM-2284) > [JTA: periodic, successfull recovery] > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:48:20,646 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131077-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.41.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.113.21.-21.110.84.100.126.76.0.0.0.42.0.0.0.0.0.0.0.0 > 10:48:23,689 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Rolled back xid < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a6a3229:7115eb6e:54647e4c:29, node_name=1, branch_uid=0:ffff0a6a3229:7115eb6e:54647e4c:2a, subordinatenodename=null, eis_name=unknown eis name > > [JTS: periodic, but fruitless recovery attempts] > 09:59:49,664 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:49,665 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 09:59:58,022 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:06,067 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:14,184 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:22,275 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:30,329 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:38,377 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:46,493 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Found 1 XA transactions to recover. > 10:00:54,545 INFO [com.versant.odbms.XARecoveryResource] (Periodic Recovery) Versant JPA: Xid to recover: 131072-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.70.49-0.0.0.0.0.0.0.0.0.0.-1.-1.10.106.50.41.-50.-61.50.100.84.100.114.-11.0.0.0.72.0.0.0.0.0.0.0.0 > [error1] > 09:59:46,904 WARN [com.arjuna.ats.jts] (EJB default - 4) ARJUNA022223: ExtendedResourceRecord.topLevelAbort caught exception: org.omg.CORBA.UNKNOWN: Server-side Exception: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25] > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:319) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1090) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.jacorb.orb.Delegate.invoke(Delegate.java:957) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80) [jacorb-2.3.2.redhat-6.jar:2.3.2.redhat-6] > at com.arjuna.ArjunaOTS._ArjunaSubtranAwareResourceStub.rollback(_ArjunaSubtranAwareResourceStub.java:75) > at com.arjuna.ats.internal.jts.resources.ExtendedResourceRecord.topLevelAbort(ExtendedResourceRecord.java:445) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2875) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2854) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1924) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494) > at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) > at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.3.4.Final-redhat-1.jar:7.3.4.Final-redhat-1] > > [error2] > 09:59:46,962 ERROR [stderr] (EJB default - 4) org.omg.CORBA.TRANSACTION_ROLLEDBACK > 09:59:46,962 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:414) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:243) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1296) > 09:59:46,963 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > 09:59:46,964 ERROR [stderr] (EJB default - 4) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:37:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:37:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2267) Create a docker image with JTS transaction manager and recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022161#comment-13022161 ] Mark Little commented on JBTM-2267: ----------------------------------- There's no obvious place where this stuff can be checked in for now so I'll add the information here. I'll also create a few relevant JIRAs. First all relevant builds and files can be found https://github.com/nmcl/docker-narayana Start with a Fedora image. Then using the Dockerfile run 'docker build .' Start the image using 'docker run -i -t ' The Dockerfile is basic. It uses a pre-built version of Narayana and then starts the recovery manager and transaction manager. The resulting IOR for the transaction manager is stored in the CosServices.cfg within the running docker image. It (or the contents) need to be copied or made available to a client running outside of the image, so we can show that we have a transactionmanager-as-a-service. I used git for this and pushed the CosServices.cfg up to the aforementioned git repo, pulling it down from there to a local fedora instance. But there has to be a better way of doing this. Anyway, once you've got the CosServices.cfg file, use the modified TMTest client to check to see that we can create a transaction in the running Docker image. Output should show this to be the case, e.g., see attached image. This is a POC. It works and demonstrates what's possible. But it needs tidying up at least. See associated JIRAs. > Create a docker image with JTS transaction manager and recovery manager > ----------------------------------------------------------------------- > > Key: JBTM-2267 > URL: https://issues.jboss.org/browse/JBTM-2267 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Mark Little > Attachments: Screen Shot 2014-11-23 at 18.35.40.png > > > Should help with a) using docker and b) providing transactions-as-a-service. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:37:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:37:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2267) Create a docker image with JTS transaction manager and recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little updated JBTM-2267: ------------------------------ Attachment: Screen Shot 2014-11-23 at 18.35.40.png > Create a docker image with JTS transaction manager and recovery manager > ----------------------------------------------------------------------- > > Key: JBTM-2267 > URL: https://issues.jboss.org/browse/JBTM-2267 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Mark Little > Attachments: Screen Shot 2014-11-23 at 18.35.40.png > > > Should help with a) using docker and b) providing transactions-as-a-service. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:39:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:39:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2267) Create a docker image with JTS transaction manager and recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2267 stopped by Mark Little. ----------------------------------------- > Create a docker image with JTS transaction manager and recovery manager > ----------------------------------------------------------------------- > > Key: JBTM-2267 > URL: https://issues.jboss.org/browse/JBTM-2267 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Mark Little > Attachments: Screen Shot 2014-11-23 at 18.35.40.png > > > Should help with a) using docker and b) providing transactions-as-a-service. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:40:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:40:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2267) Create a docker image with JTS transaction manager and recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-2267. ------------------------------- Resolution: Done > Create a docker image with JTS transaction manager and recovery manager > ----------------------------------------------------------------------- > > Key: JBTM-2267 > URL: https://issues.jboss.org/browse/JBTM-2267 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Mark Little > Attachments: Screen Shot 2014-11-23 at 18.35.40.png > > > Should help with a) using docker and b) providing transactions-as-a-service. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:40:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:40:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2267) Create a docker image with JTS transaction manager and recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2267. ----------------------------- > Create a docker image with JTS transaction manager and recovery manager > ----------------------------------------------------------------------- > > Key: JBTM-2267 > URL: https://issues.jboss.org/browse/JBTM-2267 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Mark Little > Attachments: Screen Shot 2014-11-23 at 18.35.40.png > > > Should help with a) using docker and b) providing transactions-as-a-service. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:41:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: Mark Little created JBTM-2295: --------------------------------- Summary: Expose REST-TX (and WS-TX) endpoints through Docker Key: JBTM-2295 URL: https://issues.jboss.org/browse/JBTM-2295 Project: JBoss Transaction Manager Issue Type: Feature Request Components: REST, XTS Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Michael Musgrove -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:43:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:43:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: Mark Little created JBTM-2296: --------------------------------- Summary: Provide better way of distributing IOR to users Key: JBTM-2296 URL: https://issues.jboss.org/browse/JBTM-2296 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTS Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Tom Jenkinson Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:45:40 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:45:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo In-Reply-To: References: Message-ID: Mark Little created JBTM-2297: --------------------------------- Summary: Store docker image for service(s) in JBoss repo Key: JBTM-2297 URL: https://issues.jboss.org/browse/JBTM-2297 Project: JBoss Transaction Manager Issue Type: Task Components: JTS, REST, XTS Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Michael Musgrove We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:47:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:47:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: Mark Little created JBTM-2298: --------------------------------- Summary: Use Project Atomic for docker image(s) Key: JBTM-2298 URL: https://issues.jboss.org/browse/JBTM-2298 Project: JBoss Transaction Manager Issue Type: Task Components: JTS, REST, XTS Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Michael Musgrove When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:54:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:54:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1605) Integrate STM with vert.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-1605. ------------------------------- Resolution: Done Done for now. Details published to Vert.x group a few months back. Waiting on further feedback before doing more. > Integrate STM with vert.x > ------------------------- > > Key: JBTM-1605 > URL: https://issues.jboss.org/browse/JBTM-1605 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M2 > Reporter: Mark Little > Assignee: Mark Little > > Finish the work started last year. Actor+transaction model. > Due to the typical way vert.x works (one thread per task, unique classloader instance etc.), shared state is typically not a concern even between threads. STM still useful to ensure atomic updates in the presence of failures, or sharing via message passing. However, with our STM implementation, persistent instances can be shared between threads or processes in different address spaces if needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:54:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:54:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1605) Integrate STM with vert.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-1605. ----------------------------- > Integrate STM with vert.x > ------------------------- > > Key: JBTM-1605 > URL: https://issues.jboss.org/browse/JBTM-1605 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M2 > Reporter: Mark Little > Assignee: Mark Little > > Finish the work started last year. Actor+transaction model. > Due to the typical way vert.x works (one thread per task, unique classloader instance etc.), shared state is typically not a concern even between threads. STM still useful to ensure atomic updates in the presence of failures, or sharing via message passing. However, with our STM implementation, persistent instances can be shared between threads or processes in different address spaces if needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:55:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:55:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little updated JBTM-223: ----------------------------- Assignee: (was: Mark Little) > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Fix For: 6.0.0 > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 13:56:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 13:56:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little updated JBTM-2122: ------------------------------ Summary: Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got (was: Go through JTS code and compare/contrast with capabilities missing in other diet tx code we've got) > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 14:23:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 14:23:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-185) Check POA attributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-185. ------------------------------ Resolution: Out of Date > Check POA attributes > -------------------- > > Key: JBTM-185 > URL: https://issues.jboss.org/browse/JBTM-185 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Mark Little > Assignee: Mark Little > > Check use of POA attribute for transaction context propagation in interceptors. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 14:23:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 14:23:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-185) Check POA attributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-185. ---------------------------- > Check POA attributes > -------------------- > > Key: JBTM-185 > URL: https://issues.jboss.org/browse/JBTM-185 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Mark Little > Assignee: Mark Little > > Check use of POA attribute for transaction context propagation in interceptors. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:19:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:19:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: Mark Little created JBTM-2299: --------------------------------- Summary: Why does Blacktie have its own CosTransactions.idl? Key: JBTM-2299 URL: https://issues.jboss.org/browse/JBTM-2299 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Amos Feng Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:28:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:28:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1759) Update the OTS related IDL files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022164#comment-13022164 ] Mark Little commented on JBTM-1759: ----------------------------------- Removed DRAFT3. That's dating back to 1991 and all ORBs we're using today should not be impacted by this. > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:28:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:28:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1759) Update the OTS related IDL files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022165#comment-13022165 ] Mark Little commented on JBTM-1759: ----------------------------------- Updated CosTSInteroperation.idl for not. However, we should be getting to a point where we can use the CosTransactions.idl and friends provided by the ORB we're using. That's always been the goal. > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:30:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:30:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1759) Update the OTS related IDL files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022166#comment-13022166 ] Mark Little commented on JBTM-1759: ----------------------------------- Also removed ORB_OTS_SUPPORT because all ORBs we're using today support the various OTS specific exceptions as CORBA SystemExceptions. > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:51:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:51:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1759) Update the OTS related IDL files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022164#comment-13022164 ] Mark Little edited comment on JBTM-1759 at 11/23/14 3:51 PM: ------------------------------------------------------------- Removed DRAFT3. That's dating back to 1996 and all ORBs we're using today should not be impacted by this. was (Author: marklittle): Removed DRAFT3. That's dating back to 1991 and all ORBs we're using today should not be impacted by this. > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:58:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:58:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1759) Update the OTS related IDL files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-1759. ------------------------------- Resolution: Done > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 15:58:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 15:58:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1759) Update the OTS related IDL files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-1759. ----------------------------- > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 16:52:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 16:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1450) Transaction processing in javascript In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022167#comment-13022167 ] Mark Little commented on JBTM-1450: ----------------------------------- This should now be done through the Nodyn project. > Transaction processing in javascript > ------------------------------------ > > Key: JBTM-1450 > URL: https://issues.jboss.org/browse/JBTM-1450 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Student project > Reporter: jhalli > Labels: student > Fix For: 6.0.0 > > > Student project that we are not currently offering: > {quote} > Increasingly sophisticated applications are being implemented using the javascript language. Initially popular for browser based environments, the language is also gaining traction on the server side (NodeJS, etc). A single threaded model promotes use of callbacks and asynchronous I/O operations. Ongoing standardization work is starting to provide APIs for enterprise functionality (commonJS, IndexedDB, etc). The Rhino javascript engine allows javascript to run on any JVM. These factors lead to situations where distributed business applications may be written wholly or partially in javascript and may need to interact with existing business logic or services implemented in Java. In this project you will consider how to provide transaction management capabilities to such applications. > This project will require a good knowledge of javascript programming, ideally encompassing a server side javascript environment. Candidates should also possess some knowledge of Java and transaction concepts. The work will be open source. > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 23 16:53:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 23 Nov 2014 16:53:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by AS7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022168#comment-13022168 ] Mark Little commented on JBTM-1339: ----------------------------------- Isn't this out of date now? > Ensure that JTS can use the JDK ORB provided by AS7 > --------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 03:52:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 03:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022218#comment-13022218 ] Amos Feng commented on JBTM-1683: --------------------------------- Thanks [~tomjenkinson] for pointing it out and it looks like happening every often on the catelyn node. It's maybe a time issue and I will take a look at it. > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 03:52:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 03:52:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-1683: ---------------------------- Priority: Major (was: Minor) > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:08:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 06:08:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by AS7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1339: -------------------------------- Assignee: Michael Musgrove > Ensure that JTS can use the JDK ORB provided by AS7 > --------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:09:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 06:09:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by AS7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022276#comment-13022276 ] Tom Jenkinson commented on JBTM-1339: ------------------------------------- I think Mike is still working with Tomasz on this. I have assigned it to Mike, I am not sure why it was unassigned. > Ensure that JTS can use the JDK ORB provided by AS7 > --------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:22:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 24 Nov 2014 06:22:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests failed In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2300: ------------------------------------- Summary: XATMI implemenation tests failed Key: JBTM-2300 URL: https://issues.jboss.org/browse/JBTM-2300 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Gytis Trikleris Assignee: Amos Feng Fix For: 5.0.4 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/694/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/consoleFull -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:28:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 24 Nov 2014 06:28:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2228) HotelBookingTest#testSuccess fails because of missing transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022284#comment-13022284 ] Gytis Trikleris commented on JBTM-2228: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstarts/122/ http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstarts/123/ > HotelBookingTest#testSuccess fails because of missing transaction > ----------------------------------------------------------------- > > Key: JBTM-2228 > URL: https://issues.jboss.org/browse/JBTM-2228 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana-quickstarts/93 > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.quickstarts.compensationsApi.hotel.HotelBookingTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.894 sec <<< FAILURE! > testSuccess(org.jboss.narayana.quickstarts.compensationsApi.hotel.HotelBookingTest) Time elapsed: 0.502 sec <<< ERROR! > java.lang.NullPointerException > at org.jboss.narayana.compensations.impl.CompensationManagerImpl.setCompensateOnly(CompensationManagerImpl.java:39) > at org.jboss.narayana.compensations.impl.CompensationInterceptorBase.handleException(CompensationInterceptorBase.java:94) > at org.jboss.narayana.compensations.impl.CompensationInterceptorBase.invokeInCallerTx(CompensationInterceptorBase.java:74) > at org.jboss.narayana.compensations.impl.CompensationInterceptorRequired.intercept(CompensationInterceptorRequired.java:46) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:116) > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:94) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:43) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:36) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:51) > at org.jboss.narayana.quickstarts.compensationsApi.hotel.HotelBookingClient$Proxy$_$$_WeldSubclass.makeBooking(Unknown Source) > at org.jboss.narayana.quickstarts.compensationsApi.hotel.HotelBookingTest.testSuccess(HotelBookingTest.java:72) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:243) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:230) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:149) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:195) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:733) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {code} > {code} > [0m06:06:42,113 ERROR [org.jboss.as.webservices] (default task-11) WFLYWS0056: Method invocation failed with exception: Transaction is required for invocation: org.jboss.narayana.compensations.api.TransactionalException: Transaction is required for invocation > at org.jboss.narayana.compensations.impl.CompensationInterceptorMandatory.intercept(CompensationInterceptorMandatory.java:46) [txframework-5.0.3.Final-SNAPSHOT.jar:5.0.3.Final-SNAPSHOT] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:116) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:94) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:43) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:36) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:51) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.narayana.quickstarts.compensationsApi.hotel.HotelServiceImpl$Proxy$_$$_WeldSubclass.makeBooking(Unknown Source) [test.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.webservices.deployers.WSComponentInstanceAssociationInterceptor.processInvocation(WSComponentInstanceAssociationInterceptor.java:49) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.webservices.invocation.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:130) > at org.jboss.wsf.stack.cxf.JBossWSInvoker.performInvocation(JBossWSInvoker.java:149) > at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104) > at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:237) > at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:69) > at org.jboss.wsf.stack.cxf.JBossWSInvoker.invoke(JBossWSInvoker.java:129) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51] > at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:107) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) > at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:241) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:97) > at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:131) > at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136) > at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.3.0.Final.jar:2.3.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:243) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:230) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:149) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:195) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:733) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > Caused by: org.jboss.narayana.compensations.api.TransactionRequiredException > ... 91 more > 06:06:42,173 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-11) Application {http://www.jboss.org/as/quickstarts/compensationsApi/travel/hotel}HotelServiceService#{http://www.jboss.org/as/quickstarts/compensationsApi/travel/hotel}makeBooking has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Transaction is required for invocation > at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:170) > at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:272) > at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:136) > at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:237) > at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:69) > at org.jboss.wsf.stack.cxf.JBossWSInvoker.invoke(JBossWSInvoker.java:129) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51] > at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:107) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) > at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:241) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:97) > at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:131) > at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136) > at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.3.0.Final.jar:2.3.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:243) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:230) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:149) [undertow-servlet-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:195) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:733) [undertow-core-1.1.0.Beta2.jar:1.1.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > Caused by: org.jboss.narayana.compensations.api.TransactionalException: Transaction is required for invocation > at org.jboss.narayana.compensations.impl.CompensationInterceptorMandatory.intercept(CompensationInterceptorMandatory.java:46) [txframework-5.0.3.Final-SNAPSHOT.jar:5.0.3.Final-SNAPSHOT] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:116) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:94) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:43) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:36) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:51) [weld-core-impl-2.2.1.Final.jar:2014-05-09 12:21] > at org.jboss.narayana.quickstarts.compensationsApi.hotel.HotelServiceImpl$Proxy$_$$_WeldSubclass.makeBooking(Unknown Source) [test.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.webservices.deployers.WSComponentInstanceAssociationInterceptor.processInvocation(WSComponentInstanceAssociationInterceptor.java:49) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.webservices.invocation.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:130) > at org.jboss.wsf.stack.cxf.JBossWSInvoker.performInvocation(JBossWSInvoker.java:149) > at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104) > ... 46 more > Caused by: org.jboss.narayana.compensations.api.TransactionRequiredException > ... 91 more > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:37:39 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 24 Nov 2014 06:37:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2301) PerformanceTest regression In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2301: ------------------------------------- Summary: PerformanceTest regression Key: JBTM-2301 URL: https://issues.jboss.org/browse/JBTM-2301 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.4 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/693/PROFILE=MAIN,jdk=jdk7.latest,label=linux/ {code} ------------------------------------------------------------------------------- Test set: io.narayana.perf.PerformanceTest ------------------------------------------------------------------------------- Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.898 sec <<< FAILURE! regressionTest(io.narayana.perf.PerformanceTest) Time elapsed: 6.268 sec <<< FAILURE! junit.framework.AssertionFailedError: There should have been a perf regression at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.TestCase.assertTrue(TestCase.java:192) at io.narayana.perf.PerformanceTest.regressionTest(PerformanceTest.java:296) {code} {code} Test Run: testTimeout (200 calls using 2 threads) ExecutionException exception: java.util.concurrent.BrokenBarrierException ExecutionException exception: java.util.concurrent.BrokenBarrierException testTimeout: 0.000000 calls / second (200 calls in 0 ms using 2 threads. 201 errors) Test Run: (100000 calls using 10 threads) TestPerformance for 100000!: 17164.435290 calls / second (total time: 5826 ms versus 46786 ms) Test Run: (1 calls using 1 threads) testSingleCall!: 1000.000000 calls / second (1 calls in 1 ms using 1 threads. 0 errors) Test Run: (10000 calls using 10 threads) perfTest!: 4268.032437 calls / second (10000 calls in 2343 ms using 10 threads. 0 errors) Test Run: (100 calls using 2 threads) java.lang.RuntimeException: Testing throw exception at io.narayana.perf.PerformanceTest$7.doWork(PerformanceTest.java:412) at io.narayana.perf.PerformanceTest$7.doWork(PerformanceTest.java:406) at io.narayana.perf.Measurement$1.call(Measurement.java:339) at io.narayana.perf.Measurement$1.call(Measurement.java:324) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) testCancelOnException!: 33333.333333 calls / second (100 calls in 3 ms using 2 threads. 20 errors) Test Run: io.narayana.perf.PerformanceTest_regressionTest (10000 calls using 10 threads) Test Run: io.narayana.perf.PerformanceTest_regressionTest (10000 calls using 10 threads) Test Run: (1000 calls using 10 threads) testAbortMeasurement2: 0.000000 calls / second (1000 calls in 0 ms using 10 threads. 11 errors) Test Warm Up: io.narayana.perf.PerformanceTest_readPerfArgsTest: (10 calls using 50 threads) Test Run: io.narayana.perf.PerformanceTest_readPerfArgsTest (1000000 calls using 50 threads) {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:00:40 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 24 Nov 2014 07:00:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by AS7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022305#comment-13022305 ] Mark Little commented on JBTM-1339: ----------------------------------- OK, thanks. Does the title of the issue need changing now though? I'm assuming we're not back porting this to AS7 and only focussing on WildFly. > Ensure that JTS can use the JDK ORB provided by AS7 > --------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:12:40 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 24 Nov 2014 07:12:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2302: -------------------------------------- Summary: Tooling can create two mbeans for a CMR record Key: JBTM-2302 URL: https://issues.jboss.org/browse/JBTM-2302 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.0.3, 4.17.23 Environment: JDK8 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.24, 5.0.4 The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: - the record is moved between the locations so there should only ever be one bean representation of it; - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. The fix is to do the bean remove before adding new beans for new records. It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:13:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 07:13:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1339: -------------------------------- Summary: Ensure that JTS can use the JDK ORB provided by WildFly (was: Ensure that JTS can use the JDK ORB provided by AS7) > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:13:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 07:13:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022316#comment-13022316 ] Tom Jenkinson commented on JBTM-1339: ------------------------------------- You are right, updated. > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:14:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 07:14:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-898) Align quickstart structures with WildFly quickstart pattern In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-898: ------------------------------- Summary: Align quickstart structures with WildFly quickstart pattern (was: Align quickstart structures with AS7 quickstart pattern) > Align quickstart structures with WildFly quickstart pattern > ----------------------------------------------------------- > > Key: JBTM-898 > URL: https://issues.jboss.org/browse/JBTM-898 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > > https://docs.jboss.org/author/display/AS71/Writing+a+quickstart -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:14:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 07:14:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1591) Ensure our ESB usage works on AS7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1591. ------------------------------- Resolution: Deferred We can reopen this issue if community requests it > Ensure our ESB usage works on AS7 > --------------------------------- > > Key: JBTM-1591 > URL: https://issues.jboss.org/browse/JBTM-1591 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 07:15:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 24 Nov 2014 07:15:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2302: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1165700 > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:05:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 09:05:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022378#comment-13022378 ] Amos Feng commented on JBTM-2300: --------------------------------- {code} 2014-11-19 21:38:59,659 [0x4ed7d40] DEBUG (HybridConnectionImpl :164 ) - Response: ERROR, javax.jms.JMSException: Failed to create session factory at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673) at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112) at org.codehaus.stomp.jms.ProtocolConverter.onStompConnect(ProtocolConverter.java:229) at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:182) at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) at java.lang.Thread.run(Thread.java:744) Caused by: HornetQNotConnectedException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.] at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:901) at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669) ... 5 more {code} It looks like the hornetq error and need more investigating. > XATMI implemenation tests failed > -------------------------------- > > Key: JBTM-2300 > URL: https://issues.jboss.org/browse/JBTM-2300 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/694/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/consoleFull -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:19:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 09:19:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022383#comment-13022383 ] Amos Feng commented on JBTM-1683: --------------------------------- I'm thinking to disable the btadmin tests on the windows temporarily and create the other CI job to run. > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:45:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 09:45:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2295: -------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:45:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 09:45:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2296: -------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:45:41 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 09:45:41 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2297: -------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Store docker image for service(s) in JBoss repo > ----------------------------------------------- > > Key: JBTM-2297 > URL: https://issues.jboss.org/browse/JBTM-2297 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:45:41 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 09:45:41 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2298: -------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 09:55:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 09:55:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022403#comment-13022403 ] Amos Feng commented on JBTM-2299: --------------------------------- It looks like we don't need it as we has removed the TAO dependency in JBTM-1665 and used the http rest methods to access the TM [~tomjenkinson], Does it make sense ? > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 10:29:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 10:29:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022406#comment-13022406 ] Tom Jenkinson commented on JBTM-2299: ------------------------------------- That sounds right, it looks like a relic and should be pruned. > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 10:32:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 10:32:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022407#comment-13022407 ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- I think the problem is that narayana.bat does not kill the java app server process. We should try to augment narayana.bat to kill it: https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.bat#L43 We do try to call shutdown.bat but if that hangs we don't have a mechanism to kill the process at the operating system level. We can test it out by creating a new job to target the killing because we don't have rdesktop to the node at the moment anyway so we need this right now :) > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 10:47:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 10:47:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022411#comment-13022411 ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- I think we should just add: taskkill /F /IM java.exe For some reason the java.exe that Jenkins runs under is not in the tasklist so it is safe to do it (I just did myself :) ) http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/killjavawin/6/console > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 10:56:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 10:56:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022418#comment-13022418 ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- Hi [~zhfeng], can you take a look at https://github.com/jbosstm/narayana/pull/774. It won't fix this Jira but it should prevent failures from cascading to other builds. Thanks > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 11:00:41 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 11:00:41 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2303) Cannot create jacoco report In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2303: ----------------------------------- Summary: Cannot create jacoco report Key: JBTM-2303 URL: https://issues.jboss.org/browse/JBTM-2303 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Reporter: Tom Jenkinson Assignee: Michael Musgrove {quote} [jacoco:coverage] Enhancing junit with coverage [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jdbcresources02_pgsql_jndi [junit] Tests run: 30, Failures: 0, Errors: 0, Time elapsed: 412.658 sec ci-tests: BUILD SUCCESSFUL Total time: 447 minutes 53 seconds generating test coverage report Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml jacoco-report: [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec BUILD FAILED /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 11:00:42 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 11:00:42 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2303) Cannot create jacoco report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022420#comment-13022420 ] Tom Jenkinson commented on JBTM-2303: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-codeCoverage/155/console > Cannot create jacoco report > --------------------------- > > Key: JBTM-2303 > URL: https://issues.jboss.org/browse/JBTM-2303 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > [jacoco:coverage] Enhancing junit with coverage > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jdbcresources02_pgsql_jndi > [junit] Tests run: 30, Failures: 0, Errors: 0, Time elapsed: 412.658 sec > ci-tests: > BUILD SUCCESSFUL > Total time: 447 minutes 53 seconds > generating test coverage report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 11:02:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 11:02:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2301) PerformanceTest regression In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022422#comment-13022422 ] Tom Jenkinson commented on JBTM-2301: ------------------------------------- It happened on code coverage run too: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-codeCoverage/156/console I think we should disable this on the code coverage runs > PerformanceTest regression > -------------------------- > > Key: JBTM-2301 > URL: https://issues.jboss.org/browse/JBTM-2301 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/693/PROFILE=MAIN,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: io.narayana.perf.PerformanceTest > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.898 sec <<< FAILURE! > regressionTest(io.narayana.perf.PerformanceTest) Time elapsed: 6.268 sec <<< FAILURE! > junit.framework.AssertionFailedError: There should have been a perf regression > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at io.narayana.perf.PerformanceTest.regressionTest(PerformanceTest.java:296) > {code} > {code} > Test Run: testTimeout (200 calls using 2 threads) > ExecutionException exception: java.util.concurrent.BrokenBarrierException > ExecutionException exception: java.util.concurrent.BrokenBarrierException > testTimeout: 0.000000 calls / second (200 calls in 0 ms using 2 threads. 201 errors) > Test Run: (100000 calls using 10 threads) > TestPerformance for 100000!: 17164.435290 calls / second (total time: 5826 ms versus 46786 ms) > Test Run: (1 calls using 1 threads) > testSingleCall!: 1000.000000 calls / second (1 calls in 1 ms using 1 threads. 0 errors) > Test Run: (10000 calls using 10 threads) > perfTest!: 4268.032437 calls / second (10000 calls in 2343 ms using 10 threads. 0 errors) > Test Run: (100 calls using 2 threads) > java.lang.RuntimeException: Testing throw exception > at io.narayana.perf.PerformanceTest$7.doWork(PerformanceTest.java:412) > at io.narayana.perf.PerformanceTest$7.doWork(PerformanceTest.java:406) > at io.narayana.perf.Measurement$1.call(Measurement.java:339) > at io.narayana.perf.Measurement$1.call(Measurement.java:324) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > testCancelOnException!: 33333.333333 calls / second (100 calls in 3 ms using 2 threads. 20 errors) > Test Run: io.narayana.perf.PerformanceTest_regressionTest (10000 calls using 10 threads) > Test Run: io.narayana.perf.PerformanceTest_regressionTest (10000 calls using 10 threads) > Test Run: (1000 calls using 10 threads) > testAbortMeasurement2: 0.000000 calls / second (1000 calls in 0 ms using 10 threads. 11 errors) > Test Warm Up: io.narayana.perf.PerformanceTest_readPerfArgsTest: (10 calls using 50 threads) > Test Run: io.narayana.perf.PerformanceTest_readPerfArgsTest (1000000 calls using 50 threads) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 11:07:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 11:07:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2304: ----------------------------------- Summary: Cannot compile TestModule.idl using IBM stub compiler (JDK8) Key: JBTM-2304 URL: https://issues.jboss.org/browse/JBTM-2304 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System, JTS Reporter: Tom Jenkinson Assignee: Michael Musgrove {quote} org.jboss.jbossts.qa.idl.compile.init: [idl-compiler] Parsing... [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' BUILD FAILED /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file Total time: 2 seconds qa build failed {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 11:08:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Nov 2014 11:08:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022424#comment-13022424 ] Tom Jenkinson commented on JBTM-2304: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-ibm-jdk/71/ > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 16:48:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 24 Nov 2014 16:48:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022492#comment-13022492 ] Mark Little commented on JBTM-2304: ----------------------------------- I emailed Mike yesterday and asked him to check some of the IDL/ORB changes I'd made Sunday on the IBM ORB. Not sure if this is related to those. I don't see how since the TestModule.idl looks pretty standard and doesn't use any of the preprocessor directives I removed. > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 17:04:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 24 Nov 2014 17:04:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2089) STM does not support primitive arrays In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2089 started by Mark Little. ----------------------------------------- > STM does not support primitive arrays > ------------------------------------- > > Key: JBTM-2089 > URL: https://issues.jboss.org/browse/JBTM-2089 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Mark Little > > STM objects marked with @Transactional do not support primitive type arrays -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 17:49:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 24 Nov 2014 17:49:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2089) STM does not support primitive arrays In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022497#comment-13022497 ] Mark Little commented on JBTM-2089: ----------------------------------- Unlikely to support multi-dimensional arrays. Users can provide their own saveState and restoreState methods for these object types. > STM does not support primitive arrays > ------------------------------------- > > Key: JBTM-2089 > URL: https://issues.jboss.org/browse/JBTM-2089 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Mark Little > > STM objects marked with @Transactional do not support primitive type arrays -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 21:36:40 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 21:36:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2299: ---------------------------- Fix Version/s: 5.0.4 > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.4 > > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 21:43:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 24 Nov 2014 21:43:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022506#comment-13022506 ] Amos Feng commented on JBTM-1683: --------------------------------- Thanks [~tomjenkinson], it looks good to me. > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 03:28:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 25 Nov 2014 03:28:42 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022532#comment-13022532 ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from MODIFIED to ON_QA > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 03:28:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 25 Nov 2014 03:28:44 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022542#comment-13022542 ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from MODIFIED to ON_QA > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 03:29:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 25 Nov 2014 03:29:44 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022572#comment-13022572 ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from MODIFIED to ON_QA > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 03:29:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 25 Nov 2014 03:29:44 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2188) Some code that writes to the file store is missing PrivilidgedAction blocks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022573#comment-13022573 ] RH Bugzilla Integration commented on JBTM-2188: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1162882|https://bugzilla.redhat.com/show_bug.cgi?id=1162882] from MODIFIED to ON_QA > Some code that writes to the file store is missing PrivilidgedAction blocks > --------------------------------------------------------------------------- > > Key: JBTM-2188 > URL: https://issues.jboss.org/browse/JBTM-2188 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.0.3 > > > This means the code can fail when a security manager is present, as if deployment code is on the call stack it will not be able to write or read from the files. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 06:22:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 25 Nov 2014 06:22:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022657#comment-13022657 ] Tom Jenkinson commented on JBTM-2304: ------------------------------------- Hi Mark, The build failed on Nov 19, 2014 4:29:22 PM so I don't think it can be related to those changes. Thanks for the heads up though. Tom > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 07:02:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 25 Nov 2014 07:02:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022673#comment-13022673 ] Mark Little commented on JBTM-2304: ----------------------------------- OK in that case definitely can't be me :) > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 07:04:39 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 25 Nov 2014 07:04:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2222) Rename TXFramework -> Compensations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Robinson resolved JBTM-2222. --------------------------------- Resolution: Done > Rename TXFramework -> Compensations > ----------------------------------- > > Key: JBTM-2222 > URL: https://issues.jboss.org/browse/JBTM-2222 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.4 > > > TXFramework now just focuses on Compensating transactions. The ACID transaction improvements have been moved into XTS and REST components. Therefore, we should drop the TXFramework name in favour of "Compensations" or "Compensating Transactions". -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 07:05:39 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 25 Nov 2014 07:05:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2221) Remove old TXFramework API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022677#comment-13022677 ] Paul Robinson commented on JBTM-2221: ------------------------------------- Keep this issue open, as we should remove the API altogether once it has been deprecated for long enough. > Remove old TXFramework API > -------------------------- > > Key: JBTM-2221 > URL: https://issues.jboss.org/browse/JBTM-2221 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0 > > > This is now replaced by the CDI based Compensations API. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 07:05:39 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 25 Nov 2014 07:05:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2224) Move Compensations dependency adder to transactions subsytem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Robinson resolved JBTM-2224. --------------------------------- Resolution: Done > Move Compensations dependency adder to transactions subsytem > ------------------------------------------------------------ > > Key: JBTM-2224 > URL: https://issues.jboss.org/browse/JBTM-2224 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.4 > > > The Compensating transactions API can now be used in standalone.xml as well as standalone-xts.xml. XTS is now only needed for distributed compensating transactions. > Therefore, it would be better to move the automatic dependency adding code to the transactions subsystem. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 08:33:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 25 Nov 2014 08:33:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2305) Incomplete tooling documentation In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2305: -------------------------------------- Summary: Incomplete tooling documentation Key: JBTM-2305 URL: https://issues.jboss.org/browse/JBTM-2305 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Documentation Affects Versions: 5.0.3 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.4 For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 09:14:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 25 Nov 2014 09:14:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2306: -------------------------------------- Summary: Tooling does not display the type of a heuristic Key: JBTM-2306 URL: https://issues.jboss.org/browse/JBTM-2306 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.0.3 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 6.0.0 The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: {code} /** * If this abstract record caused a heuristic then it should return an * object which implements HeuristicInformation * * @return Object to be used to order. */ public abstract Object value (); {code} HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: {code} public interface HeuristicInformation { /** * The type of heuristic. * @return the heuristic type */ public int getHeuristicType(); {code} This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 09:41:39 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 25 Nov 2014 09:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022773#comment-13022773 ] Mark Little commented on JBTM-2306: ----------------------------------- As I was explaining to Tom yesterday, HeuristicInformation was also supposed to return a reference to something which could be used to drive the heuristic at the participant to completion. You've not included the whole interface to see that, but it's important. We may not have ever used it, but we need to consider whether it should be added back - or equivalent. > Tooling does not display the type of a heuristic > ------------------------------------------------ > > Key: JBTM-2306 > URL: https://issues.jboss.org/browse/JBTM-2306 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > > The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. > There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: > {code} > /** > * If this abstract record caused a heuristic then it should return an > * object which implements HeuristicInformation > * > * @return Object to be used to order. > */ > public abstract Object value (); > {code} > HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: > {code} > public interface HeuristicInformation { > /** > * The type of heuristic. > * @return the heuristic type > */ > public int getHeuristicType(); > {code} > This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. > Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 09:44:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 25 Nov 2014 09:44:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022777#comment-13022777 ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Dominik Pospisil changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from NEW to ASSIGNED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 10:38:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 25 Nov 2014 10:38:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022819#comment-13022819 ] Michael Musgrove commented on JBTM-2306: ---------------------------------------- The missing bit of the interface is: {code} /** * A reference to the entity that caused the heuristic. * @return the entity reference */ public Object getEntityReference(); {code} I think we would need to firm up the type of reference returned in order for it to be usable for recovery purposes. We would also need to warn users that recovery via this interface may conflict with our existing recovery mechanism. When you say "we need to consider whether it should be added back" - what would be the best mechanism to discuss that, via a forum post or via a JIRA that people can vote up, or something else? > Tooling does not display the type of a heuristic > ------------------------------------------------ > > Key: JBTM-2306 > URL: https://issues.jboss.org/browse/JBTM-2306 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > > The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. > There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: > {code} > /** > * If this abstract record caused a heuristic then it should return an > * object which implements HeuristicInformation > * > * @return Object to be used to order. > */ > public abstract Object value (); > {code} > HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: > {code} > public interface HeuristicInformation { > /** > * The type of heuristic. > * @return the heuristic type > */ > public int getHeuristicType(); > {code} > This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. > Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 01:41:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 26 Nov 2014 01:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2299: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/779 > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.4 > > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 01:41:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 26 Nov 2014 01:41:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022978#comment-13022978 ] Amos Feng commented on JBTM-2299: --------------------------------- I've sent the PR to remove these idl files > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.4 > > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 02:11:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 26 Nov 2014 02:11:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022982#comment-13022982 ] Amos Feng commented on JBTM-1683: --------------------------------- I create a new job http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie-JBTM/job/JBTM-1683/ to run the test > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 03:21:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 26 Nov 2014 03:21:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023003#comment-13023003 ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- Hayk Hovsepyan changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from ON_QA to VERIFIED > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 05:31:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 05:31:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2302. ------------------------------------ Resolution: Done > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 07:25:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 26 Nov 2014 07:25:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023116#comment-13023116 ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from ON_QA to VERIFIED > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 08:50:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 08:50:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023185#comment-13023185 ] Michael Musgrove commented on JBTM-2304: ---------------------------------------- There is hardcoded path to ibmorbtools.jar in qa/tests/build-jts.xml (oops) so it should be easy to fix. > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 08:52:40 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 26 Nov 2014 08:52:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023193#comment-13023193 ] Gytis Trikleris commented on JBTM-2295: --------------------------------------- Here are three Dockerfiles which expose RTS, XTS, and both subsystems through Docker. They all use WildFly, therefore they are quite tiny. [~marklittle], if this is what you were looking for, I'll write a few quickstarts and tests for them. (I did run RTS tests on this, and everything works fine). Dockerfiles are here: https://github.com/Gytis/narayana/tree/master-JBTM-2295/scripts/docker > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 09:18:40 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 09:18:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2304: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/780 > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 09:38:40 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 26 Nov 2014 09:38:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2274: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 10:22:40 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 10:22:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2303) Cannot create jacoco report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2303: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/781 > Cannot create jacoco report > --------------------------- > > Key: JBTM-2303 > URL: https://issues.jboss.org/browse/JBTM-2303 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > [jacoco:coverage] Enhancing junit with coverage > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jdbcresources02_pgsql_jndi > [junit] Tests run: 30, Failures: 0, Errors: 0, Time elapsed: 412.658 sec > ci-tests: > BUILD SUCCESSFUL > Total time: 447 minutes 53 seconds > generating test coverage report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 10:27:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 10:27:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2303) Cannot create jacoco report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023332#comment-13023332 ] Michael Musgrove commented on JBTM-2303: ---------------------------------------- The test that tests the perf regression checker fails because of a timing issue on jaime. The test runs a bit of work twice - on the second run it adds in a one millisecondsleep and that is usually enough for it to detect a perf regression. I have increased the sleep to 5 millis and that seems to pass on jaime (it consistently failed with only a 1ms sleep). > Cannot create jacoco report > --------------------------- > > Key: JBTM-2303 > URL: https://issues.jboss.org/browse/JBTM-2303 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > [jacoco:coverage] Enhancing junit with coverage > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jdbcresources02_pgsql_jndi > [junit] Tests run: 30, Failures: 0, Errors: 0, Time elapsed: 412.658 sec > ci-tests: > BUILD SUCCESSFUL > Total time: 447 minutes 53 seconds > generating test coverage report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 14:36:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 14:36:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2303) Cannot create jacoco report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2303: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cannot create jacoco report > --------------------------- > > Key: JBTM-2303 > URL: https://issues.jboss.org/browse/JBTM-2303 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > [jacoco:coverage] Enhancing junit with coverage > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jdbcresources02_pgsql_jndi > [junit] Tests run: 30, Failures: 0, Errors: 0, Time elapsed: 412.658 sec > ci-tests: > BUILD SUCCESSFUL > Total time: 447 minutes 53 seconds > generating test coverage report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 14:44:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 14:44:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2304) Cannot compile TestModule.idl using IBM stub compiler (JDK8) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2304: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cannot compile TestModule.idl using IBM stub compiler (JDK8) > ------------------------------------------------------------ > > Key: JBTM-2304 > URL: https://issues.jboss.org/browse/JBTM-2304 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > org.jboss.jbossts.qa.idl.compile.init: > [idl-compiler] Parsing... > [idl-compiler] Processing for ibmorb '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' > BUILD FAILED > /home/hudson/workspace/narayana-ibm-jdk/qa/build.xml:123: The following error occurred while executing this line: > /home/hudson/workspace/narayana-ibm-jdk/qa/tests/build-jts.xml:229: Failed to compile '/home/hudson/workspace/narayana-ibm-jdk/qa/dist/../../ArjunaJTS/idl/src/test/idl/TestModule.idl' file > Total time: 2 seconds > qa build failed > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 18:16:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 18:16:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2307) StoreManager.getRecoveryStore() does not return the correct default In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2307: -------------------------------------- Summary: StoreManager.getRecoveryStore() does not return the correct default Key: JBTM-2307 URL: https://issues.jboss.org/browse/JBTM-2307 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Affects Versions: 5.0.3 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.4 We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2203 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. The fix is to explicitly set the name, ie replace calls like {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 18:30:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 26 Nov 2014 18:30:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2308: -------------------------------------- Summary: JTS participants are not showing up in the tooling Key: JBTM-2308 URL: https://issues.jboss.org/browse/JBTM-2308 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.0.3, 4.17.23 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.24, 5.0.4 When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 03:34:39 2014 From: issues at jboss.org (Ivo Studensky (JIRA)) Date: Thu, 27 Nov 2014 03:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Studensky updated JBTM-2302: -------------------------------- Fix Version/s: (was: 4.17.24) > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 03:34:39 2014 From: issues at jboss.org (Ivo Studensky (JIRA)) Date: Thu, 27 Nov 2014 03:34:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Studensky updated JBTM-2302: -------------------------------- Fix Version/s: 4.17.24 > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 03:38:40 2014 From: issues at jboss.org (Ivo Studensky (JIRA)) Date: Thu, 27 Nov 2014 03:38:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023441#comment-13023441 ] Ivo Studensky commented on JBTM-2302: ------------------------------------- It didn't make it to 4.17.24 but 4.17.25. The 4.17.25 is, however, missing in available Fix Versions. Can it be corrected please? > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 03:42:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 27 Nov 2014 03:42:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023443#comment-13023443 ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Ivo Studensky changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from ASSIGNED to MODIFIED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 04:13:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 27 Nov 2014 04:13:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2188) Some code that writes to the file store is missing PrivilidgedAction blocks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023454#comment-13023454 ] RH Bugzilla Integration commented on JBTM-2188: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1162882|https://bugzilla.redhat.com/show_bug.cgi?id=1162882] from ON_QA to VERIFIED > Some code that writes to the file store is missing PrivilidgedAction blocks > --------------------------------------------------------------------------- > > Key: JBTM-2188 > URL: https://issues.jboss.org/browse/JBTM-2188 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.0.3 > > > This means the code can fail when a security manager is present, as if deployment code is on the call stack it will not be able to write or read from the files. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 06:59:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 27 Nov 2014 06:59:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2307) StoreManager.getRecoveryStore() does not return the correct default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2307: -------------------------------- Description: We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2207 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. The fix is to explicitly set the name, ie replace calls like {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} was: We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2203 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. The fix is to explicitly set the name, ie replace calls like {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} > StoreManager.getRecoveryStore() does not return the correct default > ------------------------------------------------------------------- > > Key: JBTM-2307 > URL: https://issues.jboss.org/browse/JBTM-2307 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2207 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. > The fix is to explicitly set the name, ie replace calls like > {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:17:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 27 Nov 2014 07:17:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2307) StoreManager.getRecoveryStore() does not return the correct default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023552#comment-13023552 ] Tom Jenkinson commented on JBTM-2307: ------------------------------------- The purpose of JBTM-2207 it was to avoid string comparison with the default name - hence the default was moved to null. I would therefore think if we are going back to using a String for the default we are losing any value in 2207. We can of course revert 2207 but in my testing it seems to work and return the same instance? {code} Object namedInstance = BeanPopulator.getNamedInstance(Object.class, null); Object namedInstance2 = BeanPopulator.getNamedInstance(Object.class, null); assertEquals(namedInstance, namedInstance2); {code} Is it possible the instance in question is being initialised by name "default" through some access that was missed? This one for example: https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/ArjunaObjectStoreEnvironmentService.java#L78 (The reason this is not a backwards compatibility issue is com.arjuna.common.internal.util.propertyservice.BeanPopulator is internal code that the app server is using) > StoreManager.getRecoveryStore() does not return the correct default > ------------------------------------------------------------------- > > Key: JBTM-2307 > URL: https://issues.jboss.org/browse/JBTM-2307 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2207 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. > The fix is to explicitly set the name, ie replace calls like > {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:20:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:20:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng reopened JBTM-1822: ----------------------------- > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:20:40 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:20:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-1822: ---------------------------- Priority: Major (was: Minor) > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:20:40 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:20:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-1822: ---------------------------- Fix Version/s: 5.0.4 (was: 5.0.0.M4) > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:21:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 27 Nov 2014 07:21:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2307) StoreManager.getRecoveryStore() does not return the correct default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023553#comment-13023553 ] Michael Musgrove commented on JBTM-2307: ---------------------------------------- That usage (ArjunaObjectStoreEnvironmentService.java#L78) is indeed the culprit. So we should raise the bug against wildfly instead. > StoreManager.getRecoveryStore() does not return the correct default > ------------------------------------------------------------------- > > Key: JBTM-2307 > URL: https://issues.jboss.org/browse/JBTM-2307 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2207 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. > The fix is to explicitly set the name, ie replace calls like > {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:22:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:22:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023554#comment-13023554 ] Amos Feng commented on JBTM-1822: --------------------------------- http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el5/843/console > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:27:40 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:27:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023557#comment-13023557 ] Amos Feng commented on JBTM-1822: --------------------------------- {code} 2014-11-26 07:28:21,029 [0x5d97b90] TRACE (TxXAWrapper :213 ) - do_commit:213:ENTER 2014-11-26 07:28:21,031 [0x5d97b90] TRACE (TxXAWrapper :346 ) - xa_commit:346:ENTER bstate=0 2014-11-26 07:28:21,033 [0x5d97b90] DEBUG (TxXAWrapper :347 ) - Commiting resource with branch id: 131077:36:17:0_ffff0a27a817_-7d9efbf1_54757dfd_b5102:0:47:1:307405 2014-11-26 07:28:21,035 [0x5d97b90] DEBUG (AtmiBrokerLogc :72 ) - dummy_rm: apply_faults: op=7 rmid=102 2014-11-26 07:28:21,037 [0x5d97b90] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 0x487557c 2014-11-26 07:28:21,038 [0x5d97b90] TRACE (SynchronizableObject :58 ) - acquired: 0x487557c 2014-11-26 07:28:21,040 [0x5d97b90] DEBUG (AtmiBrokerLogc :72 ) - dummy_rm: cf op=7 rmid=102 2014-11-26 07:28:21,042 [0x5d97b90] DEBUG (AtmiBrokerLogc :72 ) - dummy_rm: applying fault 1 to op 7 rc 0 2014-11-26 07:28:21,044 [0x5d97b90] DEBUG (AtmiBrokerLogc :72 ) - dummy_rm: calling callback 2014-11-26 07:28:21,046 [0x5d97b90] INFO (AtmiBrokerLogc :60 ) - TestTransactions recovery_cb2 called 1 times 2014-11-26 07:28:21,050 [0x5d97b90] TRACE (SynchronizableObject :101 ) - Releasing mutex: 0x487557c 2014-11-26 07:28:21,052 [0x5d97b90] TRACE (SynchronizableObject :103 ) - released mutex: 0x487557c 2014-11-26 07:28:21,054 [0x5d97b90] DEBUG (AtmiBrokerLogc :72 ) - dummy_rm: fault return: 0 2014-11-26 07:28:21,055 [0x5d97b90] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 0x487557c 2014-11-26 07:28:21,057 [0x5d97b90] TRACE (SynchronizableObject :58 ) - acquired: 0x487557c 2014-11-26 07:28:21,059 [0x5d97b90] TRACE (SynchronizableObject :101 ) - Releasing mutex: 0x487557c 2014-11-26 07:28:21,061 [0x5d97b90] TRACE (SynchronizableObject :103 ) - released mutex: 0x487557c 2014-11-26 07:28:21,063 [0x5d97b90] TRACE (TxXAStateModel :43 ) - transition:ENTER xid=131077:36:17:0_ffff0a27a817_-7d9efbf1_54757dfd_b5102:0:47:1:307405 rv=0 flags=0 () method=6 astate=0 bstate=0 2014-11-26 07:28:21,065 [0x5d97b90] TRACE (TxXAWrapper :225 ) - resource commit rv=0 2014-11-26 07:28:21,068 [0x4b8bc90] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 0x40a15bc 2014-11-26 07:28:21,073 [0x4b8bc90] TRACE (SynchronizableObject :58 ) - acquired: 0x40a15bc 2014-11-26 07:28:21,074 [0x4b8bc90] TRACE (AtmiBrokerEnv :82 ) - Reference count: 2 2014-11-26 07:28:21,076 [0x4b8bc90] TRACE (SynchronizableObject :101 ) - Releasing mutex: 0x40a15bc 2014-11-26 07:28:21,078 [0x4b8bc90] TRACE (SynchronizableObject :103 ) - released mutex: 0x40a15bc 2014-11-26 07:28:21,080 [0x4b8bc90] DEBUG (AtmiBrokerEnv :352 ) - getenv %sBLACKTIE_RC_LOG_NAME 2014-11-26 07:28:21,081 [0x4b8bc90] DEBUG (AtmiBrokerEnv :352 ) - getenv %sBLACKTIE_SERVER_NAME 2014-11-26 07:28:21,083 [0x4b8bc90] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 0x40a15bc 2014-11-26 07:28:21,085 [0x4b8bc90] TRACE (SynchronizableObject :58 ) - acquired: 0x40a15bc 2014-11-26 07:28:21,087 [0x4b8bc90] TRACE (AtmiBrokerEnv :92 ) - Reference count: 1 2014-11-26 07:28:21,089 [0x4b8bc90] TRACE (SynchronizableObject :101 ) - Releasing mutex: 0x40a15bc 2014-11-26 07:28:21,091 [0x4b8bc90] TRACE (SynchronizableObject :103 ) - released mutex: 0x40a15bc 2014-11-26 07:28:21,092 [0x4b8bc90] TRACE (TxXARecoveryLog :98 ) - Using log file rclog 2014-11-26 07:28:21,094 [0x4b8bc90] TRACE (TxXARecoveryLog :132 ) - Loading log file: rclog 2014-11-26 07:28:21,096 [0x4b8bc90] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 0x40a15bc 2014-11-26 07:28:21,098 [0x4b8bc90] TRACE (SynchronizableObject :58 ) - acquired: 0x40a15bc 2014-11-26 07:28:21,099 [0x4b8bc90] TRACE (AtmiBrokerEnv :82 ) - Reference count: 2 2014-11-26 07:28:21,101 [0x4b8bc90] TRACE (SynchronizableObject :101 ) - Releasing mutex: 0x40a15bc 2014-11-26 07:28:21,103 [0x4b8bc90] TRACE (SynchronizableObject :103 ) - released mutex: 0x40a15bc 2014-11-26 07:28:21,105 [0x4b8bc90] DEBUG (AtmiBrokerEnv :352 ) - getenv %sBLACKTIE_MAX_RCLOG_SIZE 2014-11-26 07:28:21,107 [0x4b8bc90] TRACE (SynchronizableObject :56 ) - Acquiring mutex: 0x40a15bc 2014-11-26 07:28:21,108 [0x4b8bc90] TRACE (SynchronizableObject :58 ) - acquired: 0x40a15bc 2014-11-26 07:28:21,110 [0x4b8bc90] TRACE (AtmiBrokerEnv :92 ) - Reference count: 1 2014-11-26 07:28:21,112 [0x4b8bc90] TRACE (SynchronizableObject :101 ) - Releasing mutex: 0x40a15bc 2014-11-26 07:28:21,114 [0x4b8bc90] TRACE (SynchronizableObject :103 ) - released mutex: 0x40a15bc 2014-11-26 07:28:21,116 [0x4b8bc90] DEBUG (TxXARecoveryLog :220 ) - alocating blocks: 256 2014-11-26 07:28:21,118 [0x4b8bc90] DEBUG (TxXARecoveryLog :229 ) - increasing rc log blocks from 0 to 256 2014-11-26 07:28:21,120 [0x4b8bc90] DEBUG (TxXARecoveryLog :246 ) - ARENA: [0x61f5cb8, 0x674ecb8 2014-11-26 07:28:21,121 [0x4b8bc90] DEBUG (TxXARecoveryLog :173 ) - initialized recovery log size: 13 2014-11-26 07:28:21,123 [0x4b8bc90] TRACE (TxXARecoveryLog :120 ) - destructor 2014-11-26 07:28:21,126 [0x4b8bc90] INFO (AtmiBrokerLogc :60 ) - TestTransactions::test_run_recovery 1 recs after recovery 2014-11-26 07:28:21,131 [0x4b8bc90] DEBUG (AtmiBrokerLogc :72 ) - CHKCOND ASSERT FAILED /home/hudson/workspace/btny-pulls-narayana/PROFILE/BLACKTIE/jdk/jdk7.latest/label/linux32el5/blacktie/tx/src/test/cpp/TestTransactions.cxx:540 {code} It looks like the count_log_records() runs before the XAWrapper::do_terminate() deletes the rec. So the possible fix is to wait and check the nrecs for the reasonable seconds. > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:33:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:33:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2299: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.4 > > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:46:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:46:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-1822: ---------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/782 > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:48:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 27 Nov 2014 07:48:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023563#comment-13023563 ] Amos Feng commented on JBTM-1822: --------------------------------- [~mmusgrov] can you take a look at this fix https://github.com/jbosstm/narayana/pull/782/files ? > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:49:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 27 Nov 2014 07:49:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2307) StoreManager.getRecoveryStore() does not return the correct default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2307. ---------------------------------- Resolution: Duplicate Issue Duplicate of https://issues.jboss.org/browse/WFLY-4132 > StoreManager.getRecoveryStore() does not return the correct default > ------------------------------------------------------------------- > > Key: JBTM-2307 > URL: https://issues.jboss.org/browse/JBTM-2307 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > We used to treat requests to get a store with a null name as implicitly meaning get the default named store. But a recent change (JBTM-2207 Make default name null in order for quick lookup) meant that this is no longer the default behaviour. Now a request like the following {code} > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} will return something other than the default named instance. This is causing a problem on wildfly where the call StoreManager.getRecoveryStore() does not return what was set in the transaction subsystem service initialisation. > The fix is to explicitly set the name, ie replace calls like > {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, null);{code} with {code}BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "default");{code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 08:14:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 27 Nov 2014 08:14:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2279: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 08:25:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 27 Nov 2014 08:25:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2279: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/755, https://github.com/jbosstm/narayana/pull/770, https://github.com/jbosstm/narayana/pull/783 (was: https://github.com/jbosstm/narayana/pull/755, https://github.com/jbosstm/narayana/pull/770) > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 09:29:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 27 Nov 2014 09:29:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1939) Consider using awestruct to develop http://narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1939: -------------------------------- Fix Version/s: 5.0.4 > Consider using awestruct to develop http://narayana.io > ------------------------------------------------------ > > Key: JBTM-1939 > URL: https://issues.jboss.org/browse/JBTM-1939 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Awestruct appears to be a powerful and flexible tool to develop websites with. This task is to research the capabilities of the tool and determine if the benefits of awestruct apply to our website. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 13:09:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 27 Nov 2014 13:09:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2308: ----------------------------------- Fix Version/s: (was: 4.17.24) > JTS participants are not showing up in the tooling > -------------------------------------------------- > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 13:17:39 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 27 Nov 2014 13:17:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023690#comment-13023690 ] Michael Musgrove commented on JBTM-2308: ---------------------------------------- I have removed 4.17.x from the fix versions since I won't have time to fix it for tomorrows release. I will work on it for the one after that. The problem is that JTS participant records are not stored in-line with the owning transaction (in contrast to JTA). If I show participants as children of the owning transaction then when expose all logs is enabled we would end up creating two representations of the participant (one under CosTransactions/XAResource and the other under the JTS transaction record node). This would break on wildfly since we use the record Uid as the id of the wildfly model node and duplicate ids are not allowed. > JTS participants are not showing up in the tooling > -------------------------------------------------- > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 03:11:39 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 28 Nov 2014 03:11:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1822) BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-1822: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BT_ASSERT(nrecs < nrecs1) failed in TestTransactions::test_recovery > ------------------------------------------------------------------- > > Key: JBTM-1822 > URL: https://issues.jboss.org/browse/JBTM-1822 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/166/TESTS=BLACKTIE,jdk=jdk7.latest,label=linux64el6/consoleText > {code} > [exec] .2013-07-02 15:57:39,717 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin (cleared 4 records) > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x416C1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:39,931 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:39,984 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:40,036 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:40,089 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:40,144 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery begin 0 records > [exec] --28817:1:mallocfr newSuperblock at 0x416D1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x416E1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:40,475 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery commiting after generating a recovery condition > [exec] 2013-07-02 15:57:40,860 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 1 times > [exec] 2013-07-02 15:57:40,881 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] 2013-07-02 15:57:40,958 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb1 called 2 times > [exec] 2013-07-02 15:57:40,977 [0xcc17700] INFO (TxHttpTxManager :415 ) - closing connection to TM > [exec] --28817:1:mallocfr newSuperblock at 0x416F1A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:41,070 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery committed 1 records > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] 2013-07-02 15:57:44,014 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,017 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:0:0_ffffac118307_-4f6b5ee7_51d2e875_b2 address: 0xe10adb0 > [exec] 2013-07-02 15:57:44,023 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,026 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe613640 > [exec] 2013-07-02 15:57:44,033 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,036 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xb6899f0 > [exec] 2013-07-02 15:57:44,042 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,045 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xe761c60 > [exec] 2013-07-02 15:57:44,052 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:57:44,055 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xe632830 > [exec] 2013-07-02 15:57:44,081 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed > [exec] 2013-07-02 15:57:44,130 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x41701A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,354 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a37%3a1372777039%3a852157 > [exec] 2013-07-02 15:57:44,408 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a39%3a1372777040%3a637713 > [exec] 2013-07-02 15:57:44,461 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a42%3a1372777046%3a10751 > [exec] 2013-07-02 15:57:44,514 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a44%3a1372777046%3a814097 > [exec] 2013-07-02 15:57:44,568 [0x4037ce0] WARN (TxHttpTxManager :210 ) - TM failed recovery request: 404 for participant 131077%3a102%3a0%3a47%3a1372777060%3a383693 > [exec] --28817:1:mallocfr newSuperblock at 0x41711A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] 2013-07-02 15:57:44,578 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 179 seconds > [exec] 2013-07-02 15:57:54,583 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 169 seconds > [exec] 2013-07-02 15:58:04,587 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 159 seconds > [exec] 2013-07-02 15:58:14,592 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for 149 seconds > 15:58:15,523 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a1372777060%3a383693/terminate >  [exec] 2013-07-02 15:58:15,581 [0xcc17700] INFO (AtmiBrokerLogc :66 ) - TestTransactions recovery_cb2 called 1 times > 15:58:15,698 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a1372777040%3a637713/terminate >  [exec] 2013-07-02 15:58:15,654 [0x4037ce0] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery > 15:58:15,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1372777039%3a852157/terminate > 15:58:15,702 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a1372777046%3a10751/terminate > 15:58:15,704 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a1372777046%3a814097/terminate >  [exec] --28817:1:mallocfr newSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x413861000 (pszB 131040) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] F2013-07-02 15:58:18,897 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,902 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:25:0_ffffac118307_-4f6b5ee7_51d2e875_9e102:0:42:1372777046:10751 address: 0xe9c3c10 > [exec] 2013-07-02 15:58:18,912 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,917 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_94102:0:37:1372777039:852157 address: 0xbe9cd70 > [exec] 2013-07-02 15:58:18,927 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,931 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_97102:0:39:1372777040:637713 address: 0xbeb9fb0 > [exec] 2013-07-02 15:58:18,942 [0x4037ce0] WARN (XAResourceManager :125 ) - There are still incomplete branches > [exec] 2013-07-02 15:58:18,946 [0x4037ce0] WARN (XAResourceManager :129 ) - Deleting branch 131077:36:26:0_ffffac118307_-4f6b5ee7_51d2e875_a1102:0:44:1372777046:814097 address: 0xbeed050 > [exec] --28817:1:mallocfr newSuperblock at 0x41721A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41731A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41741A000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x411D4C000 (pszB 196576) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:mallocfr newSuperblock at 0x417562000 (pszB 1048544) owner VALGRIND/exectxt > [exec] --28817:1:mallocfr newSuperblock at 0x417662000 (pszB 438240) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:mallocfr reclaimSuperblock at 0x41751A000 (pszB 294880) unsplittable owner VALGRIND/ttaux > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:mallocfr newSuperblock at 0xEE26000 (pszB 4194272) owner CLIENT/client > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper > [exec] --28817:1:syswrap- thread_wrapper(tid=2): entry > [exec] --28817:1:syswrap- thread_wrapper(tid=2): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing > [exec] . > [exec] > [exec] > [exec] !!!FAILURES!!! > [exec] Test Results: > [exec] Run: 14 Failures: 1 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_recovery (F) line: 548 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] > [exec] > [exec] --28817:1:syswrap- thread_wrapper(tid=1): exit > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): post-thread_wrapper > [exec] --28817:1:syswrap- run_a_thread_NORETURN(tid=1): last one standing > [exec] --28817:1:main entering VG_(shutdown_actions_NORETURN) > [exec] --28817:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown (239 segments, 52 segnames) > [exec] --28817:1:aspacem ( 0) /usr/lib64/valgrind/memcheck-amd64-linux > [exec] --28817:1:aspacem ( 1) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/testsuite > [exec] --28817:1:aspacem ( 2) /lib64/ld-2.12.so > [exec] --28817:1:aspacem ( 3) /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:aspacem ( 4) /usr/lib64/valgrind/vgpreload_core-amd64-linux.so > [exec] --28817:1:aspacem ( 5) /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so > [exec] --28817:1:aspacem ( 6) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libACE.so.6.0.1 > [exec] --28817:1:aspacem ( 7) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO.so.2.0.1 > [exec] --28817:1:aspacem ( 8) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_AnyTypeCode.so.2.0.1 > [exec] --28817:1:aspacem ( 9) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CodecFactory.so.2.0.1 > [exec] --28817:1:aspacem (10) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_CosNaming.so.2.0.1 > [exec] --28817:1:aspacem (11) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_BE.so.2.0.1 > [exec] --28817:1:aspacem (12) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IDL_FE.so.2.0.1 > [exec] --28817:1:aspacem (13) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_IORInterceptor.so.2.0.1 > [exec] --28817:1:aspacem (14) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_ObjRefTemplate.so.2.0.1 > [exec] --28817:1:aspacem (15) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI.so.2.0.1 > [exec] --28817:1:aspacem (16) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PI_Server.so.2.0.1 > [exec] --28817:1:aspacem (17) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_PortableServer.so.2.0.1 > [exec] --28817:1:aspacem (18) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libTAO_Valuetype.so.2.0.1 > [exec] --28817:1:aspacem (19) /usr/lib64/gconv/gconv-modules.cache > [exec] --28817:1:aspacem (20) /usr/lib64/libapr-1.so.0.3.9 > [exec] --28817:1:aspacem (21) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-codec.so > [exec] --28817:1:aspacem (22) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-core.so > [exec] --28817:1:aspacem (23) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-idl-tao.so > [exec] --28817:1:aspacem (24) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libblacktie-transport.so > [exec] --28817:1:aspacem (25) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libexpat.so.0 > [exec] --28817:1:aspacem (26) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/liblog4cxx.so > [exec] --28817:1:aspacem (27) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf-lite.so.7 > [exec] --28817:1:aspacem (28) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotobuf.so.7 > [exec] --28817:1:aspacem (29) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libprotoc.so.7 > [exec] --28817:1:aspacem (30) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/runtime/lib/libxerces-c-3.0.so > [exec] --28817:1:aspacem (31) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libblacktie-tx-test-utilities.so > [exec] --28817:1:aspacem (32) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/cxx/test/lib/libcppunit-1.12.so.0 > [exec] --28817:1:aspacem (33) /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/target/debug/shared/libblacktie-tx.so > [exec] --28817:1:aspacem (34) /usr/lib64/libstdc++.so.6.0.13 > [exec] --28817:1:aspacem (35) /lib64/libpthread-2.12.so > [exec] --28817:1:aspacem (36) /lib64/librt-2.12.so > [exec] --28817:1:aspacem (37) /lib64/libgcc_s-4.4.7-20120601.so.1 > [exec] --28817:1:aspacem (38) /lib64/libc-2.12.so > [exec] --28817:1:aspacem (39) /lib64/libdl-2.12.so > [exec] --28817:1:aspacem (40) /lib64/libm-2.12.so > [exec] --28817:1:aspacem (41) /lib64/libuuid.so.1.3.0 > [exec] --28817:1:aspacem (42) /lib64/libcrypt-2.12.so > [exec] --28817:1:aspacem (43) /usr/lib64/libaprutil-1.so.0.3.9 > [exec] --28817:1:aspacem (44) /lib64/libnsl-2.12.so > [exec] --28817:1:aspacem (45) /lib64/libfreebl3.so > [exec] --28817:1:aspacem (46) /lib64/libexpat.so.1.5.2 > [exec] --28817:1:aspacem (47) /lib64/libdb-4.7.so > [exec] --28817:1:aspacem (48) /usr/lib64/gconv/UTF-16.so > [exec] --28817:1:aspacem (49) /usr/lib64/gconv/ISO8859-1.so > [exec] --28817:1:aspacem (51) /lib64/libnss_files-2.12.so > [exec] --28817:1:aspacem 0: RSVN 0000000000-00003fffff 4194304 ----- SmFixed > [exec] --28817:1:aspacem 1: file 0000400000-000042cfff 184320 r-xT- d=0xfd00 i=2373687 o=0 (1) > [exec] --28817:1:aspacem 2: RSVN 000042d000-000062bfff 2093056 ----- SmFixed > [exec] --28817:1:aspacem 3: file 000062c000-000062dfff 8192 rw--- d=0xfd00 i=2373687 o=180224 (1) > [exec] --28817:1:aspacem 4: RSVN 000062e000-0003ffffff 57m ----- SmFixed > [exec] --28817:1:aspacem 5: file 0004000000-000401ffff 131072 r-xT- d=0xfd00 i=4981072 o=0 (2) > [exec] --28817:1:aspacem 6: anon 0004020000-0004026fff 28672 rw--- > [exec] --28817:1:aspacem 7: 0004027000-000402afff 16384 > [exec] --28817:1:aspacem 8: anon 000402b000-000403afff 65536 rw--- > [exec] --28817:1:aspacem 9: file 000403b000-0004041fff 28672 r---- d=0xfd00 i=394016 o=0 (19) > [exec] --28817:1:aspacem 10: 0004042000-000421efff 1953792 > [exec] --28817:1:aspacem 11: file 000421f000-000421ffff 4096 r---- d=0xfd00 i=4981072 o=126976 (2) > [exec] --28817:1:aspacem 12: file 0004220000-0004220fff 4096 rw--- d=0xfd00 i=4981072 o=131072 (2) > [exec] --28817:1:aspacem 13: anon 0004221000-0004221fff 4096 rw--- > [exec] --28817:1:aspacem 14: anon 0004222000-0004222fff 4096 rwx-- > [exec] --28817:1:aspacem 15: RSVN 0004223000-0004a21fff 8384512 ----- SmLower > [exec] --28817:1:aspacem 16: file 0004a22000-0004a22fff 4096 r-xT- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 17: file 0004a23000-0004c21fff 2093056 ----- d=0xfd00 i=266265 o=4096 (4) > [exec] --28817:1:aspacem 18: file 0004c22000-0004c22fff 4096 rw--- d=0xfd00 i=266265 o=0 (4) > [exec] --28817:1:aspacem 19: file 0004c23000-0004c2efff 49152 r-xT- d=0xfd00 i=266277 o=0 (5) > [exec] --28817:1:aspacem 20: file 0004c2f000-0004e2dfff 2093056 ----- d=0xfd00 i=266277 o=49152 (5) > [exec] --28817:1:aspacem 21: file 0004e2e000-0004e2efff 4096 rw--- d=0xfd00 i=266277 o=45056 (5) > [exec] --28817:1:aspacem 22: file 0004e2f000-0004fa8fff 1548288 r-xT- d=0xfd00 i=5124752 o=0 (6) > [exec] --28817:1:aspacem 23: file 0004fa9000-00051a7fff 2093056 ----- d=0xfd00 i=5124752 o=1548288 (6) > [exec] --28817:1:aspacem 24: file 00051a8000-00051bdfff 90112 rw--- d=0xfd00 i=5124752 o=1544192 (6) > [exec] --28817:1:aspacem 25: anon 00051be000-00051befff 4096 rw--- > [exec] --28817:1:aspacem 26: file 00051bf000-0005312fff 1392640 r-xT- d=0xfd00 i=5124749 o=0 (7) > [exec] --28817:1:aspacem 27: file 0005313000-0005511fff 2093056 ----- d=0xfd00 i=5124749 o=1392640 (7) > [exec] --28817:1:aspacem 28: file 0005512000-0005524fff 77824 rw--- d=0xfd00 i=5124749 o=1388544 (7) > [exec] --28817:1:aspacem 29: file 0005525000-00055cdfff 692224 r-xT- d=0xfd00 i=5124760 o=0 (8) > [exec] --28817:1:aspacem 30: file 00055ce000-00057ccfff 2093056 ----- d=0xfd00 i=5124760 o=692224 (8) > [exec] --28817:1:aspacem 31: file 00057cd000-00057d5fff 36864 rw--- d=0xfd00 i=5124760 o=688128 (8) > [exec] --28817:1:aspacem 32: anon 00057d6000-00057d8fff 12288 rw--- > [exec] --28817:1:aspacem 33: file 00057d9000-00057ecfff 81920 r-xT- d=0xfd00 i=5124741 o=0 (9) > [exec] --28817:1:aspacem 34: file 00057ed000-00059ecfff 2097152 ----- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 35: file 00059ed000-00059effff 12288 rw--- d=0xfd00 i=5124741 o=81920 (9) > [exec] --28817:1:aspacem 36: file 00059f0000-0005a1dfff 188416 r-xT- d=0xfd00 i=5124762 o=0 (10) > [exec] --28817:1:aspacem 37: file 0005a1e000-0005c1cfff 2093056 ----- d=0xfd00 i=5124762 o=188416 (10) > [exec] --28817:1:aspacem 38: file 0005c1d000-0005c1ffff 12288 rw--- d=0xfd00 i=5124762 o=184320 (10) > [exec] --28817:1:aspacem 39: anon 0005c20000-0005c20fff 4096 rw--- > [exec] --28817:1:aspacem 40: file 0005c21000-0005ee9fff 2920448 r-xT- d=0xfd00 i=5124764 o=0 (11) > [exec] --28817:1:aspacem 41: file 0005eea000-00060e9fff 2097152 ----- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 42: file 00060ea000-0006164fff 503808 rw--- d=0xfd00 i=5124764 o=2920448 (11) > [exec] --28817:1:aspacem 43: anon 0006165000-0006168fff 16384 rw--- > [exec] --28817:1:aspacem 44: file 0006169000-000625dfff 1003520 r-xT- d=0xfd00 i=5124761 o=0 (12) > [exec] --28817:1:aspacem 45: file 000625e000-000645cfff 2093056 ----- d=0xfd00 i=5124761 o=1003520 (12) > [exec] --28817:1:aspacem 46: file 000645d000-0006485fff 167936 rw--- d=0xfd00 i=5124761 o=999424 (12) > [exec] --28817:1:aspacem 47: anon 0006486000-0006487fff 8192 rw--- > [exec] --28817:1:aspacem 48: file 0006488000-0006495fff 57344 r-xT- d=0xfd00 i=5124743 o=0 (13) > [exec] --28817:1:aspacem 49: file 0006496000-0006694fff 2093056 ----- d=0xfd00 i=5124743 o=57344 (13) > [exec] --28817:1:aspacem 50: file 0006695000-0006697fff 12288 rw--- d=0xfd00 i=5124743 o=53248 (13) > [exec] --28817:1:aspacem 51: file 0006698000-00066abfff 81920 r-xT- d=0xfd00 i=5124755 o=0 (14) > [exec] --28817:1:aspacem 52: file 00066ac000-00068abfff 2097152 ----- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 53: file 00068ac000-00068aefff 12288 rw--- d=0xfd00 i=5124755 o=81920 (14) > [exec] --28817:1:aspacem 54: file 00068af000-00068ebfff 249856 r-xT- d=0xfd00 i=5124740 o=0 (15) > [exec] --28817:1:aspacem 55: file 00068ec000-0006aeafff 2093056 ----- d=0xfd00 i=5124740 o=249856 (15) > [exec] --28817:1:aspacem 56: file 0006aeb000-0006af4fff 40960 rw--- d=0xfd00 i=5124740 o=245760 (15) > [exec] --28817:1:aspacem 57: file 0006af5000-0006b0afff 90112 r-xT- d=0xfd00 i=5124763 o=0 (16) > [exec] --28817:1:aspacem 58: file 0006b0b000-0006d0afff 2097152 ----- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 59: file 0006d0b000-0006d0efff 16384 rw--- d=0xfd00 i=5124763 o=90112 (16) > [exec] --28817:1:aspacem 60: file 0006d0f000-0006df0fff 925696 r-xT- d=0xfd00 i=5124754 o=0 (17) > [exec] --28817:1:aspacem 61: file 0006df1000-0006feffff 2093056 ----- d=0xfd00 i=5124754 o=925696 (17) > [exec] --28817:1:aspacem 62: file 0006ff0000-000700afff 110592 rw--- d=0xfd00 i=5124754 o=921600 (17) > [exec] --28817:1:aspacem 63: anon 000700b000-000700bfff 4096 rw--- > [exec] --28817:1:aspacem 64: file 000700c000-0007022fff 94208 r-xT- d=0xfd00 i=5124756 o=0 (18) > [exec] --28817:1:aspacem 65: file 0007023000-0007221fff 2093056 ----- d=0xfd00 i=5124756 o=94208 (18) > [exec] --28817:1:aspacem 66: file 0007222000-0007223fff 8192 rw--- d=0xfd00 i=5124756 o=90112 (18) > [exec] --28817:1:aspacem 67: file 0007224000-000724efff 176128 r-xT- d=0xfd00 i=264773 o=0 (20) > [exec] --28817:1:aspacem 68: file 000724f000-000744dfff 2093056 ----- d=0xfd00 i=264773 o=176128 (20) > [exec] --28817:1:aspacem 69: file 000744e000-000744ffff 8192 rw--- d=0xfd00 i=264773 o=172032 (20) > [exec] --28817:1:aspacem 70: file 0007450000-000746bfff 114688 r-xT- d=0xfd00 i=5124725 o=0 (21) > [exec] --28817:1:aspacem 71: file 000746c000-000766afff 2093056 ----- d=0xfd00 i=5124725 o=114688 (21) > [exec] --28817:1:aspacem 72: file 000766b000-000766cfff 8192 rw--- d=0xfd00 i=5124725 o=110592 (21) > [exec] --28817:1:aspacem 73: file 000766d000-00076cffff 405504 r-xT- d=0xfd00 i=5124726 o=0 (22) > [exec] --28817:1:aspacem 74: file 00076d0000-00078cefff 2093056 ----- d=0xfd00 i=5124726 o=405504 (22) > [exec] --28817:1:aspacem 75: file 00078cf000-00078d3fff 20480 rw--- d=0xfd00 i=5124726 o=401408 (22) > [exec] --28817:1:aspacem 76: file 00078d4000-0007a15fff 1318912 r-xT- d=0xfd00 i=5124727 o=0 (23) > [exec] --28817:1:aspacem 77: file 0007a16000-0007c14fff 2093056 ----- d=0xfd00 i=5124727 o=1318912 (23) > [exec] --28817:1:aspacem 78: file 0007c15000-0007c2afff 90112 rw--- d=0xfd00 i=5124727 o=1314816 (23) > [exec] --28817:1:aspacem 79: file 0007c2b000-0007c48fff 122880 r-xT- d=0xfd00 i=5124728 o=0 (24) > [exec] --28817:1:aspacem 80: file 0007c49000-0007e48fff 2097152 ----- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 81: file 0007e49000-0007e4afff 8192 rw--- d=0xfd00 i=5124728 o=122880 (24) > [exec] --28817:1:aspacem 82: file 0007e4b000-00080b7fff 2543616 r-xT- d=0xfd00 i=5124723 o=0 (26) > [exec] --28817:1:aspacem 83: file 00080b8000-00082b6fff 2093056 ----- d=0xfd00 i=5124723 o=2543616 (26) > [exec] --28817:1:aspacem 84: file 00082b7000-00082e8fff 204800 rw--- d=0xfd00 i=5124723 o=2539520 (26) > [exec] --28817:1:aspacem 85: anon 00082e9000-00082eafff 8192 rw--- > [exec] --28817:1:aspacem 86: file 00082eb000-000830cfff 139264 r-xT- d=0xfd00 i=5124736 o=0 (27) > [exec] --28817:1:aspacem 87: file 000830d000-000850bfff 2093056 ----- d=0xfd00 i=5124736 o=139264 (27) > [exec] --28817:1:aspacem 88: file 000850c000-000850dfff 8192 rw--- d=0xfd00 i=5124736 o=135168 (27) > [exec] --28817:1:aspacem 89: file 000850e000-0008602fff 1003520 r-xT- d=0xfd00 i=5124730 o=0 (28) > [exec] --28817:1:aspacem 90: file 0008603000-0008802fff 2097152 ----- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 91: file 0008803000-0008808fff 24576 rw--- d=0xfd00 i=5124730 o=1003520 (28) > [exec] --28817:1:aspacem 92: file 0008809000-00088b4fff 704512 r-xT- d=0xfd00 i=5124734 o=0 (29) > [exec] --28817:1:aspacem 93: file 00088b5000-0008ab4fff 2097152 ----- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 94: file 0008ab5000-0008ab7fff 12288 rw--- d=0xfd00 i=5124734 o=704512 (29) > [exec] --28817:1:aspacem 95: file 0008ab8000-0008e1dfff 3563520 r-xT- d=0xfd00 i=5124738 o=0 (30) > [exec] --28817:1:aspacem 96: file 0008e1e000-0008f1cfff 1044480 ----- d=0xfd00 i=5124738 o=3563520 (30) > [exec] --28817:1:aspacem 97: file 0008f1d000-0008fb4fff 622592 rw--- d=0xfd00 i=5124738 o=3559424 (30) > [exec] --28817:1:aspacem 98: file 0008fb5000-0008fbcfff 32768 r-xT- d=0xfd00 i=4466708 o=0 (31) > [exec] --28817:1:aspacem 99: file 0008fbd000-00091bbfff 2093056 ----- d=0xfd00 i=4466708 o=32768 (31) > [exec] --28817:1:aspacem 100: file 00091bc000-00091bcfff 4096 rw--- d=0xfd00 i=4466708 o=28672 (31) > [exec] --28817:1:aspacem 101: file 00091bd000-0009239fff 512000 r-xT- d=0xfd00 i=4203423 o=0 (33) > [exec] --28817:1:aspacem 102: file 000923a000-0009439fff 2097152 ----- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 103: file 000943a000-000943dfff 16384 rw--- d=0xfd00 i=4203423 o=512000 (33) > [exec] --28817:1:aspacem 104: file 000943e000-0009525fff 950272 r-xT- d=0xfd00 i=263028 o=0 (34) > [exec] --28817:1:aspacem 105: file 0009526000-0009725fff 2097152 ----- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 106: file 0009726000-000972cfff 28672 r---- d=0xfd00 i=263028 o=950272 (34) > [exec] --28817:1:aspacem 107: file 000972d000-000972efff 8192 rw--- d=0xfd00 i=263028 o=978944 (34) > [exec] --28817:1:aspacem 108: anon 000972f000-0009743fff 86016 rw--- > [exec] --28817:1:aspacem 109: file 0009744000-000975afff 94208 r-xT- d=0xfd00 i=4980773 o=0 (35) > [exec] --28817:1:aspacem 110: file 000975b000-000995afff 2097152 ----- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 111: file 000995b000-000995bfff 4096 r---- d=0xfd00 i=4980773 o=94208 (35) > [exec] --28817:1:aspacem 112: file 000995c000-000995cfff 4096 rw--- d=0xfd00 i=4980773 o=98304 (35) > [exec] --28817:1:aspacem 113: anon 000995d000-0009960fff 16384 rw--- > [exec] --28817:1:aspacem 114: file 0009961000-0009967fff 28672 r-xT- d=0xfd00 i=4980777 o=0 (36) > [exec] --28817:1:aspacem 115: file 0009968000-0009b66fff 2093056 ----- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 116: file 0009b67000-0009b67fff 4096 r---- d=0xfd00 i=4980777 o=24576 (36) > [exec] --28817:1:aspacem 117: file 0009b68000-0009b68fff 4096 rw--- d=0xfd00 i=4980777 o=28672 (36) > [exec] --28817:1:aspacem 118: file 0009b69000-0009b7efff 90112 r-xT- d=0xfd00 i=4981070 o=0 (37) > [exec] --28817:1:aspacem 119: file 0009b7f000-0009d7dfff 2093056 ----- d=0xfd00 i=4981070 o=90112 (37) > [exec] --28817:1:aspacem 120: file 0009d7e000-0009d7efff 4096 rw--- d=0xfd00 i=4981070 o=86016 (37) > [exec] --28817:1:aspacem 121: file 0009d7f000-0009f08fff 1613824 r-xT- d=0xfd00 i=4980749 o=0 (38) > [exec] --28817:1:aspacem 122: file 0009f09000-000a107fff 2093056 ----- d=0xfd00 i=4980749 o=1613824 (38) > [exec] --28817:1:aspacem 123: file 000a108000-000a10bfff 16384 r---- d=0xfd00 i=4980749 o=1609728 (38) > [exec] --28817:1:aspacem 124: file 000a10c000-000a10cfff 4096 rw--- d=0xfd00 i=4980749 o=1626112 (38) > [exec] --28817:1:aspacem 125: anon 000a10d000-000a111fff 20480 rw--- > [exec] --28817:1:aspacem 126: file 000a112000-000a113fff 8192 r-xT- d=0xfd00 i=4980755 o=0 (39) > [exec] --28817:1:aspacem 127: file 000a114000-000a313fff 2097152 ----- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 128: file 000a314000-000a314fff 4096 r---- d=0xfd00 i=4980755 o=8192 (39) > [exec] --28817:1:aspacem 129: file 000a315000-000a315fff 4096 rw--- d=0xfd00 i=4980755 o=12288 (39) > [exec] --28817:1:aspacem 130: file 000a316000-000a398fff 536576 r-xT- d=0xfd00 i=4980757 o=0 (40) > [exec] --28817:1:aspacem 131: file 000a399000-000a597fff 2093056 ----- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 132: file 000a598000-000a598fff 4096 r---- d=0xfd00 i=4980757 o=532480 (40) > [exec] --28817:1:aspacem 133: file 000a599000-000a599fff 4096 rw--- d=0xfd00 i=4980757 o=536576 (40) > [exec] --28817:1:aspacem 134: file 000a59a000-000a59dfff 16384 r-xT- d=0xfd00 i=4980923 o=0 (41) > [exec] --28817:1:aspacem 135: file 000a59e000-000a79cfff 2093056 ----- d=0xfd00 i=4980923 o=16384 (41) > [exec] --28817:1:aspacem 136: file 000a79d000-000a79dfff 4096 rw--- d=0xfd00 i=4980923 o=12288 (41) > [exec] --28817:1:aspacem 137: file 000a79e000-000a7a4fff 28672 r-xT- d=0xfd00 i=4980753 o=0 (42) > [exec] --28817:1:aspacem 138: file 000a7a5000-000a9a4fff 2097152 ----- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 139: file 000a9a5000-000a9a5fff 4096 r---- d=0xfd00 i=4980753 o=28672 (42) > [exec] --28817:1:aspacem 140: file 000a9a6000-000a9a6fff 4096 rw--- d=0xfd00 i=4980753 o=32768 (42) > [exec] --28817:1:aspacem 141: anon 000a9a7000-000a9d4fff 188416 rw--- > [exec] --28817:1:aspacem 142: file 000a9d5000-000a9f7fff 143360 r-xT- d=0xfd00 i=264775 o=0 (43) > [exec] --28817:1:aspacem 143: file 000a9f8000-000abf6fff 2093056 ----- d=0xfd00 i=264775 o=143360 (43) > [exec] --28817:1:aspacem 144: file 000abf7000-000abf8fff 8192 rw--- d=0xfd00 i=264775 o=139264 (43) > [exec] --28817:1:aspacem 145: file 000abf9000-000ac0efff 90112 r-xT- d=0xfd00 i=4980759 o=0 (44) > [exec] --28817:1:aspacem 146: file 000ac0f000-000ae0dfff 2093056 ----- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 147: file 000ae0e000-000ae0efff 4096 r---- d=0xfd00 i=4980759 o=86016 (44) > [exec] --28817:1:aspacem 148: file 000ae0f000-000ae0ffff 4096 rw--- d=0xfd00 i=4980759 o=90112 (44) > [exec] --28817:1:aspacem 149: anon 000ae10000-000ae11fff 8192 rw--- > [exec] --28817:1:aspacem 150: file 000ae12000-000ae6efff 380928 r-xT- d=0xfd00 i=4980741 o=0 (45) > [exec] --28817:1:aspacem 151: file 000ae6f000-000b06dfff 2093056 ----- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 152: file 000b06e000-000b06efff 4096 r---- d=0xfd00 i=4980741 o=376832 (45) > [exec] --28817:1:aspacem 153: file 000b06f000-000b06ffff 4096 rw--- d=0xfd00 i=4980741 o=380928 (45) > [exec] --28817:1:aspacem 154: anon 000b070000-000b073fff 16384 rw--- > [exec] --28817:1:aspacem 155: file 000b074000-000b099fff 155648 r-xT- d=0xfd00 i=4980935 o=0 (46) > [exec] --28817:1:aspacem 156: file 000b09a000-000b298fff 2093056 ----- d=0xfd00 i=4980935 o=155648 (46) > [exec] --28817:1:aspacem 157: file 000b299000-000b29bfff 12288 rw--- d=0xfd00 i=4980935 o=151552 (46) > [exec] --28817:1:aspacem 158: file 000b29c000-000b40afff 1503232 r-xT- d=0xfd00 i=4981090 o=0 (47) > [exec] --28817:1:aspacem 159: file 000b40b000-000b609fff 2093056 ----- d=0xfd00 i=4981090 o=1503232 (47) > [exec] --28817:1:aspacem 160: file 000b60a000-000b60ffff 24576 rw--- d=0xfd00 i=4981090 o=1499136 (47) > [exec] --28817:1:aspacem 161: anon 000b610000-000ba0ffff 4194304 rwx-H > [exec] --28817:1:aspacem 162: file 000ba10000-000ba11fff 8192 r-xT- d=0xfd00 i=394002 o=0 (48) > [exec] --28817:1:aspacem 163: file 000ba12000-000bc11fff 2097152 ----- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 164: file 000bc12000-000bc12fff 4096 r---- d=0xfd00 i=394002 o=8192 (48) > [exec] --28817:1:aspacem 165: file 000bc13000-000bc13fff 4096 rw--- d=0xfd00 i=394002 o=12288 (48) > [exec] --28817:1:aspacem 166: file 000bc14000-000bc14fff 4096 r-xT- d=0xfd00 i=393951 o=0 (49) > [exec] --28817:1:aspacem 167: file 000bc15000-000be14fff 2097152 ----- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 168: file 000be15000-000be15fff 4096 r---- d=0xfd00 i=393951 o=4096 (49) > [exec] --28817:1:aspacem 169: file 000be16000-000be16fff 4096 rw--- d=0xfd00 i=393951 o=8192 (49) > [exec] --28817:1:aspacem 170: anon 000be17000-000c216fff 4194304 rwx-H > [exec] --28817:1:aspacem 171: anon 000c217000-000c217fff 4096 ----- > [exec] --28817:1:aspacem 172: anon 000c218000-000cc17fff 10m rw--- > [exec] --28817:1:aspacem 173: anon 000cc18000-000d017fff 4194304 rwx-H > [exec] --28817:1:aspacem 174: file 000d018000-000d023fff 49152 r-xT- d=0xfd00 i=4980765 o=0 (51) > [exec] --28817:1:aspacem 175: file 000d024000-000d223fff 2097152 ----- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 176: file 000d224000-000d224fff 4096 r---- d=0xfd00 i=4980765 o=49152 (51) > [exec] --28817:1:aspacem 177: file 000d225000-000d225fff 4096 rw--- d=0xfd00 i=4980765 o=53248 (51) > [exec] --28817:1:aspacem 178: anon 000d226000-000f225fff 32m rwx-H > [exec] --28817:1:aspacem 179: 000f226000-0037ffffff 653m > [exec] --28817:1:aspacem 180: FILE 0038000000-0038048fff 299008 r-x-- d=0xfd00 i=266214 o=2097152 (0) > [exec] --28817:1:aspacem 181: file 0038049000-0038049fff 4096 r-xT- d=0xfd00 i=266214 o=2396160 (0) > [exec] --28817:1:aspacem 182: FILE 003804a000-003833cfff 3092480 r-x-- d=0xfd00 i=266214 o=2400256 (0) > [exec] --28817:1:aspacem 183: 003833d000-003853cfff 2097152 > [exec] --28817:1:aspacem 184: FILE 003853d000-003853ffff 12288 rw--- d=0xfd00 i=266214 o=5492736 (0) > [exec] --28817:1:aspacem 185: ANON 0038540000-003aeecfff 41m rw--- > [exec] --28817:1:aspacem 186: 003aeed000-0401ffffff 15473m > [exec] --28817:1:aspacem 187: RSVN 0402000000-0402000fff 4096 ----- SmFixed > [exec] --28817:1:aspacem 188: ANON 0402001000-0408dfefff 109m rwx-- > [exec] --28817:1:aspacem 189: ANON 0408dff000-0408e00fff 8192 ----- > [exec] --28817:1:aspacem 190: ANON 0408e01000-0408f00fff 1048576 rwx-- > [exec] --28817:1:aspacem 191: ANON 0408f01000-0408f02fff 8192 ----- > [exec] --28817:1:aspacem 192: FILE 0408f03000-0408f03fff 4096 rw--- d=0xfd00 i=4732077 o=0 (3) > [exec] --28817:1:aspacem 193: ANON 0408f04000-0409849fff 9723904 rwx-- > [exec] --28817:1:aspacem 194: 040984a000-040984bfff 8192 > [exec] --28817:1:aspacem 195: ANON 040984c000-040ce4efff 54m rwx-- > [exec] --28817:1:aspacem 196: 040ce4f000-040ce50fff 8192 > [exec] --28817:1:aspacem 197: ANON 040ce51000-040d426fff 6119424 rwx-- > [exec] --28817:1:aspacem 198: 040d427000-040d427fff 4096 > [exec] --28817:1:aspacem 199: ANON 040d428000-040d817fff 4128768 rwx-- > [exec] --28817:1:aspacem 200: 040d818000-040d818fff 4096 > [exec] --28817:1:aspacem 201: ANON 040d819000-040e5f1fff 13m rwx-- > [exec] --28817:1:aspacem 202: 040e5f2000-040e5f2fff 4096 > [exec] --28817:1:aspacem 203: ANON 040e5f3000-040eb3efff 5554176 rwx-- > [exec] --28817:1:aspacem 204: ANON 040eb3f000-040eb40fff 8192 ----- > [exec] --28817:1:aspacem 205: ANON 040eb41000-040ec40fff 1048576 rwx-- > [exec] --28817:1:aspacem 206: ANON 040ec41000-040ec42fff 8192 ----- > [exec] --28817:1:aspacem 207: ANON 040ec43000-04117ddfff 43m rwx-- > [exec] --28817:1:aspacem 208: 04117de000-04117dffff 8192 > [exec] --28817:1:aspacem 209: ANON 04117e0000-0411d87fff 5931008 rwx-- > [exec] --28817:1:aspacem 210: 0411d88000-0411d88fff 4096 > [exec] --28817:1:aspacem 211: ANON 0411d89000-041353cfff 23m rwx-- > [exec] --28817:1:aspacem 212: 041353d000-0413540fff 16384 > [exec] --28817:1:aspacem 213: ANON 0413541000-0413640fff 1048576 rwx-- > [exec] --28817:1:aspacem 214: 0413641000-0413644fff 16384 > [exec] --28817:1:aspacem 215: ANON 0413645000-0413750fff 1097728 rwx-- > [exec] --28817:1:aspacem 216: 0413751000-0413754fff 16384 > [exec] --28817:1:aspacem 217: ANON 0413755000-0413860fff 1097728 rwx-- > [exec] --28817:1:aspacem 218: 0413861000-0413880fff 131072 > [exec] --28817:1:aspacem 219: ANON 0413881000-0417519fff 60m rwx-- > [exec] --28817:1:aspacem 220: 041751a000-0417561fff 294912 > [exec] --28817:1:aspacem 221: ANON 0417562000-04176ccfff 1486848 rwx-- > [exec] --28817:1:aspacem 222: 04176cd000-07fe600fff 15983m > [exec] --28817:1:aspacem 223: RSVN 07fe601000-07feff8fff 9m ----- SmUpper > [exec] --28817:1:aspacem 224: anon 07feff9000-07ff000fff 32768 rwx-- > [exec] --28817:1:aspacem 225: 07ff001000-07ffffffff 15m > [exec] --28817:1:aspacem 226: RSVN 0800000000-37079fffff 192634m ----- SmFixed > [exec] --28817:1:aspacem 227: file 3707a00000-3707a4afff 307200 r-xT- d=0xfd00 i=4466710 o=0 (32) > [exec] --28817:1:aspacem 228: file 3707a4b000-3707c49fff 2093056 ----- d=0xfd00 i=4466710 o=307200 (32) > [exec] --28817:1:aspacem 229: file 3707c4a000-3707c4cfff 12288 rw--- d=0xfd00 i=4466710 o=303104 (32) > [exec] --28817:1:aspacem 230: RSVN 3707c4d000-370cdfffff 81m ----- SmFixed > [exec] --28817:1:aspacem 231: file 370ce00000-370ce1ffff 131072 r-xT- d=0xfd00 i=5124766 o=0 (25) > [exec] --28817:1:aspacem 232: file 370ce20000-370d01efff 2093056 ----- d=0xfd00 i=5124766 o=131072 (25) > [exec] --28817:1:aspacem 233: file 370d01f000-370d021fff 12288 rw--- d=0xfd00 i=5124766 o=126976 (25) > [exec] --28817:1:aspacem 234: RSVN 370d022000-7fffc6b43fff 130850g ----- SmFixed > [exec] --28817:1:aspacem 235: ANON 7fffc6b44000-7fffc6b58fff 86016 rw--- > [exec] --28817:1:aspacem 236: RSVN 7fffc6b59000-ffffffffff5fffff 16383e ----- SmFixed > [exec] --28817:1:aspacem 237: ANON ffffffffff600000-ffffffffff600fff 4096 r-x-- > [exec] --28817:1:aspacem 238: RSVN ffffffffff601000-ffffffffffffffff 9m ----- SmFixed > [exec] --28817:1:aspacem >>> > [exec] --28817:1:mallocfr newSuperblock at 0x413861000 (pszB 65504) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x0) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:mallocfr deferred_reclaimSuperblock at 0x413861000 (pszB 65504) (prev 0x413861000) owner VALGRIND/demangle > [exec] --28817:1:gdbsrv VG core calling VG_(gdbserver_exit) tid 1 will exit > [exec] --28817:1:gdbsrv not connected > [exec] --28817:1:gdbsrv remote_finish (reason orderly_finish) 4092 -1 > [exec] --28817:1:gdbsrv unlinking > [exec] /tmp/vgdb-pipe-from-vgdb-to-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-to-vgdb-from-28817-by-???-on-??? > [exec] /tmp/vgdb-pipe-shared-mem-vgdb-28817-by-???-on-??? > [exec] --28817:1:core_os VG_(terminate_NORETURN)(tid=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 03:18:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 03:18:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2279: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168836 > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:18:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:18:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2303) Cannot create jacoco report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2303: --------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-codeCoverage/157/ > Cannot create jacoco report > --------------------------- > > Key: JBTM-2303 > URL: https://issues.jboss.org/browse/JBTM-2303 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > {quote} > [jacoco:coverage] Enhancing junit with coverage > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jdbcresources02_pgsql_jndi > [junit] Tests run: 30, Failures: 0, Errors: 0, Time elapsed: 412.658 sec > ci-tests: > BUILD SUCCESSFUL > Total time: 447 minutes 53 seconds > generating test coverage report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:20:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:20:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2279: --------------------------------- For backport > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:24:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:24:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2279: -------------------------------- Fix Version/s: 4.17.25 > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.25, 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:29:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:29:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2279. --------------------------------- Resolution: Done > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.25, 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:29:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:29:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2302: -------------------------------- Fix Version/s: 4.17.25 (was: 4.17.24) > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:32:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:32:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2271. ------------------------------- > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:32:40 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 05:32:40 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2284. ------------------------------- > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:39:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 05:39:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023802#comment-13023802 ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from MODIFIED to ASSIGNED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 05:40:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 05:40:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023804#comment-13023804 ] RH Bugzilla Integration commented on JBTM-2279: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1168836|https://bugzilla.redhat.com/show_bug.cgi?id=1168836] from NEW to ASSIGNED > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.25, 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 06:00:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 06:00:44 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023813#comment-13023813 ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Carlo de Wolf changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from ASSIGNED to MODIFIED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 06:55:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 06:55:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023829#comment-13023829 ] RH Bugzilla Integration commented on JBTM-2279: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1168836|https://bugzilla.redhat.com/show_bug.cgi?id=1168836] from ASSIGNED to MODIFIED > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.25, 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 09:43:39 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 28 Nov 2014 09:43:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1939) Consider using awestruct to develop http://narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-1939. --------------------------------- Resolution: Done > Consider using awestruct to develop http://narayana.io > ------------------------------------------------------ > > Key: JBTM-1939 > URL: https://issues.jboss.org/browse/JBTM-1939 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Awestruct appears to be a powerful and flexible tool to develop websites with. This task is to research the capabilities of the tool and determine if the benefits of awestruct apply to our website. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 10:47:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 10:47:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2308: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168973 > JTS participants are not showing up in the tooling > -------------------------------------------------- > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 10:47:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 10:47:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023884#comment-13023884 ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from NEW to ASSIGNED > JTS participants are not showing up in the tooling > -------------------------------------------------- > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 28 10:54:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 28 Nov 2014 10:54:39 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023888#comment-13023888 ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- Hayk Hovsepyan changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from ON_QA to VERIFIED > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338)