AppSuite:MiddlewareStartup - Revision history

Marens: /* Format >= 7.8.4 */

2017-04-26T16:52:24Z

Format >= 7.8.4

← Older revision		Revision as of 16:52, 26 April 2017
Line 282:		Line 282:
	-XX:+PrintHeapAtGC -XX:+PrintGCApplicationStoppedTime -XX:+PrintTenuringDistribution"		-XX:+PrintHeapAtGC -XX:+PrintGCApplicationStoppedTime -XX:+PrintTenuringDistribution"

	which is much easier to read an maintain. Furthermore we added a useful '''JAVA_OPTS_DEBUG''' configuration parameter that comes preconfigured but unused/commented so that customers can quickly enable the most commonly used debugging options in case they have to provide detailed system information to Open-Xchange.		which is much easier to read and maintain. Furthermore we added a useful '''JAVA_OPTS_DEBUG''' configuration parameter that comes preconfigured but unused/commented so that customers can quickly enable the most commonly used debugging options in case they have to provide detailed system information to Open-Xchange.

	During the startup of the open-xchange service (step 11 of diagram ''Service startup using systemd'' and step 10 of diagram ''Service startup using upstart'') all uncommented JAVA_OPTS_* categories will then be evaluated and combined again into a single string of commandline options that can then be passed to the JVM.		During the startup of the open-xchange service (step 11 of diagram ''Service startup using systemd'' and step 10 of diagram ''Service startup using upstart'') all uncommented JAVA_OPTS_* categories will then be evaluated and combined again into a single string of commandline options that can then be passed to the JVM.

Marens: /* Verify that your system is configured with a proper unicode locale for OX */

2017-04-26T08:20:05Z

Verify that your system is configured with a proper unicode locale for OX

← Older revision		Revision as of 08:20, 26 April 2017
Line 428:		Line 428:
	Assuming you haven't reconfigured the locale of your root user		Assuming you haven't reconfigured the locale of your root user

	[root@showcase-community-centos-7 vagrant] locale charmap		[root@showcase-community-centos-7 vagrant]# locale charmap
	UTF-8		UTF-8
	[root@showcase-community-centos-7 vagrant]		[root@showcase-community-centos-7 vagrant]#

	== Warnings during early start ==		== Warnings during early start ==

Marens: /* Verify that your system is configured with a proper unicode locale for OX */

2017-04-26T08:19:41Z

Verify that your system is configured with a proper unicode locale for OX

← Older revision		Revision as of 08:19, 26 April 2017
Line 428:		Line 428:
	Assuming you haven't reconfigured the locale of your root user		Assuming you haven't reconfigured the locale of your root user

	~~i\|marens~~@~~karotte ~ $ su~~ -		[root@showcase-community-centos-7 vagrant] locale charmap
	~~Password:~~
	~~i\|karotte ~ #~~ locale charmap
	UTF-8		UTF-8
	~~i\|karotte ~ #~~		[root@showcase-community-centos-7 vagrant]

	== Warnings during early start ==		== Warnings during early start ==

Marens: /* JVM startup */

2017-04-26T08:06:13Z

JVM startup

