[JBoss JIRA] (JBIDE-9442) Investigate possibility for remote debug launch of app servers
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin... ]
Rob Stryker commented on JBIDE-9442:
------------------------------------
Here are my steps, and I cannot replicate the bug:
1) Set up a linux box with hostname hoard
2) Ensure hoard's /etc/hostname is properly set to 'hoard'
3) Ensure local machine has line in /etc/hosts that reads: 192.168.0.102 hoard
4) Create new server adapter, with hostname 'hoard'
5) Remote + FS operations
6) Point to proper wf installation on remote host, etc
7) Run in debug mode
Everything seems to work as expected :|
> Investigate possibility for remote debug launch of app servers
> --------------------------------------------------------------
>
> Key: JBIDE-9442
> URL: https://issues.jboss.org/browse/JBIDE-9442
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: new_and_noteworthy
> Fix For: 4.4.1.S116
>
>
> When launching a remote server on a remote host, we do not currently connect a remote debugger. It'd be nice if we also connected a remote debugger if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21059:
-------------------------------------
[~xcoulon] Can you provide some more detailed steps to replicate? I kinda need it spelled out for me ;)
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.1.S116
>
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22622) Opening the Web Console in the embedded browser (by default) results in error
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-22622:
-----------------------------------
Summary: Opening the Web Console in the embedded browser (by default) results in error
Key: JBIDE-22622
URL: https://issues.jboss.org/browse/JBIDE-22622
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.S116
Reporter: Fred Bricon
The Web Console opens using whatever browser is set in Eclipse (internal by default). When using the default browser, after logging in, there's an error message stating "Server connection interrupted". This error occurs on OSX and Linux at least.
I think the web console should be opened in the external browser in all cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22619:
------------------------------------
Followup to the above googledoc is this one:
https://docs.google.com/presentation/d/1LS0rL_6z_xWCHNE--tSWu_yxcdcvZTgmz...
> Decide strategy for fixversion targets in JIRA
> ----------------------------------------------
>
> Key: JBIDE-22619
> URL: https://issues.jboss.org/browse/JBIDE-22619
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.4.1.S116
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.S116
>
>
> We need to decide the strategy for milestones / fixversions in JIRA.
> One suggestion has been to align fixversions w/ sprint numbers, thus:
> * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...?
> instead of
> * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ?
> Questions/concerns:
> * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies?
> * whatever schema we adopt has to work with bzira and jiralint
> * any other systems that parse JIRA for integration purposes?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-22362:
-------------------------------------
[~adietish], [~fbricon], [~mlabuda] for now in order to make the node.js app modifiable, one needs to either change DEV_MODE to true via "Manage Environmental Variables" from Opehshift Explorer or right-click on the server adapter and choose "Restart in Debug", which will set the following environmental variables:
{code}
DEBUG=true
DEV_MODE=true
DEBUG_PORT=8787
{code}
If all other types of apps are modifiable by default than the node one should not be an exception - I can work on setting DEV_MODE to true in the server adapter
In terms of oc CLI, I put my thoughts about it in the previous comment. Basically, I do not think this is right to enable DEV_MODE by default on the image level, but if you guys think this is a must it will require updating the upstream project - https://github.com/sclorg/s2i-nodejs-container
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.S116
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22619:
----------------------------------------
This discussion refers us to the problems we are trying to solve here: https://docs.google.com/presentation/d/1yK731VGdqm62F_K8ZSt4XlAja5_Xzp-Ln...
Let's determine how important each goal is then we could just check the list of problems/goals to compare different proposals.
> Decide strategy for fixversion targets in JIRA
> ----------------------------------------------
>
> Key: JBIDE-22619
> URL: https://issues.jboss.org/browse/JBIDE-22619
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.4.1.S116
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.S116
>
>
> We need to decide the strategy for milestones / fixversions in JIRA.
> One suggestion has been to align fixversions w/ sprint numbers, thus:
> * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...?
> instead of
> * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ?
> Questions/concerns:
> * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies?
> * whatever schema we adopt has to work with bzira and jiralint
> * any other systems that parse JIRA for integration purposes?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by Daniel Atallah (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Daniel Atallah commented on JBIDE-22578:
----------------------------------------
Fortunately, I have the stdout and stderr logs too from when the above output was created (unfortunately, there doesn't appear to be anything useful).
stdout:
{noformat}
Install location:
file:/c:/lean/development/eclipse-jee-mars-R-64/
Configuration file:
file:/c:/lean/development/eclipse-jee-mars-R-64/configuration/config.ini loaded
Configuration location:
file:/c:/lean/development/eclipse-jee-mars-R-64/configuration/
Framework located:
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/org.eclipse.osgi_3.10.100.v20150529-1857.jar
Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.0.100.v20150402-1551.jar
eclipse.properties not found
Framework classpath:
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/org.eclipse.osgi_3.10.100.v20150529-1857.jar
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/org.eclipse.osgi.compatibility.state_1.0.100.v20150402-1551.jar
Splash location:
c:\lean\development\eclipse-jee-mars-R-64\\plugins\org.eclipse.platform_4.5.0.v20150603-2000\splash.bmp
Debug options:
file:/C:/lean/development/eclipse-jee-mars-R-64/.options loaded
Time to load bundles: 8
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Starting application: 1365
org.eclipse.m2e.logback.configuration: Logback config file: C:\lean\development\tms\bilbo\src\.metadata\.plugins\org.eclipse.m2e.logback.configuration\logback.1.6.0.20150526-2032.xml
org.eclipse.m2e.logback.configuration: Initializing logback
Application Started: 15597
org.jboss.ide.eclipse.as.core /finest 15/06/16 17:29.30.117 Verifying server structure
org.jboss.ide.eclipse.as.core /finest 15/06/16 17:29.30.118 Verifying jdk is available if server requires jdk
org.jboss.ide.eclipse.as.core /finer 15/06/16 17:29.31.278 Checking if a server is already started: Web Poller did not find a running server at url http://localhost:8080
{noformat}
stderr:
{noformat}
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://909.fwk66515916:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://909.fwk66515916:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_91\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:485)
at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102)
at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
at java.lang.ProcessImpl.start(ProcessImpl.java:137)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 6 more
Jun 15, 2016 5:29:38 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.1.Final
Jun 15, 2016 5:29:38 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.1.Final
Jun 15, 2016 5:29:38 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.9.Final
{noformat}
> 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: Blocker
> Fix For: 4.4.1.S116
>
> Attachments: jboss_deployment.jpg, 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
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov commented on JBIDE-22593:
-----------------------------------------
[~adietish] i've just tested it and connection dialog has the connection preselected which i recently used (more precisely: for which "Edit OpenShift Connection" was submitted most lately)
> New application wizard: preselect v3 connection that I most recently used
> -------------------------------------------------------------------------
>
> Key: JBIDE-22593
> URL: https://issues.jboss.org/browse/JBIDE-22593
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitry Bocharov
> Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.4.1.S116
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace)
> # EXEC: launch openshift wizard via File->New->OpenShift Application
> # ASSERT: connection dialog shows up
> Result:
> Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected.
> Expected result:
> Connection dialog has my v3 connection preselected, that I recently used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months