[JBoss JIRA] (JBIDE-13845) Branch install-grinder for Juno (using org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler (org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13845 at 3/23/13 2:30 AM:
-------------------------------------------------------------
Broken, needs to use org.junit:
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Will need to be changed/created to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):
* *NEW JOB*: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was (Author: nickboldt):
Broken, needs to use org.junit:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Will need to be changed/created to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *NEW JOB*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Branch install-grinder for Juno (using org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler (org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13845
> URL: https://issues.jboss.org/browse/JBIDE-13845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> As noted in JBIDE-13843, Kepler M6 no longer includes the org.junit4_4.8 bundle; instead it includes org.junit_4.11.
> So, install-grinder fails to set up the install base with this error due to the missing IU:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M6,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/102/console}
> Framework arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group
> Command-line arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group -consolelog
> !ENTRY org.eclipse.equinox.p2.director 4 1 2013-03-23 02:15:09.053
> !MESSAGE Cannot complete the install because one or more required items could not be found.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
> !MESSAGE Software bCannot complete the install because one or more required items could not be found.
> Software being installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
> Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0eing installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.sw.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36) requtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
> !MESSAGE Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36) requires 'org.junit4 0.0.0' but it could not be found
> ires 'org.junit4 0.0.0' but it could not be found
> {code}
> However, since the Juno tests still depend on SWTBot 2.0.5 and Juno (in which org.junit4 CAN be found) we need to create a jbosstools-4.0.x branch and configure all the 4.0.x jobs that depend on install-grinder so that they will use this new org.junit4_4.8 / SWTBot 2.0.5 compatible branch, while master moves ahead with SWTBot 2.1 and org.junit_4.11.
--
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
13 years
[JBoss JIRA] (JBIDE-13845) Branch install-grinder for Juno (using org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler (org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13845:
----------------------------------
Summary: Branch install-grinder for Juno (using org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler (org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
Key: JBIDE-13845
URL: https://issues.jboss.org/browse/JBIDE-13845
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Mickael Istria
Priority: Blocker
Fix For: 4.1.0.Alpha2
As noted in JBIDE-13843, Kepler M6 no longer includes the org.junit4_4.8 bundle; instead it includes org.junit_4.11.
So, install-grinder fails to set up the install base with this error due to the missing IU:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M6,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/102/console}
Framework arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group
Command-line arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group -consolelog
!ENTRY org.eclipse.equinox.p2.director 4 1 2013-03-23 02:15:09.053
!MESSAGE Cannot complete the install because one or more required items could not be found.
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
!MESSAGE Software bCannot complete the install because one or more required items could not be found.
Software being installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0eing installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.sw.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36) requtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
!MESSAGE Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36) requires 'org.junit4 0.0.0' but it could not be found
ires 'org.junit4 0.0.0' but it could not be found
{code}
However, since the Juno tests still depend on SWTBot 2.0.5 and Juno (in which org.junit4 CAN be found) we need to create a jbosstools-4.0.x branch and configure all the 4.0.x jobs that depend on install-grinder so that they will use this new org.junit4_4.8 / SWTBot 2.0.5 compatible branch, while master moves ahead with SWTBot 2.1 and org.junit_4.11.
--
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
13 years
[JBoss JIRA] (JBIDE-13844) JarAccess should ignore .class entries in jar files
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13844?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-13844:
------------------------------------------
Description:
Memory problem were reported https://community.jboss.org/message/804026#804026
JarAccess is used by internal model to optimize requests to jar files. It builds a map that binds parent folder path to its content. At present, maps include paths for all entries so that in a large workspace with 500-1000 jars memory consumed by these maps may add up to 70Mb. However, for a long time .class entries from JarAccess are not used directly for presentation in ui. Class selector based on it had been replaced by Eclipse's Class selector years ago. Builders in CDI and Seam get classes from JDT model. Open-ons work with JDT elements as well. Hence, if internal model has no more data on .class entries, it should not affect anything, while the profit is significant - memory consumed by maps in JarAccess may drop 5 to 10 times.
> JarAccess should ignore .class entries in jar files
> ---------------------------------------------------
>
> Key: JBIDE-13844
> URL: https://issues.jboss.org/browse/JBIDE-13844
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Alpha2
>
>
> Memory problem were reported https://community.jboss.org/message/804026#804026
> JarAccess is used by internal model to optimize requests to jar files. It builds a map that binds parent folder path to its content. At present, maps include paths for all entries so that in a large workspace with 500-1000 jars memory consumed by these maps may add up to 70Mb. However, for a long time .class entries from JarAccess are not used directly for presentation in ui. Class selector based on it had been replaced by Eclipse's Class selector years ago. Builders in CDI and Seam get classes from JDT model. Open-ons work with JDT elements as well. Hence, if internal model has no more data on .class entries, it should not affect anything, while the profit is significant - memory consumed by maps in JarAccess may drop 5 to 10 times.
--
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
13 years
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13818:
-------------------------------------------------
Abhishek Gupta <abhgupta(a)redhat.com> made a comment on [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369]
I have been able to reproduce it by starting, restarting, and then stopping the application in sequence. Roughly 1 out of every 5 attempts results in a failure.
rhc app start app1 -ppwd; rhc app restart app1 -ppwd; rhc app stop app1 -ppwd;
abstract-httpd and abstract-jboss seem to differ in the mechanisms for waiting for a process to stop and pid to disappear.
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> 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:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> 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:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> 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:537)
> 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:616)
> 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: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {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
13 years
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13818:
-------------------------------------------------
Abhishek Gupta <abhgupta(a)redhat.com> made a comment on [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369]
Based on my debugging, the findings are:
The failure is caused when the app_ctl_impl.sh script fails to kill the jboss pid as referenced in the log snippet below.
^[[0;37m2013-03-22 14:13:33.595^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: rpc_exec_direct: rpc_client=#<MCollective::RPC::Client:0x00000005e76580> (pid:3220)
^[[0;37m2013-03-22 14:13:33.595^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: rpc_client.custom_request('cartridge_do', {:cartridge=>"jbossas-7", :action=>"stop", :args=>{"--with-app-uuid"=>"ee0f90b6931b11e294a512313d2d6078", "--with-app-name"=>"1363975865282", "--with-container-uuid"=>"ee0f90b6931b11e294a512313d2d6078", "--with-container-name"=>"1363975865282", "--with-namespace"=>"1363975618879", "--with-request-id"=>"d849586e24d217b414cceb2f1264ccd2", "--cart-name"=>"jbossas-7"}}, ip-10-62-79-134, {'identity' => ip-10-62-79-134}) (Request ID: d849586e24d217b414cceb2f1264ccd2) (pid:3220)
^[[0;37m2013-03-22 14:13:37.301^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: [#<MCollective::RPC::Result:0x0000000455d8c8 @agent="openshift", @action="cartridge_do", @results={:sender=>"ip-10-62-79-134", :statuscode=>1, :statusmsg=>"cartridge_do_action failed -1. Output Control action 'stop' returned an error. rc=121\nSending SIGTERM to jboss:19877 ...\nkill -TERM 20091\n/usr/libexec/openshift/cartridges/jbossas-7/info/bin/app_ctl_impl.sh: line 34: kill: (20091) - No such process\nFailed to stop jbossas-7\n", :data=>{:time=>nil, :output=>"Control action 'stop' returned an error. rc=121\nSending SIGTERM to jboss:19877 ...\nkill -TERM 20091\n/usr/libexec/openshift/cartridges/jbossas-7/info/bin/app_ctl_impl.sh: line 34: kill: (20091) - No such process\nFailed to stop jbossas-7\n", :exitcode=>-1}}>] (Request ID: d849586e24d217b414cceb2f1264ccd2) (pid:3220)
^[[0;37m2013-03-22 14:13:37.303^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: MCollective Response Time (execute_direct: stop): 3.709499049s (Request ID: d849586e24d217b414cceb2f1264ccd2) (pid:3220)
^[[0;37m2013-03-22 14:13:37.304^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: server results: Control action 'stop' returned an error. rc=121 (pid:3220)
^[[0;37m2013-03-22 14:13:37.304^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: server results: Sending SIGTERM to jboss:19877 ... (pid:3220)
^[[0;37m2013-03-22 14:13:37.304^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: server results: kill -TERM 20091 (pid:3220)
^[[0;37m2013-03-22 14:13:37.304^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: server results: /usr/libexec/openshift/cartridges/jbossas-7/info/bin/app_ctl_impl.sh: line 34: kill: (20091) - No such process (pid:3220)
^[[0;37m2013-03-22 14:13:37.304^[[0m [^[[0;37mDEBUG^[[0m] DEBUG: server results: Failed to stop jbossas-7 (pid:3220)
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> 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:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> 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:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> 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:537)
> 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:616)
> 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: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {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
13 years