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

Abhinandan Prateek updated CLOUDSTACK-5914:
-------------------------------------------

    Description: 
The symptoms of this incompatibility issue is that vCenter session will be left 
invalid right after the vSphere 5.x API has successfully logged in our session 
to vCenter, it can caused a number of NPE or other exceptions due to it. 
replacing it with a right JRE version can fix the problem.  The problem happens 
in a lower JRE version 1.6.2x, it works fine with higher 1.6.4x version. 


The following messages are seen over and over in the log:
2013-10-17 11:06:00,120 DEBUG [agent.manager.AgentManagerImpl] 
(AgentTaskPool-13:null) Simulating start for resource 
c964ujp.int.thomsonreuters.com id 54
2013-10-17 11:06:00,120 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
(ClusteredAgentManager Timer:null) Loading directly connected host 
55(c599zht.int.thomsonreuters.com)
2013-10-17 11:06:00,128 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-286:null) Seq 32-361103401: Executing request
2013-10-17 11:06:00,141 DEBUG [vmware.resource.VmwareContextFactory] 
(ClusteredAgentManager Timer:null) initialize VmwareContext. url: 
https://C479REM.mgmt.tlrg.com/sdk/vimService, username: cloudstack, password: 
C*********************
2013-10-17 11:06:00,240 ERROR [vmware.resource.VmwareResource] 
(AgentTaskPool-13:null) VmwareResource intialize() failed due to : Exception: 
java.lang.NullPointerException
Message: null




  was:
The symptoms of this incompatibility issue is that vCenter session will be left 
invalid right after the vSphere 5.x API has successfully logged in our session 
to vCenter, it can caused a number of NPE or other exceptions due to it. 
replacing it with a right JRE version can fix the problem.  The problem happens 
in a lower JRE version 1.6.2x, it works fine with higher 1.6.4x version. 



> Unable to copy a template to primary storage, due java version in SSVM
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5914
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5914
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: SystemVM, VMware
>    Affects Versions: 4.2.0
>         Environment: vCenter version: 5.0 update 1a (Build 755629)
> 4.2
> 32 bits SystemVM templates
>            Reporter: Abhinandan Prateek
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> The symptoms of this incompatibility issue is that vCenter session will be 
> left invalid right after the vSphere 5.x API has successfully logged in our 
> session to vCenter, it can caused a number of NPE or other exceptions due to 
> it. replacing it with a right JRE version can fix the problem.  The problem 
> happens in a lower JRE version 1.6.2x, it works fine with higher 1.6.4x 
> version. 
> The following messages are seen over and over in the log:
> 2013-10-17 11:06:00,120 DEBUG [agent.manager.AgentManagerImpl] 
> (AgentTaskPool-13:null) Simulating start for resource 
> c964ujp.int.thomsonreuters.com id 54
> 2013-10-17 11:06:00,120 DEBUG [agent.manager.ClusteredAgentManagerImpl] 
> (ClusteredAgentManager Timer:null) Loading directly connected host 
> 55(c599zht.int.thomsonreuters.com)
> 2013-10-17 11:06:00,128 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-286:null) Seq 32-361103401: Executing request
> 2013-10-17 11:06:00,141 DEBUG [vmware.resource.VmwareContextFactory] 
> (ClusteredAgentManager Timer:null) initialize VmwareContext. url: 
> https://C479REM.mgmt.tlrg.com/sdk/vimService, username: cloudstack, password: 
> C*********************
> 2013-10-17 11:06:00,240 ERROR [vmware.resource.VmwareResource] 
> (AgentTaskPool-13:null) VmwareResource intialize() failed due to : Exception: 
> java.lang.NullPointerException
> Message: null



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to