From issues at jboss.org  Sun Feb  1 21:29:49 2015
From: issues at jboss.org (Amos Feng (JIRA))
Date: Sun, 1 Feb 2015 21:29:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process
 terminating with default action of signal 13 (SIGPIPE)
In-Reply-To: <JIRA.12531824.1392158081000@Atlassian.JIRA>
References: <JIRA.12531824.1392158081000@Atlassian.JIRA>
	<JIRA.12531824.1392158081000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531824.1392158081000.35869.1422844189141@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng updated JBTM-2090:
----------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/narayana/pull/804


> BlackTie process terminating with default action of signal 13 (SIGPIPE)
> -----------------------------------------------------------------------
>
>                 Key: JBTM-2090
>                 URL: https://issues.jboss.org/browse/JBTM-2090
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>              Labels: linux64el6, linux64el7
>             Fix For: 5.0.5
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log
> {code}
> ==11776== Process terminating with default action of signal 13 (SIGPIPE)
> ==11776==    at 0x72734ED: ??? (in /lib64/libpthread-2.12.so)
> ==11776==    by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9)
> ==11776==    by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305)
> ==11776==    by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347)
> ==11776==    by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536)
> ==11776==    by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147)
> ==11776==    by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183)
> ==11776==    by 0x6D24122: tpdiscon (XATMIc.cxx:1220)
> ==11776==    by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66)
> ==11776==    by 0x49B74A: CppUnit::TestCaller<TestTPConnect>::tearDown() (TestCaller.h:182)
> ==11776==    by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32)
> ==11776==    by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15)
> ==11776==    by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20)
> ==11776==    by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77)
> ==11776==    by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178)
> ==11776==    by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97)
> ==11776==    by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==11776==    by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==11776==    by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==11776==    by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==11776==    by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145)
> ==11776==    by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96)
> ==11776==    by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64)
> ==11776==    by 0x4F6F83: main (TestRunner.cxx:27)
> --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap()
> --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap()
> --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap()
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  2 05:42:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Mon, 2 Feb 2015 05:42:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763819@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.36216.1422873769207@Atlassian.JIRA>

Gytis Trikleris created JBTM-2336:
-------------------------------------

             Summary: MySQL JDBC tests fail
                 Key: JBTM-2336
                 URL: https://issues.jboss.org/browse/JBTM-2336
             Project: JBoss Transaction Manager
          Issue Type: Bug
          Components: JTA
            Reporter: Gytis Trikleris
            Assignee: Michael Musgrove
            Priority: Blocker
             Fix For: 5.0.5


http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  2 05:43:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Mon, 2 Feb 2015 05:43:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.36221.1422873829342@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036726#comment-13036726 ] 

Gytis Trikleris commented on JBTM-2336:
---------------------------------------

http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/735/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/

> MySQL JDBC tests fail
> ---------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Michael Musgrove
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  2 05:45:50 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Mon, 2 Feb 2015 05:45:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.36224.1422873950104@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036726#comment-13036726 ] 

Gytis Trikleris edited comment on JBTM-2336 at 2/2/15 5:45 AM:
---------------------------------------------------------------

http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/735/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/
http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/734/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/
http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/733/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/



was (Author: gytis):
http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/735/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux/

> MySQL JDBC tests fail
> ---------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Michael Musgrove
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  2 06:16:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Mon, 2 Feb 2015 06:16:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.36253.1422875809181@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove reassigned JBTM-2336:
--------------------------------------

    Assignee: Tom Jenkinson  (was: Michael Musgrove)


> MySQL JDBC tests fail
> ---------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  2 06:17:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Mon, 2 Feb 2015 06:17:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.36256.1422875869107@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036729#comment-13036729 ] 

Michael Musgrove commented on JBTM-2336:
----------------------------------------

The failures look similar to one of Toms PRs: https://github.com/jbosstm/narayana/pull/803
Please feel free to reassign back if you think the root cause is different.

> MySQL JDBC tests fail
> ---------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  2 08:32:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Mon, 2 Feb 2015 08:32:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-860) use XAResourceWrapper
 metadata for assume complete
In-Reply-To: <JIRA.12442424.1311338155000@Atlassian.JIRA>
References: <JIRA.12442424.1311338155000@Atlassian.JIRA>
	<JIRA.12442424.1311338155000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12442424.1311338155000.36716.1422883969437@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris updated JBTM-860:
---------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> use XAResourceWrapper metadata for assume complete
> --------------------------------------------------
>
>                 Key: JBTM-860
>                 URL: https://issues.jboss.org/browse/JBTM-860
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Resource Manager
>    Affects Versions: 4.15.0
>            Reporter: Jonathan Halliday
>            Assignee: Gytis Trikleris
>             Fix For: 5.x.y
>
>
> In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM.  It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control.  With the availability of RM id information from XAResourceWrapper this becomes feasible.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb  3 00:59:49 2015
From: issues at jboss.org (Amos Feng (JIRA))
Date: Tue, 3 Feb 2015 00:59:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process
 terminating with default action of signal 13 (SIGPIPE)
In-Reply-To: <JIRA.12531824.1392158081000@Atlassian.JIRA>
References: <JIRA.12531824.1392158081000@Atlassian.JIRA>
	<JIRA.12531824.1392158081000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12531824.1392158081000.38281.1422943189263@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng updated JBTM-2090:
----------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> BlackTie process terminating with default action of signal 13 (SIGPIPE)
> -----------------------------------------------------------------------
>
>                 Key: JBTM-2090
>                 URL: https://issues.jboss.org/browse/JBTM-2090
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>              Labels: linux64el6, linux64el7
>             Fix For: 5.0.5
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log
> {code}
> ==11776== Process terminating with default action of signal 13 (SIGPIPE)
> ==11776==    at 0x72734ED: ??? (in /lib64/libpthread-2.12.so)
> ==11776==    by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9)
> ==11776==    by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305)
> ==11776==    by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347)
> ==11776==    by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536)
> ==11776==    by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147)
> ==11776==    by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183)
> ==11776==    by 0x6D24122: tpdiscon (XATMIc.cxx:1220)
> ==11776==    by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66)
> ==11776==    by 0x49B74A: CppUnit::TestCaller<TestTPConnect>::tearDown() (TestCaller.h:182)
> ==11776==    by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32)
> ==11776==    by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15)
> ==11776==    by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20)
> ==11776==    by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77)
> ==11776==    by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178)
> ==11776==    by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97)
> ==11776==    by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==11776==    by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==11776==    by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==11776==    by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==11776==    by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145)
> ==11776==    by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96)
> ==11776==    by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64)
> ==11776==    by 0x4F6F83: main (TestRunner.cxx:27)
> --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap()
> --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap()
> --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap()
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 04:52:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Wed, 4 Feb 2015 04:52:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42122.1423043569018@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris reassigned JBTM-2336:
-------------------------------------

    Assignee: Gytis Trikleris  (was: Tom Jenkinson)


> MySQL JDBC tests fail
> ---------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 04:53:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Wed, 4 Feb 2015 04:53:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) MySQL JDBC tests fail
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42126.1423043629202@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037446#comment-13037446 ] 

Gytis Trikleris commented on JBTM-2336:
---------------------------------------

http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/739/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux
http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/737/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux

> MySQL JDBC tests fail
> ---------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 04:54:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Wed, 4 Feb 2015 04:54:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) JDBC tests fail on
	different databases
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42131.1423043689331@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris updated JBTM-2336:
----------------------------------
    Summary: JDBC tests fail on different databases  (was: MySQL JDBC tests fail)


> JDBC tests fail on different databases
> --------------------------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 04:56:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 04:56:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) JDBC tests fail on
	different databases
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42152.1423043809132@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2336:
--------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/narayana/pull/803


There is a bug, but now all the DB tests are failing. I think I fixed the bug in https://github.com/jbosstm/narayana/pull/803 but I think the databases are all broken atm

> JDBC tests fail on different databases
> --------------------------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:09:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:09:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) JDBC tests fail on
	different databases
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42214.1423044589159@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2336:
-----------------------------------

    Assignee: Tom Jenkinson  (was: Gytis Trikleris)


> JDBC tests fail on different databases
> --------------------------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:10:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:10:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) Transactional Driver
 tests fail on MySQL and Postgres database
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42218.1423044649296@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2336:
--------------------------------
    Summary: Transactional Driver tests fail on MySQL and Postgres database  (was: JDBC tests fail on different databases)


> Transactional Driver tests fail on MySQL and Postgres database
> --------------------------------------------------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>              Labels: Regression
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:10:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:10:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) Transactional Driver
 tests fail on MySQL and Postgres database
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42222.1423044649464@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2336:
--------------------------------
    Labels: Regression  (was: )


> Transactional Driver tests fail on MySQL and Postgres database
> --------------------------------------------------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>              Labels: Regression
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:12:48 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:12:48 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) Transactional Driver
 tests fail on MySQL and Postgres database
In-Reply-To: <JIRA.12562167.1422873763000@Atlassian.JIRA>
References: <JIRA.12562167.1422873763000@Atlassian.JIRA>
	<JIRA.12562167.1422873763000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562167.1422873763000.42226.1423044768965@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2336:
--------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Transactional Driver tests fail on MySQL and Postgres database
> --------------------------------------------------------------
>
>                 Key: JBTM-2336
>                 URL: https://issues.jboss.org/browse/JBTM-2336
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>              Labels: Regression
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:36:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:36:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2101) Blacktie integration
	CSTest hang
