MSIR.0369 Connection transferred to user (usernum) - Revision history

Dme: Dme moved page MSIR.0369 Connection transferred to USER (usernum) to MSIR.0369 Connection transferred to user (usernum)

2018-07-07T03:20:58Z

Dme moved page MSIR.0369 Connection transferred to USER (usernum) to MSIR.0369 Connection transferred to user (usernum)

← Older revision	Revision as of 03:20, 7 July 2018
(No difference)

JALWiccan: Automatically generated page update

2017-03-03T23:08:45Z

Automatically generated page update

← Older revision		Revision as of 23:08, 3 March 2017
Line 4:		Line 4:

	{{Template:MSIR.0369 footer}}		{{Template:MSIR.0369 footer}}
	~~[[Category:Sirius Mods messages]]~~ [[Category:MSIR.0200 - MSIR.0399]]		[[Category:MSIR.0200 - MSIR.0399]]

JAL: add link

2016-07-11T19:12:46Z

add link

← Older revision		Revision as of 19:12, 11 July 2016
Line 1:		Line 1:
	This informational message is issued by an ~~SDAEMON~~ thread running a Janus Web request after the request has been transferred to a different ~~SDAEMON~~ thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the ~~userid~~ so that the request had to be delayed. As soon as one of the threads running a request for the ~~userid~~ becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.		This informational message is issued by an [[Sdaemons\|Sdaemon]] thread running a Janus Web request after the request has been transferred to a different Sdaemon thread for processing. This message is only issued for [[Janus Web Server]] ports with the <var>WEBLOGHOLD</var> parameter set, when more than <var>WEBLOGMAX</var> threads were already active for the user ID so that the request had to be delayed.

			As soon as one of the threads running a request for the user ID becomes available, it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.

	{{Template:MSIR.0369 footer}}		{{Template:MSIR.0369 footer}}
	[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]		[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]

JALWiccan: Automatically generated page update

2016-07-11T18:41:01Z

Automatically generated page update

← Older revision		Revision as of 18:41, 11 July 2016
Line 1:		Line 1:
	This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.		This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.

			{{Template:MSIR.0369 footer}}
	[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]		[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]

JALWiccan: Automatically generated page update

2015-08-13T15:53:05Z

Automatically generated page update

← Older revision		Revision as of 15:53, 13 August 2015
Line 1:		Line 1:
	This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.		This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.

	[[Category:Sirius Mods messages]]		[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]

DmeWiccan: Automatically generated page update

2013-04-19T17:44:17Z

Automatically generated page update

← Older revision		Revision as of 17:44, 19 April 2013
Line 1:		Line 1:
	This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.		This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.

	[[Category:Sirius Mods ~~Messages~~]]		[[Category:Sirius Mods messages]]

Admin: 1 revision

2010-11-09T16:41:15Z

1 revision

← Older revision	Revision as of 16:41, 9 November 2010
(No difference)

198.242.244.47: Created page with "This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This me..."

2010-11-09T14:52:59Z

Created page with "This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This me..."

New page

This informational message is issued by an SDAEMON thread running a Janus Web request after the request has been transferred to a different SDAEMON thread for processing. This message is only issued for ''[[Janus Web Server]]'' ports with the WEBLOGHOLD parameter set when more than WEBLOGMAX threads were already active for the userid so that the request had to be delayed. As soon as one of the threads running a request for the userid becomes available it starts running the delayed request, first issuing a MSIR.0366. If there is already an idle Janus Web thread available for the userid when a request comes in, the request is immediately transferred to the idle thread, in this case accompanied by an MSIR.0365 instead of an MSIR.0369 that is then '''followed''' by an MSIR.0366 on the receiving thread.

[[Category:Sirius Mods Messages]]