[GLASSFISH-20636] Server created in multilingual edition can't be started. Created: 15/Jun/13  Updated: 24/Jun/13

Status: Open
Project: glassfish
Component/s: i18n
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: birdwoods Assignee: michael.fang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

windows 8 ,windows 2008 R2

Tags: codec


I'm a Chinese user and I installed the glassfish 4.0 multilingual edition on Win8 and Win2008R2 using the native installer.
As I created a server instance named 'appserver' and tried to start it from admin console,I got the error message:CLI801 Instance is already synchronized Attempting to start appserver.... Please look at the server log for more details.....
I had to followed the message and run the following command:
lib/nadmin start-local-instance --node localhost-domain1 --sync normal appserver
Then I got error messages full of my eyes.
The inner exception I found was:
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[80,41]
Message: 1 字节的 UTF-8 序列的字节 1 无效。
at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLS

I checked domain.xml in the path 'glassfish4\glassfish\nodes\localhost-domain1\appserver\config',and I found this file is GB2312 encoding(os default),and in row 80 of this file ,there is Chinese text:
<system-property description="JMS 服务将用于监听远程客户机连接的端口号。" name="JMS_PROVIDER_PORT" value="7676"></system-property>

I delete the description attribute from the orignal config file glassfish4\glassfish\domains\domain1\config\config.xml in line 80 and restart the glassfish server,problem resolved.

I guess when starting the server,glasssfish try to use UTF-8 encoding to read the xml ,however thie text encoding of this file is not specified when creating it(so it's encoding follows the OS default,which is GB2312).

The funny thing is that the default admin server's config file is also in GB2312 text encoding...

Generated at Wed Mar 04 09:07:19 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.