In-Reply-To: <JIRA.12533080.1393241679000@Atlassian.JIRA>
References: <JIRA.12533080.1393241679000@Atlassian.JIRA>
	<JIRA.12533080.1393241679000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533080.1393241679000.42276.1423046209323@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2101:
--------------------------------
    Fix Version/s: 5.0.5
                       (was: 5.x.y)


> Blacktie integration CSTest hang
> --------------------------------
>
>                 Key: JBTM-2101
>                 URL: https://issues.jboss.org/browse/JBTM-2101
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>            Reporter: Gytis Trikleris
>            Assignee: Amos Feng
>            Priority: Minor
>             Fix For: 5.0.5
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el5



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:37:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:37:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2196) QA suite failure:
 CrashRecovery05_2_Test034
In-Reply-To: <JIRA.12543942.1402911988000@Atlassian.JIRA>
References: <JIRA.12543942.1402911988000@Atlassian.JIRA>
	<JIRA.12543942.1402911988000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12543942.1402911988000.42280.1423046269338@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2196:
--------------------------------
    Fix Version/s: 5.0.5
                       (was: 5.x.y)


> QA suite failure: CrashRecovery05_2_Test034
> -------------------------------------------
>
>                 Key: JBTM-2196
>                 URL: https://issues.jboss.org/browse/JBTM-2196
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTS, Testing
>            Reporter: Gytis Trikleris
>            Assignee: Michael Musgrove
>            Priority: Minor
>             Fix For: 5.0.5
>
>         Attachments: CrashRecovery05_2_Test034.tar
>
>
> http://172.17.131.2/view/Status/job/narayana/550/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:37:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:37:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2252) QA suite failure:
 CrashRecovery05_2_Test030
In-Reply-To: <JIRA.12552158.1410774899000@Atlassian.JIRA>
References: <JIRA.12552158.1410774899000@Atlassian.JIRA>
	<JIRA.12552158.1410774899000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12552158.1410774899000.42284.1423046269493@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2252:
--------------------------------
    Fix Version/s: 5.0.5
                       (was: 5.x.y)


> QA suite failure: CrashRecovery05_2_Test030 
> --------------------------------------------
>
>                 Key: JBTM-2252
>                 URL: https://issues.jboss.org/browse/JBTM-2252
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTS, Testing
>            Reporter: Gytis Trikleris
>            Assignee: Michael Musgrove
>            Priority: Minor
>             Fix For: 5.0.5
>
>         Attachments: CrashRecovery05_2_Test030.tar
>
>
> http://172.17.131.2/view/Status/job/narayana/638/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb  4 05:37:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:37:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.42288.1423046269600@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2300:
--------------------------------
    Fix Version/s: 5.0.5
                       (was: 5.x.y)


> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Wed Feb  4 05:38:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 4 Feb 2015 05:38:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by
 coordinator in CloseTest
In-Reply-To: <JIRA.12543933.1402908381000@Atlassian.JIRA>
References: <JIRA.12543933.1402908381000@Atlassian.JIRA>
	<JIRA.12543933.1402908381000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12543933.1402908381000.42291.1423046329193@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2194:
--------------------------------
    Fix Version/s: 5.0.5
                       (was: 5.x.y)