← Older revision		Revision as of 08:06, 26 April 2017
Line 366:		Line 366:
	}		}

	Although we try to specify valid unicode encodings for every IO ~~operations~~ the Open-Xchange middleware does some parts of the JVM don't allow to specify the encoding to use and falls back to the detected default encoding. That's why admins have to make sure to provide a proper unicode environment for the middleware service during every start or use documented workarounds provided by Open-Xchange (e.g. [http://documentation.open-xchange.com/components/middleware/config/develop/index.html#mode=features&feature=Password%20Change%20Script com.openexchange.passwordchange.script.base64]: Encoded strings as Base64 to circumvent character encoding issues on improperly configured distributions).		Although we try to specify valid unicode encodings for every IO operation the Open-Xchange middleware does, some parts of the JVM don't allow to specify the encoding to use and simply falls back to the detected default encoding. That's why '''admins have to make sure to provide a proper unicode environment for the middleware service during every service start''' or use documented workarounds provided by Open-Xchange (e.g. [http://documentation.open-xchange.com/components/middleware/config/develop/index.html#mode=features&feature=Password%20Change%20Script com.openexchange.passwordchange.script.base64]: Encoded strings as Base64 to circumvent character encoding issues on improperly configured distributions).

	See the documentation of your linux distribution on how to configure a proper unicode locale.		See the documentation of your linux distribution on how to configure a proper unicode locale.

Marens: /* JVM startup */

2017-04-26T08:04:05Z

JVM startup

← Older revision		Revision as of 08:04, 26 April 2017
Line 366:		Line 366:
	}		}

	Although we try to specify valid unicode encodings for every IO operations the Open-Xchange middleware does some parts of the JVM don't allow to specify the encoding to use and falls back to the detected default encoding. That's why admins have to make sure to provide a proper unicode environment for the middleware service during every start or use documented workarounds provided by Open-Xchange (e.g. com.openexchange.passwordchange.script.base64: Encoded strings as Base64 to circumvent character encoding issues on improperly configured distributions ~~see [https://documentation~~.~~open-xchange.com/7.8.3/middleware/configuration/properties.html property documentation])~~		Although we try to specify valid unicode encodings for every IO operations the Open-Xchange middleware does some parts of the JVM don't allow to specify the encoding to use and falls back to the detected default encoding. That's why admins have to make sure to provide a proper unicode environment for the middleware service during every start or use documented workarounds provided by Open-Xchange (e.g. [http://documentation.open-xchange.com/components/middleware/config/develop/index.html#mode=features&feature=Password%20Change%20Script com.openexchange.passwordchange.script.base64]: Encoded strings as Base64 to circumvent character encoding issues on improperly configured distributions).

	See the documentation of your linux distribution on how to configure a proper unicode locale.		See the documentation of your linux distribution on how to configure a proper unicode locale.

Marens: /* Query which file encoding was detected by the JVM during startup */

2017-04-25T12:31:37Z

Query which file encoding was detected by the JVM during startup

← Older revision		Revision as of 12:31, 25 April 2017
Line 376:		Line 376:

	/opt/open-xchange/sbin/showruntimestats -r \| sed -ne 's/.${key=file.encoding, value=[^}]}$.*/\1/p'		/opt/open-xchange/sbin/showruntimestats -r \| sed -ne 's/.${key=file.encoding, value=[^}]}$.*/\1/p'
	{key=file.encoding, value=UTF-8}		{key=file.encoding, value='''UTF-8'''}

	<br clear=all>		<br clear=all>

Marens: /* Limits besides control groups */

2017-04-25T08:59:50Z

Limits besides control groups

← Older revision		Revision as of 08:59, 25 April 2017
Line 197:		Line 197:
	* LimitNPROC		* LimitNPROC

	which you have already seen when we took a look at the [[#Service_definiton\|service definition]] and [[#Drop-in_config\|drop-in configs]]		which you have already seen when we took a look at the [[#Service_definiton\|service definition]] and [[#Drop-in_config\|drop-in configs]]. ''Again'': The complete documentation wrt. resource limit configurations in drop-in configs can be found at [https://www.freedesktop.org/software/systemd/man/systemd.exec.html systemd.exec]

	== Verify limits ==		== Verify limits ==

Marens: /* Drop-in configs */

2017-04-25T08:57:43Z

Drop-in configs

← Older revision		Revision as of 08:57, 25 April 2017
Line 36:		Line 36:
	#LimitNOFILE=65536		#LimitNOFILE=65536

	The systemd.exec documentation shows a whole lot of options that can be used by admins to adapt the default service to their specific needs.		The [https://www.freedesktop.org/software/systemd/man/systemd.exec.html systemd.exec] documentation shows a whole lot of options that can be used by admins to adapt the default service to their specific needs.

	<br clear=all>		<br clear=all>

Marens: /* Drop-in configs */

2017-04-25T08:51:36Z

Drop-in configs

← Older revision		Revision as of 08:51, 25 April 2017
Line 41:		Line 41:
	[[File:mw_start_sysd.png\|thumb\|Service startup using systemd\|left\|1000px]]		[[File:mw_start_sysd.png\|thumb\|Service startup using systemd\|left\|1000px]]
	<br clear=all>		<br clear=all>

			''Note:'' The technical implementation of systemd differs as service definition and config aren't read every time during service start but the changes need to be reread with ''systemctl daemon-reload''. The above is just a simplyfied version to explain the general concept.

	== System V / Upstart ==		== System V / Upstart ==

Marens: /* JVM startup */

2017-04-24T21:46:51Z

JVM startup

← Older revision		Revision as of 21:46, 24 April 2017
Line 364:		Line 364:
	}		}

	Although we try to specify valid unicode encodings for every IO operations the Open-Xchange middleware does some parts of the JVM don't allow to specify the encoding to use and falls back to the detected default encoding. That's why admins have to make sure to provide a proper unicode environment for the middleware service during every start or use documented workarounds provided by Open-Xchange (e.g. )		Although we try to specify valid unicode encodings for every IO operations the Open-Xchange middleware does some parts of the JVM don't allow to specify the encoding to use and falls back to the detected default encoding. That's why admins have to make sure to provide a proper unicode environment for the middleware service during every start or use documented workarounds provided by Open-Xchange (e.g. com.openexchange.passwordchange.script.base64: Encoded strings as Base64 to circumvent character encoding issues on improperly configured distributions see [https://documentation.open-xchange.com/7.8.3/middleware/configuration/properties.html property documentation])

			See the documentation of your linux distribution on how to configure a proper unicode locale.

	=== Query which file encoding was detected by the JVM during startup ===		=== Query which file encoding was detected by the JVM during startup ===