Hi

I guess SESSION_TIMEOUT doesn't work for bsp (for super users !).
Pls. correct me if I am wrong...!

I tried and it doesn't work for me.. :(


Thanks.

It certainly works for super-users (on 4c4 anyway) but I don't usually login as bsp or root so I can't say if they are treated differently (although I don't think so).

SESSION_TIMEOUT doesn't seem to be working for any user...

I tried setting it in the /defaults/all file, in the user profile, in the user BW configuration....doesn't work..!

Are there any other configuration to be considered...

Thanks..

Make sure your porting set is not too old (I the minimum for 4c4 but not ERP). Also, I think your Tools package need to be up to date as well (patches). I am of course assuming that sesssion_timeout works with ERP to begin with:)

all file must contain session_timeout:60 or the time you want plus
portingset 6.1c.06.02 or above. it works with our system.

no tools update required. but if you have ttstppollmess object for messaging then it would not work. it refreshes the connection with client and reset the timer.

Hi baanjour,

Could you please confirm that it has worked for you. Because I am also having the same problem. My 4c4 is on sun solaris 5.8 and it is not working. the porting I am having is little old i.e. 6.1c.06 and the size of my object "ostpvtemul" is 13382.

Can you or someone else, advise, what is required to make session_timeout work on sun solaris? I have tried defaults/all, user file and environment variable, but it do not work.

Works fine for me....
Try this:

Login as bsp... (or any other user that does not have the ability to have his bshell closed...). Start Baan and open a ttstpshell.
Then check what processes do get processor ticks (and thus remain active, disallowing the session_timeout to timeout because there is session activity.)

Then check the bms_mask file (session ttadv4188m000) to see what files are started when bshell starts (bootflag on).

Dear OmeLuuk,

Thanks , I checked the running processes, but could not identify any, which can send message from bshell to keep it running. I have posted a case to BGS and have been advised to upgrade the porting set to 6.1c.06.01 onwards...

Thanks once again...

Ah, that is the point. It is implemented in 6.1c.06.01, but after some solutions finally the last major fix on this point has been released in 6.1c.06.03. My advice would be: take the latest.