> Activity cancelled by coordinator in CloseTest
> ----------------------------------------------
>
>                 Key: JBTM-2194
>                 URL: https://issues.jboss.org/browse/JBTM-2194
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: XTS
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>             Fix For: 5.0.5
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: com.arjuna.wstx.tests.arq.ba.CloseTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE!
> testClose(com.arjuna.wstx.tests.arq.ba.CloseTest)  Time elapsed: 2.375 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.CloseTest.testClose(CloseTest.java:64)
> {code}
> {code}
> 18:45:37,613 INFO  [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content
> 18:45:37,616 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
> 18:45:37,860 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> 18:45:37,927 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war
> 18:45:37,941 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war
> 18:45:37,946 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war
> 18:45:38,228 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test
> 18:45:38,406 INFO  [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
> 18:45:38,418 INFO  [stdout] (Thread-0) TransformListener() : handling connection on port 9091
> 18:45:38,492 INFO  [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:38,492 INFO  [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:38,493 INFO  [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,495 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:38,496 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter
> 18:45:38,497 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:38,514 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:38,517 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called
> 18:45:38,536 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:38,552 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,554 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called
> 18:45:38,556 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,558 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,559 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called
> 18:45:38,560 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:39,123 INFO  [stdout] (default task-16) Rule.execute called for create counter_3
> 18:45:39,124 INFO  [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:39,124 INFO  [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:39,124 INFO  [stdout] (default task-16) Default helper activated
> 18:45:39,124 INFO  [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:39,125 INFO  [stdout] (default task-16) Installed rule using default helper : create counter
> 18:45:39,135 INFO  [stdout] (default task-16) create counter execute
> 18:45:39,135 INFO  [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1
> 18:45:39,158 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl
> 18:45:39,205 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl
> 18:45:39,282 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl
> 18:45:40,131 WARN  [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235
> 18:45:40,188 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl
> 18:45:41,372 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl
> 18:45:42,052 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl
> 18:45:42,090 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl
> 18:45:42,409 INFO  [stdout] (default-workqueue-2) Rule.execute called for close called_6
> 18:45:42,410 INFO  [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,411 INFO  [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:42,411 INFO  [stdout] (default-workqueue-2) Installed rule using default helper : close called
> 18:45:42,411 INFO  [stdout] (default-workqueue-2) close called execute
> 18:45:42,412 INFO  [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting
> 18:45:42,412 INFO  [stdout] (TaskWorker-2) Rule.execute called for complete called_4
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) Installed rule using default helper : complete called
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) complete called execute
> 18:45:42,414 INFO  [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement
> 18:45:42,414 INFO  [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking
> 18:45:42,414 INFO  [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken
> 18:45:42,415 INFO  [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake
> 18:45:42,415 WARN  [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity
> 18:45:42,428 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl
> 18:45:42,439 INFO  [stdout] (TaskWorker-1) Rule.execute called for complete called_4
> 18:45:42,441 INFO  [stdout] (TaskWorker-1) complete called execute
> 18:45:42,496 INFO  [stdout] (Thread-0) TransformListener() : handling connection on port 9091
> 18:45:42,598 INFO  [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:42,599 INFO  [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:42,599 INFO  [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:42,815 INFO  [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,816 INFO  [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,816 INFO  [stdout] (Thread-0) Uninstalled rule using default helper : create counter
> 18:45:42,817 INFO  [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,817 INFO  [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,818 INFO  [stdout] (Thread-0) Uninstalled rule using default helper : complete called
> 18:45:42,818 INFO  [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,819 INFO  [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,819 INFO  [stdout] (Thread-0) Uninstalled rule using default helper : close called
> 18:45:42,819 INFO  [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:42,820 INFO  [stdout] (Thread-0) Default helper deactivated
> 18:45:42,830 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test
> 18:45:42,845 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war
> 18:45:42,855 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms
> 18:45:42,942 INFO  [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content
> 18:45:42,942 INFO  [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war")
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


From issues at jboss.org  Thu Feb  5 11:02:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Thu, 5 Feb 2015 11:02:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2332)
	resolve_initial_references on JDK ORB
In-Reply-To: <JIRA.12561007.1421339956000@Atlassian.JIRA>
References: <JIRA.12561007.1421339956000@Atlassian.JIRA>
	<JIRA.12561007.1421339956000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12561007.1421339956000.45781.1423152169183@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2332:
-----------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/quickstart/pull/132


The existing code already uses resolve_initial_references and is tied into the orb portability layer. I have created a quickstart to demonstrate this:

https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/standalone



> resolve_initial_references on JDK ORB
> -------------------------------------
>
>                 Key: JBTM-2332
>                 URL: https://issues.jboss.org/browse/JBTM-2332
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Michael Musgrove
>
> Check how the JDK ORB uses resolve_initial_references and that it is tied into the ORB Portability layer.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb  5 11:03:50 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Thu, 5 Feb 2015 11:03:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2332)
	resolve_initial_references on JDK ORB
In-Reply-To: <JIRA.12561007.1421339956000@Atlassian.JIRA>
References: <JIRA.12561007.1421339956000@Atlassian.JIRA>
	<JIRA.12561007.1421339956000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12561007.1421339956000.45794.1423152230086@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2332:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> resolve_initial_references on JDK ORB
> -------------------------------------
>
>                 Key: JBTM-2332
>                 URL: https://issues.jboss.org/browse/JBTM-2332
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Michael Musgrove
>
> Check how the JDK ORB uses resolve_initial_references and that it is tied into the ORB Portability layer.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb  5 12:22:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Thu, 5 Feb 2015 12:22:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for
 triggering a performance check
In-Reply-To: <JIRA.12562527.1423156948000@Atlassian.JIRA>
References: <JIRA.12562527.1423156948000@Atlassian.JIRA>
	<JIRA.12562527.1423156948948@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562527.1423156948000.45954.1423156969001@Atlassian.JIRA>

Michael Musgrove created JBTM-2337:
--------------------------------------

             Summary: Add a PR profile for triggering a performance check
                 Key: JBTM-2337
                 URL: https://issues.jboss.org/browse/JBTM-2337
             Project: JBoss Transaction Manager
          Issue Type: Enhancement
          Components: Testing
    Affects Versions: 5.0.4
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.x.y


Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 05:39:48 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 05:39:48 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
	on IPv6
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149199@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.47191.1423219188982@Atlassian.JIRA>

Michael Musgrove created JBTM-2338:
--------------------------------------

             Summary: cdi arquillian tests fail on IPv6
                 Key: JBTM-2338
                 URL: https://issues.jboss.org/browse/JBTM-2338
             Project: JBoss Transaction Manager
          Issue Type: Bug
          Components: Testing
    Affects Versions: 5.0.4
            Reporter: Michael Musgrove
            Assignee: Tom Jenkinson


The arquillian cdi tests fail on IPv6 with the error: "Could not start container"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 05:40:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 05:40:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
	on IPv6
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.47197.1423219249288@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2338:
-----------------------------------
    Attachment: surefire-reports.zip


> cdi arquillian tests fail on IPv6
> ---------------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>         Attachments: surefire-reports.zip
>
>
> The arquillian cdi tests fail on IPv6 with the error: "Could not start container"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 10:19:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 10:19:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.47793.1423235988997@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2338:
-----------------------------------
    Summary: cdi arquillian tests fail  (was: cdi arquillian tests fail on IPv6)


> cdi arquillian tests fail
> -------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>         Attachments: surefire-reports.zip
>
>
> The arquillian cdi tests fail on IPv6 with the error: "Could not start container"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 10:21:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 10:21:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.47796.1423236109261@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2338:
-----------------------------------
    Description: The arquillian cdi tests fail on IPv6 with the error: "Deployment Cannot deploy: test.war"  (was: The arquillian cdi tests fail on IPv6 with the error: "Could not start container")


> cdi arquillian tests fail
> -------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>
> The arquillian cdi tests fail on IPv6 with the error: "Deployment Cannot deploy: test.war"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 10:21:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 10:21:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.47799.1423236109339@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2338:
-----------------------------------
    Attachment:     (was: surefire-reports.zip)


> cdi arquillian tests fail
> -------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>
> The arquillian cdi tests fail on IPv6 with the error: "Deployment Cannot deploy: test.war"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 11:02:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 11:02:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for
 triggering a performance check
In-Reply-To: <JIRA.12562527.1423156948000@Atlassian.JIRA>
References: <JIRA.12562527.1423156948000@Atlassian.JIRA>
	<JIRA.12562527.1423156948000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562527.1423156948000.47975.1423238569363@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038401#comment-13038401 ] 

Michael Musgrove commented on JBTM-2337:
----------------------------------------

The tests run fine in IPv4 and IPv6 mode on my laptop so it's an environmental issue.

> Add a PR profile for triggering a performance check
> ---------------------------------------------------
>
>                 Key: JBTM-2337
>                 URL: https://issues.jboss.org/browse/JBTM-2337
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.x.y
>
>
> Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 11:03:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 11:03:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for
 triggering a performance check
In-Reply-To: <JIRA.12562527.1423156948000@Atlassian.JIRA>
References: <JIRA.12562527.1423156948000@Atlassian.JIRA>
	<JIRA.12562527.1423156948000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562527.1423156948000.47980.1423238629532@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2337:
-----------------------------------
    Comment: was deleted

(was: The tests run fine in IPv4 and IPv6 mode on my laptop so it's an environmental issue.)


> Add a PR profile for triggering a performance check
> ---------------------------------------------------
>
>                 Key: JBTM-2337
>                 URL: https://issues.jboss.org/browse/JBTM-2337
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.x.y
>
>
> Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 11:04:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 11:04:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.47990.1423238689488@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038405#comment-13038405 ] 

Michael Musgrove commented on JBTM-2338:
----------------------------------------

The tests run fine in IPv4 and IPv6 mode on my laptop so it's an environmental issue.

> cdi arquillian tests fail
> -------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>
> The arquillian cdi tests fail on IPv6 with the error: "Deployment Cannot deploy: test.war"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 11:16:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 11:16:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.48098.1423239409657@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2338:
-----------------------------------
    Attachment: surefire-reports.zip


The tests fail because undertow fails to start:
{code}
Caused by: java.net.BindException: Address already in use
{code}

> cdi arquillian tests fail
> -------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>         Attachments: surefire-reports.zip
>
>
> The arquillian cdi tests fail on IPv6 with the error: "Deployment Cannot deploy: test.war"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 11:56:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 6 Feb 2015 11:56:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2338) cdi arquillian tests fail
In-Reply-To: <JIRA.12562589.1423219149000@Atlassian.JIRA>
References: <JIRA.12562589.1423219149000@Atlassian.JIRA>
	<JIRA.12562589.1423219149000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562589.1423219149000.48297.1423241809020@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove closed JBTM-2338.
----------------------------------
    Resolution: Rejected


jsvc (the launcher for the jenkins web gui) is holding port 8080 open so the arquillian container cannot start undertow. I am going to disable the CDI arq tests for the time being.

> cdi arquillian tests fail
> -------------------------
>
>                 Key: JBTM-2338
>                 URL: https://issues.jboss.org/browse/JBTM-2338
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>         Attachments: surefire-reports.zip
>
>
> The arquillian cdi tests fail on IPv6 with the error: "Deployment Cannot deploy: test.war"



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb  6 18:22:51 2015
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 6 Feb 2015 18:22:51 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management
 interface to see a list of Xids that are being being considered for
 recovery by the recovery manager
In-Reply-To: <JIRA.12560543.1420737406000@Atlassian.JIRA>
References: <JIRA.12560543.1420737406000@Atlassian.JIRA>
	<JIRA.12560543.1420737406000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12560543.1420737406000.49067.1423264971214@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038576#comment-13038576 ] 

RH Bugzilla Integration commented on JBTM-2326:
-----------------------------------------------

Paul Gier <pgier at redhat.com> changed the Status of [bug 1178798|https://bugzilla.redhat.com/show_bug.cgi?id=1178798] from MODIFIED to ON_QA

> Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2326
>                 URL: https://issues.jboss.org/browse/JBTM-2326
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: JTA, Tooling
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>
> Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state:
> https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  9 08:26:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Mon, 9 Feb 2015 08:26:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for
 triggering a performance check
In-Reply-To: <JIRA.12562527.1423156948000@Atlassian.JIRA>
References: <JIRA.12562527.1423156948000@Atlassian.JIRA>
	<JIRA.12562527.1423156948000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562527.1423156948000.50344.1423488409021@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2337:
-----------------------------------
    Fix Version/s: 5.0.5
                       (was: 5.x.y)


> Add a PR profile for triggering a performance check
> ---------------------------------------------------
>
>                 Key: JBTM-2337
>                 URL: https://issues.jboss.org/browse/JBTM-2337
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  9 08:54:48 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Mon, 9 Feb 2015 08:54:48 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2339) MongoDB extension for
	Compensations
In-Reply-To: <JIRA.12562725.1423490069000@Atlassian.JIRA>
References: <JIRA.12562725.1423490069000@Atlassian.JIRA>
	<JIRA.12562725.1423490069766@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562725.1423490069000.50364.1423490088983@Atlassian.JIRA>

Gytis Trikleris created JBTM-2339:
-------------------------------------

             Summary: MongoDB extension for Compensations
                 Key: JBTM-2339
                 URL: https://issues.jboss.org/browse/JBTM-2339
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: TXFramework
            Reporter: Gytis Trikleris
            Assignee: Gytis Trikleris
             Fix For: 5.0.5






--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb  9 08:56:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Mon, 9 Feb 2015 08:56:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2340) Implement POC of MongoDB
	extension
In-Reply-To: <JIRA.12562726.1423490153000@Atlassian.JIRA>
References: <JIRA.12562726.1423490153000@Atlassian.JIRA>
	<JIRA.12562726.1423490153985@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562726.1423490153000.50371.1423490209173@Atlassian.JIRA>

Gytis Trikleris created JBTM-2340:
-------------------------------------

             Summary: Implement POC of MongoDB extension
                 Key: JBTM-2340
                 URL: https://issues.jboss.org/browse/JBTM-2340
             Project: JBoss Transaction Manager
          Issue Type: Sub-task
          Components: TXFramework
            Reporter: Gytis Trikleris
            Assignee: Gytis Trikleris
             Fix For: 5.0.5






--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 10 09:55:49 2015
From: issues at jboss.org (SBS JIRA Integration (JIRA))
Date: Tue, 10 Feb 2015 09:55:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.52830.1423580149779@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SBS JIRA Integration updated JBTM-2300:
---------------------------------------
    Forum Reference: https://developer.jboss.org/message/918317#918317


> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Tue Feb 10 10:01:49 2015
From: issues at jboss.org (Amos Feng (JIRA))
Date: Tue, 10 Feb 2015 10:01:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.52836.1423580509728@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039154#comment-13039154 ] 

Amos Feng commented on JBTM-2300:
---------------------------------

It looks like the client lost the connection. I just tried to use <reconnect-attempts> and asked on the HornetQ forum.

> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Tue Feb 10 12:16:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Tue, 10 Feb 2015 12:16:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.53090.1423588609185@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039202#comment-13039202 ] 

Tom Jenkinson commented on JBTM-2300:
-------------------------------------

Its weird, isn't the stomp to HQ communication using the in memory transport - I wonder how it could lose the connection?

> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Tue Feb 10 21:51:49 2015
From: issues at jboss.org (Amos Feng (JIRA))
Date: Tue, 10 Feb 2015 21:51:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.53758.1423623109529@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039279#comment-13039279 ] 

Amos Feng commented on JBTM-2300:
---------------------------------

yeah, it uses the in-vm connection and Justin also thinks that it's not even possible as it has been fixed in HORNEQ-1314 whith HornetQ 2.4.5.Final

> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Tue Feb 10 21:51:49 2015
From: issues at jboss.org (Amos Feng (JIRA))
Date: Tue, 10 Feb 2015 21:51:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.53762.1423623109681@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039279#comment-13039279 ] 

Amos Feng edited comment on JBTM-2300 at 2/10/15 9:51 PM:
----------------------------------------------------------

yeah, it uses the in-vm connection and Justin also thinks that it's not even possible as it has been fixed in HORNETQ-1314 whith HornetQ 2.4.5.Final


was (Author: zhfeng):
yeah, it uses the in-vm connection and Justin also thinks that it's not even possible as it has been fixed in HORNEQ-1314 whith HornetQ 2.4.5.Final

> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Wed Feb 11 04:10:50 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 11 Feb 2015 04:10:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.53968.1423645850926@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039448#comment-13039448 ] 

Tom Jenkinson commented on JBTM-2300:
-------------------------------------

The discussion on HORNETQ-1314 seems to suggest it was reintroduced at some point so have asked on that Jira whether 2.4.5 had the fix in or not

> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Thu Feb 12 04:16:49 2015
From: issues at jboss.org (SBS JIRA Integration (JIRA))
Date: Thu, 12 Feb 2015 04:16:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of
 distributing IOR to users
In-Reply-To: <JIRA.12558007.1416768182000@Atlassian.JIRA>
References: <JIRA.12558007.1416768182000@Atlassian.JIRA>
	<JIRA.12558007.1416768182000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558007.1416768182000.55714.1423732609231@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SBS JIRA Integration updated JBTM-2296:
---------------------------------------
    Forum Reference: https://developer.jboss.org/message/918129#918129


> 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
>             Fix For: 5.0.5
>
>
> 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.11#6341)

From issues at jboss.org  Thu Feb 12 08:40:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Thu, 12 Feb 2015 08:40:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for
 triggering a performance check
In-Reply-To: <JIRA.12562527.1423156948000@Atlassian.JIRA>
References: <JIRA.12562527.1423156948000@Atlassian.JIRA>
	<JIRA.12562527.1423156948000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562527.1423156948000.56167.1423748449500@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2337:
-----------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/narayana/pull/805


> Add a PR profile for triggering a performance check
> ---------------------------------------------------
>
>                 Key: JBTM-2337
>                 URL: https://issues.jboss.org/browse/JBTM-2337
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb 12 08:40:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Thu, 12 Feb 2015 08:40:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for
 triggering a performance check
In-Reply-To: <JIRA.12562527.1423156948000@Atlassian.JIRA>
References: <JIRA.12562527.1423156948000@Atlassian.JIRA>
	<JIRA.12562527.1423156948000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12562527.1423156948000.56169.1423748449552@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2337:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Add a PR profile for triggering a performance check
> ---------------------------------------------------
>
>                 Key: JBTM-2337
>                 URL: https://issues.jboss.org/browse/JBTM-2337
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Testing
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 13 12:49:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 13 Feb 2015 12:49:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738927@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.59420.1423849789588@Atlassian.JIRA>

Michael Musgrove created JBTM-2341:
--------------------------------------

             Summary: Add two more statistics
                 Key: JBTM-2341
                 URL: https://issues.jboss.org/browse/JBTM-2341
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: Transaction Core
    Affects Versions: 5.0.4
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.0.5


Add the following two statistics:

System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 17 06:51:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Tue, 17 Feb 2015 06:51:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.63157.1424173909005@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2341:
--------------------------------
    Forum Reference: https://developer.jboss.org/message/918972#918972


> Add two more statistics
> -----------------------
>
>                 Key: JBTM-2341
>                 URL: https://issues.jboss.org/browse/JBTM-2341
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Transaction Core
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add the following two statistics:
> System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
> Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 17 08:38:49 2015
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 17 Feb 2015 08:38:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management
 interface to see a list of Xids that are being being considered for
 recovery by the recovery manager
In-Reply-To: <JIRA.12560543.1420737406000@Atlassian.JIRA>
References: <JIRA.12560543.1420737406000@Atlassian.JIRA>
	<JIRA.12560543.1420737406000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12560543.1420737406000.63458.1424180329597@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040865#comment-13040865 ] 

RH Bugzilla Integration commented on JBTM-2326:
-----------------------------------------------

Pavel Jelinek <pjelinek at redhat.com> changed the Status of [bug 1178798|https://bugzilla.redhat.com/show_bug.cgi?id=1178798] from ON_QA to VERIFIED

> Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2326
>                 URL: https://issues.jboss.org/browse/JBTM-2326
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: JTA, Tooling
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>
> Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state:
> https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 17 12:02:48 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Tue, 17 Feb 2015 12:02:48 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.64245.1424192568972@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2341:
-----------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/narayana/pull/806


> Add two more statistics
> -----------------------
>
>                 Key: JBTM-2341
>                 URL: https://issues.jboss.org/browse/JBTM-2341
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Transaction Core
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add the following two statistics:
> System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
> Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb 18 09:18:48 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Wed, 18 Feb 2015 09:18:48 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.66650.1424269128981@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2341:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Add two more statistics
> -----------------------
>
>                 Key: JBTM-2341
>                 URL: https://issues.jboss.org/browse/JBTM-2341
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Transaction Core
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add the following two statistics:
> System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
> Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb 18 12:04:50 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 18 Feb 2015 12:04:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.67520.1424279090689@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reopened JBTM-2341:
---------------------------------


Hi Mike, as per Marks comment on the forum I don't think https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/TxStatsMBean.java#L60 is clear the method is calculating the timing of the commit() call not the time from begin -> commit().

> Add two more statistics
> -----------------------
>
>                 Key: JBTM-2341
>                 URL: https://issues.jboss.org/browse/JBTM-2341
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Transaction Core
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add the following two statistics:
> System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
> Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 20 05:30:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 20 Feb 2015 05:30:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests
	failed
In-Reply-To: <JIRA.12558035.1416828099000@Atlassian.JIRA>
References: <JIRA.12558035.1416828099000@Atlassian.JIRA>
	<JIRA.12558035.1416828099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558035.1416828099000.73702.1424428249441@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042294#comment-13042294 ] 

Tom Jenkinson commented on JBTM-2300:
-------------------------------------

http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/753/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el7/consoleFull

HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

> 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.5
>
>
> 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.11#6341)

From issues at jboss.org  Fri Feb 20 07:53:50 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 20 Feb 2015 07:53:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2342) Add callbacks for
 thread-to-transaction association changes
In-Reply-To: <JIRA.12563793.1424436792000@Atlassian.JIRA>
References: <JIRA.12563793.1424436792000@Atlassian.JIRA>
	<JIRA.12563793.1424436792324@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563793.1424436792000.74022.1424436830636@Atlassian.JIRA>

Michael Musgrove created JBTM-2342:
--------------------------------------

             Summary: Add callbacks for thread-to-transaction association changes
                 Key: JBTM-2342
                 URL: https://issues.jboss.org/browse/JBTM-2342
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: Application Server Integration
    Affects Versions: 5.0.4
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.0.5


This feature calls for a mechanism to avoid issues around concurrent access to a JPA EM if a transaction times out. Currently EM cleanup happens in AC callbacks - if those callbacks happen on the application thread there is no issue but if they happen on the reaper thread then it is possible for the EM to be manipulated whilst the application is still using it.

The linked forum thread came up with 4 proposals to handle the problem:
# Reaper marks transaction as set rollback only: this solution has potentially insurmountable issues (eg JVM1 -> JVM2, JVM1 crashes, txn never gets commit/rollback called on it). In addition it would need to be configurable - some users want the reaper to do the timely rollback;
# WildFly wraps the TM/TSR and coordinates the running of all Synchronization callbacks. This solution is complex and does the AS have sufficient knowledge to coordinate callbacks correctly. Option 4 below is similar but the decision about what to do and when to do it is left in the hands of the relevant callbacks where the knowlege resides;
# Start a discussion on the JPA expert group to get certain thread unsafe Synchronization JPA callbacks used by EE container/Persistence providers changed. This is an option for the future;
# Trigger callbacks when the transaction is disassociated from a thread. For example, detaching any loaded entities and closing the EM can be done when all relevant callbacks, namely the afterCompletion callback (triggered on the reaper thread) and the txn disassociated callback (triggered on the application thread) have been seen.

This JIRA will implement option 4.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 20 07:58:48 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Fri, 20 Feb 2015 07:58:48 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) New interface for
 tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100300@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.74038.1424437128993@Atlassian.JIRA>

Michael Musgrove created JBTM-2343:
--------------------------------------

             Summary: New interface for tracking thread-to-transaction association changes
                 Key: JBTM-2343
                 URL: https://issues.jboss.org/browse/JBTM-2343
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: SPI
    Affects Versions: 5.0.4
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.0.5


We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb 23 05:21:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Mon, 23 Feb 2015 05:21:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.76285.1424686909211@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-2341:
-----------------------------------
    Git Pull Request: https://github.com/jbosstm/narayana/pull/808, https://github.com/jbosstm/documentation/pull/29  (was: https://github.com/jbosstm/narayana/pull/806)


> Add two more statistics
> -----------------------
>
>                 Key: JBTM-2341
>                 URL: https://issues.jboss.org/browse/JBTM-2341
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Transaction Core
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add the following two statistics:
> System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
> Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Mon Feb 23 07:51:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Mon, 23 Feb 2015 07:51:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics
In-Reply-To: <JIRA.12563185.1423849738000@Atlassian.JIRA>
References: <JIRA.12563185.1423849738000@Atlassian.JIRA>
	<JIRA.12563185.1423849738000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563185.1423849738000.76582.1424695909647@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove resolved JBTM-2341.
------------------------------------
    Resolution: Done


javadoc and doc repo for the stat have been updated.

> Add two more statistics
> -----------------------
>
>                 Key: JBTM-2341
>                 URL: https://issues.jboss.org/browse/JBTM-2341
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Transaction Core
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> Add the following two statistics:
> System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log);
> Average Commit Time.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 24 07:00:52 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Tue, 24 Feb 2015 07:00:52 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) New interface for
 tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.79239.1424779252259@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043120#comment-13043120 ] 

Mark Little commented on JBTM-2343:
-----------------------------------

How is this different to the current class that allows thread-to-transaction association and disassociation?

> New interface for tracking thread-to-transaction association changes
> --------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 24 09:23:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Tue, 24 Feb 2015 09:23:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) New interface for
 tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.80177.1424787829096@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043182#comment-13043182 ] 

Michael Musgrove commented on JBTM-2343:
----------------------------------------

This is an interface that clients (such as JPA and IJ) implement and register with us (via javax.transaction.transaction#registerSynchronization(Synchronization sync). We call them back when the  thread-to-transaction association changes. So it is different. I have updated the forum thread so that we can track the API discussion.

Perhaps I should have not have raised a separate JIRA for it (and subsumed it into JBTM-2342). The reason I chose a separate JIRA is because I though the interface belongs to the SPI (https://github.com/jbosstm/jboss-transaction-spi) whereas JBTM-2342 is for the implementation of the feature.


> New interface for tracking thread-to-transaction association changes
> --------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.0.5
>
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 24 09:26:50 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Tue, 24 Feb 2015 09:26:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) New interface for
 tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.80194.1424788010102@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2343:
--------------------------------
    Fix Version/s:     (was: 5.0.5)


> New interface for tracking thread-to-transaction association changes
> --------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 24 09:28:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Tue, 24 Feb 2015 09:28:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) New interface for
 tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.80199.1424788129399@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043183#comment-13043183 ] 

Tom Jenkinson commented on JBTM-2343:
-------------------------------------

Rather than delete this Jira only to re-add it as a result of our discussions on the forum I have removed the fix version temporarily until we all agree that this is the approach we are taking. I will tweak the subject as well.

> New interface for tracking thread-to-transaction association changes
> --------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 24 09:28:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Tue, 24 Feb 2015 09:28:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) Consider adding a new
 Observer pattern for tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.80203.1424788129512@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2343:
--------------------------------
    Summary: Consider adding a new Observer pattern for tracking thread-to-transaction association changes  (was: New interface for tracking thread-to-transaction association changes)


> Consider adding a new Observer pattern for tracking thread-to-transaction association changes
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Tue Feb 24 09:29:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Tue, 24 Feb 2015 09:29:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) Consider adding a new
 Observer SPI for tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.80207.1424788189627@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2343:
--------------------------------
    Summary: Consider adding a new Observer SPI for tracking thread-to-transaction association changes  (was: Consider adding a new Observer pattern for tracking thread-to-transaction association changes)


> Consider adding a new Observer SPI for tracking thread-to-transaction association changes
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb 25 04:17:49 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Wed, 25 Feb 2015 04:17:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) Consider adding a new
 Observer SPI for tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.82647.1424855869408@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043460#comment-13043460 ] 

Mark Little commented on JBTM-2343:
-----------------------------------

I get that it's a different API (SPI) but I think we should try to use the same class for tracking thread-to-transaction association within that implementation somewhere. I'll add this to the forum thread though.

> Consider adding a new Observer SPI for tracking thread-to-transaction association changes
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Wed Feb 25 06:00:54 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Wed, 25 Feb 2015 06:00:54 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) Consider adding a new
 Observer SPI for tracking thread-to-transaction association changes
In-Reply-To: <JIRA.12563795.1424437100000@Atlassian.JIRA>
References: <JIRA.12563795.1424437100000@Atlassian.JIRA>
	<JIRA.12563795.1424437100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12563795.1424437100000.82866.1424862054218@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Little updated JBTM-2343:
------------------------------
    Forum Reference: https://developer.jboss.org/thread/243360, https://developer.jboss.org/message/919921  (was: https://developer.jboss.org/thread/243360)


> Consider adding a new Observer SPI for tracking thread-to-transaction association changes
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-2343
>                 URL: https://issues.jboss.org/browse/JBTM-2343
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: SPI
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>
> We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb 26 06:02:49 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Thu, 26 Feb 2015 06:02:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528624@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.85499.1424948569101@Atlassian.JIRA>

Mark Little created JBTM-2344:
---------------------------------

             Summary: Add Docker (or Container) component to JIRA?
                 Key: JBTM-2344
                 URL: https://issues.jboss.org/browse/JBTM-2344
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: Build System
    Affects Versions: 5.0.4
            Reporter: Mark Little
            Assignee: Tom Jenkinson
            Priority: Minor


Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb 26 06:04:49 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Thu, 26 Feb 2015 06:04:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for
 docker transaction service
In-Reply-To: <JIRA.12564317.1424948688000@Atlassian.JIRA>
References: <JIRA.12564317.1424948688000@Atlassian.JIRA>
	<JIRA.12564317.1424948688180@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564317.1424948688000.85508.1424948689306@Atlassian.JIRA>

Mark Little created JBTM-2345:
---------------------------------

             Summary: Off image storage for docker transaction service
                 Key: JBTM-2345
                 URL: https://issues.jboss.org/browse/JBTM-2345
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: Build System, JTS
    Affects Versions: 5.0.4
            Reporter: Mark Little
            Assignee: Tom Jenkinson


Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb 26 06:45:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Thu, 26 Feb 2015 06:45:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by
 coordinator in CloseTest
In-Reply-To: <JIRA.12543933.1402908381000@Atlassian.JIRA>
References: <JIRA.12543933.1402908381000@Atlassian.JIRA>
	<JIRA.12543933.1402908381000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12543933.1402908381000.85596.1424951149464@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043880#comment-13043880 ] 

Gytis Trikleris commented on JBTM-2194:
---------------------------------------

http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/757/PROFILE=XTS,jdk=jdk7.latest,label=linux/

> Activity cancelled by coordinator in CloseTest
> ----------------------------------------------
>
>                 Key: JBTM-2194
>                 URL: https://issues.jboss.org/browse/JBTM-2194
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: XTS
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>             Fix For: 5.0.5
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: com.arjuna.wstx.tests.arq.ba.CloseTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE!
> testClose(com.arjuna.wstx.tests.arq.ba.CloseTest)  Time elapsed: 2.375 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.CloseTest.testClose(CloseTest.java:64)
> {code}
> {code}
> 18:45:37,613 INFO  [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content
> 18:45:37,616 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
> 18:45:37,860 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> 18:45:37,927 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war
> 18:45:37,941 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war
> 18:45:37,946 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war
> 18:45:38,228 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test
> 18:45:38,406 INFO  [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
> 18:45:38,418 INFO  [stdout] (Thread-0) TransformListener() : handling connection on port 9091
> 18:45:38,492 INFO  [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:38,492 INFO  [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:38,493 INFO  [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,495 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:38,496 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter
> 18:45:38,497 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:38,514 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:38,517 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called
> 18:45:38,536 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:38,552 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,554 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called
> 18:45:38,556 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,558 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:38,559 INFO  [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called
> 18:45:38,560 INFO  [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:39,123 INFO  [stdout] (default task-16) Rule.execute called for create counter_3
> 18:45:39,124 INFO  [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:39,124 INFO  [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:39,124 INFO  [stdout] (default task-16) Default helper activated
> 18:45:39,124 INFO  [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:39,125 INFO  [stdout] (default task-16) Installed rule using default helper : create counter
> 18:45:39,135 INFO  [stdout] (default task-16) create counter execute
> 18:45:39,135 INFO  [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1
> 18:45:39,158 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl
> 18:45:39,205 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl
> 18:45:39,282 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl
> 18:45:40,131 WARN  [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235
> 18:45:40,188 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl
> 18:45:41,372 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl
> 18:45:42,052 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl
> 18:45:42,090 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl
> 18:45:42,409 INFO  [stdout] (default-workqueue-2) Rule.execute called for close called_6
> 18:45:42,410 INFO  [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,411 INFO  [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:42,411 INFO  [stdout] (default-workqueue-2) Installed rule using default helper : close called
> 18:45:42,411 INFO  [stdout] (default-workqueue-2) close called execute
> 18:45:42,412 INFO  [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting
> 18:45:42,412 INFO  [stdout] (TaskWorker-2) Rule.execute called for complete called_4
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) Installed rule using default helper : complete called
> 18:45:42,413 INFO  [stdout] (TaskWorker-2) complete called execute
> 18:45:42,414 INFO  [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement
> 18:45:42,414 INFO  [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking
> 18:45:42,414 INFO  [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken
> 18:45:42,415 INFO  [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake
> 18:45:42,415 WARN  [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity
> 18:45:42,428 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl
> 18:45:42,439 INFO  [stdout] (TaskWorker-1) Rule.execute called for complete called_4
> 18:45:42,441 INFO  [stdout] (TaskWorker-1) complete called execute
> 18:45:42,496 INFO  [stdout] (Thread-0) TransformListener() : handling connection on port 9091
> 18:45:42,598 INFO  [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules
> 18:45:42,599 INFO  [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
> 18:45:42,599 INFO  [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl
> 18:45:42,815 INFO  [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,816 INFO  [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,816 INFO  [stdout] (Thread-0) Uninstalled rule using default helper : create counter
> 18:45:42,817 INFO  [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,817 INFO  [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,818 INFO  [stdout] (Thread-0) Uninstalled rule using default helper : complete called
> 18:45:42,818 INFO  [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,819 INFO  [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper
> 18:45:42,819 INFO  [stdout] (Thread-0) Uninstalled rule using default helper : close called
> 18:45:42,819 INFO  [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper
> 18:45:42,820 INFO  [stdout] (Thread-0) Default helper deactivated
> 18:45:42,830 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test
> 18:45:42,845 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war
> 18:45:42,855 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms
> 18:45:42,942 INFO  [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content
> 18:45:42,942 INFO  [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war")
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


From issues at jboss.org  Thu Feb 26 06:51:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Thu, 26 Feb 2015 06:51:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2346) CMRIntegrationTest
 deployment failed because of Weld
In-Reply-To: <JIRA.12564323.1424951451000@Atlassian.JIRA>
References: <JIRA.12564323.1424951451000@Atlassian.JIRA>
	<JIRA.12564323.1424951451581@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564323.1424951451000.85607.1424951509363@Atlassian.JIRA>

Gytis Trikleris created JBTM-2346:
-------------------------------------

             Summary: CMRIntegrationTest deployment failed because of Weld
                 Key: JBTM-2346
                 URL: https://issues.jboss.org/browse/JBTM-2346
             Project: JBoss Transaction Manager
          Issue Type: Bug
          Components: JTA
            Reporter: Gytis Trikleris
            Assignee: Tom Jenkinson
             Fix For: 5.0.5


http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/758/PROFILE=MAIN,jdk=jdk7.latest,label=linux/

{code}
-------------------------------------------------------------------------------
Test set: com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.077 sec <<< FAILURE!
com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest  Time elapsed: 16.075 sec  <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:146)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
	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:94)
	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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
	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:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
	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:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
	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:94)
	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.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
	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:94)
	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.client.ContainerEventController.execute(ContainerEventController.java:101)
	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:94)
	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.createClassContext(TestContextHandler.java:84)
	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:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
	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:94)
	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.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
	at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
	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:309)
	at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
	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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
{code}

{code}
Feb 24, 2015 6:54:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
WARNING: Bundles path is deprecated and no longer used.
Feb 24, 2015 6:54:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -XX:MaxPermSize=512m, -Djava.net.preferIPv4Stack=true, -server, -Xmx1024m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/configuration, -c=standalone-cmr.xml]
Listening for transport dt_socket at address: 8787
18:54:40,441 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final
18:54:41,291 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
18:54:41,487 WARN  [org.jboss.as.warn.fd-limit] (main) WFLYSRV0071: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended
18:54:41,567 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting
18:54:44,597 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
18:54:44,837 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
18:54:44,867 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.0.Final
18:54:44,886 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.0.Final
18:54:44,928 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.7.Final
18:54:45,053 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) WFLYCLINF0001: Activating Infinispan subsystem.
18:54:45,135 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 45) WFLYNAM0001: Activating Naming Subsystem
18:54:45,130 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 43) WFLYJSF0007: Activated the following JSF Implementations: [main]
18:54:45,226 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 51) WFLYSEC0002: Activating Security Subsystem
18:54:45,281 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
18:54:45,296 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 32) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
18:54:45,214 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 52) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
18:54:45,957 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 36) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
18:54:46,288 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) WFLYWS0002: Activating WebServices Extension
18:54:46,312 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.2.Final)
18:54:46,577 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2
18:54:46,600 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
18:54:46,610 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
18:54:48,054 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
18:54:48,063 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.2.0.Beta8 starting
18:54:48,065 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0003: Undertow 1.2.0.Beta8 starting
18:54:48,112 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
18:54:48,170 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
18:54:48,172 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0014: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/welcome-content
18:54:48,183 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
18:54:48,733 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Beta3
18:54:49,074 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/deployments
18:54:49,766 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
18:54:49,766 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
18:54:49,767 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) started in 10128ms - Started 203 of 380 services (210 services are lazy, passive or on-demand)
18:54:50,870 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/be/d1c9cd47a4d9b1119731defb4991fec5b863c8/content
18:54:50,895 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
18:54:51,851 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
18:54:51,852 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jboss-transaction-spi:main") which may be changed or removed in future versions without notice.
18:54:51,905 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment test.war
18:54:51,995 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.1.3.Final
18:54:52,703 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: test.war
18:54:52,748 INFO  [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.9 (Final)
18:54:52,868 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war
18:54:54,097 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."test.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".WeldStartService: Failed to start service
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.4.Final.jar:1.2.4.Final]
	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.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
javax.enterprise.event.ObserverException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at java.lang.Class.newInstance(Class.java:374)
	at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40)
	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78)
	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97)
	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79)
	at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299)
	at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284)
	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262)
	at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217)
	at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204)
	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120)
	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	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)
Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/sql/PooledConnection"
	at java.lang.Class.getDeclaredMethods0(Native Method)
	at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
	at java.lang.Class.privateGetPublicMethods(Class.java:2651)
	at java.lang.Class.privateGetPublicMethods(Class.java:2661)
	at java.lang.Class.getMethods(Class.java:1467)
	at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39)
	at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63)
	at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85)
	at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169)
	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.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89)
	... 26 more

	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.4.Final.jar:1.2.4.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.4.Final.jar:1.2.4.Final]
	... 3 more

18:54:54,181 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".WeldStartService: Failed to start service
    Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
javax.enterprise.event.ObserverException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at java.lang.Class.newInstance(Class.java:374)
	at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40)
	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78)
	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97)
	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79)
	at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299)
	at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284)
	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262)
	at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217)
	at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204)
	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120)
	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	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)
Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name \"javax/sql/PooledConnection\"
	at java.lang.Class.getDeclaredMethods0(Native Method)
	at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
	at java.lang.Class.privateGetPublicMethods(Class.java:2651)
	at java.lang.Class.privateGetPublicMethods(Class.java:2661)
	at java.lang.Class.getMethods(Class.java:1467)
	at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39)
	at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63)
	at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85)
	at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169)
	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.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89)
	... 26 more
