Commons-logging jar file useage

How to create a commons-logging.properties file and what are all paramter should me there in the propeties file. Basically i was using log4j.jar for logging the message. Now i want to use the commons-logging.jar for logging messsge. for that i have to create properties files with the specific paramter.
help me....
thanks in advacne

Here is home page of commons logging project:
http://jakarta.apache.org/commons/logging/
And short user guide available there:
http://jakarta.apache.org/commons/logging/guide.html

Similar Messages

  • Commons-logging.jar

    How to use commons-logging.jar files ?
    i want to get the .java files from this

    How to use commons-logging.jar files ?
    i want to get the .java files from this1. Go here.
    2. Follow links to download source.

  • Replace commons-logging.jar with another version

    Hi all,
    I'm using CR4E version 2 Update 4(v. 12.2.205) and I would use instead of
    commons-logging.jar (v. 1.1.1) provided, the version used in my application
    (v. 1.0.4). Is possible without errors?
    I specify that I not use the provided log4j.jar in CR4E v.2.
    Thanks a lot

    The versions that we provide with our product is the version that we expect to be using when using our product.  Any other version may or may not work and there would be no way to fix an issue specific to using a different version than what we provide.

  • Cluster and commons-logging jar LogConfigurationException

    Hi,
    My configuration:
    -OAS 10.1.3.1 on 2 machines with oracle cluster configuration (discovery).
    My app:
    -ear which includes simple ejb3 module with commons-logging-1.1.jar lib (Jakarta commons logging)
    -clustering and replication is configured (in orion-application.xml):
    <cluster allow-colocation="false">
         <replication-policy trigger="onSetAttribute" scope="allAttributes" />
         <flow-control-policy enabled="false" />
         <protocol>
              <peer>
                   <opmn-discovery />
              </peer>
         </protocol>
    </cluster>
    When I'm trying to deploy my application I always get an error during deployment:
    [19-Jun-2007 16:46:44] Initializing ClassLoader(s)
    [01-Jan-1970 01:00:00] Error deserializing return-value: org.apache.commons.logging.LogConfigurationException; nested exception is: java.lang.ClassNotFoundException: org.apache.commons.logging.LogConfigurationException
    It doesn't matter if I try to deploy it on one or both machines. The exception is always the same on each machine.
    When I get rid of clustering/replication configuration (from orion-application.xml or during deployment) application is deployed without any problem.
    Also when I remove commons-logging-1.1.jar application is deployed.
    I know that there is already apache.commons.logging 1.0.4 in OAS shared libraries by it's not selected in "Configure Class Loading" by default.
    I also tried use the same version (1.0.4) in my app - didn't help.
    I can also deploy without any problem war file or ear file with web module, which has commons-logging-1.1.jar. But not ejb!
    Any advice?
    Thanks
    darek

    Hey Darek -- I just gave it a quick try -- the ListQueries query works as expected.
    This is how I executed it and the results it returned.
    d:\java\oc4j-10131-prod\j2ee\home>java -Doc4j.start.query=ListQueries+Exit -jar oc4j.jar
    07/06/25 00:51:41 Shutting down OC4J...
    AuditLoader - Performs various diagnostics on the contents of the speci
    fied loader(s).
    Callers - List all classes that call the specified method(s).
    ClassLoadMetrics - Report metrics from specified loader(s) or all if none specified.
    ClassPath - List the code-sources in use.
    Dependencies - List the dependencies of the specified class.
    Depends - List all classes that depend on the specified class(s).
    DuplicateClasses - List duplicate classes, both loaded and in code-sources.
    DuplicateCodeSources - List code-sources that have more than 1 subscriber, or the same name.
    Exit - Exits the process (does shutdown if system is running).
    FindResource - List the code-sources containing the specified resource.
    GetResource - Call getResource() or getResources() on a specified loader and report the results.
    HttpSessions - View summary of active HttpSessions for deployed applications.
    LeakedLoaders - Control detection of class loader leaks and inspect results.
    ListQueries - List built-in subclasses of the "oracle.classloader.query.Query" class.
    LoadClass - Call loadClass() or Class.forName() using a specified loader and report the results.
    LoadedClasses - List the names of all loaded classes (if available).
    LoaderTree - List the class loader tree.
    Packages - List the package names contained within the specified code-source(s).
    SharedLibraries - List shared-libraries and the loaders that have imported them.
    SystemProperties - List or set System properties.
    ThreadPools - List application server related thread for the current VM.
    Threads - List thread info for the current VM.
    UnusedCodeSources - List any code-sources from which no classes or resources have been loaded.
    Uptime - Report how long the system has been running.
    VMStat - List statistic info for the current VM.
    Specify the query name for a full description, or use the '-l' option to see ful
    l descriptions for all.

  • J2ee.jar causes problems with commons-logging.jar

    Hi All -
    (JDK 1.5.0_03, commons-logging 1.0.4, latest j2ee.jar, Eclipse 3.1.0 RC3 )
    I am developing some components that are to be used within j2ee containers and in standalone mode as well. When I run the software under Tomcat, it works correctly (Tomcat is not using the j2ee.jar that comes with Sun's App server obviously), but when I develop with the j2ee.jar file that comes with Sun's App server, I can't use commons-logging. For example, the code supplied below (a class with only this line in the main method, not using any j2ee features) will fail JUST by having j2ee.jar in my path, but if I take it out of the path, it works fine. I am also on the commons-logging mail list and no one there has been able to solve this issue for me. Again, if I deploy my application to Tomcat, I don't have this problem.
    The isolated line that is giving me the issue (and will give the issue even in a non j2ee application that just has this one line) is this:
    log= LogFactory.getLog(CommonsLoggingTest.class);
    When I run this without j2ee.jar in the path, it works fine. When I run it with j2ee.jar in the path, I get this:
    Exception in thread "main" org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException))
         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.redhawk.testing.CommonsLoggingTest.doTest(CommonsLoggingTest.java:27)
         at com.redhawk.testing.CommonsLoggingTest.main(CommonsLoggingTest.java:45)
    Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException)
         at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
         at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
         ... 5 more
    Caused by: java.lang.NullPointerException
         at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:374)
         ... 6 more
    Anyone have any ideas? Its really annoying to have to take this jar file out of my path every time I want to run a test. I could just start developing against other implementations of the j2ee classes I need (for example, Tomcat's jar files do not give this error) but for various reasons that is also undesirable.
    Thanks!
    Jason

    This problem does not arise with commons-logging 1.0.3.
    Any idea what is different in 1.0.4 that would introduce problems when Sun's j2ee.jar is in the path?

  • Commons-logging.jar and log4j.jar

    Folks:
    First of all, what are those commons-xxx.jar, such as commons-beanutil.jar, commons-collections.jar, commons-digester.jar, etc?
    What is the difference between commons-loggin.jar ann log4j.jar? I read a post somewhere saying that commons-loggin.jar points to log4j.jar, why?
    Could somebody throw some thoughts to enlighten me, please?
    Thanks a lot !

    http://jakarta.apache.org/commons/index.html

  • Commons-logging error when starting Flex2 in JRun

    Created new JRun Server and deployed Flex2 to this server.
    Receiving this error when starting up this server instance.
    Starting Macromedia JRun 4.0 (Build 92909), logicerm2 server
    07/13 22:23:28 info JRun Naming Service listening on *:2911
    07/13 22:23:28 warning No sessionSecret has been specified in
    jrun.xml. Installi
    ng a self generated sessionSecret.
    07/13 22:23:28 info No JDBC data sources have been configured
    for this server (s
    ee jrun-resources.xml)
    07/13 22:23:28 info JRun Web Server listening on *:8102
    07/13 22:23:28 info Deploying enterprise application
    "default-ear" from: file:/C
    :/JRun4/servers/logicerm2/default-ear/
    07/13 22:23:28 info Deploying web application "JRun Default
    Web Application" fro
    m: file:/C:/JRun4/servers/logicerm2/default-ear/
    07/13 22:23:29 info Web Services in default-ear#default-war:
    07/13 22:23:29 info AdminService
    07/13 22:23:29 warning default-war web application has
    'reload' as true in jrun-
    web.xml. Consider setting it false if the application is
    running in production e
    nvironment.
    07/13 22:23:29 warning default-war web application has
    'compile' as true in jrun
    -web.xml. Consider setting it false if the application is
    running in production
    environment.
    07/13 22:23:29 user JSPServlet: init
    07/13 22:23:29 info Deploying web application "Flex Data
    Services" from: file:/C
    :/JRun4/servers/logicerm2/flex/
    07/13 22:23:29 user JSPServlet: init
    07/13 22:23:29 user FlexMxmlServlet: init
    07/13 22:23:29 INFO Loading configuration file
    C:\JRun4\servers\logicerm2\flex\W
    EB-INF\flex\flex-webtier-config.xml
    07/13 22:23:30 INFO Loading configuration file
    C:\JRun4\servers\logicerm2\flex\W
    EB-INF\flex\flex-config.xml
    07/13 22:23:30 user FlexMxmlServlet: Starting Adobe Flex Web
    Tier Compiler
    07/13 22:23:30 user FlexMxmlServlet: Adobe Flex Web Tier
    Compiler Build: 143451
    07/13 22:23:30 user MessageBrokerServlet: init
    07/13 22:23:31 user FlexSwfServlet: init
    07/13 22:23:31 user FlexInternalServlet: init
    07/13 22:23:31 info Deploying web application "Flex Admin Web
    Application" from:
    file:/C:/JRun4/servers/logicerm2/flex-admin/
    07/13 22:23:31 user JSPServlet: init
    07/13 22:23:31 user MessageBrokerServlet: init
    07/13 22:23:31 info Deploying web application "Flex Data
    Services Samples" from:
    file:/C:/JRun4/servers/logicerm2/samples/
    07/13 22:23:31 user JSPServlet: init
    07/13 22:23:31 user FlexMxmlServlet: init
    07/13 22:23:32 INFO Loading configuration file
    C:\JRun4\servers\logicerm2\sample
    s\WEB-INF\flex\flex-webtier-config.xml
    07/13 22:23:32 INFO Loading configuration file
    C:\JRun4\servers\logicerm2\sample
    s\WEB-INF\flex\flex-config.xml
    07/13 22:23:32 user FlexMxmlServlet: Starting Adobe Flex Web
    Tier Compiler
    07/13 22:23:32 user FlexMxmlServlet: Adobe Flex Web Tier
    Compiler Build: 143451
    07/13 22:23:32 user MessageBrokerServlet: init
    07/13 22:23:32 error Could not pre-load servlet:
    MessageBrokerServlet
    [1]org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logg
    ing.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationExcept
    ion: Invalid class loader hierarchy. You have more than one
    version of 'org.apa
    che.commons.logging.Log' visible, which is not allowed.
    (Caused by org.apache.co
    mmons.logging.LogConfigurationException: Invalid class loader
    hierarchy. You ha
    ve more than one version of 'org.apache.commons.logging.Log'
    visible, which is n
    ot allowed.) (Caused by
    org.apache.commons.logging.LogConfigurationException: or
    g.apache.commons.logging.LogConfigurationException: Invalid
    class loader hierarc
    hy. You have more than one version of
    'org.apache.commons.logging.Log' visible,
    which is not allowed. (Caused by
    org.apache.commons.logging.LogConfigurationExc
    eption: Invalid class loader hierarchy. You have more than
    one version of 'org.
    apache.commons.logging.Log' visible, which is not allowed.))
    at
    org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
    Impl.java:543)
    at
    org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
    Impl.java:235)
    at
    org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
    Impl.java:209)
    at
    org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
    at
    org.apache.commons.httpclient.params.DefaultHttpParams.<clinit>(Defau
    ltHttpParams.java:53)
    at
    flex.messaging.services.http.HTTPProxyAdapter.<init>(HTTPProxyAdapter
    .java:111)
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
    Method)
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
    Source)
    at
    sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
    Sou
    rce)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at java.lang.Class.newInstance0(Unknown Source)
    at java.lang.Class.newInstance(Unknown Source)
    at
    flex.messaging.util.ClassUtil.createDefaultInstance(ClassUtil.java:71
    at
    flex.messaging.Destination.createAdapter(Destination.java:277)
    at
    flex.messaging.Destination.initDestination(Destination.java:103)
    at
    flex.messaging.services.HTTPProxyService.createDestination(HTTPProxyS
    ervice.java:78)
    at
    flex.messaging.services.AbstractService.createDestinations(AbstractSe
    rvice.java:82)
    at
    flex.messaging.config.MessagingConfiguration.createServices(Messaging
    Configuration.java:187)
    at
    flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
    gConfiguration.java:84)
    at
    flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
    5)
    at
    jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
    java:1242)
    at
    jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
    ice.java:789)
    at
    jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
    va:291)
    at
    jrun.deployment.DeployerService.initModules(DeployerService.java:711)
    at
    jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
    ce.java:242)
    at
    jrun.deployment.DeployerService.deploy(DeployerService.java:430)
    at
    jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
    ce.java:179)
    at
    jrun.deployment.DeployerService.run(DeployerService.java:891)
    at
    jrunx.scheduler.SchedulerService.invokeRunnable(SchedulerService.java
    :223)
    at
    jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
    ava:426)
    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
    Caused by:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.comm
    ons.logging.LogConfigurationException: Invalid class loader
    hierarchy. You have
    more than one version of 'org.apache.commons.logging.Log'
    visible, which is not
    allowed. (Caused by
    org.apache.commons.logging.LogConfigurationException: Inval
    id class loader hierarchy. You have more than one version of
    'org.apache.common
    s.logging.Log' visible, which is not allowed.)
    at
    org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
    actoryImpl.java:397)
    at
    org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
    Impl.java:529)
    ... 30 more
    Caused by:
    org.apache.commons.logging.LogConfigurationException: Invalid class
    l
    oader hierarchy. You have more than one version of
    'org.apache.commons.logging.
    Log' visible, which is not allowed.
    at
    org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
    actoryImpl.java:385)
    ... 31 more
    [0]flex.messaging.config.ConfigurationException: Unable to
    create service 'flex.
    messaging.services.HTTPProxyService' for 'proxy-service' due
    to the following er
    ror: org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.lo
    gging.LogConfigurationException: Invalid class loader
    hierarchy. You have more
    than one version of 'org.apache.commons.logging.Log' visible,
    which is not allow
    ed. (Caused by
    org.apache.commons.logging.LogConfigurationException: Invalid cla
    ss loader hierarchy. You have more than one version of
    'org.apache.commons.logg
    ing.Log' visible, which is not allowed.) (Caused by
    org.apache.commons.logging.L
    ogConfigurationException:
    org.apache.commons.logging.LogConfigurationException:
    Invalid class loader hierarchy. You have more than one
    version of 'org.apache.c
    ommons.logging.Log' visible, which is not allowed. (Caused by
    org.apache.commons
    .logging.LogConfigurationException: Invalid class loader
    hierarchy. You have mo
    re than one version of 'org.apache.commons.logging.Log'
    visible, which is not al
    lowed.)).
    at
    flex.messaging.config.MessagingConfiguration.createServices(Messaging
    Configuration.java:202)
    at
    flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
    gConfiguration.java:84)
    at
    flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
    5)
    at
    jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
    java:1242)
    at
    jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
    ice.java:789)
    at
    jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
    va:291)
    at
    jrun.deployment.DeployerService.initModules(DeployerService.java:711)
    at
    jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
    ce.java:242)
    at
    jrun.deployment.DeployerService.deploy(DeployerService.java:430)
    at
    jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
    ce.java:179)
    at
    jrun.deployment.DeployerService.run(DeployerService.java:891)
    at jrunx.scheduler.SchedulerS07/13 22:23:33 user
    FlexSwfServlet: init
    ervice.invokeRunnable(SchedulerService.java:223)
    at
    jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
    ava:426)
    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
    PLEASE Help!!!
    Bernie

    Figured this one out:
    Searched thru instance of JRun that flex was installed in and
    removed all the additional commons-logging jar files I
    found.

  • Struts, log4j, commons-logging problems in 9.0.4 too??

    ok... I have a J2EE project that uses struts, log4j, a couple ejbs. I can successfully deploy and run on JBoss. However, our client insists that we use the 10g App Server, so I tried to deploy on 10g v10.1.2 (after making the appropriate changes to the deployment descriptors); the ear file deployed without problems, but when using the application, I encountered the following error when the app got to part of my code that tries to create a log file using the commons-logging framework:
    java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
    I see from these forums that there is a known problem regarding commons-logging and log4j with v10.1.2 (Help: 10g, struts, commons-logging and log4j doesn't work in 10g!? 9i fine! )..... so, I installed v9.0.4 of the 10g AppServer, deployed and ...... drum roll please.... I get the same error.
    The commons-logging.jar file IS in the [application dir]/WEB-INF/lib directory so the app should be finding the org.apache.commons.logging.LogFactory class file. And - struts is working based on page navigation prior to hitting the error (which I've heard indicates that the commons-logging.jar library is being invoked at some point).
    So... am I missing something? or does v9.0.4 also have the bug (related to classloaders)???
    sure hope someone can help....
    Scott

    I don't know why it's not working either, unless it's related to that classloader issue.... I have the following files in my WEB-INF/lib directory:
    commons-beanutils.jar
    commons-collections.jar
    commons-digester.jar
    commons-logging.jar
    commons-validator.jar
    jakarta-oro.jar
    log4j-1.2.9.jar
    struts.jar
    ScottsTester-ejb.jar (my ejb classes)
    ScottsTester-web.jar (my struts-related classes)
    I'm running into problems when the app tries to create an instance of my ejb (which has as a member variable an org.apache.commons.logging.Log object which is created by the org.apache.commons.logging.LogFactory object - the Oracle App Server is telling me it can't find the LogFactory class despite the fact that the commoons-logging.jar file is in the WEB-INF/lib directory.... and, as other postings have noted, this appears to be a problem with the classloaders. Unfortunately, the workaround suggesting by Qiang causes problems with my ejbs - when I try to get a home object, I encounter a ClassCastException somewhere in the PortableRemoteObject.narrow(o, DbConnectionHome.class); call..... maybe Oracle should stick to databases.....

  • Weblogic admin console fails to start when commons logging is used.

    I have an application that requires commons logging.
    I followed the instructions as per the documentation and other forum entries such as How to use log4j into weblogic 10.3 to add the commons logging jar from apache and the weblogic jar specified. Plus I set the system property for the LogFactory.
    When I start up the application server I see messages as expected from my application. But when I start up the weblogic Admin console I get and exception and the console fails to start. I even tried to put the jars in my applicaiton instead of the domain/lib directory to try to iscolate the issue but still got issues with starting the Console.
    Any ideas on why this is occuring?
    See the error below:
    ####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <----------------------------------------Retention Init()---------------------------------------->
    ####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <Thu May 20 05:00:00 EDT 2010>
    ####<May 19, 2010 4:16:06 PM EDT> <Info> <Health> <TE001XU-CATOR1> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1274300166060> <BEA-310002> <81% of the total memory in the server is free>
    ####<May 19, 2010 4:35:03 PM EDT> <Info> <WorkManager> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301303146> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
    ####<May 19, 2010 4:35:17 PM EDT> <Error> <HTTP> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301317582> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
    java.lang.ExceptionInInitializerError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
    at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
    at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
    at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
    at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl cannot be cast to org.apache.commons.logging.LogFactory)
    at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:574)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
    at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:254)
    at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
    at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.<clinit>(MBeanUtilsInitSingleFileServlet.java:23)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
    at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
    at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
    at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
    at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Thank you for replying. Yes that is the first place we looked and tried. Actually to be more specific we followed the instrcutions under: "How to Use the Commons API with WebLogic Logging Services" of the same link.
    Are you thinking that maybe we are we missing a step somewhere else within the site?
    Not sure if I was clear before but we are using Weblogic 10.3 and also tried up to version 10.3.3. And we get the same results.
    We prefer to use the method with commons logging for our application.
    One more specific here what we did on our last attempt.
    1. added this to the startWeblogic script JAVAOPTIONS -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
    2. we put the WebLogic-specific Commons classes, $BEA_HOME/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar, together with the commons-logging.jar file in one of the following locations: APP-INF/LIB or WEB-INF/LIB directory or DOMAIN_NAME/LIB directory server CLASSPATH
    We are still not able to get the Weblogic admin console to start
    Any other ideas?
    Edited by: user13094648 on May 21, 2010 10:29 AM
    Edited by: user13094648 on May 21, 2010 10:37 AM

  • Commons logging hell

    I wounder if others have struggeled with commons logging problems with BEA portal 9.2. I've added commons-logging into APP-INF/lib, but the portal web application gives me ClassNotFoundException.
    So I tried to remove it from APP-INF/lib and add it to WEB-INF/lib. I still got an ClassNotFoundException. Last try was to extract the jar file into WEB-INF/classes. Finally the I was able to avoid getting the ClassNotFoundException, but another problem came. But BEA - why do you have to give us the same stacktrace FOUR TIMES??????
    Throwable: java.lang.NullPointerException
    Stack Trace:
    java.lang.NullPointerException
    at com.bea.wlw.netui.pageflow.internal.WeblogicPageFlowEventReporter.exceptionRaised(WeblogicPageFlowEventReporter.java:155)
    at org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler.handleException(DefaultExceptionsHandler.java:132)
    at org.apache.beehive.netui.pageflow.FlowController.handleException(FlowController.java:272)
    at org.apache.beehive.netui.pageflow.FlowController.create(FlowController.java:579)
    at org.apache.beehive.netui.pageflow.PageFlowController.create(PageFlowController.java:433)
    at org.apache.beehive.netui.pageflow.FlowControllerFactory.createPageFlow(FlowControllerFactory.java:307)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.getFlowController(PageFlowRequestProcessor.java:610)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:512)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
    at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
    at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1169)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1200)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1200)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:688)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:268)
    at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.render(PageFlowStubImpl.java:136)
    at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:288)
    at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:427)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:708)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:183)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:339)
    at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:186)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:140)
    at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:370)
    at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:229)
    at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:195)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:180)
    at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:221)
    at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:594)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:251)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Trond Andersen, Invenia AS, http://www.invenia.no

    How to use commons-logging.jar files ?
    i want to get the .java files from this1. Go here.
    2. Follow links to download source.

  • BPEL 2.1.2 lacks commons-logging

    I found a packaging issue with OC4J/BPEL 2.1.2 which is apparently not tracked in the forum. When starting a web application integrating something like the Apache Struts framework you get an error on Struts configuration initialization. I think it is a classloader problem, because Struts calls commons-digester which calls commons-beanutils which is packaged in orabpel.jar (1.6.1), which in turn calls commons-logging which is not packaged with BPEL. The classloader cannot load it back from the WEB-INF/lib directory.
    By the way wouldn't it be better to package all those commons-*.jar libraries outsise orabpel. It would be easier to track those kind of problems.

    Hi tbeigbeder,
    I am stuck with the same problem of commons-logging.jar.
    I have soasuite v10.1.3.1.0 installed on my system. The BPEL version soasuite is using is v10.1.3.1.0.
    I am trying to deploy a STRUTS application under home>hw_services:
    Application Name: gpi-mms-app (one web-module and one ejb)
    Parent Application: hw_services (Human Workflow Services)
    Binding web-module to site: default-web-site
    But I get the same error that you faced. Then I tried your solution of putting the commons-logging.jar file entry in global OC4J application.xml.
    But while starting soasuite it says class loader hierarchy is not correct and complained to remove commons-logging.jar file from global OC4J application.xml.
    I tried copying commons-logging.jar file in each and every lib folder. but got the same error class loader hierarchy is not correct.
    Here is the stack trace when I tried deploying the application.
    07/05/24 15:12:27.892 10.1.3.1.0 Started
    07/05/24 15:12:32.299 gpi-mms: Error initializing servlet
    java.lang.NoClassDefFoundError
         at org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:505)
         at org.apache.commons.digester.Rule.end(Rule.java:276)
         at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1318)
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
         at org.apache.commons.digester.Digester.parse(Digester.java:1567)
         at org.apache.struts.action.ActionServlet.initServlet(ActionServlet.java:1433)
         at org.apache.struts.action.ActionServlet.init(ActionServlet.java:466)
         at javax.servlet.GenericServlet.init(GenericServlet.java:256)
         at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2361)
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4810)
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4734)
         at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4922)
         at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1134)
         at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:738)
         at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
         at com.evermind.server.Application.getHttpApplication(Application.java:545)
         at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
         at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1909)
         at com.evermind.server.http.HttpSite.addHttpApplication(HttpSite.java:1606)
         at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:238)
         at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:99)
         at oracle.oc4j.admin.internal.ApplicationDeployer.bindWebApp(ApplicationDeployer.java:547)
         at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:202)
         at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
         at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
         at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
         at java.lang.Thread.run(Thread.java:595)
    07/05/24 15:12:32.314 gpi-mms: Error preloading servlet
    javax.servlet.ServletException: Error initializing servlet
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4837)
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4734)
         at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4922)
         at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1134)
         at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:738)
         at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
         at com.evermind.server.Application.getHttpApplication(Application.java:545)
         at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
         at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1909)
         at com.evermind.server.http.HttpSite.addHttpApplication(HttpSite.java:1606)
         at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:238)
         at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:99)
         at oracle.oc4j.admin.internal.ApplicationDeployer.bindWebApp(ApplicationDeployer.java:547)
         at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:202)
         at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
         at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
         at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
         at java.lang.Thread.run(Thread.java:595)
    07/05/24 15:12:32.314 gpi-mms: 10.1.3.1.0 Started

  • Problems with signed JAR files in JWS/JRE6 environment.

    Hello All,
    I'm encountering a problem running our desktop application as a Java Web Start deployment in a JRE 6 environment. There were never any problems when running the same application as a JWS deployment in JRE 1.4, or 5, environments. There are also currently no problems in a JRE 6 environment when running the application as a standard desktop application.
    The problem which I am having has nothing to do with launching the application. But for good measure, I verified the JNLP file with JaNeLA. A couple things we out of order, which I addressed to make JaNeLA happy, but my problem still persists. Here is my JNLP file (anonymized to protect the innocent):
    TS: 2010-10-18 17:04:46
    <?xml version="1.0" encoding="UTF-8"?>
    <jnlp codebase="$$codebase" href="$$name">
         <information>
              <title>Acme Desktop</title>
              <vendor>Acme Corporation</vendor>
              <homepage href="http://www.acme.com/"/>
              <description>Acme Client for Acme Server</description>
              <description kind="tooltip">Acme Client for Acme Server</description>
              <icon href="desktop.gif"/>
              <offline-allowed/>
         </information>
         <security>
              <all-permissions/>
         </security>
         <resources>
              <j2se version="1.5+"/>
              <jar href="acmedesktop.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/antlr-2.7.2.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/backport-util-concurrent.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/commons-codec-1.3.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/commons-httpclient.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/commons-logging.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/acmeapi.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/HelpJavaDT.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/HelpJavaDT_es.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/jacorb.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/Multivalent.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/slf4j-api-1.5.6.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/slf4j-jdk14-1.5.6.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/snow.jar" download="lazy" version="8.00.01.00+"/>
              <jar href="lib/AcmeTMClient.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/xercesImpl.jar" download="eager" version="8.00.01.00+"/>
              <jar href="lib/xml-apis.jar" download="eager" version="8.00.01.00+"/>
              <extension name="installer" href="desktopInstaller.jnlp" />
              <extension name="Java Help" href="help.jnlp"/>
              <property name="java.library.path" value="./lib"/>
              <property name="admin" value="false"/>
              <property name="webstart" value="true"/>          
              <!-- The following two lines are for SSO implementation only
              <property name="urladdress" value="http://localhost:8080/AcmeDesktop/servlet/AcmeServlet"/>
              <property name="cookiespec" value="RFC2109"/>
              -->          
         </resources>
         <resources os="Windows">
              <nativelib href="lib/jniWin32.jar" version="8.00.01.00+"/>
         </resources>
         <application-desc main-class="desktop"/>     
    </jnlp>-----
    When running as a JWS deployment, on JRE 6, the application will be functioning normally for a little while, and then suddenly the following exception is thrown, and the current operation fails because the class in question cannot be accessed:
    java.lang.SecurityException: class "acmeapi.communication.CDocImpl"'s signer information does not match signer information of other classes in the same package
         at java.lang.ClassLoader.checkCerts(ClassLoader.java:807)
         at java.lang.ClassLoader.preDefineClass(ClassLoader.java:488)
         at java.lang.ClassLoader.defineClassCond(ClassLoader.java:626)
         at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
         at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
         at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
         at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
         at com.sun.jnlp.JNLPClassLoader.findClass(JNLPClassLoader.java:288)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at acmeapi.common.CDoc.getAnnotationsInfo(CDoc.java:493)
         at acmedesktop.communication.CCommunicationManager.privateGetAnnotations(CCommunicationManager.java:1976)
         at acmedesktop.communication.CCommunicationManager.getAnnotations(CCommunicationManager.java:1828)
         at acmedesktop.annotations.CViewAnnotations.getAnnotations(CViewAnnotations.java:826)
         at acmedesktop.annotations.CViewAnnotations.createView(CViewAnnotations.java:583)
         at acmedesktop.annotations.CViewAnnotations.setData(CViewAnnotations.java:736)
         at acmedesktop.annotations.CViewAnnotations.init(CViewAnnotations.java:205)
         at acmedesktop.hitspanel.CHitsPanel.viewAnnotations(CHitsPanel.java:281)
         at acmedesktop.hitspanel.CHitsTab$3.mousePressed(CHitsTab.java:316)
         at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:263)
         at java.awt.Component.processMouseEvent(Component.java:6260)
         at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
         at java.awt.Component.processEvent(Component.java:6028)
         at java.awt.Container.processEvent(Container.java:2041)
         at java.awt.Component.dispatchEventImpl(Component.java:4630)
         at java.awt.Container.dispatchEventImpl(Container.java:2099)
         at java.awt.Component.dispatchEvent(Component.java:4460)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4235)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
         at java.awt.Container.dispatchEventImpl(Container.java:2085)
         at java.awt.Window.dispatchEventImpl(Window.java:2478)
         at java.awt.Component.dispatchEvent(Component.java:4460)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)-----
    The classes of our desktop product are contained within the 'acmedesktop' and 'acmeapi' packages. It requires access to the hard drive of the workstation, and therefore, all jar files included with the application are signed using the following ANT task when compiled:
    <signjar keystore="resources/codesigning/keystore.pfx" storetype="pkcs12" storepass="myPassword" alias="myAlias">
         <fileset dir="${jws_dist}/app" includes="*.jar"/>
         <fileset dir="${jws_dist}/app/lib" includes="*.jar" excludes="jhall__V${dt_version}.jar"/>
    </signjar>-----
    Therefore, all classes, within all jar files, are signed with the same certificate (with the exception of the JavaHelp libraries, which are already signed by Sun - but the class in question attempting to be loaded here is not contained within the JavaHelp jar file anyway). So, the point being, that the exception message stating that the "signer information of the acmeapi.communication.CDocImpl class doesn't match the signer information of other classes in the same package", is simply not correct. All classes within that jar file were signed using the same certificate.
    I downloaded the JRE 6 source from dev.java.net and picked through this issue with a debugger. The ClassLoader.checkCerts() method compares the certificate used to sign the current class which is attempting to be loaded, with the certificates which signed all other previously loaded classes within the same package. If they don't match, the exception above is thrown. What is causing the issue is when the checkCerts() method attempts to get the certificates which signed the currently loading class, null is returned. And obviously, comparing null, with an array of the certificates which signed the previously loaded classes, isn't going to match; therefore this exception is thrown.
    The checkCerts() method gets the certificates of the currently loading class by calling the java.security.CodeSource.getCertificates() method. Tracing deeper in the debugger, the CodeSource object ultimately gets the certificates from the 'signersRef' member variable of the com.sun.deploy.cache.CachedJarFile class. signerRef is a SoftReference object and can therefore be garbage collected at some point. If it has already been garbage collected, the CachedJarFile class will attempt to retrieve it again from the loaded cache entry by calling com.sun.deploy.cache.MemoryCache.getLoadedResource().
    The MemoryCache class maintains the cache entries to the jar files as MemoryCache.CachedResourceReference objects, which subclass WeakReference, and therefore these objects can be garbage collected as well. If the cache entries have also been garbage collected, this leaves the CachedJarFile class with no ability to repopulate the CachedJarFile.signerRef object. Therefore it is completely out of luck getting the certificates which signed the currently loading class, which ultimately causes the above exception.
    When the com.sun.deploy.cache.Cache class attempts to retrieve a cache entry using its getCacheEntry() method, it will attempt to get the entry from the MemoryCache class, if null is returned, it will recreate the cache entry and add it back to the MemoryCache. In contrast, when the CachedJarFile class attempts to get a cache entry from the MemoryCache class, if null is returned, it just gives up.
    (from com.sun.deploy.cache.CachedJarFile:244)
    private CacheEntry getCacheEntry() {
         /* if it was not created by Cache do not search for entry */
         if (resourceURL == null)
              return null;
         CacheEntry ce = (CacheEntry) MemoryCache.getLoadedResource(resourceURL);
         if (ce == null) {
              //This should not happen because CacheEntry should not get collected
              // before CachedJarFile is collected.
              Trace.println("Missing CacheEntry for " + resourceURL + "\n" + ce,
                   TraceLevel.CACHE);
         return ce;
    When debugging, code execution falls within the code block with the comment stating "This should not happen...", but it is happening in my case.
    On an interesting side note, using the jvisualvm.exe tool included with JDK 6, I was able to tell that it seems as though these objects are collected the first time that the JVM allocates more heap space, and then the issue will occur. If I set the initial heap size very large (using -Xms) this issue won't occur at all. But that is kind of a bad solution which I would rather not do, but it is interesting to note for the sake of troubleshooting this issue. The max heap size (-Xmx) is plenty big enough, so the issue is not that we are running out of memory here.
    Does anyone have any insight as to what could be causing this? I've searched, and found a couple threads with similar problems but with no clear solutions. It is not just one workstation either, it happens everywhere I deploy the app as a Java Web Start application in a JRE 6 environment. I have been using version 1.6.0_18 on XP, but it seems to happen on any update version of 1.6. Is the fact that the CachedJarFile class doesn't attempt to reload the resource when it can't retrieve it from MemoryCache a bug? I've dug as deep as I can on this and I'm at wits end, does anybody have any ideas?
    Thank you
    Jake
    Edited by: jkc532 on Nov 12, 2010 10:35 AM

    jkc532 wrote:
    .. Is the fact that the CachedJarFile class doesn't attempt to reload the resource when it can't retrieve it from MemoryCache a bug? From your comprehensive investigation and report, it seems so to me.
    ..I've dug as deep as I can on this and I'm at wits end, does anybody have any ideas?Just after read the summary I was tired, so I have some understanding of the effort you have already invested in this (the 'wits' you have already spent). I think you should raise a bug report and seek Oracle's response.

  • Error in deploying .jar file from JDeveloper 10.1.3.5

    Hello,
    I want to deploy .jar file in a machine, instead of having to install JDeveloper to run the application (it contains: Web Services and Data Base).
    I have followed the following steps in JDeveloper to create the .jar file:
    1) Right click over the project: New... --> General (All Technologies option selected) --> Deployment Profiles --> JAR File
    2) I have selected "Include Manifest File" option specifying the application's main class
    3) In JAR Deployment Profile Properties window: File Groups --> Project Output --> Contributors are selected: "Project Output Directory" and "Project Dependencies"
    4) With the previous steps, JDeveloper generates a .deploy file. It is created in Resources folder. From this folder, I have selected the .deploy file and right click and I have selected "Deploy to JAR file"
    The .jar is created succesfully. In this point, I try to execute with the command:
    java -jar NAME_OF_THE_DIRECTORY_WHERE_THE FILEIS_DEPLOYED\NameFile.jar
    and I have the following error:
    Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/rpc/ServiceFactory
    at project.proxy.AccountClient.<init><AccountClient.java>
    at project.proxy.AccountClient.main<init><AccountClient.java>
    The Manifest File content is:
    Manifest-Version: 1.0
    Created-By: Oracle JDeveloper 10.1.3.5.0
    Main-Class: project.proxy.AccountClient
    I have tested with differents variables to create the .jar file, but always the error is the same. And I haven't found information to solve it. For this reason, I appreciate any help.
    Thank you and regards.
    Edited by: user1634407 on 31-mar-2010 8:27
    Edited by: user1634407 on 31-mar-2010 8:47

    If you are just building a client that access a Web service you need a JAR and not a WAR.
    Ok!
    One thing to try is look at the command line that JDeveloper uses to run your client (it's in the log window) - specifically look at the classpath used.
    Then try and run the same thing from a command line and see if it works.
    Nowadays, the application is running with a .BAT file, it contains the statement released from the JDeveloper console, and it is working perfectlly.
    I try to do the same from a command line, and it works too.
    Assuming it is - you can either use that, or you'll need to make sure that your JAR includes all the mentioned jars that were in the class path - this is done through the library type file group.
    To create the .JAR file I have choosen the following options (JAR Deployment Profile Properties):
    1) Include Manifest File --> I have selected the class that contains the main class (from the Browse option)
    2) I left the default File Groups (Project Output) --> it has: Project Output Directory + Project Dependencies
    3) As you said me, I have created a new File Group (type: Libraries) --> and here, I have selected all the possible Contributors. These match those specified in the project (Oracle XML Parser v2, J2EE, JAX-RPC Client, Commons Logging 1.0.3, Ojdbc14.jar).
    4) Deployment to JAR File successfully.
    The resulting MANIFEST.MF is:
    Manifest-Version: 1.0
    Created-By: Oracle JDeveloper 10.1.3.5.0
    Main-Class: project.proxy.Execution
    It hasn't definied "Class-Path", althought to especified a new File Group with the libraries... Is it an error?
    If I extract the .JAR file, I see all libraries, and I have two folders: one with .class files of my project and other one is META-INF with MANIFEST.MF file.
    5) From command line I executed:
    C:\jdevstudio10135\jdk\bin > java -jar C:\jdevstudio10135\jdev\mywork\project\project\deploy\NameFile.jar
    And the result is an error:
    Exception in thread "main": java.lang.NoClassDefFoundError: javax/xml/rpc/ServiceFactory
    I think the error is because it can not find the library ServiceFactory, but it is especified inside JAX-RPC Client library. What is wrong?
    *6)* I have tried too to insert in "JAR Deployment Profile Properties" (in JAR options) an additional Manifest File to merge into MANIFEST.MF, to include "Class-Path" with all libraries's project (the same JAR from the statement released from the JDeveloper console), but I think that it is a limit, because if I insert all libraries the "Class-Path" doesn't inserted in MANIFEST.MF. The maxim is:
    Class-Path: C:\jdevstudio10135\jdev\mywork\project\project\classes C:\jdevstudio10135\lib\xmlparserv2.jar C:\jdevstudio10135\lib\xml.jar C:\jdevstudio10135\j2ee\home\lib\activation.jar C:\jdevstudio10135\j2ee\home\lib\ejb.jar C:\jdevstudio10135\j2ee\home\lib\jms.jar C:\jdevstudio10135\j2ee\home\lib\jta.jar C:\jdevstudio10135\j2ee\home\lib\mail.jar C:\jdevstudio10135\j2ee\home\lib\servlet.jar C:\jdevstudio10135\webservices\lib\jaxrpc-api.jar
    The following libraries afther the previous one aren't allowed to include because I think that is exceeding the maximum size.
    I have tested to create various MANIFEST.MF with different PATHs libraries, but it isn't work to include in the MANIFEST.MF file all libraries...
    (C:\jdevstudio10135\webservices\lib\wsclient.jar
    C:\jdevstudio10135\webservices\lib\wsserver.jar
    C:\jdevstudio10135\webservices\lib\wssecurity.jar
    C:\jdevstudio10135\webservices\lib\wsdl.jar
    C:\jdevstudio10135\webservices\lib\orasaaj.jar
    C:\jdevstudio10135\webservices\lib\saaj-api.jar
    C:\jdevstudio10135\webservices\lib\orawsdl.jar
    C:\jdevstudio10135\webservices\lib\orawsrm.jar
    C:\jdevstudio10135\webservices\lib\jaxr_api.jar
    C:\jdevstudio10135\webservices\lib\orajaxr.jar
    C:\jdevstudio10135\webservices\lib\relaxngDatatype.jar
    C:\jdevstudio10135\webservices\lib\jaxb-impl.jar
    C:\jdevstudio10135\webservices\lib\jaxb-libs.jar
    C:\jdevstudio10135\webservices\lib\xsdlib.jar
    C:\jdevstudio10135\webservices\lib\mdds.jar
    C:\jdevstudio10135\jlib\jaxen.jar
    C:\jdevstudio10135\jlib\oraclepki.jar
    C:\jdevstudio10135\jlib\ojpse.jar
    C:\jdevstudio10135\jlib\osdt_core.jar
    C:\jdevstudio10135\jlib\osdt_cert.jar
    C:\jdevstudio10135\jlib\osdt_xmlsec.jar
    C:\jdevstudio10135\jlib\osdt_wss.jar
    C:\jdevstudio10135\jlib\osdt_saml.jar
    C:\jdevstudio10135\jlib\repository.jar
    C:\jdevstudio10135\jlib\ojmisc.jar
    C:\jdevstudio10135\j2ee\home\lib\http_client.jar
    C:\jdevstudio10135\j2ee\home\jazncore.jar
    C:\jdevstudio10135\j2ee\home\oc4jclient.jar
    C:\jdevstudio10135\rdbms\jlib\xdb.jar
    C:\jdevstudio10135\diagnostics\lib\ojdl2.jar
    C:\jdevstudio10135\jakarta-taglibs\commons-logging-1.0.3\commons-logging-api.jar
    C:\jdevstudio10135\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar
    C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14.jar
    C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14_g.jar
    C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14dms.jar
    C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14dms_g.jar)
    With this .MF file (or including only "C:\jdevstudio10135\jdev\mywork\project\project\classes") I have solved the other problem (not found the libraries), but it still not working, the error is a little different:
    Exception in thread "main": java.lang.NoClassDefFoundError: project/proxy/Execution
    The path where the main class is: C:\jdevstudio10135\jdev\mywork\project\project\classes\project\proxy\Execution.class
    I have tried to insert directlly the following paths in "Main Class" option of "Include Manifest File":
    C:\jdevstudio10135\jdev\mywork\project\project\classes\project\proxy\Execution
    C:\\jdevstudio10135\\jdev\\mywork\\project\\project\\classes\\project\\proxy\\Execution
    And with these values, the error is the same: Exception in thread "main": java.lang.NoClassDefFoundError
    I am not sure if the error is a bug of JDeveloper 10.1.3.5 or it is something that I don't correctly. Any idea?
    Thank you again and regards.
    Edited by: user12085357 on 08-abr-2010 1:31
    Edited by: user12085357 on 08-abr-2010 1:38
    Edited by: user12085357 on 08-abr-2010 6:58

  • How to use commons.logging in weblogic (8.1)?

    Greetings,
    I'm trying to use commons.logging framework to manage the logs of my
    application. With Weblogic I will use an implementation that works with
    weblogic.logging package but with other J2EE products I'll use another
    native log implementations or frameworks (for instance, for jboss I will
    use log4j).
    1) I created a class WeblogicLogger which implements the Log interface::
    public final class WeblogicLogger implements Log {
    I packaged this class in a jar file with a properties file,
    commons-logging.properties, which has the property setting my class
    below has the default logger:
    org.apache.commons.logging.Log=pt.ptinovacao.weblogic.logging.WeblogicLogger
    2) My sample code has the following code:
    import org.apache.commons.logging.Log;
    import org.apache.commons.logging.LogFactory;
    private static final Log log = LogFactory.getLog(
    LogTimeStartHandler.class.getName());
    something(){
    log.info(this.getClass()+" test log");
    3) I added the commons-logging jars and my jar with my custom wrapper
    weblogic logger in ${WL_HOME}/common/bin/commEnv.sh:
    WEBLOGIC_CLASSPATH=
    (...)${CLASSPATHSEP}${WL_HOME}/server/lib/weblogiclogger.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging-api.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging.jar
    However, my loggings still not appear in my weblogic server. Did I miss
    something?
    thanks,
    Pedro Salazar

    Did you manage to get this working?
    If yes ... what did you do?
    I am having the same problem implementing commons-logging with log4j

  • How do you know the version of a JAR file ?

    how do you know the version of a JAR file ?
    is it what is written on MANIFEST.MF ?
    for example i have a JAR file
    whose MANIFEST.MF has this
    Manifest-Version: 1.0
    Created-By: Ant 1.4.1so, whats the version of this JAR ? 1.0 ?

    anyway, that was JSTL..jar.
    Now, come to another JAR file....
    whose MANIFEST.MF has......
    Manifest-Version: 1.0
    Created-By: Apache Ant 1.5.1
    Extension-Name: Struts Framework
    Specification-Title: Struts Framework
    Specification-Vendor: Apache Software Foundation
    Specification-Version: 1.1
    Implementation-Title: Struts Framework
    Implementation-Vendor: Apache Software Foundation
    Implementation-Vendor-Id: org.apache
    Implementation-Version: 1.1
    Class-Path:  commons-beanutils.jar commons-collections.jar commons-dig
    ester.jar commons-logging.jar commons-validator.jar jakarta-oro.jar s
    truts-legacy.jarso, How do you believe whats the version now ? do u go with the comment "Manifest-Version: 1.0" or "Specification-Version: 1.1" ?
    definitely, you would go with the "Specification-Version: 1.1" and declare this JAR as STRUTS 1.1
    hmmm, so, if nothing is mentioned like above should we follow the MANIFEST version as the JSTL version ? in my earlier example i did not find any comment on ""Specification-Version" ......so , if anybody gives me that JAR , how do i decide whether its 1.0 specification or 1.1 specifucation compliant ?
    can you tell whats the JSTL version of my earler example JAR file ?

Maybe you are looking for