Hi, I am trying to deploy a Phobos app to a virtual server and I am getting the following error in my logs.

The deploy says it is successful, but the app does not respond to requests. Can anyone tell me how to resolve this?

Thanks,
Tony

om.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.)) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at com.sun.org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370) at org.apache.catalina.startup.DigesterLogger.<init>(ContextConfig.java:1038) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:339) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:784) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:263) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:130) at org.apache.catalina.core.StandardContext.start(StandardContext.java:5021) at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:182) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224) at org.apache.catalina.core.StandardHost.start(StandardHost.java:924) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520) at org.apache.catalina.startup.Embedded.start(Embedded.java:917) at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70) at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:478) at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304) Caused by: com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 17 more Caused by: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) ... 18 more

 

 

which version of web server are you using here ?

if you are not trying it out with web server 7 update 2, can u try it out and let us know
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJWS-7.0U2-OTH-G-F@CDS-CDS_SMI

 

 

I am sorry for not being more clear. I am using version 7 update 2. I just installed it about two weeks ago.

I am running it on Debian Linux.
I do have four virtual hosts in one configuration set up on four different ip addresses.
Two of the virtual hosts have Java applications installed and running fine.
The third virtual host is just serving static content.
The fourth virtual host I am trying to install the Phobos app on.

The other Java apps have many jar files as they are forum software ecommerce software.

I am new to the Sun Web Server so this is my first time setting up a production server. Should each virtual host be in its own configuration? or does that not make any difference in this situation?

Thanks,

Tony

 

 

Check the .jars in your Java class-path and/or in the Phobos app. The error message from your stack trace indicates that there are 2 .jar files with different versions of the same class - com.sun.org.apache.commons.logging.Log

Caused by: com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.) at

 

 

Any idea on how to find the double class inside all of the jar files? When I try to deploy a bare bones Phobos app, this is what shows up in the log. If you look at the beginning, there are a few errors before the stack trace. I know this class comes in jsf-impl.jar, but there is only one of those in my class path.

Here is my class path as well from my server.xml.

<jvm>
<java-home>/usr/lib/jvm/java-6-sun-1.6.0.04</java-home>
<class-path-prefix/>
<server-class-path>/sun/webserver7/lib/webserv-rt.jar:/sun/webserver7/lib/pwc.jar:/sun/webserver7/lib/ant.jar:${java.home}/lib/tools.jar:/sun/webserver7/lib/ktsearch.jar:/sun/webserver7/lib/webserv-jstl.jar:/sun/webserver7/lib/jsf-impl.jar:/sun/webserver7/lib/jsf-api.jar:/sun/webserver7/lib/webserv-jwsdp.jar:/sun/webserver7/lib/container-auth.jar:/sun/webserver7/lib/mail.jar:/sun/webserver7/lib/activation.jar</server-class-path>
<class-path-suffix/>
<native-library-path-prefix/>
<debug>false</debug>
<debug-jvm-options>-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7896</debug-jvm-options>
<jvm-options>-Djava.security.auth.login.config=login.conf</jvm-options>
<jvm-options>-Xms512m -Xmx768m</jvm-options>
<jvm-options>-XX:MaxPermSize=256m</jvm-options>
</jvm>

24/Mar/2008:14:16:19 failure Click to view more details for this message PWC3014: Parse error in application web.xml
com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.)) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at
com.sun.org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370) at org.apache.catalina.startup.DigesterLogger.<init>(ContextConfig.java:1038) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:339) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:784) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:263) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:130) at org.apache.catalina.core.StandardContext.start(StandardContext.java:5021) at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:182) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224) at org.apache.catalina.core.StandardHost.start(StandardHost.java:924) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520) at org.apache.catalina.startup.Embedded.start(Embedded.java:917) at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70) at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:478) at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304) Caused by: com.sun.org.apache.commons.logging.LogConfigurationException: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. (Caused by com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed.) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 17 more Caused by: com.sun.org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'com.sun.org.apache.commons.logging.Log' visible, which is not allowed. at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) ... 18 more
24/Mar/2008:14:16:19 failure PWC3040: Marking this application unavailable due to previous error(s)
24/Mar/2008:14:16:19 failure PWC1306: Startup of context failed due to previous errors
24/Mar/2008:14:16:19 failure Null component com.sun.web-2:type=JspMonitor,name=jsp,WebModule=//planetphobos/,J2EEApplication=null,J2EEServer=none
24/Mar/2008:14:16:19 info CORE3280: A new configuration was successfully installed
24/Mar/2008:14:16:18 info CORE3276: Installing a new configuration
24/Mar/2008:14:16:18 info WEB0100: Loading web module in virtual server [planetphobos] at [/]

 

 

Your server-class-path entries look ok. Check inside each of the .jar files in the phobos web application's WEB-INF/lib directory.

Edited by: Arvind_Srinivasan on Mar 25, 2008 5:54 AM

 

 

I found it in a jar file inside the Phobos lib directory. So what are my options for fixing this? I also emailed the Phobos mailing list on this.

Thanks,

Tony Z

 

 

Please could you point me to the Phobos sample that is giving you this problem. I was able to successfully deploy both example.war and demoj1.war from https://phobos.dev.java.net/getting_started.html. If I can reproduce your problem then I'll be able to tell you which file you need to remove/change to fix the startup issue.

 

 

Thank you for responding. I downloaded and can deploy each of the examples you referenced as well, and they work fine. However, I am using Netbeans 6. If I do a sample new application, build it, and deploy it, I get the error messages I previously posted. Those war files may be somewhat dated on the Phobos site. I will post this info to the Phobos mailing list as well. Is there anyway to manually adjust these? What if you had two applications that needed two different versions of a library?

Thanks,

Tony Z

 

 

Thanks. I was able to reproduce the problem.

I was able to work-around/fix the problem in 2 ways

1. Removing/renaming WEB-INF/lib/logging-api-1.0.4.jar from the Phobos sample application
2. Creating/adding WEB-INF/sun-web.xml and setting the class-loader delegate attribute to true.

% cat /tmp/phob/WEB-INF/sun-web.xml
<?xml version="1.0" encoding="UTF-8" ?>
 
<!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 Servlet 2.3//EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-web-app_2_3-0.dtd'>
 
 
<sun-web-app>
    <class-loader delegate='true'/>
</sun-web-app>

#2 is the preferred solution, although I doubt #1 will do any serious harm.
Two applications requiring different versions of a library wouldn't be a problem as each web application could keep that library in its WEB-INF/lib directory. The problem (like in this case) occurs when a web application uses a different version of the library that is also in the server classpath or is also used by the servlet/jsp implementation in the server.

Ideally, the implementation classes of the servlet/jsp container wouldn't be visible to web applications and then you wouldn't run into this kind of problem. We'd planned to do this but haven't yet done so.

http://docs.sun.com/app/docs/doc/819-2634/gdqup?a=view documents the classloader hierarchy in Web Server. By setting the class-loader delegate flag, you can configure the preferred order in which classloaders are used for loading a particular class.

 

 

Thank you for helping me through this. I would never have traced this down without your help. I tried solution two and it worked like a charm. I have also updated the Phobos mailing list. I will now know how to recognize this in the future if needed. We will be able to move on to more programming! :-)

 

 

Happy to help. Thanks for choosing to use Web Server 7.