You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2012/10/25 17:36:28 UTC
[Bug 54053] New: LogManager initialization failed when running from
Jdeveloper.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54053
Priority: P2
Bug ID: 54053
Assignee: log4j-dev@logging.apache.org
Summary: LogManager initialization failed when running from
Jdeveloper.
Severity: critical
Classification: Unclassified
Reporter: elutsky@gmail.com
Hardware: PC
Status: NEW
Version: unspecified
Component: Configurator
Product: Log4j
Environment:
JDeveloper 11.1.1.6.0
logj42 (apache-log4j-2.0-beta2-bin)
Windows 7 64bits
Steps to Reproduce:
//config file presents or not - does not meter.
Run / Debug simple application:
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
public class test_log {
public test_log() {
super();
}
static Logger logger = LogManager.getLogger(test_log.class.getName());
public static void main(String[] args) {
test_log test_log = new test_log();
logger.entry();
logger.debug("test");
logger.error("test Err");
logger.exit();
}
...
}
Actual Results:
Failed with error
java.lang.ExceptionInInitializerError
at view.test_log.<clinit>(test_log.java:13)
Caused by: java.lang.ClassCastException: oracle.xml.parser.v2.DTD cannot be
cast to org.w3c.dom.Element
at java.util.XMLUtils.load(XMLUtils.java:61)
at java.util.Properties.loadFromXML(Properties.java:852)
at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:77)
Additional Info:
When xmlparserv2.jar is deleted - application run fine.
But - it have to be presents - when deleted, JDeveloper failed to start.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[Bug 54053] LogManager initialization failed when running from
Jdeveloper.
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54053
Evgeny <el...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |elutsky@gmail.com
OS| |All
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[Bug 54053] LogManager initialization failed when running from
Jdeveloper.
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54053
--- Comment #2 from Ralph Goers <Ra...@dslextreme.com> ---
Please see https://issues.apache.org/jira/browse/LOG4J2-104
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[Bug 54053] LogManager initialization failed when running from
Jdeveloper.
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54053
Ralph Goers <Ra...@dslextreme.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Ralph Goers <Ra...@dslextreme.com> ---
Log4j 2 issues should be reported in Jira, not bugzilla.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org