This Exception is never thrown!!
Wrong Id reference it is not LBStickinessResponse!!
Why do we need this wrapper?
> Review request for cloudstack and Vijay Venkatachalam.
> load_balancer_healthcheck_policies table will hold the data for healthcheck polices.
> commands will take the lbrule id as mandatory param and execute the action.
>   It will create monitor (tcp/http) depending upon the LB protocol.
>   NetScaler will take care of monitoring according to the monitor params.
>  Initially only one monitor is supported for an LB rule.
>  if createLBHealthCheck returns an error, it will cleanup the entry created in db.
>    LB ruleid is the mandatory param to the api.
>    DB entry in load_balancer_healthcheck_policies will be deleted.
>     LB ruleid is the mandatory param to the api.
> 	this command will list LB HealthChecks created on the LB rule.
> The time interval fo the LBHealthManager can be configured from Global Settings(healthcheck.update.interval).
> This addresses bug https://issues.apache.org/jira/browse/CLOUDSTACK-664.
> 1. create LB rule of TCP protocol and assing instances, create lb healthcheck on lb rule.
rule. HTTP monitor is created and it will binded to all the services.
services and its properties pingpath value will be present.
to the newly added service.
and service will be removed.
and monitor will get removed.
> 7.delete LB rule, lb vserver will be deleted and the monitor will be deleted.