PAS sessions never stopped (after idle timeout)

The 'Idle Resource Timeout' property is disabled (set to 0). Set it to some timeout value just like other properties and you should see the some messages in the session manager log.

Testing now.  Will use 10000 (docs say it is milliseconds).

I found another value at the server level (psc.as.session.timeout).  At first I was hopeful about it, but there is a KB saying that using it would have had no effect.  Its a bit confusing to have a session timeout config over there as well (just as well it doesn't work).

KB: knowledgebase.progress.com/.../Changing-idle-session-timeout-option-has-no-effect-in-PASOE

Those two are two different timeouts. The one you wanted is IdleResourceTimeout. The psc.as.session.timeout is tomcat sessiontimeout value.

Is there a better doc about the different ABL App timeouts?  Here is the one I'm reading:

documentation.progress.com/.../index.html

It talks briefly about timeouts but I don't know which timeout serves which purpose.  The top two timeouts in the list below have the exact same explanation in the documentation.  

Agent listener timeout

Idle agent timeout

Idle resource timeout

Idle session timeout

Good docs are pretty important.  Without your help I would never have thought that my idle session must be configured with a timeout value using a different  property other than the "idle session timeout".

These timeouts are really confusing, spending a lot of time with them.

IdleResourceTimeout should now work (i'm using 11.6.3.22)

Clarifying Information in KB 000077758:

Notes

The idleResourceTimeouts which involve idleSessionTimeout,idleConnectionTimeout and idleAgentTimeout were working from beginning but we never completely tested it and we did not have confidence on how it works, that was the reason we mentioned as ‘NOT IMPLEMENTED !’.

When we tested the same in 11.6.3 and 11.7.1 we observed that it is working fine and there no repercussions. Now that we see it working fine, we started suggesting others to use it.

If you want to try out in a 11.6.3 or  11.7.1 test environment, then you can enable idleResourceTimeout and idleAgentTimeout to a minimum value and you should see that the agent gets terminated in the given period.

agentListenerTimeout  -  When the session manager starts a Multi-session Agent, it creates a listening socket and

passes that port number to the agent as a startup argument.  After startup, the agent process completes the network initialization based the timeout value specified for this property.

So, this only affects when you startup the PASOE Instance. You have to modify this value if your agent does not start in the given time.

Also the Idle session timeout means the session-manager sessions and not the MS-Agent session.

All the other properties are as mentioned in the document. And yes, these were there from the beginning but we never suggested them to customers, hence the idleResourceTimeout was always disabled.

If the documentation is not clear, then we have to fix it. Will log a bug for it.

Thanks for all the help Irfan.

Now that my ABL client sessions are timing out and restarting, I'm getting a bunch of odd errors when a new APSV remote client uses one of the restarted clients sessions.  See below.

[17/11/22@12:33:21.122-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.130-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.133-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.138-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.146-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.149-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.153-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)
[17/11/22@12:33:21.163-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031)

This is not easily found in my google searches (and certainly not referenced in relation to PAS).  As far as I am aware, the only thing I've been playing with for the past two hours is the timeout properties (I'm now seeing my ABL's restart on their own for the first time ever).  I think this is directly related...  Thoughts?

(This doesn't affect any behavior , but floods the logs rapidly at logging level 1).

I do not think these are related to timeouts, this should be something with your application. Were you not getting the  same errors before you enabled timeouts ?

No, nor when I stopped my multi-session agents manually.  It seems to be a new thing related to how the agent is being restarted after a timeout.  I will try to gather more details.  It doesn't seem to be impacting my app behavior.

I wonder if this is happening to others but they aren't looking in the logs, or they are ignoring it.  It seems like something that shouldn't be ignored.

Let me know if you have reproducible. I ran idleResourcetimeout enabled for days and did not find any such errors.