Layer7 API Management

  • Private Community

  • 1.  Issue with Policy Manager after setting cluster parameter 'xslt.engine.force20' to True

    Posted Apr 02, 2015 02:54 AM

    Hi,

     

    We tried setting 'xslt.engine.force20' cluster parameter value to true .After a while the policy manager went down and after restart,few of the utilies like oauth started giving java null pointer exception.

    After setting xslt.engine.force20 to false,things went back to normal.

    Can you please explain why XSL 2.0 engine affected the policy manager,performance so much.Are their any recommendations on setting this cluster property.

     

    Regards,

    Sonalee Shyam



  • 2.  Re: Issue with Policy Manager after setting cluster parameter 'xslt.engine.force20' to True

    Posted Apr 02, 2015 04:23 AM

    Just to add on to it,the gateway version we are using is 8.1.1



  • 3.  Re: Issue with Policy Manager after setting cluster parameter 'xslt.engine.force20' to True

    Posted Apr 17, 2015 04:08 PM

    Anyone up to the challenge of answering this question?

     

    Thanks!



  • 4.  Re: Issue with Policy Manager after setting cluster parameter 'xslt.engine.force20' to True

    Posted Apr 17, 2015 05:00 PM

    I think this is something to ask support. Sounds like a bug to me. You could check the release notes for the newer gateway versions to see if anything like this was fixed. Is there any reason you have not upgraded to a more recent version of the gateway?



  • 5.  Re: Issue with Policy Manager after setting cluster parameter 'xslt.engine.force20' to True
    Best Answer

    Posted Apr 28, 2015 06:00 PM

    Hi, Sonalee.

     

    As Michiel notes, a new case with support (api-support@ca.com) should probably be opened up for this.

     

    The Release Notes for version 8.2 of the API Gateway state in part:  "Corrected an issue with XSLT 2.0 that caused inconsistencies in how XSL is parsed prior to transformation. (SSG-7255)".

     

    --Gary