Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0016055Openbravo ERPZ. Otherspublic2011-02-25 11:132011-05-24 10:55
adrianromero 
jpabloae 
urgentminorsometimes
closedfixed 
20Community Appliance
2.50MP26 
3.0RC5 
Core
No
0016055: Tomcat connector not properly configured
The tomcat connector in the configuration file conf/server.xml must be configured to support UTF-8 encoding. The problem of not doing this are the related errors with locale characters like Ñ, Á, Ü in Spanish when using selectors.
Follow the steps to reproduce of the related issues.
Modify the connector configuration file conf/sever.xml and add the attribute:

 URIEncoding="utf-8"

This must be done in the AJP/1.3 connector if using apache with mod_jk and other connectors used. The AJP/1.3 connector configuration must be similar to the following line:

    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" URIEncoding="utf-8"/>

If using Tomcat standalone you must modify the HTTP/1.1 connector:

<Connector connectionTimeout="20000" port="8084" protocol="HTTP/1.1" redirectPort="8443" URIEncoding="utf-8"/>

closingMay2011
related to backport 00156752.50MP27 closed jonalegriaesarte In bank statement, create lines from the business partner selector does not work fine if you search for the character ñ 
depends on backport 00156772.50MP27 closed jonalegriaesarte The account element value selector does not work well with accents or ñ 
Issue History
2011-02-25 11:13adrianromeroNew Issue
2011-02-25 11:13adrianromeroAssigned To => jpabloae
2011-02-25 11:13adrianromeroModules => Core
2011-02-25 11:14adrianromeroRelationship addedrelated to 0015675
2011-02-25 11:14adrianromeroRelationship addeddepends on 0015676
2011-02-25 11:14adrianromeroRelationship deleteddepends on 0015676
2011-02-25 11:14adrianromeroRelationship addeddepends on 0015677
2011-02-25 14:15dmitry_mezentsevNote Added: 0034371
2011-02-28 10:53adrianromeroProposed Solution updated
2011-02-28 11:04jpabloaeNote Added: 0034400
2011-02-28 11:25iciordiaNote Added: 0034404
2011-02-28 16:32dmitry_mezentsevNote Added: 0034431
2011-03-04 15:50jpabloaeStatusnew => scheduled
2011-03-04 15:50jpabloaefix_in_branch => pi
2011-03-04 15:51jpabloaeNote Added: 0034571
2011-03-04 15:51jpabloaeStatusscheduled => resolved
2011-03-04 15:51jpabloaeFixed in Version => 3.0RC5
2011-03-04 15:51jpabloaeFixed in SCM revision => n/a
2011-03-04 15:51jpabloaeResolutionopen => fixed
2011-03-04 15:52jpabloaeNote Added: 0034572
2011-05-24 10:12dalsasuaTag Attached: closingMay2011
2011-05-24 10:55dalsasuaStatusresolved => closed

Notes
(0034371)
dmitry_mezentsev   
2011-02-25 14:15   
Juan Pablo,

Do we have these parameters correctly configured in our standard OB deliverables like appliances, Ubuntu package?
(0034400)
jpabloae   
2011-02-28 11:04   
Dmitry,

No, this is why this bug is assigned to me. We need to fix this in both.
(0034404)
iciordia   
2011-02-28 11:25   
Juan Pablo, it is not clear to me what is the severy of the issue. Does it mean that old selectors do not render 'non-ascii' characters properly in any case? If that's the case I would increase the severity to 'Major' and target a fix for the next MP.

Ismael
(0034431)
dmitry_mezentsev   
2011-02-28 16:32   
Actually, seems like NOW is the best timing to fix it because we are about to release MP27 and also RC4.1 is coming.
(0034571)
jpabloae   
2011-03-04 15:51   
Fixed for the upcoming 3.0RC5 and 2.50MP28, both in the appliance and for the Ubuntu package.
(0034572)
jpabloae   
2011-03-04 15:52   
Isma: yes, it looks like that's what happens. Strange that we haven't noticed until now.