Paul Clapham wrote:And when you use that properties file, are you ensuring that your code reads it as UTF-8? I ask because the methods in the java.util.Properties class assume that the file is encoded in ISO-8859-1, with Unicode escapes being used for characters which aren't in the Latin character set. Have a look at the API documentation for Properties for more detail.
Tim Moores wrote:Just to ask the obvious: which encoding is the ar_AR.properties file in? (I'm assuming that you do have a font installed that has Arabic characters.)
Also, you might try asking in the forums where the JForum developers hang out at http://jforum.andowson.com/forums/
Jaikiran Pai wrote:
Sherif Shehab wrote:Thanks , but i want to know what is the root cause for this problem ?
I already explained the potential problem in one of my previous posts in this very thread.
Jaikiran Pai wrote:It usually depends on the DB admin policies. You'll have to check with whoever manages your DB server.
Jaikiran Pai wrote:The idle timeout configuration in that screenshot looks suspicious. If you let the connection stay idle in the pool for a long time then the DB side of the connection can be terminated (the DB admins usually set a connection timeout). When the pool then hands out such an idle (and terminated connection) you can run into exceptions like these.
Make sure you set some reasonable value for idle timeout for the pooled connections.
Jaikiran Pai wrote:What does your application's connection handling code look like? If you are using datasource(s) what does the configuration look like?