Hi, just in case: the session timeout is defined in minutes, not seconds.
If it still is an issue for you could you open a jira-issue[1] with a sample project telling the expected behaviour? Best case would be unit test that fails :-) regards, Achim [1] - https://ops4j1.jira.com/browse/PAXWEB 2014-12-29 14:31 GMT+01:00 Bellski <[email protected]>: > Achim Nierbeck wrote > > yep, it's org.ops4j.pax.web.session.timeout > > can also be found at the Pax Web documentation [1] > > > > regards, Achim > > As i right understoon. I created org.ops4j.pax.web.cfg in /karaf_home/etc/ > and put > org.osgi.service.http.port=8080 > org.ops4j.pax.web.session.timeout=1 > > Port working, session timeout - not. > > Karaf 3.0.2 > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Jetty-Session-timeout-tp4037460p4037462.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
