[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:
-------------------------------------------------
Bill DeCoste <wdecoste(a)redhat.com> changed the Status of [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369] from ASSIGNED to ON_QA
> 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] (JBTIS-29) Migrate runtime detection plugins for SOA Tooling to their respective projects
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-29?page=com.atlassian.jira.plugin.s... ]
Nick Boldt commented on JBTIS-29:
---------------------------------
[~maxandersen]:
Tests and verifications were done in the three respective projects, including [~rob.stryker]'s PR here: https://github.com/droolsjbpm/droolsjbpm-tools/pull/18
I'm not 100% everything works correctly, but then that's most likely because all we did was MOVE it, but not actually update the code to work w/ Kepler. [~ldimaggio] would be able to say more on this.
{quote}
On 03/23/2013 12:35 AM, Nick Boldt wrote:
> Yes. Although this PR [1] is still pending, you no longer need to include the runtime-soa stuff in JBTIS 4.0.
> [1] https://github.com/jbosstools/jbosstools-runtime-soa/pull/11
> Any idea who owns that project and can apply the PR? It'd be great to be able to finally close JBIDE-11098.
On 03/22/2013 03:04 PM, Paul Leacu wrote:
> Hey Nick -
> Are we at the point where I can remove runtime-soa from the compositeArtifacts/Content xmls
> in JBTIS?
> Thanks!
> --paull
{quote}
> Migrate runtime detection plugins for SOA Tooling to their respective projects
> ------------------------------------------------------------------------------
>
> Key: JBTIS-29
> URL: https://issues.jboss.org/browse/JBTIS-29
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution, drools/ jBPM5, ESB, jBPM3, releng, runtime-soa
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.0.0
>
>
> You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites:
> * org.jboss.tools.runtime.drools.detector
> * org.jboss.tools.runtime.esb.detector
> * org.jboss.tools.runtime.jbpm.detector
--
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:
-------------------------------------------------
Bill DeCoste <wdecoste(a)redhat.com> made a comment on [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369]
I've recreated some bad behavior. After a stop successfully returns the jboss process is still active for a short period of time:
[root@ip-10-12-17-55 ~]# rhc app stop -p 123456 -a as7
RESULT:
as7 stopped
[root@ip-10-12-17-55 ~]# ps -ef | grep jboss
501 22759 1 28 10:04 ? 00:00:09 /usr/lib/jvm/jre-1.7.0/bin/java -D[Standalone] -server -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=as7-bdecoste94e.dev.rhcloud.com -Djgroups.bind_addr=127.0.250.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/0af121d693c111e286d412313d2926cd/jbossas-7/jbossas-7/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/0af121d693c111e286d412313d2926cd/jbossas-7/jbossas-7/standalone/configuration/logging.properties -jar /var/lib/openshift/0af121d693c111e286d412313d2926cd/jbossas-7/jbossas-7/jboss-modules.jar -mp /var/lib/openshift/0af121d693c111e286d412313d2926cd//jbossas-7/jbossas-7/standalone/configuration/modules::/var/lib/openshift/0af121d693c111e286d412313d2926cd//jbossas-7/jbossas-7/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/var/lib/openshift/0af121d693c111e286d412313d2926cd/jbossas-7/jbossas-7
root 23111 11682 0 10:04 pts/3 00:00:00 grep jboss
[root@ip-10-12-17-55 ~]# ps -ef | grep jboss
root 23115 11682 0 10:04 pts/3 00:00:00 grep jboss
> 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-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 commented on JBIDE-13845:
------------------------------------
And this job is still using SWTBot 2.0.5:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fupdates%2Fnightly%2Fcore%2F4.0.juno%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fupdates%2Fnightly%2Fcore%2F4.0.juno%2Fjbosstools-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console}
[b13e07d2] $ /qa/tools/opt/groovy-1.8.6/bin/groovy /mnt/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/b13e07d2/testInstall.groovy /mnt/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/b13e07d2/eclipse/ http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno;http:/...
Preparing tests, installing framework
/mnt/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/b13e07d2/repository
The args attribute is deprecated. Please use nested arg elements.
Installing org.jboss.tools.tests.installation 4.1.0.Alpha1-v20130304-1324.
Installing org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36.
Operation completed in 17232 ms.
Product is: org.eclipse.epp.package.jee.product
Installing content from http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno
The jvmargs attribute is deprecated. Please use nested jvmarg elements.
{code}
> 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)
[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13845:
------------------------------------
This isn't good:
{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%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fjbosstools-directory.xml,eclipseBundleVersion=kepler.M6,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/111/console}
Framework arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/releases/latest/file:////qa... -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/releases/latest/file:////qa... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group -consolelog
!ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2013-03-23 09:56:24.338
!MESSAGE No repository found at http://download.eclipse.org/technology/swtbot/releases/latest/file:////qa....
!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2013-03-23 09:56:25.286
!MESSAGE No repository found at http://download.eclipse.org/technology/swtbot/releases/latest/file:////qa....
Installation failed.
!ENTRY org.eclipse.equinox.p2.core 4 0 2013-03-23 09:56:25.287
!MESSAGE Unable to load repositories.
Unable to load repositories.
Application failed, log file location: /qa/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/640333b9/eclipse/configuration/1364046973239.log
{code}
> 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)
[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13845:
------------------------------------
Well, if org.junit_4.10.0.v4_10_0_v20120426-0900.jar is resolved instead of org.junit4_4.8.1.v20120523-1257.jar, and org.junit_3.8.2.v3_8_2_v20100427-1100.jar is ignored, then yes, we should be fine here for Juno tests. Ref: http://download.jboss.org/jbosstools/updates/requirements/juno/2013021321...
> 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