[JBoss JIRA] (JBTM-1517) Transactional File I/O build fails
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1517?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1517:
-----------------------------------
JAVA_HOME is certainly an issue, but this is the only component that fails to build on a Mac at the moment. So whatever we've done to make sure everything else builds should probably just be duplicated here.
> Transactional File I/O build fails
> ----------------------------------
>
> Key: JBTM-1517
> URL: https://issues.jboss.org/browse/JBTM-1517
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System, Transactional File I/O
> Affects Versions: 5.0.0.M1
> Environment: Mac OS 10
> java version "1.7.0_17"
> Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jbossts-transactional-fileio: Compilation failure
> [ERROR] Failure executing javac, but could not parse the error:
> [ERROR] /bin/sh: /bin/javac: No such file or directory
> Looks like the build is hard coded with the assumption for the path to javac.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1517) Transactional File I/O build fails
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1517?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1517:
----------------------------------------
I think this is because JAVA_HOME isn't exported. So the question is do we want to require JAVA_HOME - my preference would be to to remove the line <executable>${JAVA_HOME}/bin/javac</executable> from the fileio/pom.xml
> Transactional File I/O build fails
> ----------------------------------
>
> Key: JBTM-1517
> URL: https://issues.jboss.org/browse/JBTM-1517
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System, Transactional File I/O
> Affects Versions: 5.0.0.M1
> Environment: Mac OS 10
> java version "1.7.0_17"
> Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jbossts-transactional-fileio: Compilation failure
> [ERROR] Failure executing javac, but could not parse the error:
> [ERROR] /bin/sh: /bin/javac: No such file or directory
> Looks like the build is hard coded with the assumption for the path to javac.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1479?focusedWorklogId=12428744&page=... ]
Gytis Trikleris logged work on JBTM-1479:
-----------------------------------------
Author: Gytis Trikleris
Created on: 06/Mar/13 1:35 PM
Start Date: 06/Mar/13 1:35 PM
Worklog Time Spent: 5 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 day (was: 1 day, 5 hours)
Time Spent: 2 days (was: 1 day, 3 hours)
Worklog Id: (was: 12428744)
> Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
> -------------------------------------------------------------------------
>
> Key: JBTM-1479
> URL: https://issues.jboss.org/browse/JBTM-1479
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M3
>
> Attachments: test-ds.xml, transaction.xml
>
> Original Estimate: 3 days
> Time Spent: 2 days
> Remaining Estimate: 1 day
>
> See JBTM-809 for the algorithm
> You might want to put the startup in the context listener:
> public class MyServletContextListener implements ServletContextListener {
> public void contextInitialized(ServletContextEvent sce) {
> // Initialize RecoveryManager
> // Initialize TransactionManager
> // Initialize IronJacamar
> }
>
> @Override
> public void contextDestroyed(ServletContextEvent sce) {
> // Clean IronJacamar
> // Clean TransactionManager
> // Clean RecoveryManager
> }
> }
> Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1519) NullPointerException thrown in org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getCurrentTXID
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1519?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris closed JBTM-1519.
---------------------------------
Resolution: Duplicate Issue
> NullPointerException thrown in org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getCurrentTXID
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1519
> URL: https://issues.jboss.org/browse/JBTM-1519
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
>
> See: http://172.17.131.2/job/narayana/180
> {noformat}
> Caused by: java.lang.NullPointerException
> at org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getCurrentTXID(HandlerFactory.java:111) [txframework-5.0.0.M2-SNAPSHOT.jar:]
> at org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getInstance(HandlerFactory.java:49) [txframework-5.0.0.M2-SNAPSHOT.jar:]
> at org.jboss.as.xts.XTSEJBInterceptor.processInvocation(XTSEJBInterceptor.java:73)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:94) [jboss-as-weld-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> ... 58 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1519) NullPointerException thrown in org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getCurrentTXID
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1519:
-------------------------------------
Summary: NullPointerException thrown in org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getCurrentTXID
Key: JBTM-1519
URL: https://issues.jboss.org/browse/JBTM-1519
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Gytis Trikleris
Assignee: Paul Robinson
Priority: Minor
Fix For: 5.0.0.M3
See: http://172.17.131.2/job/narayana/180
{noformat}
Caused by: java.lang.NullPointerException
at org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getCurrentTXID(HandlerFactory.java:111) [txframework-5.0.0.M2-SNAPSHOT.jar:]
at org.jboss.narayana.txframework.impl.handlers.HandlerFactory.getInstance(HandlerFactory.java:49) [txframework-5.0.0.M2-SNAPSHOT.jar:]
at org.jboss.as.xts.XTSEJBInterceptor.processInvocation(XTSEJBInterceptor.java:73)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [jboss-as-jpa-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:94) [jboss-as-weld-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) [jboss-invocation-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
... 58 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1517) Transactional File I/O build fails
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1517?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1517:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/230
> Transactional File I/O build fails
> ----------------------------------
>
> Key: JBTM-1517
> URL: https://issues.jboss.org/browse/JBTM-1517
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System, Transactional File I/O
> Affects Versions: 5.0.0.M1
> Environment: Mac OS 10
> java version "1.7.0_17"
> Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jbossts-transactional-fileio: Compilation failure
> [ERROR] Failure executing javac, but could not parse the error:
> [ERROR] /bin/sh: /bin/javac: No such file or directory
> Looks like the build is hard coded with the assumption for the path to javac.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1517) Transactional File I/O build fails
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1517?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1517:
--------------------------------
Component/s: Build System
Transactional File I/O
> Transactional File I/O build fails
> ----------------------------------
>
> Key: JBTM-1517
> URL: https://issues.jboss.org/browse/JBTM-1517
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System, Transactional File I/O
> Affects Versions: 5.0.0.M1
> Environment: Mac OS 10
> java version "1.7.0_17"
> Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jbossts-transactional-fileio: Compilation failure
> [ERROR] Failure executing javac, but could not parse the error:
> [ERROR] /bin/sh: /bin/javac: No such file or directory
> Looks like the build is hard coded with the assumption for the path to javac.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1517) Transactional File I/O build fails
by Mark Little (JIRA)
Mark Little created JBTM-1517:
---------------------------------
Summary: Transactional File I/O build fails
Key: JBTM-1517
URL: https://issues.jboss.org/browse/JBTM-1517
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 5.0.0.M1
Environment: Mac OS 10
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Reporter: Mark Little
Assignee: Tom Jenkinson
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jbossts-transactional-fileio: Compilation failure
[ERROR] Failure executing javac, but could not parse the error:
[ERROR] /bin/sh: /bin/javac: No such file or directory
Looks like the build is hard coded with the assumption for the path to javac.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBTM-1517) Transactional File I/O build fails
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1517?page=com.atlassian.jira.plugin.... ]
Mark Little updated JBTM-1517:
------------------------------
Issue Type: Bug (was: Feature Request)
> Transactional File I/O build fails
> ----------------------------------
>
> Key: JBTM-1517
> URL: https://issues.jboss.org/browse/JBTM-1517
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.0.0.M1
> Environment: Mac OS 10
> java version "1.7.0_17"
> Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jbossts-transactional-fileio: Compilation failure
> [ERROR] Failure executing javac, but could not parse the error:
> [ERROR] /bin/sh: /bin/javac: No such file or directory
> Looks like the build is hard coded with the assumption for the path to javac.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months