"}}
18:54:54,191 ERROR [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message: 
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".WeldStartService: Failed to start service
    Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
javax.enterprise.event.ObserverException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at java.lang.Class.newInstance(Class.java:374)
	at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40)
	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78)
	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97)
	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79)
	at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299)
	at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284)
	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262)
	at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217)
	at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204)
	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120)
	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	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)
Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name \"javax/sql/PooledConnection\"
	at java.lang.Class.getDeclaredMethods0(Native Method)
	at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
	at java.lang.Class.privateGetPublicMethods(Class.java:2651)
	at java.lang.Class.privateGetPublicMethods(Class.java:2661)
	at java.lang.Class.getMethods(Class.java:1467)
	at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39)
	at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63)
	at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85)
	at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169)
	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.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89)
	... 26 more
"}}
18:54:54,221 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war
18:54:54,294 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 91ms
18:54:54,298 INFO  [org.jboss.as.controller] (management-handler-thread - 4) WFLYCTL0183: Service status report
WFLYCTL0184:    New missing/unsatisfied dependencies:
      service jboss.deployment.unit."test.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, WFLYCTL0208: ... and 7 more ] 
      service jboss.deployment.unit."test.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, WFLYCTL0208: ... and 6 more ] 
      service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START] 
      service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START] 
      service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START] 
      service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START] 
      service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] 
      service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] 
      service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] 
      service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] 
      service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START] 
      service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START] 
      service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START] 
      service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START] 
      service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] 
      service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] 
      service jboss.deployment.unit."test.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
      service jboss.deployment.unit."test.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START, service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START, WFLYCTL0208: ... and 4 more ] 
      service jboss.server.global-request-controller.control-point."test.war".undertow (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
      service jboss.undertow.deployment.default-server.default-host./test (missing) dependents: [service jboss.deployment.unit."test.war".deploymentCompleteService] 
      service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test] 
      service jboss.undertow.deployment.default-server.default-host./test.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
      service jboss.undertow.deployment.default-server.default-host./test.session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
