MSIR.0658 Persistent/legacy session on port (portname) terminated, about to exceed site's (type) connection limit: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(Automatically generated page update) |
||
| Line 3: | Line 3: | ||
Note that security sessions (held via SSLSES or SESCOOKIE) are not counted against a site's connection limit since these do not hold a connection of any sort while in effect. | Note that security sessions (held via SSLSES or SESCOOKIE) are not counted against a site's connection limit since these do not hold a connection of any sort while in effect. | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]] | ||
Revision as of 16:04, 13 August 2015
An attempt to start a new persistent or legacy session was terminated because it would cause the site's connection limit for either Janus TCP/IP Base or Janus Web Server to be exceeded. Try to reduce the number of persistent or legacy sessions active at a time, perhaps by decreasing STIMEOUT, FORMPOSTWAIT, or MAXIPSES on the port definition, or by changing the applications to not use persistent or legacy sessions. If none of these options are feasible, it might be necessary to purchase a license that allows a higher connection limit.
Note that security sessions (held via SSLSES or SESCOOKIE) are not counted against a site's connection limit since these do not hold a connection of any sort while in effect.