[JBoss JIRA] (JBTM-2103) ORB-less JTS
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2103?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2103:
-----------------------------------
Assignee: Michael Musgrove (was: Tom Jenkinson)
> ORB-less JTS
> ------------
>
> Key: JBTM-2103
> URL: https://issues.jboss.org/browse/JBTM-2103
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: JTS
> Affects Versions: 5.0.0
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Fix For: 5.later
>
>
> At some point in the future there's a good chance that the ORB requirement will be removed from EE entirely. If that happens we need to be able to react and ensure that the JTS continues to work because it’s the most complete distributed transaction implementation that we possess. Now there are two ways to do that:
> (i) we ship our own ORB, either JacORB or something else, say.
> (ii) we remove the dependency on CORBA entirely.
> Whilst (i) is a good short term option, I think we need to look at (ii). An old in-house TM that JBoss had which Narayana replaced had a JTS implementation which supported CORBA and JBoss Remoting (I think it was Remoting). Ultimately what we need is a high performance distributed transactions implementation and JTS is it today but it has a dependency on CORBA that we need to try to remove and yet keep most of the non-ORB generated code/dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional driver
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-809:
-------------------------------
Summary: Provide instructions for using ironjacamar as well as transactional driver (was: Provide instructions for using ironjacamar as well as transactional drive)
> Provide instructions for using ironjacamar as well as transactional driver
> --------------------------------------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Resource Manager
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 6.later
>
>
> Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server.
> There are several bugs open against transactional driver that will be resolved by completing this work.
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-809:
-------------------------------
Fix Version/s: 6.later
> Replace transactional driver with ironjacamar
> ---------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Resource Manager
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 6.later
>
>
> Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server.
> There are several bugs open against transactional driver that will be resolved by completing this work.
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional drive
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-809:
-------------------------------
Summary: Provide instructions for using ironjacamar as well as transactional drive (was: Replace transactional driver with ironjacamar)
> Provide instructions for using ironjacamar as well as transactional drive
> -------------------------------------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Resource Manager
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 6.later
>
>
> Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server.
> There are several bugs open against transactional driver that will be resolved by completing this work.
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-809:
-------------------------------
Fix Version/s: (was: 6.later)
> Replace transactional driver with ironjacamar
> ---------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Resource Manager
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
>
> Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server.
> There are several bugs open against transactional driver that will be resolved by completing this work.
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2490:
--------------------------------
Issue Type: Task (was: Feature Request)
> Possibility to run "qa" module with openjdk-orb
> -----------------------------------------------
>
> Key: JBTM-2490
> URL: https://issues.jboss.org/browse/JBTM-2490
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Hayk Hovsepyan
> Assignee: Michael Musgrove
> Priority: Blocker
> Fix For: 5.next
>
>
> In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled.
> The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables.
> "QA_TESTS=1" and "JAC_ORB=1"
> We need to modify these jobs to run with "openjdk-orb" enabled.
> So what we request:
> Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.... ]
Michael Musgrove reassigned JBTM-2454:
--------------------------------------
Assignee: Tom Jenkinson (was: Michael Musgrove)
> Internal IBM J9 compiler error building XTS
> -------------------------------------------
>
> Key: JBTM-2454
> URL: https://issues.jboss.org/browse/JBTM-2454
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.2.0
> Reporter: Michael Musgrove
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.next
>
> Attachments: compensations.tar
>
>
> On lancel we get the following error. I am unable to reproduce it on my laptop.
> The compiler details are:
> {quote}
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR1_20150410_1531_B243669
> JIT - tr.r14.java_20150402_88976.03
> GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS
> J9CL - 20150410_243669)
> JCL - 20150413_01 based on Oracle jdk8u45-b13
> {quote}
> and the build error is:
> {quote}
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes
> An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
> java.lang.NullPointerException
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142)
> at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758)
> at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162)
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:891)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868)
> at com.sun.tools.javac.main.Main.compile(Main.java:535)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
> at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months