[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-23869.
---------------------------------
Closing as an upstream issue. Please follow linked issues on Github.
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.5.1.AM2
>
> Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Mohit Suman commented on JBDS-3868:
-----------------------------------
[~dgolovin] _Next is not always leads to installation right away. In most cases red hat account information is required. _
* For the same, the text I mentioned earlier was: Please verify the confirmation summary and proceed to Next step. Please let me know if that works.
Regarding the border at the end is kept to maintain a card layout UX, so the components will be present and scrolling is enabled.
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
> Attachments: cnf-review.png, confirmation-page.png, screenshot-1.png
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24779?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-24779:
----------------------------------------
Unfortunately, I don't recall the details and don't have much time to try reproduce it right now. If you can't reproduce, feel free to mark it as such, and I'll reopen it later if it happens again, taking care of listing very detailed steps.
> Starting an OpenShift application seems to lock workspace
> ---------------------------------------------------------
>
> Key: JBIDE-24779
> URL: https://issues.jboss.org/browse/JBIDE-24779
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
>
> I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages.
> In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete.
> I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24779?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-24779:
------------------------------------------
[~mickael_istria] i have just created an Openshift application and was able to manipulate with the project while the build was running and container were being created in the pod.
What do you mean by "*starting* Openshift application" ? Creating it? Running the build? Could you, please, provide more detailed steps?
Also it would be great to have the exact projects that you have problems with.
> Starting an OpenShift application seems to lock workspace
> ---------------------------------------------------------
>
> Key: JBIDE-24779
> URL: https://issues.jboss.org/browse/JBIDE-24779
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
>
> I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages.
> In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete.
> I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24995) Server adapter: restarting into debug after restarting Eclipse errors trying to set duplicate port names
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24995?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24995.
---------------------------------
Error is not shown, please follow up linked JIRAs.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.1.0.AM3
Build id: AM3-v20170926-0420-B1147
Build date: 20170926-0420
> Server adapter: restarting into debug after restarting Eclipse errors trying to set duplicate port names
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24995
> URL: https://issues.jboss.org/browse/JBIDE-24995
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM2
>
> Attachments: image-2017-09-07-15-33-48-897.png
>
>
> reported originally in https://github.com/jbosstools/jbosstools-openshift/pull/1561#pullrequestr... (with slight different steps)
> # ASSERT: make sure that you have an app based on the "nodejs-mongo-persistent" template
> # ASSERT: make sure that you have the source imported to your workspace and a server adapter for it
> # EXEC: Server adapter: Start/Restart adapter Debugging
> # ASSERT: Server adapter: adapter is debugging, you see the debugging output in the console and the env vars have devmode set to true and the debugging port set to some value (5858 by default)
> # EXEC: Server adapter: Restart adapter (not debugging)
> Result:
> !image-2017-09-07-15-33-48-897.png!
> {code}
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.2:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/nod... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].ports[2].name: Duplicate value: "debug"
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.sendAndGetNewPod(OpenShiftDebugMode.java:308)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:220)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24938) server.it.weekly jenkins job runs out of disk space on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24938?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24938:
---------------------------------------
PR for JBIDE-24964 is now merged, so HUDSON_STATIC_ENV should start working on Windows. Once the Windows images are rebuilt, I will verify this.
> server.it.weekly jenkins job runs out of disk space on Windows
> --------------------------------------------------------------
>
> Key: JBIDE-24938
> URL: https://issues.jboss.org/browse/JBIDE-24938
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.5.1.AM2
>
>
> This job is failing on Windows:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> It's because it runs out of disk space.
> The windows instances have (I believe) 30GB of disk space. This is set up in our openstack instance by eng-ops:
> https://ci-rhos.centralci.eng.rdu2.redhat.com/dashboard/
> If we wanted more space, we would need to ask eng ops to change this. But it's probably the same for all other users, so I don't think they would change it easily. And in any case, it should be enough.
> The main thing is that we need to reduce the space the tests are using.
> They download all the runtimes via the itests pom:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> The main problem is that this happens 4 times:
> 3.5G ./org.jboss.tools.as.management.itests/target/requirements
> 3.5G ./org.jboss.tools.as.itests/target/requirements
> 3.5G ./target/requirements
> 3.5G ./org.jboss.tools.as.ui.bot.itests/target/requirements
> Fortunately this doesn't mean that all the servers are really downloaded 4 times - they are downloaded once and stored in the local maven download cache. But then the zips are copied over for each of the modules and unzipped.
> So, there are several options:
> a) Get rid of the zips once they're unzipped - that would save half the space. Unfortunately the download plugin does not support this:
> https://github.com/maven-download-plugin/maven-download-plugin
> b) Delete the requirements dir for each module at the end of the maven module lifecycle. This might be doable, needs investigating.
> c) Change the overall setup so that only one download is needed for all the tests - i.e. the child modules don't inherit the download plugin call, but instead use the downloaded runtimes from the higher pom (itests)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24872) NullPointerException in ResourceUtils.getBuildConfigFor
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24872?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24872.
---------------------------------
Closing. NPE is gone.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.1.0.AM3
Build id: AM3-v20170926-0420-B1147
Build date: 20170926-0420
> NullPointerException in ResourceUtils.getBuildConfigFor
> -------------------------------------------------------
>
> Key: JBIDE-24872
> URL: https://issues.jboss.org/browse/JBIDE-24872
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Automated Error Reporting Bot
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.5.1.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.NullPointerException: null
> at org.jboss.tools.openshift.internal.core.util.ResourceUtils.getBuildConfigFor(ResourceUtils.java:663)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage$11.widgetSelected(ServerSettingsWizardPage.java:494)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 |
> | org.jboss.tools.openshift.core | 3.3.3.v20170510-1453 | 3.3.3.v20170510-1453 |
> | org.jboss.tools.openshift.ui | 3.3.3.v20170510-2204 | 3.3.3.v20170510-2204 |
> Operating Systems:
> | Linux | 4.11.11.fc26 | 4.11.11.fc26 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/598bb1a2e4b085ca039... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24184.
---------------------------------
Closing. Verified with steps from PR in:
Red Hat JBoss Developer Studio
Version: 11.1.0.AM3
Build id: AM3-v20170926-0420-B1147
Build date: 20170926-0420
> Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24184
> URL: https://issues.jboss.org/browse/JBIDE-24184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM1
>
>
> to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}:
> * nodejs
> {code}
> "Labels": {
> ...
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> ...
> {code}
> * eap
> {code}
> "Labels": {
> ...
> "com.redhat.dev-mode": "DEBUG:true",
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787",
> ...
> {code}
> Our code on the other hand is hard-coding these, not reading the keys from the docker image:
> {code}
> public class OpenShiftDebugUtils {
> private static final String DEBUG_KEY = "DEBUG";
> private static final String DEBUG_PORT_KEY = "DEBUG_PORT";
> ...
> {code}
> {code}
> public class OpenShiftLaunchController extends AbstractSubsystemController
> implements ISubsystemController, ILaunchServerController {
> ...
> private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months