[Apiman-user] Keycloak OAuth plugin persistence bug
Marc Savy
marc.savy at redhat.com
Fri Jun 2 06:26:44 EDT 2017
Hi Andy,
I spent time yesterday evening trying to replicate this after our chat
on IRC, but I haven't been able to trigger it. Perhaps with more
information we can narrow this down.
Which version of Postgres are you using? Which driver version?
I've been using: Postgres 9.6.2, Driver 42.1.1, apiman 1.3.0.Final
(should be same as 1.2.9.Final for this).
Have you done any export-import?
Have you observed the precise action that corresponds with the
extraneous pd_templates entries being inserted?
Regards,
Marc
On 2 June 2017 at 08:05, Andy Yar <andyyar66 at gmail.com> wrote:
>
> Hello,
> Keycloak OAuth plugin's presence generates a certain amount of records
> to pd_templates table on each action of Apiman Manager related to a
> Keycloak OAuth policy (even read-only ones like listing a plan's
> policies, etc.).
>
> Over time the number of records in pd_templates table can grow to
> milions resulting in Apiman Manager OoM exceptions. Given these
> records are basically just text hints it is really funny.
>
> A workaround is to periodically dedup the records.
>
> I guess this issue should be an easy fix.
>
> Affected version is: Apiman 1.2.9.Final + corresponding Keycloak OAuth plugin.
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
More information about the Apiman-user
mailing list