March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24006: -------------------------------- Sprint: devex #129 March 2017 > Wildfly server adapter does not report error and works inconsistently > --------------------------------------------------------------------- > > Key: JBIDE-24006 > URL: https://issues.jboss.org/browse/JBIDE-24006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: server, server_adapter, wildfly > Fix For: 4.4.4.AM2 > > > If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work. > Here is an except we've got from the customer: > {noformat} > I have an important update on this. I think it's mostly good news. > I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict. > I tried the same thing on Eclipse with exactly the same results. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23785) WF11 server adapter needed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23785?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23785: -------------------------------- Sprint: devex #129 March 2017 > WF11 server adapter needed > --------------------------- > > Key: JBIDE-23785 > URL: https://issues.jboss.org/browse/JBIDE-23785 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > WF 11 server adapter needed. THis may require a new set of jars (or may not). Current test of wf11 nightly build seems to work with mgmt, no significant changes, but that can break. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23872: -------------------------------- Sprint: devex #129 March 2017 > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Assignee: Rob Stryker > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: publish.log > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23784: -------------------------------- Sprint: devex #129 March 2017 > WF 11 / EAP 7.1 Incremental MGMT publishing > ------------------------------------------- > > Key: JBIDE-23784 > URL: https://issues.jboss.org/browse/JBIDE-23784 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM2 > > > WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion. > WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4181) No valid JDK found

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4181: ------------------------------ Sprint: devex #129 March 2017 > No valid JDK found > ------------------ > > Key: JBDS-4181 > URL: https://issues.jboss.org/browse/JBDS-4181 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: common, upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 24, > openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode) > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 10.x > > > When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log > {code} > java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs. > java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs. > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22578: -------------------------------- Sprint: devex #129 March 2017 > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.Final > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23057) Integration tests: test import project in server adapter wizard

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23057?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-23057: ---------------------------------- Assignee: Radim Hopp (was: Andre Dietisheim) > Integration tests: test import project in server adapter wizard > --------------------------------------------------------------- > > Key: JBIDE-23057 > URL: https://issues.jboss.org/browse/JBIDE-23057 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Radim Hopp > Fix For: 4.5.0.AM1 > > > JBIDE-22621 allows the user to import a project in the server adapter wizard. We should add an integration test for this scenarion in CreateServerAdapterTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24083: ------------------------------------- Story Points: 8 > Debug NodeJS app is broken - Failed to connect to Standalone V8 VM > ------------------------------------------------------------------ > > Key: JBIDE-24083 > URL: https://issues.jboss.org/browse/JBIDE-24083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Assignee: Andre Dietisheim > Priority: Critical > Labels: regression > Fix For: 4.4.4.AM2 > > Attachments: jbide-23961-restart-1.png > > > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24081) runtime detection for cdk 3 via minishift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24081?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24081: ------------------------------- Sprint: devex #129 March 2017 > runtime detection for cdk 3 via minishift > ----------------------------------------- > > Key: JBIDE-24081 > URL: https://issues.jboss.org/browse/JBIDE-24081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection > Affects Versions: 4.4.4.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > CDK3 has no runtime detection support -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23828) Move jst.reddeer plugin from integration-tests to jbosstools-jst

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23828?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-23828. ------------------------------ > Move jst.reddeer plugin from integration-tests to jbosstools-jst > ----------------------------------------------------------------- > > Key: JBIDE-23828 > URL: https://issues.jboss.org/browse/JBIDE-23828 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, jst > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > > refactoring / repackaging will be needed, CQ probably as well -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017