[
https://issues.apache.org/jira/browse/CLOUDSTACK-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587471#comment-13587471
]
Kelven Yang commented on CLOUDSTACK-1173:
-----------------------------------------
This issue was slipped due to one slight difference between maven build and
previous ant build system. With current maven build system, the patch of
systemvm ISO is not triggered at per build basis. It seems that it is triggered
when release number changes. Therefore, the broken changes was not immediately
noticed as my host had an old copy of the patch ISO.
If you are running XS hypervisor host, to verify the bug, you need to clear the
XS CloudStack version tag.
> ConsoleProxyResource instantiation exception
> --------------------------------------------
>
> Key: CLOUDSTACK-1173
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1173
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VNC Proxy
> Affects Versions: 4.1.0
> Environment: devcloud
> Reporter: Marcus Sorensen
> Assignee: Kelven Yang
> Priority: Blocker
> Fix For: 4.1.0
>
>
> Looks like ConsoleProxy software is not coming up in the latest branches:
> log4j:WARN No appenders could be found for logger
> (org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Unable to start agent: Instantiation excetion when loading resource:
> com.cloud.agent.resource.consoleproxy.ConsoleProxyResource due to:
> java.lang.InstantiationException
--
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
