[JBoss JIRA] (JBTM-1792) blacktie-stompconnect cannot be deployed
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1792?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-1792.
---------------------------------
Assignee: Tom Jenkinson (was: Amos Feng)
Resolution: Done
> blacktie-stompconnect cannot be deployed
> ----------------------------------------
>
> Key: JBTM-1792
> URL: https://issues.jboss.org/browse/JBTM-1792
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/117/con...
> {code}
> [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default) on project blacktie-stompconnect: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> [ERROR] "address" => [],
> [ERROR] "operation" => "read-attribute",
> [ERROR] "name" => "launch-type"
> [ERROR] }'. java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default) on project blacktie-stompconnect: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:601)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal deploy on /home/hudson/workspace/narayana-dualstack/blacktie/stompconnect-1.0/target/blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar. Reason: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:155)
> at org.jboss.as.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:69)
> at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.IllegalStateException: Error could not execute operation '{
> "address" => [],
> "operation" => "read-attribute",
> "name" => "launch-type"
> }'.
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:186)
> at org.jboss.as.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:132)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:109)
> at org.jboss.as.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:167)
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:133)
> ... 23 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:181)
> ... 27 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:156)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:111)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:94)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 29 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :blacktie-stompconnect
> UID PID PPID C STIME TTY TIME CMD
> hudson 6674 25496 0 18:38 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 7393 6674 0 18:39 ? 00:00:00 ps -f
> hudson 25494 29253 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 25496 25494 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 29208 29205 0 Apr26 ? 00:38:02 sshd: hudson@notty
> hudson 29246 29208 0 Apr26 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar
> hudson 29253 29246 0 Apr26 ? 01:49:14 java -jar slave.jar
> testsuite: no process killed
> server: no process killed
> client: no process killed
> cs: no process killed
> UID PID PPID C STIME TTY TIME CMD
> hudson 6674 25496 0 18:38 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 7404 6674 0 18:39 ? 00:00:00 ps -f
> hudson 25494 29253 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 25496 25494 0 18:02 ? 00:00:00 /bin/bash -xe /tmp/hudson929305314090322865.sh
> hudson 29208 29205 0 Apr26 ? 00:38:02 sshd: hudson@notty
> hudson 29246 29208 0 Apr26 ? 00:00:00 bash -c cd '/home/hudson' && java -jar slave.jar
> hudson 29253 29246 0 Apr26 ? 01:49:14 java -jar slave.jar
> Some tests failed: http://172.17.131.2/job/narayana-dualstack/117/
> BlackTie build failed
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: gtrikler(a)redhat.com zfeng(a)redhat.com mmusgrov(a)redhat.com tom.jenkinson(a)redhat.com mlittle(a)redhat.com
> Finished: FAILURE
> {code}
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1815) jatmibroker-xatmi compilcatoin error
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1815?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1815:
-------------------------------------
[~zhfeng] I have temporarily disabled the codeCoverage build, please re-enable when you have fixed this: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/
> jatmibroker-xatmi compilcatoin error
> ------------------------------------
>
> Key: JBTM-1815
> URL: https://issues.jboss.org/browse/JBTM-1815
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/40
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/41
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Blacktie Java XATMI Implementation 5.0.0.M4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ blacktie-jatmibroker-xatmi ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ blacktie-jatmibroker-xatmi ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ blacktie-jatmibroker-xatmi ---
> [INFO] Compiling 58 source files to /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/target/classes
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[26,17] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[27,17] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[31,12] error: cannot find symbol
> [ERROR] class CorbaSenderImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[41,17] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[43,39] error: cannot find symbol
> [ERROR] class EndpointQueuePOA
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/TransportImpl.java:[192,15] error: incompatible types
> [ERROR] CorbaReceiverImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[37,21] error: cannot find symbol
> [ERROR] class CorbaSenderImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[84,43] error: method activate_object in interface POAOperations cannot be applied to given types;
> [ERROR] actual argument CorbaReceiverImpl cannot be converted to Servant by method invocation conversion
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[87,56] error: method servant_to_reference in interface POAOperations cannot be applied to given types;
> [ERROR] actual argument CorbaReceiverImpl cannot be converted to Servant by method invocation conversion
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[89,22] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[89,64] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[142,8] error: cannot find symbol
> [ERROR] class CorbaReceiverImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[157,24] error: cannot find symbol
> [ERROR] class CorbaReceiverImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[236,12] error: cannot find symbol
> {code}
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1815) jatmibroker-xatmi compilcatoin error
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1815?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1815:
-------------------------------------
[~zhfeng], when you get to this, it is due to the code being instrumented by emma
> jatmibroker-xatmi compilcatoin error
> ------------------------------------
>
> Key: JBTM-1815
> URL: https://issues.jboss.org/browse/JBTM-1815
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/40
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/41
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Blacktie Java XATMI Implementation 5.0.0.M4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ blacktie-jatmibroker-xatmi ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ blacktie-jatmibroker-xatmi ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ blacktie-jatmibroker-xatmi ---
> [INFO] Compiling 58 source files to /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/target/classes
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[26,17] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[27,17] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[31,12] error: cannot find symbol
> [ERROR] class CorbaSenderImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[41,17] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[43,39] error: cannot find symbol
> [ERROR] class EndpointQueuePOA
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/TransportImpl.java:[192,15] error: incompatible types
> [ERROR] CorbaReceiverImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaSenderImpl.java:[37,21] error: cannot find symbol
> [ERROR] class CorbaSenderImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[84,43] error: method activate_object in interface POAOperations cannot be applied to given types;
> [ERROR] actual argument CorbaReceiverImpl cannot be converted to Servant by method invocation conversion
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[87,56] error: method servant_to_reference in interface POAOperations cannot be applied to given types;
> [ERROR] actual argument CorbaReceiverImpl cannot be converted to Servant by method invocation conversion
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[89,22] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[89,64] error: package AtmiBroker does not exist
> [ERROR] /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[142,8] error: cannot find symbol
> [ERROR] class CorbaReceiverImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[157,24] error: cannot find symbol
> [ERROR] class CorbaReceiverImpl
> /home/hudson/workspace/narayana-codeCoverage/blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/transport/hybrid/CorbaReceiverImpl.java:[236,12] error: cannot find symbol
> {code}
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1821) Make @Transactional work without specifying the "org.jboss.jts export services" dependency
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1821?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1821:
-------------------------------------
Conversation with Gytis on a potential solution:
pfrobinson: whilst you are at it, can you have a quick check to see if you can add modules to the classloader in that phase too?
[12:06pm] gytist: you mean dependencies like org.jboss.xts?
[12:10pm] pfrobinson: yeah
[12:10pm] pfrobinson: I want to scan for the use of @Transactional and then add the org.jboss.jts depenedency to the deployment
[12:10pm] gytist: I think it is, some of the subsystems automatically add dependencies
[12:11pm] pfrobinson: yeah, that was my thoughts too
[12:11pm] pfrobinson: for example, if persistence.xml is present, you add the jpa deps
[12:11pm] gytist: I saw it when I was researching my issue on Monday
[12:11pm] gytist: need to find it again
[12:12pm] gytist: grep for this class WSDependenciesProcessor
[12:12pm] gytist: that's what you need
[12:12pm] pfrobinson: great, thanks
> Make @Transactional work without specifying the "org.jboss.jts export services" dependency
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1821
> URL: https://issues.jboss.org/browse/JBTM-1821
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M4
>
>
> Currently all deployments that use @Tranactional should have a MANIFEST.MF containing "Dependencies: org.jboss.jts export services".
> We should find a better approach to activating these interceptors.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1747) CNFE when invoking a plain Web service with standalone-xts.xml config
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1747?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1747:
-------------------------------------
Conversation with Gytis on a potential solution:
pfrobinson: whilst you are at it, can you have a quick check to see if you can add modules to the classloader in that phase too?
[12:06pm] gytist: you mean dependencies like org.jboss.xts?
[12:10pm] pfrobinson: yeah
[12:10pm] pfrobinson: I want to scan for the use of @Transactional and then add the org.jboss.jts depenedency to the deployment
[12:10pm] gytist: I think it is, some of the subsystems automatically add dependencies
[12:11pm] pfrobinson: yeah, that was my thoughts too
[12:11pm] pfrobinson: for example, if persistence.xml is present, you add the jpa deps
[12:11pm] gytist: I saw it when I was researching my issue on Monday
[12:11pm] gytist: need to find it again
[12:12pm] gytist: grep for this class WSDependenciesProcessor
[12:12pm] gytist: that's what you need
[12:12pm] pfrobinson: great, thanks
> CNFE when invoking a plain Web service with standalone-xts.xml config
> ---------------------------------------------------------------------
>
> Key: JBTM-1747
> URL: https://issues.jboss.org/browse/JBTM-1747
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 days
> Time Spent: 5 hours
> Remaining Estimate: 1 day, 3 hours
>
> I've not had chance to reproduce this, but this is what I think I did:
> 1. Start Wildfly with the standalone-xts.xml configuration
> 2. Deploy a plain (non-XTS) web service to the server
> 3. Invoke the web service from inside this server, ensuring that org.jboss.xts is not in the dependencies. Which it shouldn't be if you are just invoking a plain WS.
> 4. Observe the CNFE on one of the TXBridge interceptors (I don't remember which).
> I think the problem is that XTS is adding the handler chain for doing default context propagation to all web services, rather than just those that have the XTS dependency.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1823) Narayana fails to build on a codebase not checked out of SCM
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1823?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1823:
--------------------------------
Assignee: Amos Feng (was: Paul Robinson)
> Narayana fails to build on a codebase not checked out of SCM
> ------------------------------------------------------------
>
> Key: JBTM-1823
> URL: https://issues.jboss.org/browse/JBTM-1823
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4, 4.17.5
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Fix For: 5.0.0.M4, 4.17.6
>
>
> To reproduce:
> * go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
> * Download and extract the zip
> * run: './build.sh clean install -DskipTests'
> * Observe:
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. UnsupportedOperationException
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :arjunacore
> {code}
> Alternatively, it works if you do this:
> {code}
> git clone git@github.com:jbosstm/narayana.git
> git checkout 4.17.4.Final
> ./build.sh clean install -DskipTests
> {code}
> It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
> NOTE: it also happens for the 4.17.5.Final zip.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1823) Narayana fails to build on a codebase not checked out of SCM
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1823?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1823:
--------------------------------
Description:
To reproduce:
* go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
* Download and extract the zip
* run: './build.sh clean install -DskipTests'
* Observe:
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command. UnsupportedOperationException
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :arjunacore
{code}
Alternatively, it works if you do this:
{code}
git clone git@github.com:jbosstm/narayana.git
git checkout 4.17.4.Final
./build.sh clean install -DskipTests
{code}
It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
NOTE: it also happens for the 4.17.5.Final zip.
was:
To reproduce:
* go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
* Download and extract the zip
* run: './build.sh clean install -DskipTests'
* Observe:
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command. UnsupportedOperationException
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :arjunacore
{code}
Alternatively, it works if you do this:
{code}
git clone git@github.com:jbosstm/narayana.git
git checkout 4.17.4.Final
./build.sh clean install -DskipTests
{code}
It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
> Narayana fails to build on a codebase not checked out of SCM
> ------------------------------------------------------------
>
> Key: JBTM-1823
> URL: https://issues.jboss.org/browse/JBTM-1823
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4
> Reporter: Paul Robinson
> Assignee: Paul Robinson
>
> To reproduce:
> * go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
> * Download and extract the zip
> * run: './build.sh clean install -DskipTests'
> * Observe:
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. UnsupportedOperationException
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :arjunacore
> {code}
> Alternatively, it works if you do this:
> {code}
> git clone git@github.com:jbosstm/narayana.git
> git checkout 4.17.4.Final
> ./build.sh clean install -DskipTests
> {code}
> It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
> NOTE: it also happens for the 4.17.5.Final zip.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1823) Narayana fails to build on a codebase not checked out of SCM
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1823?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1823:
--------------------------------
Fix Version/s: 5.0.0.M4
4.17.6
> Narayana fails to build on a codebase not checked out of SCM
> ------------------------------------------------------------
>
> Key: JBTM-1823
> URL: https://issues.jboss.org/browse/JBTM-1823
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4, 4.17.5
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4, 4.17.6
>
>
> To reproduce:
> * go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
> * Download and extract the zip
> * run: './build.sh clean install -DskipTests'
> * Observe:
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. UnsupportedOperationException
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :arjunacore
> {code}
> Alternatively, it works if you do this:
> {code}
> git clone git@github.com:jbosstm/narayana.git
> git checkout 4.17.4.Final
> ./build.sh clean install -DskipTests
> {code}
> It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
> NOTE: it also happens for the 4.17.5.Final zip.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1823) Narayana fails to build on a codebase not checked out of SCM
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1823?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1823:
--------------------------------
Affects Version/s: 4.17.5
> Narayana fails to build on a codebase not checked out of SCM
> ------------------------------------------------------------
>
> Key: JBTM-1823
> URL: https://issues.jboss.org/browse/JBTM-1823
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4, 4.17.5
> Reporter: Paul Robinson
> Assignee: Paul Robinson
>
> To reproduce:
> * go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
> * Download and extract the zip
> * run: './build.sh clean install -DskipTests'
> * Observe:
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. UnsupportedOperationException
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :arjunacore
> {code}
> Alternatively, it works if you do this:
> {code}
> git clone git@github.com:jbosstm/narayana.git
> git checkout 4.17.4.Final
> ./build.sh clean install -DskipTests
> {code}
> It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
> NOTE: it also happens for the 4.17.5.Final zip.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1823) Narayana fails to build on a codebase not checked out of SCM
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1823?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1823:
--------------------------------
Description:
To reproduce:
* go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
* Download and extract the zip
* run: './build.sh clean install -DskipTests'
* Observe:
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command. UnsupportedOperationException
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :arjunacore
{code}
Alternatively, it works if you do this:
{code}
git clone git@github.com:jbosstm/narayana.git
git checkout 4.17.4.Final
./build.sh clean install -DskipTests
{code}
It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
was:
To reproduce:
* go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
* Download and extract the zip
* run: './build.sh clean install -DskipTests'
* Observe:
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command. UnsupportedOperationException
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :arjunacore
{code}
> Narayana fails to build on a codebase not checked out of SCM
> ------------------------------------------------------------
>
> Key: JBTM-1823
> URL: https://issues.jboss.org/browse/JBTM-1823
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4
> Reporter: Paul Robinson
> Assignee: Paul Robinson
>
> To reproduce:
> * go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final
> * Download and extract the zip
> * run: './build.sh clean install -DskipTests'
> * Observe:
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. UnsupportedOperationException
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :arjunacore
> {code}
> Alternatively, it works if you do this:
> {code}
> git clone git@github.com:jbosstm/narayana.git
> git checkout 4.17.4.Final
> ./build.sh clean install -DskipTests
> {code}
> It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario.
--
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
10 years, 11 months