4:09 p.m.
[
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)
3652
days inactive
3652
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Rob Stryker (JIRA)