[jbosstools-issues] [JBoss JIRA] (JBIDE-10325) Error logged when doing Run As > Run on Server on AS 7.0.2

Max Rydahl Andersen (Commented) (JIRA) jira-events at lists.jboss.org
Sat Dec 3 08:12:40 EST 2011


    [ https://issues.jboss.org/browse/JBIDE-10325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647809#comment-12647809 ] 

Max Rydahl Andersen commented on JBIDE-10325:
---------------------------------------------

Rob - I've committed basically same fix as Fred plus I actually made the code wait for the server to start (now it just reported could not load service because it connected before the server actually launched).

This code cannot ever have worked so Rob, could you please review this and say if I changed something that might have other sideeffects. Thanks!
                
> Error logged when doing Run As > Run on Server on AS 7.0.2
> ----------------------------------------------------------
>
>                 Key: JBIDE-10325
>                 URL: https://issues.jboss.org/browse/JBIDE-10325
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M5
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.3.0.M5
>
>         Attachments: as7manager.patch
>
>
> When doing Run As > Run on server on a web project, after selecting an AS 7.0.2 instance, an error is caught and logged : 
> {noformat}
> !ENTRY org.jboss.ide.eclipse.as.ui 4 0 2011-12-02 22:08:06.603
> !MESSAGE Could not acquire the management service for this JBoss installation
> !STACK 0
> java.lang.IllegalArgumentException
> 	at org.jboss.dmr.ModelValue.getChild(ModelValue.java:108)
> 	at org.jboss.dmr.ModelNode.get(ModelNode.java:798)
> 	at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.getDeploymentNames(AS71Manager.java:335)
> 	at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.hasDeployment(AS71Manager.java:328)
> 	at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.getDeploymentStateSafe(AS71Manager.java:189)
> 	at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.getDeploymentState(JBoss71ManagerService.java:79)
> 	at org.jboss.ide.eclipse.as.core.server.v7.management.JBoss7ManagerServiceProxy.getDeploymentState(JBoss7ManagerServiceProxy.java:59)
> 	at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.waitJBoss7(JBTWebLaunchableClient.java:112)
> 	at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.wait(JBTWebLaunchableClient.java:100)
> 	at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.launch2(JBTWebLaunchableClient.java:80)
> 	at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient$1.run(JBTWebLaunchableClient.java:72)
> {noformat}
> The server response in AS71Manager.getDeploymentNames contains an array of war names, but doing response.get(RESULT) throws the IAE.
> The error is then caught and logged in JBTWebLaunchableClient.waitJBoss7 under a misleading message : "Could not acquire the management service for this JBoss installation"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list