WFLYCTL0186:   Services which failed to start:      service jboss.deployment.unit."test.war".WeldStartService

18:54:54,377 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0211: Suspending server
18:54:54,390 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
18:54:54,398 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
18:54:54,406 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: Host default-host stopping
18:54:54,480 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
18:54:54,501 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending
18:54:54,501 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
18:54:54,797 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.2.0.Beta8 stopping
18:54:54,865 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) stopped in 423ms

{code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


From issues at jboss.org  Thu Feb 26 06:51:49 2015
From: issues at jboss.org (Gytis Trikleris (JIRA))
Date: Thu, 26 Feb 2015 06:51:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2346) CMRIntegrationTest
 deployment failed because of Weld
In-Reply-To: <JIRA.12564323.1424951451000@Atlassian.JIRA>
References: <JIRA.12564323.1424951451000@Atlassian.JIRA>
	<JIRA.12564323.1424951451000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564323.1424951451000.85609.1424951509511@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043883#comment-13043883 ] 

Gytis Trikleris commented on JBTM-2346:
---------------------------------------

http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/759/PROFILE=MAIN,jdk=jdk7.latest,label=linux/

> CMRIntegrationTest deployment failed because of Weld
> ----------------------------------------------------
>
>                 Key: JBTM-2346
>                 URL: https://issues.jboss.org/browse/JBTM-2346
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>            Reporter: Gytis Trikleris
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.5
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/758/PROFILE=MAIN,jdk=jdk7.latest,label=linux/
> {code}
> -------------------------------------------------------------------------------
> Test set: com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.077 sec <<< FAILURE!
> com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest  Time elapsed: 16.075 sec  <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war
> 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> 	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
> 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
> 	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
> 	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:146)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> 	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:94)
> 	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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
> 	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:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
> 	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:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> 	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:94)
> 	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.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
> 	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:94)
> 	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.client.ContainerEventController.execute(ContainerEventController.java:101)
> 	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:94)
> 	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.createClassContext(TestContextHandler.java:84)
> 	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:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
> 	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:94)
> 	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.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> 	at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> 	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:309)
> 	at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> 	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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> 	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159)
> 	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
> {code}
> {code}
> Feb 24, 2015 6:54:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> WARNING: Bundles path is deprecated and no longer used.
> Feb 24, 2015 6:54:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -XX:MaxPermSize=512m, -Djava.net.preferIPv4Stack=true, -server, -Xmx1024m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/configuration, -c=standalone-cmr.xml]
> Listening for transport dt_socket at address: 8787
> 18:54:40,441 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final
> 18:54:41,291 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
> 18:54:41,487 WARN  [org.jboss.as.warn.fd-limit] (main) WFLYSRV0071: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended
> 18:54:41,567 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting
> 18:54:44,597 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
> 18:54:44,837 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 18:54:44,867 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.0.Final
> 18:54:44,886 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.0.Final
> 18:54:44,928 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.7.Final
> 18:54:45,053 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) WFLYCLINF0001: Activating Infinispan subsystem.
> 18:54:45,135 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 45) WFLYNAM0001: Activating Naming Subsystem
> 18:54:45,130 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 43) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 18:54:45,226 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 51) WFLYSEC0002: Activating Security Subsystem
> 18:54:45,281 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
> 18:54:45,296 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 32) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 18:54:45,214 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 52) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> 18:54:45,957 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 36) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
> 18:54:46,288 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) WFLYWS0002: Activating WebServices Extension
> 18:54:46,312 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.2.Final)
> 18:54:46,577 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2
> 18:54:46,600 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
> 18:54:46,610 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 18:54:48,054 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 18:54:48,063 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.2.0.Beta8 starting
> 18:54:48,065 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0003: Undertow 1.2.0.Beta8 starting
> 18:54:48,112 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
> 18:54:48,170 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
> 18:54:48,172 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0014: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/welcome-content
> 18:54:48,183 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
> 18:54:48,733 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Beta3
> 18:54:49,074 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/deployments
> 18:54:49,766 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 18:54:49,766 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 18:54:49,767 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) started in 10128ms - Started 203 of 380 services (210 services are lazy, passive or on-demand)
> 18:54:50,870 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/be/d1c9cd47a4d9b1119731defb4991fec5b863c8/content
> 18:54:50,895 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
> 18:54:51,851 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> 18:54:51,852 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jboss-transaction-spi:main") which may be changed or removed in future versions without notice.
> 18:54:51,905 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment test.war
> 18:54:51,995 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.1.3.Final
> 18:54:52,703 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: test.war
> 18:54:52,748 INFO  [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.9 (Final)
> 18:54:52,868 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war
> 18:54:54,097 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."test.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".WeldStartService: Failed to start service
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.4.Final.jar:1.2.4.Final]
> 	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.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> javax.enterprise.event.ObserverException
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at java.lang.Class.newInstance(Class.java:374)
> 	at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40)
> 	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78)
> 	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97)
> 	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79)
> 	at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89)
> 	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299)
> 	at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
> 	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284)
> 	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262)
> 	at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217)
> 	at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204)
> 	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120)
> 	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
> 	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
> 	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
> 	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
> 	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
> 	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
> 	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
> 	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
> 	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> 	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)
> Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/sql/PooledConnection"
> 	at java.lang.Class.getDeclaredMethods0(Native Method)
> 	at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
> 	at java.lang.Class.privateGetPublicMethods(Class.java:2651)
> 	at java.lang.Class.privateGetPublicMethods(Class.java:2661)
> 	at java.lang.Class.getMethods(Class.java:1467)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85)
> 	at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169)
> 	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.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89)
> 	... 26 more
> 	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> 	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
> 	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
> 	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
> 	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
> 	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
> 	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.4.Final.jar:1.2.4.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.4.Final.jar:1.2.4.Final]
> 	... 3 more
> 18:54:54,181 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".WeldStartService: Failed to start service
>     Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> javax.enterprise.event.ObserverException
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at java.lang.Class.newInstance(Class.java:374)
> 	at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40)
> 	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78)
> 	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97)
> 	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79)
> 	at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89)
> 	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299)
> 	at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
> 	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284)
> 	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262)
> 	at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217)
> 	at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204)
> 	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120)
> 	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
> 	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
> 	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
> 	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
> 	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
> 	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
> 	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
> 	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
> 	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> 	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)
> Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name \"javax/sql/PooledConnection\"
> 	at java.lang.Class.getDeclaredMethods0(Native Method)
> 	at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
> 	at java.lang.Class.privateGetPublicMethods(Class.java:2651)
> 	at java.lang.Class.privateGetPublicMethods(Class.java:2661)
> 	at java.lang.Class.getMethods(Class.java:1467)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85)
> 	at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169)
> 	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.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89)
> 	... 26 more
> "}}
> 18:54:54,191 ERROR [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message: 
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".WeldStartService: Failed to start service
>     Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> javax.enterprise.event.ObserverException
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at java.lang.Class.newInstance(Class.java:374)
> 	at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40)
> 	at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78)
> 	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97)
> 	at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79)
> 	at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89)
> 	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299)
> 	at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
> 	at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284)
> 	at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262)
> 	at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217)
> 	at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204)
> 	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120)
> 	at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
> 	at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
> 	at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
> 	at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33)
> 	at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138)
> 	at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128)
> 	at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322)
> 	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273)
> 	at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406)
> 	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> 	at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> 	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)
> Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name \"javax/sql/PooledConnection\"
> 	at java.lang.Class.getDeclaredMethods0(Native Method)
> 	at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
> 	at java.lang.Class.privateGetPublicMethods(Class.java:2651)
> 	at java.lang.Class.privateGetPublicMethods(Class.java:2661)
> 	at java.lang.Class.getMethods(Class.java:1467)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63)
> 	at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85)
> 	at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169)
> 	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.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89)
> 	... 26 more
> "}}
> 18:54:54,221 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war
> 18:54:54,294 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 91ms
> 18:54:54,298 INFO  [org.jboss.as.controller] (management-handler-thread - 4) WFLYCTL0183: Service status report
> WFLYCTL0184:    New missing/unsatisfied dependencies:
>       service jboss.deployment.unit."test.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, WFLYCTL0208: ... and 7 more ] 
>       service jboss.deployment.unit."test.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, WFLYCTL0208: ... and 6 more ] 
>       service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START] 
>       service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START] 
>       service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START] 
>       service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START] 
>       service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] 
>       service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] 
>       service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] 
>       service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] 
>       service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START] 
>       service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START] 
>       service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START] 
>       service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START] 
>       service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] 
>       service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] 
>       service jboss.deployment.unit."test.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
>       service jboss.deployment.unit."test.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START, service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START, WFLYCTL0208: ... and 4 more ] 
>       service jboss.server.global-request-controller.control-point."test.war".undertow (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
>       service jboss.undertow.deployment.default-server.default-host./test (missing) dependents: [service jboss.deployment.unit."test.war".deploymentCompleteService] 
>       service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test] 
>       service jboss.undertow.deployment.default-server.default-host./test.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
>       service jboss.undertow.deployment.default-server.default-host./test.session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] 
> WFLYCTL0186:   Services which failed to start:      service jboss.deployment.unit."test.war".WeldStartService
> 18:54:54,377 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0211: Suspending server
> 18:54:54,390 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
> 18:54:54,398 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 18:54:54,406 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: Host default-host stopping
> 18:54:54,480 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 18:54:54,501 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending
> 18:54:54,501 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
> 18:54:54,797 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.2.0.Beta8 stopping
> 18:54:54,865 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) stopped in 423ms
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


