From: Anissa Lam <anissa.lam_at_oracle.com>
Date: Fri, 28 Jan 2011 08:11:55 -0800

Yesterday, I did a quick testing to see if we support multibyte char in
v2 and thought it is supported.
I did more testing, and see that it wasn't supported 'end-to-end'.
Some element does, like node-agent does. You can use multibyte and
start that fine. Instance thats NOT multibyte can use this agent and
start ok too. (image attached)
For cluster and instance, you can create and list them ok. They are
persisted correctly in domain.xml. But have issue starting.
I guess we should say multibyte wasn't supported in v2 afterall. Sorry
for the confusion I raised.

thanks
Anissa.

On 1/28/11 7:37 AM, Tom Mueller wrote:
> I updated the bug with a comment. The problem is likely that the LANG
> environment variable is not set to support UTF-8 when starting the
> server. Try setting LANG=en_US.utf-8. Then the characters will be
> written correctly to the domain.xml file.
>
> BTW, I've assigned the original bug that bought up this issue (15706)
> to Carla for investigation. I suspect that what is happening is that
> when create-instance invokes the asadmin command to run various hidden
> commands, such as _create-instance-filesystem, an instance name that
> has a multibyte character is not being passed correctly on the command
> line for some operating systems. I was able to create an instance
> with a multibyte character on Linux, just as you were able to on
> MacOS, but this fails on Windows. While you were able to delete an
> instance on MacOS, this definitely fails on both Windows and Linux.
> So there is some OS variation here.
>
> Tom
>
>
> On 1/27/2011 9:09 PM, Jason Lee wrote:
>> I see the same behavior from the CLI, but not from REST. Perhaps
>> asadmin is lousing up the MB chars...
>>
>> On 1/27/11 7:03 PM, Anissa Lam wrote:
>>>
>>>
>>> On 1/27/11 4:38 PM, Jason Lee wrote:
>>>> I'm not seeing a problem in REST. I created a test that creates an
>>>> instance named i1듈2. I then get a list of all the servers,
>>>> request that particular server, then delete. All operations
>>>> succeed, and the value is stored correctly in domain.xml.