June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23993) Reverse engineering editor generates duplicate ID values

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23993?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-23993: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.4.Final) > Reverse engineering editor generates duplicate ID values > -------------------------------------------------------- > > Key: JBIDE-23993 > URL: https://issues.jboss.org/browse/JBIDE-23993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.3.Final > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.5.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1122) Update SOARequirements.xsd file

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1122?page=com.atlassian.jira.plugin... ] Tomáš Sedmík closed JBTIS-1122. ------------------------------- verified > Update SOARequirements.xsd file > ------------------------------- > > Key: JBTIS-1122 > URL: https://issues.jboss.org/browse/JBTIS-1122 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.3.3.Final > > Attachments: SOARequirements.xsd > > > I introduced Fuse requirement type (because we want to use camelVersion definition on Fuse on EAP runtimes). Updated XSD file is in the attachment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22717) Remove all server log view code

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22717?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22717. --------------------------------- Confirmed, Server Log view is no more. Verified in devstudio-11.0.0.AM1-v20170601-1252-B198-installer-standalone.jar > Remove all server log view code > ------------------------------- > > Key: JBIDE-22717 > URL: https://issues.jboss.org/browse/JBIDE-22717 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.5.0.AM1 > > > Follow up on: https://issues.jboss.org/browse/JBIDE-22635 > Remove the deprecated classes and extension points. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24186) Eclipse workspace deadlocking during refresh/rebuild

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24186?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24186. --------------------------------- Closing. Feel free to reopen. > Eclipse workspace deadlocking during refresh/rebuild > ---------------------------------------------------- > > Key: JBIDE-24186 > URL: https://issues.jboss.org/browse/JBIDE-24186 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server > Affects Versions: 4.4.3.Final > Reporter: Beirti O'Nunain > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > - Windows 7 > - Eclipse Neon.2 (4.6.2) > - Developer Studio 10.3.0 > After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane: > + "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'" > + Updating Maven Project (Waiting) > + Updating Maven Project (Waiting) > + Updating Maven Project (Waiting) > + Updating Maven Project (Waiting) > .... > The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace. > Profiling with yourkit detects a deadlock in the following thread: > Worker-33 <--- Frozen for at least 8m 27s > org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526 > org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035 > org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228 > org.eclipse.core.internal.jobs.Worker.run() Worker.java:55 > I started profiling Yourkit when the build hung. It shows the following as the live call stack: > Call Tree Time (ms) Level > <All threads> 530944 1 > org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2 > org.eclipse.equinox.launcher.Main.run(String[]) 436 2 > org.eclipse.core.internal.jobs.Worker.run() 421 2 > I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed > Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs: > Frozen threads found (potential deadlock) > It seems that the following threads have not changed their stack for more than 10 seconds. > These threads are possibly (but not necessarily!) in a deadlock or hung. > main <--- Frozen for at least 2m 21s > org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527 > org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150 > org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112 > org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69 > org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206 > org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273 > org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297 > org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259 > org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108 > org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92 > org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67 > org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126 > org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42 > org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123 > org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121 > org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231 > org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56 > org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228 > org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114 > org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343 > org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358 > org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31 > org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450 > org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158 > org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42 > org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50 > org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173 > org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155 > org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191 > org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229 > org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258 > org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242 > org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236 > org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405 > org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84 > org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418 > org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079 > org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236 > org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824 > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121 > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336 > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022 > org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150 > org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693 > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336 > org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610 > org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148 > org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138 > org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196 > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134 > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104 > org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388 > org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243 > sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native) > sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62 > sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43 > java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498 > org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673 > org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610 > org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519 > Worker-33 <--- Frozen for at least 14m 43s > org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526 > org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035 > org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228 > org.eclipse.core.internal.jobs.Worker.run() Worker.java:55 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24520) Server editor says I need a valid shutdown poller, but I didn't touch it

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24520?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24520. --------------------------------- Verified in the simplified form - with a local EAP 7.0. It's fixed now. (devstudio-11.0.0.AM1-v20170601-1252-B198-installer-standalone.jar) > Server editor says I need a valid shutdown poller, but I didn't touch it > ------------------------------------------------------------------------ > > Key: JBIDE-24520 > URL: https://issues.jboss.org/browse/JBIDE-24520 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > I just wanted to test the EAP 7.1 adapter in devstudio 11 (devstudio-11.0.0.AM1-v20170529-1745-B180-installer-standalone.jar) and I got surprised by this error when I opened the server editor and then tried to save it: > The server cannot be saved for the following reasons: > [Overview] Your server must have a valid shutdown poller selected. > In fact both startup and shutdown pollers are empty, not sure why. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24483) Incremental mgmt tests for wf11

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24483?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24483. --------------------------------- The new test is in master. But it's not run in jenkins, in fact none of the itests is being executed. I created JBIDE-24535 > Incremental mgmt tests for wf11 > ------------------------------- > > Key: JBIDE-24483 > URL: https://issues.jboss.org/browse/JBIDE-24483 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Need an incremental mgmt test that uses our server adapter and service to deploy incrementally. It doesn't need to be a full test using the management publisher, but it should be a test of the service at least. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24535) itests are not run for server in Jenkins

