jacopoc commited revision 1352575 which would prevent stack traces to be logged when viewing the cache overview screen in /webtools. However, a stacktrace is still logged when the caches contain collections which themselves contain objects which cannot be serialized.
jleroux: I simply used logWarning instead of info
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1480079 13f79535-47bb-0310-9956-ffa450edef68
Yesterday, I faced a weird bug in properties management.
For a reason, a copy of a project slipped in the project itself (like if you had a copy of ofbiz root in ofbiz root).
And in this project a properties file (in a hotdeploy component) as the same name than the project (like ofbiz.properties)
Then, as properties for this file, I got all the content of the sub-dir (here would be the files in ofbiz/ofbiz) instead of the properties
This fixes it, no performance issues since properties are cached so properties file are only accessed once
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1470176 13f79535-47bb-0310-9956-ffa450edef68
int org.ofbiz.base.util.UtilValidate.java file:
public static final String isMinuteMsg = "The Hour must be a number between 0 and 59.";
public static final String isSecondMsg = "The Hour must be a number between 0 and 59.";
should be
public static final String isMinuteMsg = "The Minute must be a number between 0 and 59.";
public static final String isSecondMsg = "The Second must be a number between 0 and 59.";
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1465351 13f79535-47bb-0310-9956-ffa450edef68
* el-api-2.2.jar is a duplicate of juel-2.2.1.jar
* geronimo-qname_1.1_spec-1.0.jar is a duplicate of xml-apis-2.9.1.ja
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1465281 13f79535-47bb-0310-9956-ffa450edef68
For example, in in the release package apache-ant-1.9.0.zip we have the jar ant-launcher.jar, the name of the jar in OFBiz is: ant-1.9.0-ant-launcher.jar
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1461709 13f79535-47bb-0310-9956-ffa450edef68
The problem is that the wrong class loader is used for the "ofbiz-config-*" threads (NativeLibClassLoader instead of CachedClassLoader). This happens when the threads are created by the static code in ExecutionPool.java when it is executed before the ClassLoaderContainer.init() initializes the CachedClassLoader.
This also causes other problems like: The local resolution of XML Schema files won't work any more because it's also using the wrong classloader, which can't find the XSD files:
[java] 2011-07-21 12:21:45,333 (ofbiz-config-0) [ UtilXml:1022:WARN ] [UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with publicId [null] and the file/resource is [service-eca.xsd]
You can trigger this behavior in current ofbiz trunk by setting an expire time for the properties cache in cache.properties
properties.UtilPropertiesResourceCache.expireTime=10000
The Debug.log() statements in the ContainerLoader then load the logging configuration properties file and cache it. If an expire time is set, the ExecutionPool is used and creates the "ofbiz-config-*" threads too early.
By not pre-starting the "ofbiz-config-*" threads in the static code (patch above), the threads are then created later on, when the "main" thread classloader has become the CachedClassLoader and everythings starts working again.
jleroux:
* I don't see any issues, but performance, to not start the whole core threads. This is BTW the default behaviour. So I'd recommend to use it for GLOBAL_EXECUTOR.
* I also removed the useless deprecated methods
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1435701 13f79535-47bb-0310-9956-ffa450edef68
I tried to use the non useLog4J branch and localised it to show more like how useLog4J renders. But I found some issues with (time was not in sync useLog4J when I used both) and finally did not use it. So it's only the l10n part
I also added a convenient get()
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1426606 13f79535-47bb-0310-9956-ffa450edef68
When a groovy script fails, currently you can only follow the stack trace to rg.ofbiz.base.util.ScriptUtil.executeScript(ScriptUtil.java:348), but not into the failed script itself, which makes debugging really hard.
This can easily be improved by wrapping the exception there:
- throw new IllegalArgumentException(errMsg);
+ throw new IllegalArgumentException(errMsg, e);
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1398679 13f79535-47bb-0310-9956-ffa450edef68