[undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha 4 with umlauts

[Wolfgang Knauf]

Many thanks!

I am a bit ashamed, because in my sample, I forgot everything that I 
know about encodings in JSP pages, and relied on the server defaults for 
years... This deadlock bug was the appropriate punishment for this 
laziness ;-).

After declaring everything properly ("@page contentType=...", <meta 
http-equiv="content-type" ...>) and applying 
"request.setCharacterEncoding(...)", it works like a charm.

Best regards

Wolfgang

-------- Original-Nachricht --------
Betreff: Re: [undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha	4 
with umlauts
Von: Stuart Douglas <sdouglas at redhat.com>
An: Wolfgang Knauf <wolfgang.knauf at gmx.de>
Kopie (CC): undertow-dev at lists.jboss.org
Datum: 29.08.2013 15:05

> Ok, fixed for real this time. The form parser was defaulting to UTF-8 when no charset was present in the request.
>
> Stuart
>
> ----- Original Message -----
>> From: "Stuart Douglas" <sdouglas at redhat.com>
>> To: "Wolfgang Knauf" <wolfgang.knauf at gmx.de>
>> Cc: undertow-dev at lists.jboss.org
>> Sent: Thursday, 29 August, 2013 2:39:35 PM
>> Subject: Re: [undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha	4	with umlauts
>>
>>
>>
>> ----- Original Message -----
>>> From: "Wolfgang Knauf" <wolfgang.knauf at gmx.de>
>>> To: "Stuart Douglas" <sdouglas at redhat.com>
>>> Cc: undertow-dev at lists.jboss.org
>>> Sent: Thursday, 29 August, 2013 2:30:20 PM
>>> Subject: Aw: Re: [undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha	4
>>> 	with umlauts
>>>
>>> Hi Stuart,
>>> thanks for the fast fix! The question mark is probably some kind of
>>> standard
>>> for non displayable strings ;-). Maybe also a log message, to trace down
>>> the
>>> error better?
>>> Any chance for me to test this against WildFly 8 Alpha 4 (without building
>>> it
>>> myself)?
>>
>> Unfortunatly not yet. Once I release Undertow (probably next week) it will be
>> possible to get a nightly build.
>>
>>> I assume that on my JSP page which handles the request, I have to do
>>> something like this:
>>> request.setCharacterEncoding ("ISO-8859-1");
>>
>> This is the default character set. Hmm, I need to investigate what is going
>> on here, this is just using the standard charset encoder for ISO-8859-1, so
>> I am not sure why it is reporting those characters as unmappable.
>>
>> Stuart
>>
>>> This should hopefully write the correct characters to the database. I will
>>> do
>>> more testing this evening.
>>> On previous JBoss versions, my sample worked without those modifications.
>>> Did
>>> the Undertow migration include some change to character encoding handling?
>>
>> Hmm, I will need to investigate this, and see how this was handled in
>> previous versions.
>>