[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mice Xia resolved CLOUDSTACK-204.
---------------------------------

    Resolution: Fixed

changing thie global config and allow to accept UUID of a system offering, if 
failed to find system offering with this UUID, use default one.

commit in master 
7e751405377622d133b5ab240e35a3292741f4ef
2da5b448a1e5024dda6d24aa68a1f08b1734ae52
                
> Setting global config 'consoleproxy.service.offering' causes mgmt failed to 
> start
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-204
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-204
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Management Server
>    Affects Versions: pre-4.0.0
>            Reporter: Mice Xia
>            Assignee: Mice Xia
>             Fix For: pre-4.0.0
>
>
> [reproduce steps]
> setting global config consoleproxy.service.offering to an existing system 
> service offering like 'testOffering'
> restart mgmt server serivce
> [observed result]
> mgmt server failed start, 
> [log]
> Unable to load configuration for management-server from components.xml
> java.lang.NumberFormatException: For input string: ""
>         at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>         at java.lang.Long.parseLong(Long.java:450)
>         at java.lang.Long.parseLong(Long.java:478)
>         at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.configure(ConsoleProxyManagerImpl.java:1518)
>         at
> com.cloud.utils.component.ComponentLocator.configureManagers(ComponentLocator.java:428)
>         at
> com.cloud.utils.component.ComponentLocator.parse(ComponentLocator.java:215)
>         at
> com.cloud.utils.component.ComponentLocator.getLocatorInternal(ComponentLocator.java:812)
>         at
> com.cloud.utils.component.ComponentLocator.getLocator(ComponentLocator.java:850)
>         at
> com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:46)
>         at javax.servlet.GenericServlet.init(GenericServlet.java:212)
>         at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
>         at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
>         at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4187)
>         at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4496)
>         at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
>         at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
>         at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
>         at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
>         at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
>         at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
>         at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
>         at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
>         at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>         at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to