October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-4095. ------------------------------- Assignee: Rob Stryker (was: Dmitrii Bocharov) Resolution: Done > unparseable date in o.j.t.foundation.checkup > -------------------------------------------- > > Key: JBDS-4095 > URL: https://issues.jboss.org/browse/JBDS-4095 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: foundation > Affects Versions: 10.2.0.AM1 > Environment: {code} > Red Hat JBoss Developer Studio > Version: 10.2.0.AM1 > Build id: AM1-v20160923-1714-B6096 > Build date: 20160923-1714 > $➔ uname -a > Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1 > $➔ java -version > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 10.2.0.AM2 > > Attachments: unparesable-date.png > > > Just started up devstudio 10.2.0.AM1-v20160923-1714-B6096 and got this error: > {code} > Unparseable date: "Thu Oct 06 13:55:38 EDT 2016" > java.text.ParseException: Unparseable date: "Thu Oct 06 13:55:38 EDT 2016" > at java.text.DateFormat.parse(DateFormat.java:366) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.getSessionDate(JVMProblemDetector.java:677) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.scanLine(JVMProblemDetector.java:240) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.readLogFile(JVMProblemDetector.java:186) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:118) > at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:77) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:53) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2829) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23069) Server adapter wizard: Importing of project should skip Select Build Config wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23069?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23069: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Server adapter wizard: Importing of project should skip Select Build Config wizard page > --------------------------------------------------------------------------------------- > > Key: JBIDE-23069 > URL: https://issues.jboss.org/browse/JBIDE-23069 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.2.AM3 > > > This is follow up on JBIDE-22621. In the JIRA has been implemented importing of source code as an eclipse project. Import dialog works with preselected service from New Server Adapter wizard and thus the Select Build Config wizard page is useless because different service cannot (and probably should not) be selected there and it just force user to click Next on a wizard page where nothing can be changed. We should open the Import OpenShift Application wizard dialog with the Import the _service-name_ OpenShift application wizard page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22051: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Redesing route prompting in server adapter wizard, show in browser etc. > ----------------------------------------------------------------------- > > Key: JBIDE-22051 > URL: https://issues.jboss.org/browse/JBIDE-22051 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.2.AM3 > > > We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser. > According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22915: ------------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Deploy Docker Image: Replication controller is not created for some images > -------------------------------------------------------------------------- > > Key: JBIDE-22915 > URL: https://issues.jboss.org/browse/JBIDE-22915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1") -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22915: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Deploy Docker Image: Replication controller is not created for some images > -------------------------------------------------------------------------- > > Key: JBIDE-22915 > URL: https://issues.jboss.org/browse/JBIDE-22915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1") -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23006: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) Sprint: devex #119 August 2016, devex #122 October 2016 (was: devex #119 August 2016, devex #121 October 2016) > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.AM3 > > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22773: ------------------------------------- [~jeffmaury] Is there even anything we can do about this? Isnt this all upstream? Should we keep this issue open? > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.4.2.AM2 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22810: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) Sprint: devex #119 August 2016, devex #122 October 2016 (was: devex #119 August 2016, devex #121 October 2016) > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.AM3 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23019: ------------------------------------- This is a feature request for integration tests at https://github.com/jbosstools/jbosstools-integration-tests which we wont freeze today. We thus keep this opened with fixVersion 4.4.2.AM2 in the hope that we can finalize it in the following days. > Integration tests: have them running automatically, continuously > ---------------------------------------------------------------- > > Key: JBIDE-23019 > URL: https://issues.jboss.org/browse/JBIDE-23019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.AM2 > > > The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. > There are several pain-points currently: > - there's no dedicated OS instance to run them against > - tests are not stable > - etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23061) Integration tests: have warning when scaling to 0 asserted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23061?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23061: ------------------------------------- this test is included in the PR for JBIDE-23029 > Integration tests: have warning when scaling to 0 asserted > ---------------------------------------------------------- > > Key: JBIDE-23061 > URL: https://issues.jboss.org/browse/JBIDE-23061 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016