It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×10,962
×7,469
×6,036
×5,939
×4,318

question asked: Jul 04 '16, 9:39 a.m.
question was seen: 3,961 times
last updated: Jul 05 '16, 8:06 p.m.

Related questions

502 startup get Exception: org.apache.commons.lo ception: Invalid class loader hierarchy.

0
Norman Dignard (356●6●96●177) | asked Jul 04 '16, 9:39 a.m.
Trying to do a server rename. On startup we get  in tomcat catalina

INFO: Server startup in 66402 ms
Exception in thread "Thread-22" org.apache.commons.logging.LogConfigurationException: org.apache.commons.lo
ception: Invalid class loader hierarchy.  You have more than one version of 'org.apache.commons.logging.Log
igurationException: Invalid class loader hierarchy.  You have more than one version of 'org.apache.commons.
ging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader
 visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid cl
ogging.Log' visible, which is not allowed.))
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
        at com.ibm.rdm.fronting.server.concurrent.RRSConcurrency$1.uncaughtException(RRSConcurrency.java:62
        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:799)
        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:797)
        at java.lang.Thread.uncaughtException(Thread.java:1241)
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfiguratio
 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogC
 version of 'org.apache.commons.logging.Log' visible, which is not allowed.)
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
        ... 7 more
Caused by: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy.  You have
t allowed.
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385)


and the services fail to start. What/how do i resolve this error?
Comments
Bas Bekker commented Jul 04 '16, 11:27 a.m.
JAZZ DEVELOPER

Please provide more details; what application(s) your are using that gives this error, what version of the application, where do you see this error (log file, console?).

Norman Dignard commented Jul 04 '16, 12:25 p.m.

We're running 502 ifix14  single clm install using tomcat and oracle backend on RH 6.4. The error is on startup in the catalina.out 

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered Jul 04 '16, 9:42 p.m.
Did you accidentally throw a .jar file into the Tomcat library path? The class org.apache.commons.logging.Log is provided in the file org.apache.commons.logging_###.jar and each CLM application has a copy of this file (same version: 1.0.4.v201005080501, except CLMHelp which is 1.0.4.v201101211617). If a different version of this file has already loaded by Tomcat, the others will fail to load. So double check whether there is an extra copy of this file lying around somewhere.
Comments
Norman Dignard commented Jul 05 '16, 7:38 a.m.

I believe I found the issue. In dropping https in the server rename, I may have missed changing an apps web.xml setting from "confidential" to "NONE". This may have been the root cause.  

Donald Nong commented Jul 05 '16, 8:06 p.m.

Just to clarify, did you resolve the issue by correcting one of the web.xml files?

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.