I'm hitting the same problem described in here, but I don't know my websphere version at the time
More questions 1) does Removing commons-logging-1.1.jar fix it? 2) what if I really need to put commons-logging-1.1.jar in my application? How can I fix this?
This happens because the class org.apache.commons.logging.impl.Jdk14Logger
is loaded by a different classloader than the one that loaded the Log
interface.
According to IBM's documentation, whenever you use a third-party library that WebSphere itself uses for its own internal purposes, you must:
PARENT_LAST
; andIn your case:
PARENT_LAST
commons-logging-1.1.jar
within your EAR (you can place it in the "EAR Library" directory, usually EAR/lib
).