September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1937) Ensure that CI runs with findbugs on (do not fail on findbugs issues) and make sure the report is archived in the job config

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1937?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1937: ----------------------------------- Assignee: Tom Jenkinson (was: Amos Feng) > Ensure that CI runs with findbugs on (do not fail on findbugs issues) and make sure the report is archived in the job config > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1937 > URL: https://issues.jboss.org/browse/JBTM-1937 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > As the summary says: > 1. Findbugs ran in the main CI run (not default therefore) > 2. Issues don't cause the build to fail > 3. Reports are archived for review -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1937) Ensure that CI runs with findbugs on (do not fail on findbugs issues) and make sure the report is archived in the job config

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1937?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1937: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/454 > Ensure that CI runs with findbugs on (do not fail on findbugs issues) and make sure the report is archived in the job config > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1937 > URL: https://issues.jboss.org/browse/JBTM-1937 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > As the summary says: > 1. Findbugs ran in the main CI run (not default therefore) > 2. Issues don't cause the build to fail > 3. Reports are archived for review -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1855: ------------------------------------- I raised an initial PR from [~zhfeng]' commit, it hasn't been revised as per [~gytis] comment but it should make it easier when [~zhfeng] gets back to see if there is a problem. I also took the opportunity to add a pull to remove using the restat-web.war and just use the rts subsystem > No unit tests for queue with RTS transport > ------------------------------------------ > > Key: JBTM-1855 > URL: https://issues.jboss.org/browse/JBTM-1855 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, REST, Testing > Reporter: Crispin Boylan > Assignee: Amos Feng > Fix For: 5.0.0.M5 > > > There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml. > When TXN_CFG is manually added to the btconfig.xml the tests actually fail with error: > 15:15:44,584 ERROR [jacorb.orb] (StompConnect Transport: tcp:///127.0.0.1:49804) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><coordinator><status>TransactionActive</status><created>1970-01-01T01:00:00.060+01:00</created><timeout>300</timeout><txnURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</volatileParticipantEnlistmentURI></coordinator> > at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:484) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:486) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ParsedIOR.<init>(ParsedIOR.java:225) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ORB.string_to_object(ORB.java:1961) [jacorb-2.3.2.jbossorg-4.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.createControlWrapper(ProtocolConverter.java:110) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.controlToTx(ProtocolConverter.java:98) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.onStompReceive(ProtocolConverter.java:310) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:172) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1855: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/453, https://github.com/jbosstm/narayana/pull/452 > No unit tests for queue with RTS transport > ------------------------------------------ > > Key: JBTM-1855 > URL: https://issues.jboss.org/browse/JBTM-1855 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, REST, Testing > Reporter: Crispin Boylan > Assignee: Amos Feng > Fix For: 5.0.0.M5 > > > There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml. > When TXN_CFG is manually added to the btconfig.xml the tests actually fail with error: > 15:15:44,584 ERROR [jacorb.orb] (StompConnect Transport: tcp:///127.0.0.1:49804) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><coordinator><status>TransactionActive</status><created>1970-01-01T01:00:00.060+01:00</created><timeout>300</timeout><txnURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</volatileParticipantEnlistmentURI></coordinator> > at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:484) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:486) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ParsedIOR.<init>(ParsedIOR.java:225) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ORB.string_to_object(ORB.java:1961) [jacorb-2.3.2.jbossorg-4.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.createControlWrapper(ProtocolConverter.java:110) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.controlToTx(ProtocolConverter.java:98) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.onStompReceive(ProtocolConverter.java:310) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:172) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1016: ------------------------------------- Faionerror set to true: https://github.com/jbosstm/narayana/pull/451 > Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code > ------------------------------------------------------------------------------------- > > Key: JBTM-1016 > URL: https://issues.jboss.org/browse/JBTM-1016 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > I've found many bugs in the XTS crash recovery tests that where due to changes being made to the XTS code without updating the byteman scripts. The problem is that these inconsistencies often go unnoticed when the tests run, until you notice a failure in the test. > Can we run bmcheck as part of the maven build and make the build fail if it detects errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin > NOTE: Before raising the pull req it will be necessary to resolve any the discovered errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1783) no matching injection point in ArjunaCore/arjuna/test/byteman-scripts/reaper.txt

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1783?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1783: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/451 > no matching injection point in ArjunaCore/arjuna/test/byteman-scripts/reaper.txt > --------------------------------------------------------------------------------- > > Key: JBTM-1783 > URL: https://issues.jboss.org/browse/JBTM-1783 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > Original Estimate: 3 days > Time Spent: 2 hours > Remaining Estimate: 2 days, 6 hours > > {noformat} > [INFO] Checking 3 byteman scripts in /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 3" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 65 against method check() void > org.jboss.byteman.rule.exception.TypeWarningException: no matching injection point for method check() void > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 3" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 65 > org.jboss.byteman.rule.exception.TypeWarningException: failed to find any matching trigger method in class com.arjuna.ats.arjuna.coordinator.TransactionReaper > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 79 against method check() void > org.jboss.byteman.rule.exception.TypeWarningException: no matching injection point for method check() void > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 79 > org.jboss.byteman.rule.exception.TypeWarningException: failed to find any matching trigger method in class com.arjuna.ats.arjuna.coordinator.TransactionReaper > [WARNING] WARNING : Warning type checking rule "pause transaction reaper worker 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 186 against method doCancellations() void > org.jboss.byteman.rule.exception.TypeWarningException: no matching injection point for method doCancellations() void > [WARNING] WARNING : Warning type checking rule "pause transaction reaper worker 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 186 > org.jboss.byteman.rule.exception.TypeWarningException: failed to find any matching trigger method in class com.arjuna.ats.arjuna.coordinator.TransactionReaper > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1753) Merge TXFramework and CompensationsAPI-prototype

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1753?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1753: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > Merge TXFramework and CompensationsAPI-prototype > ------------------------------------------------ > > Key: JBTM-1753 > URL: https://issues.jboss.org/browse/JBTM-1753 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0.Final > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The current implementation of the compensations API was a quick prototype I knocked up ready for JUDCon. It needs merging into the existing TXFramework API. > This will need some investigation as there are now multiple ways of doing the same thing. We need to decide which or both to keep. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1934) BlackTie attempting to stop the messagelistener connection - invalid according to JMS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1934?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1934: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BlackTie attempting to stop the messagelistener connection - invalid according to JMS > ------------------------------------------------------------------------------------- > > Key: JBTM-1934 > URL: https://issues.jboss.org/browse/JBTM-1934 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > 12:06:42,851 ERROR [org.codehaus.stomp.jms.StompSubscription] (Thread-10 (HornetQ-client-global-threads-11543367)) Could not stop the connection: javax.jms.IllegalStateException: HQ129006: It is illegal to call this method from within a Message Listener: javax.jms.IllegalStateException: HQ129006: It is illegal to call this method from within a Message Listener > at org.hornetq.jms.client.ThreadAwareContext.assertNotMessageListenerThread(ThreadAwareContext.java:137) > at org.hornetq.jms.client.HornetQConnection.stop(HornetQConnection.java:311) > at org.codehaus.stomp.jms.StompSession.stop(StompSession.java:373) [wildfly-blacktie-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.codehaus.stomp.jms.StompSubscription.onMessage(StompSubscription.java:75) [wildfly-blacktie-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:104) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1117) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:57) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1252) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1938?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1938: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Caching of datasource for JDBC store incompatible with WildFly :reload operation > -------------------------------------------------------------------------------- > > Key: JBTM-1938 > URL: https://issues.jboss.org/browse/JBTM-1938 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.11, 5.0.0.M5 > > > The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace). > Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1939) Consider using awestruct to develop http://narayana.io

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1939?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1939: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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 > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 6.0.0.Final > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2013