From issues at jboss.org  Thu Feb 26 06:57:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Thu, 26 Feb 2015 06:57:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for
 docker transaction service
In-Reply-To: <JIRA.12564317.1424948688000@Atlassian.JIRA>
References: <JIRA.12564317.1424948688000@Atlassian.JIRA>
	<JIRA.12564317.1424948688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564317.1424948688000.85619.1424951868999@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043886#comment-13043886 ] 

Tom Jenkinson commented on JBTM-2345:
-------------------------------------

Gytis is looking into this. One option we are considering is the JDBC object store.

> Off image storage for docker transaction service
> ------------------------------------------------
>
>                 Key: JBTM-2345
>                 URL: https://issues.jboss.org/browse/JBTM-2345
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>              Labels: docker
>
> Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb 26 07:23:49 2015
From: issues at jboss.org (Michael Musgrove (JIRA))
Date: Thu, 26 Feb 2015 07:23:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for
 docker transaction service
In-Reply-To: <JIRA.12564317.1424948688000@Atlassian.JIRA>
References: <JIRA.12564317.1424948688000@Atlassian.JIRA>
	<JIRA.12564317.1424948688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564317.1424948688000.85643.1424953429391@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043890#comment-13043890 ] 

Michael Musgrove commented on JBTM-2345:
----------------------------------------

