Is there anyway to reduce the idle time from 30 minutes to something like 1 or 2?
Because information matters
[OpenKM 4.0] Reduce Idle Time
- OpenKM has many interesting features, but requires some configuration process to show its full potential.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
There's no good idea. First you must understand something.
1- Session by default is 30 minutes
2- Session are not lost meanwhile user make some operation, to ensure while openkm is enabled user don't loses session, there's a background method in UI that each 15 minutes makes a call to server to prevent losing session ( scenario -> users has left for more than 30 minutes his job computer, with OpenKM screen openend or simply has closed the window while is doing something in other ... he's not making operations and could lose session to prevent it we've got this background method fired automatically each 15 minutes ).
What could happen
1- You could configure for less than 15 minutes ( if you understand what I said before you must understand the problems that you'll got changing it ).
2- To better configuration it might be changed the method period ( by source code ) to the new .. really having 1-2 minutes that you purpose it not good idea, if you understand the idea of session ...
I think your problem is bad users logout no ? in version 5.0 we're working to correct the one session per user, that will solve the problem, users can start other session meanwhile the other is still alive ( meanwhile you could use administrative utilities to kill user session ? )
In wiki you've got explained how to reduce session time out
http://wiki.openkm.com/index.php/Changi ... ut_session
1- Session by default is 30 minutes
2- Session are not lost meanwhile user make some operation, to ensure while openkm is enabled user don't loses session, there's a background method in UI that each 15 minutes makes a call to server to prevent losing session ( scenario -> users has left for more than 30 minutes his job computer, with OpenKM screen openend or simply has closed the window while is doing something in other ... he's not making operations and could lose session to prevent it we've got this background method fired automatically each 15 minutes ).
What could happen
1- You could configure for less than 15 minutes ( if you understand what I said before you must understand the problems that you'll got changing it ).
2- To better configuration it might be changed the method period ( by source code ) to the new .. really having 1-2 minutes that you purpose it not good idea, if you understand the idea of session ...
I think your problem is bad users logout no ? in version 5.0 we're working to correct the one session per user, that will solve the problem, users can start other session meanwhile the other is still alive ( meanwhile you could use administrative utilities to kill user session ? )
In wiki you've got explained how to reduce session time out
http://wiki.openkm.com/index.php/Changi ... ut_session
Yes, I do understand that but I'm using WebServices, so, if a user does not logout properly the admin has to access to web console and I'm putting all me efforts to avoid using openKM's web interface...
I don't know which programming language are you to connect via webservices. But it's good practice to make login - logout closed cycles ( for example all ms addins are based in this concept ).
Capture all errors and ensure at ends catch ( it's made the logout ) althought logic operation it'll be compromised you'll be ensured that user that you're using to login across webservices has loged out successfully ( I think your problems comes during programming cycle no ? )
Our actual effors are in making multi user login in 5.0, but always is bad practice to leave zombies connections, you must ensure all ws connections are closed (logout) before login is executed.
Take a look for example here ( startup method cycle open / close connection ):
http://openkm.svn.sourceforge.net/viewv ... iew=markup
Capture all errors and ensure at ends catch ( it's made the logout ) althought logic operation it'll be compromised you'll be ensured that user that you're using to login across webservices has loged out successfully ( I think your problems comes during programming cycle no ? )
Our actual effors are in making multi user login in 5.0, but always is bad practice to leave zombies connections, you must ensure all ws connections are closed (logout) before login is executed.
Take a look for example here ( startup method cycle open / close connection ):
http://openkm.svn.sourceforge.net/viewv ... iew=markup