February 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2107) CMRIntegrationTest fails to start the container

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2107?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2107: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/55/ > CMRIntegrationTest fails to start the container > ----------------------------------------------- > > Key: JBTM-2107 > URL: https://issues.jboss.org/browse/JBTM-2107 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 4.17.18, 5.0.2.Final > > > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1860 > {code} > ------------------------------------------------------------------------------- > Test set: com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.56 sec <<< FAILURE! > com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest Time elapsed: 0 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:180) > at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) > Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [60] s > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:176) > ... 68 more > {code} > {code} > Feb 27, 2014 3:24:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.7.0_45/bin/java, ${jvm.args.other}, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/jbossts-EAP61/jboss-as/build/target/jboss-as-7.2.0.Final, -Dorg.jboss.boot.log.file=/home/hudson/workspace/jbossts-EAP61/jboss-as/build/target/jboss-as-7.2.0.Final/standalone/log/boot.log, -Dlogging.configuration=file:/home/hudson/workspace/jbossts-EAP61/jboss-as/build/target/jboss-as-7.2.0.Final/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/hudson/workspace/jbossts-EAP61/jboss-as/build/target/jboss-as-7.2.0.Final/bundles, -jar, /home/hudson/workspace/jbossts-EAP61/jboss-as/build/target/jboss-as-7.2.0.Final/jboss-modules.jar, -mp, /home/hudson/workspace/jbossts-EAP61/jboss-as/build/target/jboss-as-7.2.0.Final/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone-cmr.xml] > Error: Could not find or load main class ${jvm.args.other} > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2106) Hibernate version changed from 5.0.1.Final to 5.0.2.Final-SNAPSHOT by release script in jca-and-tomcat QS

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2106: ------------------------------------- Summary: Hibernate version changed from 5.0.1.Final to 5.0.2.Final-SNAPSHOT by release script in jca-and-tomcat QS Key: JBTM-2106 URL: https://issues.jboss.org/browse/JBTM-2106 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.2.Final http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts-windo... Change ${version.org.hibernate} from 5.0.2.Final-SNAPSHOT to 5.0.1.Final -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2104) XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2104?page=com.atlassian.jira.plugin.... ] Gytis Trikleris resolved JBTM-2104. ----------------------------------- Resolution: Done > XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file > --------------------------------------------------------------------------------------------------------- > > Key: JBTM-2104 > URL: https://issues.jboss.org/browse/JBTM-2104 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Lin Gao > Assignee: Gytis Trikleris > Fix For: 4.6.1.CP15 > > > There are 4 war files within jbossxts.sar: > wstx11.war > wscf11.war > ws-c11.war > ws-t11.war > 2 of them contains *.class files within it, 2 others no *.class files. > Please, pack the .class files in the war/WEB-INF/classes into a jar, then put the jar within the war, so that the jar can be signed. > Thanks! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2105) TxStats.enable generates excessive GC overhead

by Will Reichert (JIRA)

