[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20845:
--------------------------------
Fix Version/s: (was: 4.3.x)
> Unable to install breakpoint even if line number set to be generated
> --------------------------------------------------------------------
>
> Key: JBIDE-20845
> URL: https://issues.jboss.org/browse/JBIDE-20845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.CR2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
> Attachments: breakpoint-error.png, compiler-settings.png, html5-page.png, lineNumber.png
>
>
> I am unable to get breakpoints to work for a html5 project running on WildFly.
> I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error:
> Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes.
> Reason: Absent Line Number Information
> !breakpoint-error.png!
> I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has:
> org.eclipse.jdt.core.compiler.debug.lineNumber=generate
> This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same.
> I'm not really sure which component this should belong to, it looks like an upstream issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Aileen Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Aileen Cunningham edited comment on JBTIS-654 at 4/20/16 5:14 PM:
------------------------------------------------------------------
Success! Got it installed on Windows with Java 8. I now see Fuse in New menu and the Fuse cheat sheets.
It's a big improvement on the 2 phase install - now we need the new wizard to guide users through next stage.
was (Author: aileenc):
Success! Got it installed on Windows with Java 8. I now see Fuse in New menu and the Fuse cheat sheets.
It's a bit improvement on the 2 phase install - now we need the new wizard to guide users through next stage.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[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 resolved JBIDE-20798.
---------------------------------
Resolution: Done
pushed a small change to error message, but other than that I cannot replicate.
> 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
[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 commented on JBIDE-20798:
-------------------------------------
There's 3 callers for the method that attempts to get scanners. One ignores the error and returns an empty array of scanners. One will attempt 5 times before logging an error. The last API will not log errors on its own but will rethrow them up the stack to handle on their own. The callers for this third API are limited to when we shut down the server, or when we publish (publishStart will suspend scanners, publishFinish will resume scanners, for AS3 through AS6).
So it seems to me this isn't happening during startup. I also cannot replicate.
[~mmalina] can you replicate? I'll make a commit to adjust the error messaging as per max's request, but other than that, I think I'll close this issue and let you guys try to verify as well.
> 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
[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:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.4.x)
> 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
[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3848?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3848:
------------------------------------
Assignee: Rob Stryker (was: Max Rydahl Andersen)
> Server adapter types not displayed on Windows10 for JBDS 9.1.0
> --------------------------------------------------------------
>
> Key: JBDS-3848
> URL: https://issues.jboss.org/browse/JBDS-3848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 9.1.0.GA
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160414-0124-B497
> Build date: 20160414-0124
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: CDK_RHEL.png, CDK_Win10.png
>
>
> See attached screenshots - after installing 9.1.0, server adapters are seen on RHEL, not on Windows10.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[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:
--------------------------------
Fix Version/s: (was: 4.3.x)
> 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.x
>
> 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