[JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2540:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
> -------------------------------------------------------------------
>
> Key: JBTM-2540
> URL: https://issues.jboss.org/browse/JBTM-2540
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie, Build System
> Affects Versions: 5.2.6.Final
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s]
> [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s]
> [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s]
> [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 10.345s
> [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015
> [INFO] Final Memory: 51M/234M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro
> visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-2540:
----------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/930
> Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
> -------------------------------------------------------------------
>
> Key: JBTM-2540
> URL: https://issues.jboss.org/browse/JBTM-2540
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie, Build System
> Affects Versions: 5.2.6.Final
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s]
> [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s]
> [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s]
> [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 10.345s
> [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015
> [INFO] Final Memory: 51M/234M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro
> visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-2540:
---------------------------------
Thanks Tom for looking into it and I think it would be some configuration changes.
> Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
> -------------------------------------------------------------------
>
> Key: JBTM-2540
> URL: https://issues.jboss.org/browse/JBTM-2540
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie, Build System
> Affects Versions: 5.2.6.Final
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s]
> [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s]
> [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s]
> [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 10.345s
> [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015
> [INFO] Final Memory: 51M/234M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro
> visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2540:
-------------------------------------
I pushed a commit to align with current build tools and wildfly core but this hasn't helped: https://github.com/jbosstm/narayana/commit/ada5603d9f2e758b402a3f351a32e9...
I pushed it anyway because it needs to be done during the upgrade and it didn't make it worse...
{code}
[ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR2:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR2:build failed: java.lang.RuntimeException: java.lang.NullPointerException
{code}
> Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
> -------------------------------------------------------------------
>
> Key: JBTM-2540
> URL: https://issues.jboss.org/browse/JBTM-2540
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie, Build System
> Affects Versions: 5.2.6.Final
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s]
> [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s]
> [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s]
> [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 10.345s
> [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015
> [INFO] Final Memory: 51M/234M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro
> visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-2540:
-----------------------------------
Summary: Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT
Key: JBTM-2540
URL: https://issues.jboss.org/browse/JBTM-2540
Project: JBoss Transaction Manager
Issue Type: Bug
Components: BlackTie, Build System
Affects Versions: 5.2.6.Final
Reporter: Tom Jenkinson
Assignee: Amos Feng
Priority: Blocker
Fix For: 5.next
{code}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s]
[INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s]
[INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s]
[INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.345s
[INFO] Finished at: Wed Oct 21 16:40:05 BST 2015
[INFO] Final Memory: 51M/234M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro
visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2433:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.6.Final)
> TransactionRolledBackException in MultiCloseTest
> ------------------------------------------------
>
> Key: JBTM-2433
> URL: https://issues.jboss.org/browse/JBTM-2433
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: XTS
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 5.next
>
> Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt
>
>
> It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion.
> {code}
> -------------------------------------------------------------------------------
> Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE!
> testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR!
> com.arjuna.wst.TransactionRolledBackException: null
> at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95)
> at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157)
> at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2318) Too verbose startup?
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2318:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.6.Final)
> Too verbose startup?
> --------------------
>
> Key: JBTM-2318
> URL: https://issues.jboss.org/browse/JBTM-2318
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Transaction Core
> Affects Versions: 5.0.4
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.next
>
>
> At startup of the most basic example we see ...
> Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185
> Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185
> Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2234:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.6.Final)
> out of memory when logging more messages than heap size (surefire issue)
> ------------------------------------------------------------------------
>
> Key: JBTM-2234
> URL: https://issues.jboss.org/browse/JBTM-2234
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Performance Testing
> Affects Versions: 5.0.2
> Environment: JTS testing
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Optional
> Fix For: 5.next
>
>
> Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished.
> In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months