For what it’s worth this worked and brought our maximum duration down to 1 min rather than
30 minutes.
I’m not sure what’s running that long since the transaction timeout is lower than a minute
but it helped improve our average response time.
On Nov 7, 2018, at 10:12 AM, Phillip Fleischer
<pcfleischer(a)outlook.com> wrote:
Hi,
We use new relic APM to monitor keycloak and seems that on occasion there will be
transactions running for ~30min which seems to be exceptionally long. We already lowered
our database transaction timeouts, but thinking we should also add/change the wildly
servlet timeout timeout from the default of 30 minutes.
<servlet-container name="default" default-session-timeout="1">
<jsp-config/>
<websockets/>
</servlet-container>
I can’t see this being related to any of the “keycloak session” timeouts, just wondering
if anyone would know if this is a terrible idea??
— Phil
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.j...