This bug has 2 manifestations somehow depending if you use an MySQL DB or only the build in database
Steps to reproduce:
1. Upload a video use umlaute "äöü" or probably other non ASCII characters in the "presenter" field.
2. The video gets uploaded the confirmation screen contains the right presenter name.
With internal database: the umlaute in the presenter name are replaced by "?" AFTER the initialising step. During INITALIZING the Presenter name is still correct. The processed video is not playable.
With the MySQL database the Job gets stuck in INITALIZING and I get the error message in the code snippet.
I spent the day looking at this, and it appears to me now that the title and presenter are ok, right up until they're put over the network as part of the Job dispatch. But that code hasn't changed between 1.4.0 and 1.4.x...
After a short look to the job dispatcher it may help to set the encoding of the UrlEncodedFormEntity to 'UTF-8', it's just a guess: ServiceRegistryJpaImpl:1864
Can someone try it? I don't have time this week.
String jobXml = JobParser.toXml(jpaJob);
List<BasicNameValuePair> params = new ArrayList<BasicNameValuePair>();
params.add(new BasicNameValuePair("job", jobXml));
UrlEncodedFormEntity entity = new UrlEncodedFormEntity(params, "UTF-8");
Committed Lukas' fix into trunk with rev 15740. I'm going to take another look either tomorrow or Thursday and see if the remote implementations need this as well.
Confirmed to work in 1.4.x. Merged in with rev 15741 (as a separate patch, d'oh).