Would we need a variant of WFLY-1119 (Assign an unique NodeID automatically) to avoid conflicts (ie would different images share the same JDBC store).

Also it is possible to point the tooling (ObjStoreBrowser) at a filesystem to manage the logs although it is unsupported (normally it is done via a JMX browser connected to the TM process). Do we need similar functionality for accessing the JDBC store directly?

> Off image storage for docker transaction service
> ------------------------------------------------
>
>                 Key: JBTM-2345
>                 URL: https://issues.jboss.org/browse/JBTM-2345
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>              Labels: docker
>
> Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Thu Feb 26 07:32:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Thu, 26 Feb 2015 07:32:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.85655.1424953969007@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043893#comment-13043893 ] 

Tom Jenkinson commented on JBTM-2344:
-------------------------------------

Happy to go with either, I wonder if Container could be confused with JEE container though. Maybe Cloud? I had a quick look at other projects and Forge has Docker and LiveOak seemed to use Cloud.

I am happy with Docker though even with the potential overloading.

> Add Docker (or Container) component to JIRA?
> --------------------------------------------
>
>                 Key: JBTM-2344
>                 URL: https://issues.jboss.org/browse/JBTM-2344
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 07:41:49 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Fri, 27 Feb 2015 07:41:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.89952.1425040909168@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044634#comment-13044634 ] 

