Has Apigee fixed anything for Assign Message policy between 4.14.07.03 and 4.15.07.00 private cloud releases.

[#1]

Posting this on behalf of a customer.

For a proxy we are working on Assign Message policy is failing with the following error message on 4.14.07.03.

{"Envelope":{"encodingStyle":"http:\/\/schemas.xmlsoap.org\/soap\/encoding\/","Body":{"Fault": {"faultcode":"soap:Server","faultstring":"com.apigee.jsonparser.JSONArray cannot be cast to java.lang.String","faultactor":{},"detail":{"source": {"errorcode":"Internal Server Error"}}}}}}

But now on on 4.15.07.00 this proxy is working fine with no issues. Can we get a confirmation that there was a known issue with this policy fixed between these releases. We want to ensure that's the case before we upgrade our production environment to a more recent version.

[mschreuder]

@Aravind Kumar Tadakamalla,

The best way to confirm what has been fixed is to review the release notes, you can get those for Private Cloud and Public Cloud here.

You would need to start by looking in the .00 releases since 4.14.07.03, i.e.:

4.15.01.00 Make sure to also follow the links in the "Bugs Fixed" section.

4.15.04.00 Make sure to also follow the links in the "Bugs Fixed" section.

4.15.07.00 This one lists the whole release content in one page.

[adas]

@Aravind Kumar Tadakamalla Yes, release notes for private cloud would be the right thing to look at. However, please note that not all bugs that get fixed in a release are mentioned in the release notes. The release notes only captures those issues/bugs which were reported by customers, or have a major implication such as security, backward compatibility etc. We might have fixed certain bugs which were reported by our internal testing, those would not show up in the release notes.

[adas]

@Aravind Kumar Tadakamalla I just looked through JIRA and seems like this could be related to APIRT-1550 which was fixed earlier this year around Mar-Apr 2015. The fix should be available in 1507 which confirms their observation too. You can find more details about that issue in JIRA.