Will Reichert created JBTM-2105: ----------------------------------- Summary: TxStats.enable generates excessive GC overhead Key: JBTM-2105 URL: https://issues.jboss.org/browse/JBTM-2105 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 5.0.1.Final, 4.17.15 Reporter: Will Reichert Assignee: Tom Jenkinson Fix For: 4.17.18, 4.17.15 TxStats.enable() calls arjPropertyManager.getCoordinatorEnvironmentBean() with each invocation which results in String concatenation to generate a HashMap key. The String concatenation generated 1.61GB of GC overhead during a 20 minute performance test. Changing TxStats to use a private static reference to the Bean decreases the GC overhead to 20KB for the same 20 minute test -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1342) XTS sar distribution - pack .class files from exploded directory to a jar file

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1342?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1342. ------------------------------- > XTS sar distribution - pack .class files from exploded directory to a jar file > ------------------------------------------------------------------------------- > > Key: JBTM-1342 > URL: https://issues.jboss.org/browse/JBTM-1342 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Affects Versions: 4.6.1.CP13 > Reporter: Ondřej Chaloupka > Assignee: Gytis Trikleris > Fix For: 4.6.1.CP14 > > > Some files are distributed as .class files in exploded directory in sar archive. > It's possible to sign neither sar nor exploded directory. The EAP demands the distribution to be signed. > Please, pack the .class files in exploded directory to a jar archive. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2104) XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2104?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2104: -------------------------------- Fix Version/s: 4.6.1.CP15 > XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file > --------------------------------------------------------------------------------------------------------- > > Key: JBTM-2104 > URL: https://issues.jboss.org/browse/JBTM-2104 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Lin Gao > Assignee: Gytis Trikleris > Fix For: 4.6.1.CP15 > > > There are 4 war files within jbossxts.sar: > wstx11.war > wscf11.war > ws-c11.war > ws-t11.war > 2 of them contains *.class files within it, 2 others no *.class files. > Please, pack the .class files in the war/WEB-INF/classes into a jar, then put the jar within the war, so that the jar can be signed. > Thanks! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2104) XTS war distribution within jbossxts.sar - pack .class files from exploded directory to a jar file

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBTM-2104?page=com.atlassian.jira.plugin.... ] Lin Gao updated JBTM-2104: -------------------------- Summary: XTS war distribution within jbossxts.sar - pack .class files from exploded directory to a jar file (was: XTS sar distribution - pack .class files from exploded directory to a jar file) Fix Version/s: (was: 4.6.1.CP14) Description: There are 4 war files within jbossxts.sar: wstx11.war wscf11.war ws-c11.war ws-t11.war 2 of them contains *.class files within it, 2 others no *.class files. Please, pack the .class files in the war/WEB-INF/classes into a jar, then put the jar within the war, so that the jar can be signed. Thanks! was: Some files are distributed as .class files in exploded directory in sar archive. It's possible to sign neither sar nor exploded directory. The EAP demands the distribution to be signed. Please, pack the .class files in exploded directory to a jar archive. Affects Version/s: (was: 4.6.1.CP13) > XTS war distribution within jbossxts.sar - pack .class files from exploded directory to a jar file > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2104 > URL: https://issues.jboss.org/browse/JBTM-2104 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Lin Gao > Assignee: Gytis Trikleris > > There are 4 war files within jbossxts.sar: > wstx11.war > wscf11.war > ws-c11.war > ws-t11.war > 2 of them contains *.class files within it, 2 others no *.class files. > Please, pack the .class files in the war/WEB-INF/classes into a jar, then put the jar within the war, so that the jar can be signed. > Thanks! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2104) XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBTM-2104?page=com.atlassian.jira.plugin.... ] Lin Gao updated JBTM-2104: -------------------------- Summary: XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file (was: XTS war distribution within jbossxts.sar - pack .class files from exploded directory to a jar file) > XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file > --------------------------------------------------------------------------------------------------------- > > Key: JBTM-2104 > URL: https://issues.jboss.org/browse/JBTM-2104 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Lin Gao > Assignee: Gytis Trikleris > > There are 4 war files within jbossxts.sar: > wstx11.war > wscf11.war > ws-c11.war > ws-t11.war > 2 of them contains *.class files within it, 2 others no *.class files. > Please, pack the .class files in the war/WEB-INF/classes into a jar, then put the jar within the war, so that the jar can be signed. > Thanks! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2104) XTS sar distribution - pack .class files from exploded directory to a jar file

by Lin Gao (JIRA)

Lin Gao created JBTM-2104: ----------------------------- Summary: XTS sar distribution - pack .class files from exploded directory to a jar file Key: JBTM-2104 URL: https://issues.jboss.org/browse/JBTM-2104 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.6.1.CP13 Reporter: Lin Gao Assignee: Gytis Trikleris Fix For: 4.6.1.CP14 Some files are distributed as .class files in exploded directory in sar archive. It's possible to sign neither sar nor exploded directory. The EAP demands the distribution to be signed. Please, pack the .class files in exploded directory to a jar archive. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2069) Review BlackTie docs

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2069?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2069: -------------------------------- Fix Version/s: 5.0.2.Final (was: 5.0.1.Final) > Review BlackTie docs > -------------------- > > Key: JBTM-2069 > URL: https://issues.jboss.org/browse/JBTM-2069 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.2.Final > > > Ensure no erroneous information > Update AS7 references to WildFly > For example: > run.sh -> standalone.sh (changed parameters too) > JBossAS->WildFly > paths, are they up-to-date (for example what apps should be deployed and where) -- 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, 10 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 February 2014