Mark Little commented on JBTM-2344:
-----------------------------------

Yes you're right: container is too confusing. I think Cloud could be too generic but perhaps that's ok.

> Add Docker (or Container) component to JIRA?
> --------------------------------------------
>
>                 Key: JBTM-2344
>                 URL: https://issues.jboss.org/browse/JBTM-2344
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 07:42:49 2015
From: issues at jboss.org (Mark Little (JIRA))
Date: Fri, 27 Feb 2015 07:42:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for
 docker transaction service
In-Reply-To: <JIRA.12564317.1424948688000@Atlassian.JIRA>
References: <JIRA.12564317.1424948688000@Atlassian.JIRA>
	<JIRA.12564317.1424948688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564317.1424948688000.89956.1425040969022@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044635#comment-13044635 ] 

Mark Little commented on JBTM-2345:
-----------------------------------

Whatever we use, let's make sure it's not based on a Docker image ;)

> Off image storage for docker transaction service
> ------------------------------------------------
>
>                 Key: JBTM-2345
>                 URL: https://issues.jboss.org/browse/JBTM-2345
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>              Labels: docker
>
> Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:04:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:04:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for
 docker transaction service
In-Reply-To: <JIRA.12564317.1424948688000@Atlassian.JIRA>
References: <JIRA.12564317.1424948688000@Atlassian.JIRA>
	<JIRA.12564317.1424948688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564317.1424948688000.90003.1425042289032@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044643#comment-13044643 ] 

Tom Jenkinson commented on JBTM-2345:
-------------------------------------

Another option that we are considering (I think Gytis intends it to be the default in the example) is to use drive mapping to leave the object store on the host. He will also document how to map an /etc with a jbossts-properties.xml (probably with the JDBC object configured).

> Off image storage for docker transaction service
> ------------------------------------------------
>
>                 Key: JBTM-2345
>                 URL: https://issues.jboss.org/browse/JBTM-2345
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>              Labels: docker
>
> Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:06:50 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:06:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.90016.1425042410085@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044648#comment-13044648 ] 

Tom Jenkinson commented on JBTM-2344:
-------------------------------------

I will go with Cloud then. If anyone lands here from a search, the outcome is that a Cloud component for the Jira project will be created.

> Add Docker (or Container) component to JIRA?
> --------------------------------------------
>
>                 Key: JBTM-2344
>                 URL: https://issues.jboss.org/browse/JBTM-2344
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:06:50 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:06:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.90019.1425042410177@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2344:
--------------------------------
    Component/s: Cloud


> Add Docker (or Container) component to JIRA?
> --------------------------------------------
>
>                 Key: JBTM-2344
>                 URL: https://issues.jboss.org/browse/JBTM-2344
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, Cloud
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:07:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:07:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.90023.1425042469303@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson resolved JBTM-2344.
---------------------------------
    Resolution: Done


> Add Docker (or Container) component to JIRA?
> --------------------------------------------
>
>                 Key: JBTM-2344
>                 URL: https://issues.jboss.org/browse/JBTM-2344
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, Cloud
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:07:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:07:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2297) Store docker image for
 service(s) in JBoss repo
In-Reply-To: <JIRA.12558008.1416768327000@Atlassian.JIRA>
References: <JIRA.12558008.1416768327000@Atlassian.JIRA>
	<JIRA.12558008.1416768327000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558008.1416768327000.90027.1425042469545@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2297:
--------------------------------
    Component/s: Cloud


> 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: Cloud, 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.11#6341)

From issues at jboss.org  Fri Feb 27 08:07:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:07:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for
 docker transaction service
In-Reply-To: <JIRA.12564317.1424948688000@Atlassian.JIRA>
References: <JIRA.12564317.1424948688000@Atlassian.JIRA>
	<JIRA.12564317.1424948688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564317.1424948688000.90031.1425042469704@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2345:
--------------------------------
    Component/s: Cloud


> Off image storage for docker transaction service
> ------------------------------------------------
>
>                 Key: JBTM-2345
>                 URL: https://issues.jboss.org/browse/JBTM-2345
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, Cloud, JTS
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>              Labels: docker
>
> Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:08:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:08:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for
	docker image(s)
In-Reply-To: <JIRA.12558009.1416768413000@Atlassian.JIRA>
References: <JIRA.12558009.1416768413000@Atlassian.JIRA>
	<JIRA.12558009.1416768413000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558009.1416768413000.90035.1425042529594@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2298:
--------------------------------
    Component/s: Cloud


> 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: Cloud, 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.11#6341)

From issues at jboss.org  Fri Feb 27 08:08:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:08:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2293) Create a docker file to
 make web page update easier
In-Reply-To: <JIRA.12557822.1416488601000@Atlassian.JIRA>
References: <JIRA.12557822.1416488601000@Atlassian.JIRA>
	<JIRA.12557822.1416488601000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557822.1416488601000.90038.1425042529731@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2293:
--------------------------------
    Component/s: Cloud


> 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, Cloud
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>
> 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.11#6341)

From issues at jboss.org  Fri Feb 27 08:08:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:08:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and
 WS-TX) endpoints through Docker
In-Reply-To: <JIRA.12558006.1416768089000@Atlassian.JIRA>
References: <JIRA.12558006.1416768089000@Atlassian.JIRA>
	<JIRA.12558006.1416768089000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558006.1416768089000.90042.1425042529866@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2295:
--------------------------------
    Component/s: Cloud


> 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: Cloud, REST, XTS
>    Affects Versions: 5.0.3
>            Reporter: Mark Little
>            Assignee: Gytis Trikleris
>




--
This message was sent by Atlassian JIRA
(v6.3.11#6341)

From issues at jboss.org  Fri Feb 27 08:08:50 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:08:50 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of
 distributing IOR to users
In-Reply-To: <JIRA.12558007.1416768182000@Atlassian.JIRA>
References: <JIRA.12558007.1416768182000@Atlassian.JIRA>
	<JIRA.12558007.1416768182000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558007.1416768182000.90046.1425042530018@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2296:
--------------------------------
    Component/s: Cloud


> 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: Cloud, JTS
>    Affects Versions: 5.0.3
>            Reporter: Mark Little
>            Assignee: Gytis Trikleris
>             Fix For: 5.0.5
>
>
> 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.11#6341)

From issues at jboss.org  Fri Feb 27 08:09:49 2015
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Fri, 27 Feb 2015 08:09:49 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2344) Add Docker (or Container)
 component to JIRA?
In-Reply-To: <JIRA.12564315.1424948528000@Atlassian.JIRA>
References: <JIRA.12564315.1424948528000@Atlassian.JIRA>
	<JIRA.12564315.1424948528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564315.1424948528000.90049.1425042589033@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson closed JBTM-2344.
-------------------------------


> Add Docker (or Container) component to JIRA?
> --------------------------------------------
>
>                 Key: JBTM-2344
>                 URL: https://issues.jboss.org/browse/JBTM-2344
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Build System, Cloud
>    Affects Versions: 5.0.4
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> Wondering if it makes sense. If it does then Container would give us flexibility to support more than Docker images without having to overload the term Docker.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)