Blocking Task Changes in 5.5? (Server.findAllForType() issues)

[Sirry]

I have a short script that I run to quickly kill all tasks that I have running in vCD for testing purposes.

it is as follows:

var blockingTasks = Server.findAllForType("vCloud:BlockingTask");

for each (var bt in blockingTasks)

{

    bt.abort("");

}

I am currently trying to migrate into a 5.5 environment from a 5.1 environment. When I run this exact same script in the new environment, it throws an error:

[2014-05-08 18:18:10.803] [I] Server error : ch.dunes.model.sdk.SDKFinderException: Unable to execute 'fetchAll' for type : BlockingTask

I don't see any deprecation in the documentation, so I assume I am doing something wrong.... can anyone help me?

[Sirry]

An update since I realized I didn't post much information....

I am running on vCenter, vCD, vCO 5.5 with vCD plugin 5.5.0.1421257

I was able to print out a captured AMQP message, showing that the type does indeed exist....

<vmext:EntityLink rel="entity" type="vcloud:blockingTask" name="vdcInstantiateVapp" id="urn:vcloud:blockingTask:9188ea53-0fe3-486e-9955-5b1d1d930350"/>

[cdecanini_]

It does not look good, seems the findAll method in the plug-in is broken. Maybe you can list these using the query service as an alternative. In the meantime you should contanct GSS to have them verify that the plug-in has an issue.

[Sirry]

Thank you; how would I list these using a query service? By GSS, you mean the support services, right? Should I try to re-install the plugin first at the very least?

[Sirry]

Also, have you tried your Notifications package for 5.5? I am getting some really strange output...

my scripts have the same start as your notifications package example

props = subscription.retrieveLastOnMessageTrigger();

var broker = Server.getCustomProperty(subscription, "broker");

messageBody = props.get('body');  

var headers = props.get('headers');  

var properties = props.get('properties');

I used to get xml values for messageBody, headers, and properties, but now with this code,

dLog("Prop Keys:" + props.keys,1);

dLog("Props:" + props,1);

dLog("messageBody:" + messageBody,1);

dLog("headers:" + headers,1);

dLog("properties:" + properties,1);

I get this:

[2014-05-09 11:47:27.570] [I] Prop Keys:body,properties,headers_,properties_,headers

[2014-05-09 11:47:27.571] [I] Props:Properties:1004860662

[2014-05-09 11:47:27.571] [I] messageBody:<?xml version="1.0" encoding="UTF-8"?>

<vmext:Notification xmlns:vmext="http://www.vmware.com/vcloud/extension/v1.5" type="com/vmware/vcloud/event/blockingtask/create" eventId="1875217b-91ea-4c82-a2c2-0d71cf3f2d6f" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/extension/v1.5 http://myserver.corp/api/v1.5/schema/vmwextensions.xsd">

    <vmext:Link rel="entityResolver" href="https://yp-vcd55.kingstonlab.corp/api/entity/"/>

    <vmext:EntityLink rel="entity" type="vcloud:blockingTask" name="vdcInstantiateVapp" id="urn:vcloud:blockingTask:d8e74eba-6bef-4e59-9aa2-e86a0896d329"/>

    <vmext:EntityLink rel="down" type="vcloud:user" name="system" id="urn:vcloud:user:45995325-5704-4454-a6da-1924e5e42767"/>

    <vmext:EntityLink rel="up" type="vcloud:org" name="LAB-TestOrg" id="urn:vcloud:org:e6335d1f-5d8d-4d78-a195-fdd502efc819"/>

    <vmext:EntityLink rel="task" type="vcloud:task" name="vdcInstantiateVapp" id="urn:vcloud:task:dc595374-418c-4a3f-bbcc-e17497f1694f"/>

    <vmext:EntityLink rel="task:owner" type="vcloud:vapp" id="urn:vcloud:vapp:9636d671-34c7-4377-bbac-d75b3d9780e3"/>

    <vmext:Timestamp>2014-05-09T11:47:23.376-07:00</vmext:Timestamp>

    <vmext:OperationSuccess>true</vmext:OperationSuccess>

</vmext:Notification>

[2014-05-09 11:47:27.571] [I] headers:Properties:881746226

[2014-05-09 11:47:27.572] [I] properties:Properties:1871656082

[Sirry]

Is there a way to re-install vCO without needing to reinstall/reconfigure the vCenter server that it is on? I want to make sure that the vCO server isn't corrupted... it has some sporadic unexpected behavior that is causing me to think that there may be some corrupted files.

[iiliev]

Yes, you can install/re-install vCO using vCO installer executable bundled in vCenter ISO image. Once you have the vCenter ISO image file, you can open it with some program that can read ISO archives (WinRar, WinZip, 7-zip, etc). The Orchestrator installer executable is located at \vCenter-Server\vCO\vCenterOrchestrator.exe

Another option would be to deploy vCO appliance.

[mcfadyenj]

you can export the configuration and apply it to a new build. but you will still need to upload all the plugins etc.

you can also reload all the plugins from the troubleshooting menu.

notifications is not supported on 5.5 however I use it anyway and found there were some issues with integrating it. I didnt write it all down but I recall you need a specific version of the amqp plugin to process the content from vcd correctly.