May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25923: --------------------------------------- [~mmalina] I tried playing around the issue and steps to reproduce and could not reproduce. So it seems fine for me. > Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over > ------------------------------------------------------------------------------------ > > Key: JBIDE-25923 > URL: https://issues.jboss.org/browse/JBIDE-25923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.Final > Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.6.0.AM1 > > Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif > > > When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log: > {code} > 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml") > 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml") > 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml") > 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms > 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml") > 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms > 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml") > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25821) Automate building of Nexus instance

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25821?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25821. --------------------------------- Resolution: Done [~jrichter1] have finished this. Closing. > Automate building of Nexus instance > ----------------------------------- > > Key: JBIDE-25821 > URL: https://issues.jboss.org/browse/JBIDE-25821 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-platform > Affects Versions: 4.5.3.AM3 > Reporter: Lukáš Valach > Assignee: Jan Richter > Fix For: 4.6.0.AM2 > > > There is Nexus server named 'rhel-nexus' running on openstack \[1\]. It has been made by hand, but the creation process should be automated. > \[1\] https://ci-rhos.centralci.eng.rdu2.redhat.com -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25821) Automate building of Nexus instance

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25821?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25821: ---------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite/merg..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m... (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite/merg...) > Automate building of Nexus instance > ----------------------------------- > > Key: JBIDE-25821 > URL: https://issues.jboss.org/browse/JBIDE-25821 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-platform > Affects Versions: 4.5.3.AM3 > Reporter: Lukáš Valach > Assignee: Jan Richter > Fix For: 4.6.0.AM2 > > > There is Nexus server named 'rhel-nexus' running on openstack \[1\]. It has been made by hand, but the creation process should be automated. > \[1\] https://ci-rhos.centralci.eng.rdu2.redhat.com -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25821) Automate building of Nexus instance

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25821?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-25821: ------------------------------------- Assignee: Jan Richter (was: Vojtech Prusa) > Automate building of Nexus instance > ----------------------------------- > > Key: JBIDE-25821 > URL: https://issues.jboss.org/browse/JBIDE-25821 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-platform > Affects Versions: 4.5.3.AM3 > Reporter: Lukáš Valach > Assignee: Jan Richter > Fix For: 4.6.0.AM2 > > > There is Nexus server named 'rhel-nexus' running on openstack \[1\]. It has been made by hand, but the creation process should be automated. > \[1\] https://ci-rhos.centralci.eng.rdu2.redhat.com -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25821) Automate building of Nexus instance

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25821?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25821: ---------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.x) > Automate building of Nexus instance > ----------------------------------- > > Key: JBIDE-25821 > URL: https://issues.jboss.org/browse/JBIDE-25821 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-platform > Affects Versions: 4.5.3.AM3 > Reporter: Lukáš Valach > Assignee: Jan Richter > Fix For: 4.6.0.AM2 > > > There is Nexus server named 'rhel-nexus' running on openstack \[1\]. It has been made by hand, but the creation process should be automated. > \[1\] https://ci-rhos.centralci.eng.rdu2.redhat.com -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26035) Convert SSP to function in an osgi environment

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26035?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-26035: -------------------------------- Summary: Convert SSP to function in an osgi environment (was: Conversion to OSGi not going so well) > Convert SSP to function in an osgi environment > ---------------------------------------------- > > Key: JBIDE-26035 > URL: https://issues.jboss.org/browse/JBIDE-26035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.6.0.AM2 > > > {code} > mkdir felix > cd felix > wget http://download.nextag.com/apache/felix/org.apache.felix.main.distributio... > unzip org.apache.felix.main.distribution-5.6.10.zip > cd ../ > git clone git@github.com:robstryker/org.jboss.tools.ssp.git > cd org.jboss.tools.ssp > git checkout osgi_branch1 > mvn clean install > #cp api/target/org.jboss.tools.ssp.api-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/ > #cp launching/target/org.jboss.tools.ssp.launching-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle > #cp server-spi/target/org.jboss.tools.ssp.server.spi-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/ > #cp server/target/org.jboss.tools.ssp.server-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/ > du -ah | grep "jar$" | grep "target/" | grep -v "test-classes" | grep -v "classes/" | grep -v "schema" | grep -v "client" | cut -c 1,2,3,4 --complement | awk '{ print "cp " $0 " ../felix/felix-framework-5.6.10/bundle/";}' | sh > cd ../felix/felix-framework-5.6.10/ > java -jar bin/felix.jar > {code} > Note error: > API Bundle Started > Launching Bundle Started > Server bundle started > ERROR: Bundle org.jboss.tools.ssp.server.wildfly [11] Error starting file:/home/rob/tmp/ssp_osgi/felix/felix-framework-5.6.10/bundle/org.jboss.tools.ssp.server.wildfly-0.8-SNAPSHOT.jar (org.osgi.framework.BundleException: Activator start error in bundle org.jboss.tools.ssp.server.wildfly [11].) > java.lang.NoClassDefFoundError: org/osgi/framework/BundleActivator > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007) > This is very strange. All the other bundles start fine. This bundle can't even find its osgi classes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25905: ------------------------------------------ postponing to 4.6.0.AM3 > [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25905 > URL: https://issues.jboss.org/browse/JBIDE-25905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.6.0.AM3 > > Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png > > > [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard. > Service Ports table starts to behave awkward after reset. > steps: > # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports) > # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu > # ASSERT: "Deploy Image to OpenShift" wizard shows up > # EXEC: get to the "Services & Routing Settings" page > # ASSERT: all ports are listed, a port is checked in column "Used by route" > !services-routing-page.png! > # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports) > # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry) > Result: > Labels for columns "Name", "Service Port", "Pod Port" disappear > !services-routing-page-no-labels.png! > !service-ports.gif! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25905: ------------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.x) > [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25905 > URL: https://issues.jboss.org/browse/JBIDE-25905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.6.0.AM3 > > Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png > > > [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard. > Service Ports table starts to behave awkward after reset. > steps: > # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports) > # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu > # ASSERT: "Deploy Image to OpenShift" wizard shows up > # EXEC: get to the "Services & Routing Settings" page > # ASSERT: all ports are listed, a port is checked in column "Used by route" > !services-routing-page.png! > # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports) > # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry) > Result: > Labels for columns "Name", "Service Port", "Pod Port" disappear > !services-routing-page-no-labels.png! > !service-ports.gif! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25905: ------------------------------------------ I looked into the code. The bug isn't obvious at all, it looks as if it's a databinding problem. In the code you'll find the following comment pointing to a workaround that was implemented {code:title=DeployImageWizardModel#updateServicePort} final int pos = this.servicePorts.indexOf(source); if (pos > -1) { List<IServicePort> old = new ArrayList<>(this.servicePorts); this.servicePorts.set(pos, target); /** * databinding would not replace old object with a new one if only a * boolean property is modified. I could not understand why it is * so, but I found that when target port (String) and route port * (Boolean) are changed in Edit dialog together, everything works. * * @see https://github.com/jbosstools/jbosstools-openshift/pull/1365 */ String p = target.getTargetPort(); target.setTargetPort("dummy"); fireIndexedPropertyChange(PROPERTY_SERVICE_PORTS, pos, old, Collections.unmodifiableList(servicePorts)); if (((ServicePortAdapter) target).isRoutePort()) { setRoutingPort(target); } else if (((ServicePortAdapter) source).isRoutePort() && !((ServicePortAdapter) target).isRoutePort()) { setRoutingPort(null); } target.setTargetPort(p); } {code} The linked github [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1365] shows similar screenshots like the one in this jira. > [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25905 > URL: https://issues.jboss.org/browse/JBIDE-25905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.6.0.AM3 > > Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png > > > [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard. > Service Ports table starts to behave awkward after reset. > steps: > # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports) > # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu > # ASSERT: "Deploy Image to OpenShift" wizard shows up > # EXEC: get to the "Services & Routing Settings" page > # ASSERT: all ports are listed, a port is checked in column "Used by route" > !services-routing-page.png! > # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports) > # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry) > Result: > Labels for columns "Name", "Service Port", "Pod Port" disappear > !services-routing-page-no-labels.png! > !service-ports.gif! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26037) Deploy Docker Wizard: always prompt to create a new connection, does not preselect most recently used connection

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-26037: ---------------------------------------- Summary: Deploy Docker Wizard: always prompt to create a new connection, does not preselect most recently used connection Key: JBIDE-26037 URL: https://issues.jboss.org/browse/JBIDE-26037 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.6.0.AM2 Reporter: Andre Dietisheim Attachments: image-2018-05-23-22-51-38-221.png steps: # ASSERT: make sure that you have at least 1 connection to a OpenShift server defined # ASSERT: do some operations involving your existing connection (ex. open children for it in OpenShift Explorer) # EXEC: in "Docker Explorer": select an image and pick in the context menu "Deploy to OpenShift..." Result: You get prompted to create a <New Connection> !image-2018-05-23-22-51-38-221.png! If you unfold the "Connection" combo box to list all connections you discover your connection and can pick it instead of the suggested <New Connection> Expected result: The connection page shows up with the most recently connection preselected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 May 2018