[JBoss JIRA] Created: (JBCACHE-693) TreeCache configuration bombs with InvocationTargetException when JVM locale is set to Turkish.
by Yasar Safkan (JIRA)
TreeCache configuration bombs with InvocationTargetException when JVM locale is set to Turkish.
-----------------------------------------------------------------------------------------------
Key: JBCACHE-693
URL: http://jira.jboss.com/jira/browse/JBCACHE-693
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Tested on Linux, using Resin 3.0.14 with Hibernate 3.
Reporter: Yasar Safkan
Assigned To: Manik Surtani
When the parameters:
-Duser.language=tr -Duser.country=TR
are passed to the JVM, the AppServer startup bombs when it tires to configure TreeCache using treecache.xml. Seems that it reads the value fine, but thinks the value is invalid for some reason.
My best guess is this stems from the way the letters i and I are handled in Turkish. If there is any upper/lowercase conversion code within JBossCache, these letters are handled funny, thus string constants like READ_COMMITED are not recognized.
The fix will probably be to use upper/lowercase conversion by specifying a character set in the JBossCache code, and not relying on the JVM defaults.
The JVM itself had a similar bug, which prevented encrytion from working under these same conditions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBAS-3546) Change log level on CachedConnectionManager.closeConnection() to warn
by Felipe Leme (JIRA)
Change log level on CachedConnectionManager.closeConnection() to warn
---------------------------------------------------------------------
Key: JBAS-3546
URL: http://jira.jboss.com/jira/browse/JBAS-3546
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Felipe Leme
Assigned To: Weston Price
Priority: Trivial
The feature of the CachedConnectionManager automatically closing connections (and warning about the fact) is pretty useful; in fact, so useful that we would like to receive email notifications when it occurs. But, unfortunatelly, we are not receiving such notifications, as our log4j SMTP appender is set to the WARN threshold, while such warnings are being logged as info:
if (e != null)
log.info("Closing a connection for you. Please close them yourself: " + c, e);
else
log.info("Closing a connection for you. Please close them yourself: " + c);
m.invoke(c, new Object[]{});
}
catch (Throwable t)
{
log.info("Throwable trying to close a connection for you, please close it yourself", t);
}
}
catch (NoSuchMethodException nsme)
{
log.info("Could not find a close method on alleged connection objects. Please close your own connections.");
}
So, I'm proposing these loggings are changed from info() to warn() - I don't think such change will cause any 'logging havoc', as the messages are only logged when the CachedConnectionManager is set to debug them...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months