I suspect you are getting tripped by new additional parameters being sent
in the json payload during the bind request.
Add following to the ServiceBinding code:

@JsonIgnoreProperties(ignoreUnknown = true)

This would ignore new unknown parameters.

Rebuild the broker and redeploy and then try create service and bind.

-Sabha

On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io>
wrote:

Kumaresh,

Continue to check the logs even as you issue the bind to app. Dont stop
just with health check. Also, the logs get buffered for a bit before they
show up in the cf logs. Retry the bind (or service creation) if needed
till you see the request making it to the broker and any associated error.

-Sabha

On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com>
wrote:

Hi Sabha,

I got healthcheck passed status for haash-service-broker-app. It doesn't
show errors in logs.
What may be the problem?


Regards,
Kumaresh

On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:

Kumaresh,

Marco meant you to check the logs of your Haash service broker app
running on CF or elsewhere. If running on CF, issue cf logs
<haash-service-broker-app> and from another window try the bind again and
check the errors getting thrown by the broker.

-Sabha

On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com>
wrote:

No Marco. I got above exception when attempt to bind the service
instance with an app.

--
Sabha Parameswaran
Platform Engineering, Cloud Foundry
Pivotal, Inc.
m: +1 (415) 244-5554

--
Sabha Parameswaran
Platform Engineering, Cloud Foundry
Pivotal, Inc.
m: +1 (415) 244-5554

--
Sabha Parameswaran
Platform Engineering, Cloud Foundry
Pivotal, Inc.
m: +1 (415) 244-5554