February 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Description: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenShift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. Steps: # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) # EXEC: Import project within fuse-on-openshift.zip into your workspace # EXEC: open launch configuration and change: ** -Dkubernetes.master= so that it first your cdk instance ** -Dkubernetes.namespace= to the name of the project that you create in step 1. ** -Dfabric8.generator.from=fabric8/s2i-java # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) # ASSERT: server adapter is created and is *[started]* # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end {code} simple-route - >>> 455 simple-route - >>> 695 simple-route - >>> 935 {code} # EXEC: In Project Explorer: open class MyTransformer and change the transform method # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod was: currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. The requirements are: - rsync unpacked jar - rsync without the jar name as folder - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": - there is a SpringBoot app deployed on OpenShift - the developer want to develop evolution of the SpringBoot app -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance -- Remote java debug should be available when the OpenShift server adapter is in debug mode. Steps: # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) # EXEC: Import project within fuse-on-openshift.zip into your workspace # EXEC: open launch configuration and change: ** -Dkubernetes.master= so that it first your cdk instance ** -Dkubernetes.namespace= to the name of the project that you create in step 1. # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) # ASSERT: server adapter is created and is *[started]* # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end {code} simple-route - >>> 455 simple-route - >>> 695 simple-route - >>> 935 {code} # EXEC: In Project Explorer: open class MyTransformer and change the transform method # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.Final > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > ** -Dfabric8.generator.from=fabric8/s2i-java > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25587) Running EAP 7.1 server is not selected by default when deploying

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25587?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-25587: --------------------------------------- Hi [~rob.stryker], I have imported quickstart, but I have not changed runtime in project properties (after import there was nothing selected). Afterwards I have started WildFly 11 and selected *Run On Server* on project and in *Run On Server* was selected WildFly 10(which is stopped), but in my opinion in this case should be selected by default running server(if there is any). > Running EAP 7.1 server is not selected by default when deploying > ---------------------------------------------------------------- > > Key: JBIDE-25587 > URL: https://issues.jboss.org/browse/JBIDE-25587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: FC27 > Red Hat JBoss Developer Studio > Version: 11.2.0.GA > Build id: GA-v20180115-0516-B1866 > Build date: 20180115-0516 > EAP 7.1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.6.0.AM1 > > Attachments: JBIDE-25587.ogv, image-2018-01-16-13-42-38-197.png > > > Please make default selection on running server in *Run On Server* dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25689) Create new jenkins job for Minishift server adapter itests

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-25689: ------------------------------------- Summary: Create new jenkins job for Minishift server adapter itests Key: JBIDE-25689 URL: https://issues.jboss.org/browse/JBIDE-25689 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk, integration-tests Affects Versions: 4.5.3.AM1 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.5.3.AM1 Set up new jenkins job for running minishift server adapter test suite from openshift/itests/o.j.t.cdk. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25584) batch itests on macosx fail or timeout most of the time

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25584?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25584: --------------------------------------- Troubles come from Zamek machine itself. Tests are ok here, hence I am resolving this. Work will continue in linked jira. > batch itests on macosx fail or timeout most of the time > ------------------------------------------------------- > > Key: JBIDE-25584 > URL: https://issues.jboss.org/browse/JBIDE-25584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Reporter: Nick Boldt > Assignee: Ondrej Dockal > Fix For: 4.5.3.AM1 > > > Not sure if we care about this since the tests pass on Win10 and RHEL7, but the Batch tests on OSX pretty consistently either timeout (120 mins) or fail. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Last good build was 20 runs ago on Jan 12: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So if only one good build happens in 20+ runs over 2 days... there's a problem. > Related question is: why is this test running so often? 20 itest runs in 2 days? Seems overkill, no? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25584) batch itests on macosx fail or timeout most of the time

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25584?page=com.atlassian.jira.plugi... ] Ondrej Dockal resolved JBIDE-25584. ----------------------------------- Resolution: Done > batch itests on macosx fail or timeout most of the time > ------------------------------------------------------- > > Key: JBIDE-25584 > URL: https://issues.jboss.org/browse/JBIDE-25584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Reporter: Nick Boldt > Assignee: Ondrej Dockal > Fix For: 4.5.3.AM1 > > > Not sure if we care about this since the tests pass on Win10 and RHEL7, but the Batch tests on OSX pretty consistently either timeout (120 mins) or fail. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Last good build was 20 runs ago on Jan 12: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So if only one good build happens in 20+ runs over 2 days... there's a problem. > Related question is: why is this test running so often? 20 itest runs in 2 days? Seems overkill, no? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25688) Hanging java process consuming all cpu on Zamek machine

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-25688: ------------------------------------- Summary: Hanging java process consuming all cpu on Zamek machine Key: JBIDE-25688 URL: https://issues.jboss.org/browse/JBIDE-25688 Project: Tools (JBoss Tools) Issue Type: Bug Components: qa Reporter: Ondrej Dockal Assignee: Jan Richter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25603) IOException below OCBinaryVersionValidator.getVersion (thrown in UNIXProcess.forkAndExec)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25603?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25603. --------------------------------- > IOException below OCBinaryVersionValidator.getVersion (thrown in UNIXProcess.forkAndExec) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-25603 > URL: https://issues.jboss.org/browse/JBIDE-25603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Automated Error Reporting Bot > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > The following problem was reported via the automated error reporting: > Message: Cannot run program "/": error=13, Permission denied > {noformat} > java.io.IOException: error=13, Permission denied > at java.lang.UNIXProcess.forkAndExec(UNIXProcess.java:-2) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > at org.jboss.tools.openshift.internal.core.preferences.OCBinaryVersionValidator.getVersion(OCBinaryVersionValidator.java:77) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$OCVersionUIJob.run(AdvancedConnectionEditor.java:244) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.9.0.v20170322-0013 | 3.9.1.v20170714-0547 | > | org.jboss.tools.openshift.core | 3.4.0.v20170731-2244 | 3.4.1.v20171025-1008 | > | org.jboss.tools.openshift.ui | 3.4.0.v20170802-1433 | 3.4.1.v20171025-1219 | > Operating Systems: > | Linux | 4.11.11.fc26 | 4.11.11.fc26 | > | MacOSX | 10.13.2 | 10.13.2 | > The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/59885106e4b007...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25603) IOException below OCBinaryVersionValidator.getVersion (thrown in UNIXProcess.forkAndExec)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25603?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-25603: --------------------------------------- Closing. Cannot verify as there are no steps to reproduce. > IOException below OCBinaryVersionValidator.getVersion (thrown in UNIXProcess.forkAndExec) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-25603 > URL: https://issues.jboss.org/browse/JBIDE-25603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Automated Error Reporting Bot > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > The following problem was reported via the automated error reporting: > Message: Cannot run program "/": error=13, Permission denied > {noformat} > java.io.IOException: error=13, Permission denied > at java.lang.UNIXProcess.forkAndExec(UNIXProcess.java:-2) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > at org.jboss.tools.openshift.internal.core.preferences.OCBinaryVersionValidator.getVersion(OCBinaryVersionValidator.java:77) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$OCVersionUIJob.run(AdvancedConnectionEditor.java:244) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.9.0.v20170322-0013 | 3.9.1.v20170714-0547 | > | org.jboss.tools.openshift.core | 3.4.0.v20170731-2244 | 3.4.1.v20171025-1008 | > | org.jboss.tools.openshift.ui | 3.4.0.v20170802-1433 | 3.4.1.v20171025-1219 | > Operating Systems: > | Linux | 4.11.11.fc26 | 4.11.11.fc26 | > | MacOSX | 10.13.2 | 10.13.2 | > The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/59885106e4b007...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25591) JBoss EAP 7.0 Server adapter fails to start with OpenJDK9

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25591?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25591. --------------------------------- Closing. It is not possible to select Java9 as execution environment for EAP7.0. Verified in: Red Hat JBoss Developer Studio Version: 11.3.0.AM1 Build id: AM1-v20180205-0249-B1992 Build date: 20180205-0249 > JBoss EAP 7.0 Server adapter fails to start with OpenJDK9 > --------------------------------------------------------- > > Key: JBIDE-25591 > URL: https://issues.jboss.org/browse/JBIDE-25591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: Fedora 26 > java-9-openjdk-9.0.1.11-4.fc26.x86_64 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.3.AM1 > > Attachments: .log, server.log > > > Starting of EAP 7.0 server adapter with defined Java Runtime Environment to JavaSE-9 ends up in state stopped and errors are produced. > See logs: > Server: [^server.log] > IDE: [^.log] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4649) JDK9 Certification - Runtime Detection

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4649?page=com.atlassian.jira.plugin.... ] Josef Kopriva resolved JBDS-4649. --------------------------------- Resolution: Done Resolving, I have not found any issues with Java9, please reopen, if anything changes. > JDK9 Certification - Runtime Detection > -------------------------------------- > > Key: JBDS-4649 > URL: https://issues.jboss.org/browse/JBDS-4649 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: runtime-detection > Reporter: Pavol Srna > Assignee: Josef Kopriva > Fix For: 11.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 February 2018