hi all,

After setting up session_timeout option in ufile, the system logs out the idle user. But, it displays BW error msg and waits for the return key. Can't this be avoided?

i.e., I've set a timeout of 15 min. for an idle user. After 15 min of inactivity the system logs the user off automatically. When the user is logged off, BW error windows appears, saying "BW connect error ...." and waits for the return key to be pressed.

Can't this be avoided? so, that the user will not even know that he was thrown out by the server.

sriram

The error message is generated by the client and not the server so it can't be avoided. It's just a generic message that appears whenever the client loses connectivity no matter what the cause.

for a slicker solution to this problem, take a look at
www.closeidle.co.uk (http://www.closeidle.co.uk)

Before cleanly logging out users after a preset time of inactivity - CloseIdle will save data in any of the user's open sessions. You can have different timeouts per user and can exclude certain sessions or users from timeout as required. I've used it and think it's great!

Hi Andy

Just curious about one thing. What would CloseIdle do with a session where the required fields are only halfway completed? Issuing a "Save&Exit" command would surely result in errors! Does CloseIdle handle this?

closeidle is a third party software, i'm sure you don't want an extra cost.

Hi Nico,

As I know, CloseIdle investigates the process to database, if it is active then it does not shutdown the session even though it exceeds the preset time-out.

-Suhas

Hi Shriram,

The descriptive message itself shows reason of bshell disconnection, otherwise users may complain that bshell is disappering. Hence, I think, it can't be unavoided.

-Suhas

suhas-mahajan: As I know, CloseIdle investigates the process to database, if it is active then it does not shutdown the session even though it exceeds the preset time-out.I think Nico meant the situation like this:
Insert sales order
start creating a sales order line: enter item code, but do not enter a quantity or price yet. Now have CloseIdle close your session:
- fieldvalues may not be saved to database since it will result in a sales orderline with an item without price or quantity
- ignoring the input data will cause data loss...
- session is in "waiting" state on input on a field, thus database is idle

Hi OmeLuuk,

Your comments are vital & has certainly set me re-thinking. I read documentation of CloseIdle, where they wrote and assurred this. I don't know exact architecture of CloseIdle, long time ago we used it in demo period. Later we inhouse built the functionality of CloseIdle.
Let someone cross-check it, If the data is in field values only, small data loss might be there.

-Suhas

Originally posted by NvanBeest
Hi Andy

Just curious about one thing. What would CloseIdle do with a session where the required fields are only halfway completed? Issuing a "Save&Exit" command would surely result in errors! Does CloseIdle handle this?

In my experience, if a form is half-way completed and a 'save and exit' would cause a Baan error if attempted, then CloseIdle will not close the session. Hope that makes sense