-
June 13th, 2016, 10:01 AM
#1
Since the setup of a session involves a few steps, we don't count sessions for the <max_sessions> check until the startup has completed.
During this startup, we count sessions as "prestarted" (for instance in the JMX statistics of the ResourceMBean).
If a session starts when <max_sessions> is reached, it is refused immediately with the second log message.
If the session starts and <max_sessions> is not reached, it is allowed; but it may be refused later, when it tries to exit the prestarted state, if other sessions have preceded it.
In this case, you will see both messages.
Similar Threads
-
By syacharn in forum General
Replies: 1
Last Post: January 8th, 2014, 08:41 AM
-
By WorkingMan in forum General
Replies: 3
Last Post: May 23rd, 2013, 08:57 AM
-
By jonasby1 in forum General
Replies: 4
Last Post: February 16th, 2012, 08:47 AM
-
By BKnight in forum General
Replies: 3
Last Post: February 10th, 2012, 09:33 AM
-
By stephenallred in forum Client SDKs
Replies: 1
Last Post: June 7th, 2010, 11:13 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 03:18 AM.
Bookmarks