April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22227: -------------------------------- Story Points: 10 > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22227. --------------------------------- Resolution: Done > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22120) CDK plugin description is outdated

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22120?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22120: -------------------------------- Story Points: 1 > CDK plugin description is outdated > ---------------------------------- > > Key: JBIDE-22120 > URL: https://issues.jboss.org/browse/JBIDE-22120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Trivial > Fix For: 4.4.0.Alpha1 > > > JBIDE-22047 changed the cdk feature to tech preview. > While verifying that, I noticed that the cdk plugin has a very much different name and description - see that JIRA for screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20798) log filling up with "unable to retrieve a list of remote deployments"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20798?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20798: -------------------------------- Story Points: 1 > log filling up with "unable to retrieve a list of remote deployments" > --------------------------------------------------------------------- > > Key: JBIDE-20798 > URL: https://issues.jboss.org/browse/JBIDE-20798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > Attachments: Java_EE_-_JBoss_EAP_6_4_-_Eclipse_-__Users_max_Documents_workspace-deploy-demo.png > > > when starting/stopping EAP 6.4 server I 'm getting my logs filled with: > {code} > Unable to retrieve a list of remote deployment scanners > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [ > {"subsystem" => "deployment-scanner"}, > {"scanner" => "*"} > ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available". > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361) > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:236) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:234) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:122) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDefaultDeploymentScanner(AS7DeploymentScannerUtility.java:212) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadDefaultScannerFromServer(LocalJBoss7DeploymentScannerAdditions.java:148) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersAdded(LocalJBoss7DeploymentScannerAdditions.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.updateDeploymentScanners(AbstractDeploymentScannerAdditions.java:61) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions$1.run(AbstractDeploymentScannerAdditions.java:74) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [ > {"subsystem" => "deployment-scanner"}, > {"scanner" => "*"} > ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available". > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352) > ... 15 more > {code} > since these are done during startup and it is possible to see in the error then I would expect we did not log this by default for this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3758: ----------------------------- > when something goes wrong, give user call to action / report of what went wrong > ------------------------------------------------------------------------------- > > Key: JBDS-3758 > URL: https://issues.jboss.org/browse/JBDS-3758 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png > > > I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS. > I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached). > If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ? > Also, should there be a call to action for the user? > Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3761: ----------------------------- > when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3761 > URL: https://issues.jboss.org/browse/JBDS-3761 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.GA > > Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png, vbox-install-omits-guestadditions.png > > > I had Virtual Box 5.0.16 installed. > The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox. > As a result, my existing VB install cannot find the Guest Additions iso image. > !vbox-install-omits-guestadditions.png! > I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox. > Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3761: -------------------------------- > when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3761 > URL: https://issues.jboss.org/browse/JBDS-3761 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.GA > > Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png, vbox-install-omits-guestadditions.png > > > I had Virtual Box 5.0.16 installed. > The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox. > As a result, my existing VB install cannot find the Guest Additions iso image. > !vbox-install-omits-guestadditions.png! > I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox. > Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3807) Create detailed-description and manual-instructions for devplatform installer exe in CSP

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3807?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3807: ----------------------------- > Create detailed-description and manual-instructions for devplatform installer exe in CSP > ---------------------------------------------------------------------------------------- > > Key: JBDS-3807 > URL: https://issues.jboss.org/browse/JBDS-3807 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, documentation, installer, platform-installer > Affects Versions: 9.1.0.CR1, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.1.GA, 10.0.0.Alpha1 > > > Release engineering requires two documents to be produced as metadata for each artifact published in the CSP. > * detailed-description > * manual-instructions > We can keep this simple, or we can include details about min/recommended disk/RAM settings, link to CDK getting started page, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3807) Create detailed-description and manual-instructions for devplatform installer exe in CSP

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3807?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3807: -------------------------------- > Create detailed-description and manual-instructions for devplatform installer exe in CSP > ---------------------------------------------------------------------------------------- > > Key: JBDS-3807 > URL: https://issues.jboss.org/browse/JBDS-3807 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, documentation, installer, platform-installer > Affects Versions: 9.1.0.CR1, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.1.GA, 10.0.0.Alpha1 > > > Release engineering requires two documents to be produced as metadata for each artifact published in the CSP. > * detailed-description > * manual-instructions > We can keep this simple, or we can include details about min/recommended disk/RAM settings, link to CDK getting started page, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3642: ----------------------------- > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016