Errors with vCD Plug-In under vCO 5.5

[kmzimm]

Hello,

I'm attempting to run the "Add a vDC" workflow under the vCD 5.1-558 plugin in vCO 5.5, and I'm receiving the following error:

Could not call sun.net.www.http.KeepAliveCache.writeObject() : Could not call sun.net.www.http.ClientVector.writeObject() : null

---- Debugging information ----

message             : Could not call sun.net.www.http.ClientVector.writeObject()

cause-exception     : java.io.NotSerializableException

cause-message       : null

-------------------------------

message             : Could not call sun.net.www.http.KeepAliveCache.writeObject()

cause-exception     : com.thoughtworks.xstream.converters.ConversionException

cause-message       : Could not call sun.net.www.http.ClientVector.writeObject() : null

-------------------------------

From the server.log:

2013-11-01 00:22:55.826+0000 [WorkflowExecutorPool-Thread-4] WARN  {mike@kmzhomenet.local:Add a vDC:46808080808080808080808080808080A880808001266312685778e677578588f:ff8080814210fce40142110a8b510027} [WorkflowItemTaskRunner] Script execution error on workflow : Add a vDC / 'Create Trigger'(item1) : Could not call sun.net.www.http.KeepAliveCache.writeObject() : Could not call sun.net.www.http.ClientVector.writeObject() : null

---- Debugging information ----

message             : Could not call sun.net.www.http.ClientVector.writeObject()

cause-exception     : java.io.NotSerializableException

cause-message       : null

-------------------------------

message             : Could not call sun.net.www.http.KeepAliveCache.writeObject()

cause-exception     : com.thoughtworks.xstream.converters.ConversionException

cause-message       : Could not call sun.net.www.http.ClientVector.writeObject() : null

It appears to be stopped at the Create Trigger action within the Wait for a task sub workflow. The creation of the vDC actually succeeds in vCD and no errors are thrown there. It worked previously without any change to the workflow as late as yesterday, but has since stopped.

I've done everything I can think of, including reinstalling vCO completely, but no luck. I'd be happy for any ideas.

[Stephan84]

Hi, I have also still issues and still an open vmware case (#13417940112).I am able to run Workflows, when I use the "Shared session" option. The wait for task event seems to stuck when "Session per user" option is configured.

My setup :

• vCO Appliance 5.5.0.1281930
• vCD plugin 5.5.0.1528081
• vCD 5.5.0.1323688

*edit*

VMware Support suggested to configure vCloud Director SSO (what I have currently not), and then use SAML Authentication + Sesseion per user Option in the vCO vCloud Director Plugin. But I had no time to change the configuration till jet.

[Slymsoft]

I use "Shared session" and have the bug so I'm not sure it's related.

I would prefer to avoid SSO integration.

If I can't find a solution then I may duplicate the workflow and remove the "Wait for task". That's the only solution I see right now.

[cdecanini_ · Accepted solution]

For those having this issue you may want to contact (or contact again) GSS. They may be able to get a newer version of the plug-in fixing this issue.

[Slymsoft]

You were right. They sent me a new version : o11nplugin-vcloud-5.5.0-1654089.vmoapp

Problem is solved for me in this version.

[qc4vmware]

I am having the same issue since updating to 5.5.1 or at least the same symptom of the "Wait for Task" just hanging.  I see all sorts of errors in the logs.  Any chance they can just post the o11nplugin-vcloud-5.5.0-1654089.vmoapp up here for easier access?  I have a case open but have yet to hear from anyone.  I'll end up calling in in the morning but right now our dev/test is completely offline.

[Stephan84]

I just installed o11nplugin-vcloud-5.5.0-1654089.vmoapp, but i have still the same problem:

I am still in contact with VMware Support.

[Slymsoft]

Did you restart the server after applying the new version ? if not, double-check build number in vCO Configuration interface and status of the plugin (maybe you still have "restart required").

[byrdog]

Can anyone confirm this plugin version o11nplugin-vcloud-5.5.0-1654089.vmoapp works with vCloud Director 5.1 and vCO 5.5? 

[Stephan84]

Yes, I restarted the whole vCO Server:

[qc4vmware]

I was finally able to get the 1654089 plugin and it cleared up my first issues as well.

Message was edited by: qc4vmware

[MarkCrossley]

I am having this issue as well when attempting to power off VMs. I have a case open (14471178804), and have upgraded the plugin to o11nplugin-vcloud-5.5.0-1780005.vmoapp

Configured to use a shared session, no saml, to the System organisation.

One further possibly related problem, I cannot add/delete/update the vCD connections with the "Plug-in Configuration" workflows, I get "Access is forbidden", but I can add/delete/update them via the plugin interface in the config service using exactly the same configuration. Once the connections are configured on the server, I can browse all the vCloud objects in the vCO inventory fine.

[jizaymes]

Where were you able to get the updated plugin from? The only version I can find is : 5.5.0.1421257

[MarkCrossley]

I got that version from the forum...  Technical Preview of VMware vCenter Orchestrator Plug-In for vCloud Director 5.5 for VMware vCenter ...

[jizaymes]

I was able to get the new version that Mark provided, and performed a complete plugin removal/reinstall (VMware KB: Uninstalling a plug-in from VMware vCenter Orchestrator ) however the 'Add a VDC' workflow is now generating a new Java error. Anyone seen this or got any resolution?

Could not call java.util.concurrent.CopyOnWriteArrayList.writeObject() : null

---- Debugging information ----

message             : Could not call java.util.concurrent.CopyOnWriteArrayList.writeObject()

cause-exception     : java.util.ConcurrentModificationException

cause-message       : null

VCO: 5.5.1 (5.5.1.1617127)

VCD Plugin: 5.5.0.1780005

[MarkCrossley]

Did you find a resolution to this, I'm now also getting that same a very similar error with the vCD 5.5.0-1780005 plugin.

This was attempting to shutdown a VM (the shutdown does actually work)

Could not call java.util.concurrent.CopyOnWriteArrayList.writeObject() : Could not call $ResourceLocalizer_1461472c650.writeReplace() : The ServiceSerializationSupport instance has not been set; this indicates that the HiveMind Registry has not been created within this JVM.

---- Debugging information ----

message             : Could not call java.util.concurrent.CopyOnWriteArrayList.writeObject()

cause-exception     : com.thoughtworks.xstream.converters.reflection.ObjectAccessException

cause-message       : Could not call $ResourceLocalizer_1461472c650.writeReplace() : The ServiceSerializationSupport instance has not been set; this indicates that the HiveMind Registry has not been created within this JVM.

-------------------------------

[jizaymes]

No updates yet. I had opened a case with VMware and they gathered the support logs and said they'd have to pick up on it with the developers. I haven't received any updates on it yet.

I've found that it actually does the operation with vCD but returns a failure which stops any future workflows from running.

Also, I've found that running the workflow through the vsphere web client, it completes cleanly.

[MarkCrossley]

OK, the dev team have provided me with build 5.5.0-1872251 which finally fixes the problems in my installation, I think it is due to go GA next week, currently in testing.

[igaydajiev]

Technical preview version of the pug-in containing all fixes to be released can be downloaded here : Technical Preview of VMware vCenter Orchestrator Plug-In for vCloud Director 5.5 for VMware vCenter ...

As of now there is no planned date for GA release of this build.

[istroh]

I can confirm that build 1872251 fixes those NotSerializableException's

[igaydajiev]

Thanks for the feedback