January 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2296: ----------------------------------- Worth mentioning for completeness that if we stick with pure CORBA approaches then we could use a CORBA Naming Service and tie things together that way. But there are pros and cons. > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2296: -------------------------------- Fix Version/s: 5.0.5 > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2295: ------------------------------------- [~gytis], I think the docker scripts you have here look like a good start to me > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2297: ------------------------------------- There are instructions here on whom to contact to get this uploaded: http://www.jboss.org/docker/ > Store docker image for service(s) in JBoss repo > ----------------------------------------------- > > Key: JBTM-2297 > URL: https://issues.jboss.org/browse/JBTM-2297 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2295: ------------------------------------- When we create a quickstart etc for this I think it would be nice to create a blog article too somewhat similar to http://rpestano.wordpress.com/2015/01/10/a-simple-java-ee-docker-example/ > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE)

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2090: --------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana... > 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.x.y > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACK... > {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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2331?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2331: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TransactionalDriver may leave a JDBC Connection associated after transaction termination > ---------------------------------------------------------------------------------------- > > Key: JBTM-2331 > URL: https://issues.jboss.org/browse/JBTM-2331 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > 1) Start a transaction; > 2) Obtain a connection via the TransactionalDriver > 3) End transaction > 4) start another transaction > 5) Call connection.isClosed() > this will produce the following exception because the transactional driver thinks the connection is still associated: > {code} > java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) > at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) > at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) > at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) > Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) > at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) > at ceylon.dbc.Sql.access$100(Sql.ceylon:701) > at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) > at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) > at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) > at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) > at example.ceylon.transaction.tm.run_.main(transaction.ceylon) > 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 ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) > at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) > at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) > at ceylon.modules.Main.execute(Main.java:69) > at ceylon.modules.Main.main(Main.java:42) > 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.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from ON_QA to VERIFIED > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2331?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2331: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/799 > TransactionalDriver may leave a JDBC Connection associated after transaction termination > ---------------------------------------------------------------------------------------- > > Key: JBTM-2331 > URL: https://issues.jboss.org/browse/JBTM-2331 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > 1) Start a transaction; > 2) Obtain a connection via the TransactionalDriver > 3) End transaction > 4) start another transaction > 5) Call connection.isClosed() > this will produce the following exception because the transactional driver thinks the connection is still associated: > {code} > java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) > at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) > at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) > at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) > Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) > at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) > at ceylon.dbc.Sql.access$100(Sql.ceylon:701) > at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) > at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) > at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) > at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) > at example.ceylon.transaction.tm.run_.main(transaction.ceylon) > 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 ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) > at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) > at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) > at ceylon.modules.Main.execute(Main.java:69) > at ceylon.modules.Main.main(Main.java:42) > 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.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2331: -------------------------------------- Summary: TransactionalDriver may leave a JDBC Connection associated after transaction termination Key: JBTM-2331 URL: https://issues.jboss.org/browse/JBTM-2331 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.0.4 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.5 1) Start a transaction; 2) Obtain a connection via the TransactionalDriver 3) End transaction 4) start another transaction 5) Call connection.isClosed() this will produce the following exception because the transactional driver thinks the connection is still associated: {code} java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) at ceylon.dbc.Sql.access$100(Sql.ceylon:701) at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) at example.ceylon.transaction.tm.run_.main(transaction.ceylon) 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 ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) at ceylon.modules.Main.execute(Main.java:69) at ceylon.modules.Main.main(Main.java:42) 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.modules.Module.run(Module.java:312) at org.jboss.modules.Main.main(Main.java:460) at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) ... 10 more {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2015