by Martin Malina (JIRA)

Martin Malina created JBIDE-24535: ------------------------------------- Summary: itests are not run for server in Jenkins Key: JBIDE-24535 URL: https://issues.jboss.org/browse/JBIDE-24535 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.5.0.AM1 Reporter: Martin Malina Assignee: Rob Stryker I wanted to verify JBIDE-24483 which added itests for incremental deployment via management. But it turns out none of the itests are run here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Shouldn't they be run? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23835) jbosstools .it.smoke tests fail, abort, or are unstable.

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23835?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-23835: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > jbosstools .it.smoke tests fail, abort, or are unstable. > -------------------------------------------------------- > > Key: JBIDE-23835 > URL: https://issues.jboss.org/browse/JBIDE-23835 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.5.0.AM2 > > > All of the .it.smoke tests listed in this buildflow job [1] result in either an unstable build, a failed build, or an aborted build. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We need to get these jobs to green or they're meaningless as a measurement tool at the end of every sprint. > {code}aerogear.it.smoke #14 completed: UNSTABLE > batch.it.smoke #2 completed: FAILURE > browsersim.it.smoke #15 completed: FAILURE > cdi.it.smoke #15 completed: FAILURE > cdk.devstudio.it.smoke #2 completed: UNSTABLE > central.it.smoke #184 completed: FAILURE > docker.it.smoke #192 completed: UNSTABLE > examples.javaee.it.smoke #30 completed: FAILURE > forge.it.smoke #24 completed: ABORTED > freemarker.it.smoke #3 completed: ABORTED > hibernate.it.smoke #18 completed: ABORTED > jax-rs.it.smoke #5 completed: ABORTED > jax-ws.it.smoke #5 completed: ABORTED > jsf.it.smoke #3 completed: FAILURE > jst.it.smoke #42 completed: FAILURE > livereload.it.smoke #8 completed: FAILURE > maven.it.smoke #33 completed: FAILURE > vpe.it.smoke #7 completed: FAILURE > websocket.it.smoke #4 completed: FAILURE > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24220) Run itests with RedDeer 2.0

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24220?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-24220: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Run itests with RedDeer 2.0 > --------------------------- > > Key: JBIDE-24220 > URL: https://issues.jboss.org/browse/JBIDE-24220 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Pavol Srna > Assignee: Rastislav Wagner > Fix For: 4.5.0.AM2 > > > Use jbosstools-4.4.x-reddeer-2.0 branch in jbosstools-integration-tests repository. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24263) run hibernate with reddeer2

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24263?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-24263: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > run hibernate with reddeer2 > --------------------------- > > Key: JBIDE-24263 > URL: https://issues.jboss.org/browse/JBIDE-24263 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.5.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017