Hello,
I have problem after upgrade from Karaf 4.4.5 to Karaf 4.4.6.
I have code that uses Session to store backend values.
When I test locally (under Windows) Sessions are not working – they are created, but very soon they are destroyed (after 1, max 2 minutes).
(I have SessionListener that logs when session is destroyed).
I have configured in org.ops4j.pax.web.cfg:
org.ops4j.pax.web.session.timeout=15
and I have keepalive every 30 seconds.
In the productive setup (Ubuntu-based docker image) there are no such problems.
I can remember session problems for a few years, where keepalive wasn’t working, and also only it was only on Windows, but it wasn’t such severe (now sessions seem to be timeouted almost immediately, which breaks the whole app).
Do you have any ideas, what can be causing such behavior?
As workaround, I can use older Karaf for development…
Best regards,
Lukasz Lech
--
--
------------------
OPS4J - http://www.ops4j.org - op...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/GV0P278MB01786777BAD4DB24F293825DF61A2%40GV0P278MB0178.CHEP278.PROD.OUTLOOK.COM.
Hello,
The logs are application-specific so it wouldn’t help you so much, but I’ve found in debugger something interesting.
There are 2 places in JettyServerWrapper that set maxInactiveInterval on Jetty. Jetty expects time in seconds, and the ops4j config in minutes. In one place, the value is multiplied by 60, in other, it’s not.
On Karaf 4.4.5 both places are called. First set parameter from my configuration (15), so the session timeout is set to 15 seconds.
Second one sets 30 (I suppose, it’s default value) and multiplies it by 60, so 30 minutes timeout are set. Parameter from my configuration is ignored.
On Karaf 4.4.6, only the first call is made. It means, that the session timeout is 15 seconds, instead of minutes.
I’ve updated org.ops4j.pax.web.session.timeout to 900 and all my automatic tests are completed. I need now to wait if the sessions will be actually deleted after this 15 minutes.
I hope that helps.
Best regards,
Lukasz Lech
To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/CAAdXmhqcQE7LvpbhC%2BRpESzit2CF-G1mLeQa1NOwefXH10GPsg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/GV0P278MB01789CFD18534CD4BEA44F4DF61A2%40GV0P278MB0178.CHEP278.PROD.OUTLOOK.COM.