3

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?

Improve this question

2 Answers 2

Reset to default
1

Theres a fix pack of ibm for this. https://www-304.ibm.com/support/docview.wss?uid=swg21502693

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

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:

  1. Set your EAR's classloader policy to PARENT_LAST; and
  2. Ensure that your EAR is self-sufficient. That is, that your third-party libraries (and their dependencies) are bundled within the EAR.

In your case:

  1. Set your EAR's classloader policy to PARENT_LAST
  2. Include commons-logging-1.1.jar within your EAR (you can place it in the "EAR Library" directory, usually EAR/lib).
Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.