Warn in log4j

hi i have i small problem that is :
im using oracle ADF & myFaces(tomahawk) With ejb
im using the log4j in the ejb interceptor not in the View layer
and deploy them to oc4j
i put the logConfig.xml in the bin folder
every think is ok but there is this warn when i start the container
=================
:WARN No appenders could be found for logger (com.sun.fac
es.config.ConfigureListener).
07/01/20 11:09:37 log4j:WARN Please initialize the log4j system properly.
=============
ok and my Config.xml is like that
===================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration debug="false" xmlns:log4j='http://jakarta.apache.org/log4j/'>
<appender name="jdbcApp" class="org.apache.log4j.jdbc.JDBCAppender">
<param name="Driver" value="oracle.jdbc.OracleDriver"/>
<param name="User" value="OPT2006"/>
<param name="Password" value="accad"/>
<param name="URL" value="jdbc:oracle:thin:@speed:1521:accad"/>
<param name="Sql" value="INSERT INTO LOGTABLE (LDATE,LNAME,LLEVEL,LMESSAGE) VALUES (to_date('%d{dd-MM-yyyy HH:mm:ss}','dd-MM-yyyy HH24:MI:ss') ,'%c' , '%p' , '%m')"/>
</appender>
<logger name="net.accad">
<level value="all"/>
<appender-ref ref="jdbcApp"/>
</logger>
<logger name="oracle.adf" level="INFO"/>
<logger name="oracle.adfinternal" level="INFO"/>
<logger name="oracle.jbo" level="INFO"/>
<logger name="com.sun.faces.config.ConfigureListener" level="INFO"/>
<root>
<level value ="off"/>
<appender-ref ref="jdbcApp"/>
</root>
</log4j:configuration>
==================
so what should i do to remove this warn
thanks

Hi mihran,
could you tell me how you configured the log4j for your ejb-module?
I've tried to configure log4j correctly for my J2EE-application but I'm getting errors from my ejb module that he can't find the log4j-configuration?
I've created an ejb-jar file for the ejbModule and included this is my war-file where I've specified the log4j-library and commons-library and I'm still getting this error?

Similar Messages

  • Warning on logger of Beehive class

    Hi all,
    When starting Weblogic Network Gatekeeper, I always encountered warning against Log4j on one of Beehive's class as follows:
    log4j:WARN No appenders could be found for logger (org.apache.beehive.netui.pageflow.internal.AdapterManager).
    log4j:WARN Please initialize the log4j system properly.
    I have pointed the log4j configuration to the correct location of log4jconfiguration.xml, but the warning keeps poping up on me.
    Any help would be greatly appreciated.
    Regards,
    Setya

    Hi,
    Or you can try making a Validation View Object (VVO) for the VO that populates the advancedTable, and check if the mapped value is empty there...
    Hope it Helps!
    Thiago

  • Log4j-style logging configuration

    Hi,
    from the AdminGuide for OIM 11.1.1.5 (http://docs.oracle.com/cd/E21764_01/doc.1111/e14308/log.htm#CEGEAGIB) I learned I can use the log4j style logging in my Java code. I tried, and I could successfully generate messages with the WARN level or more severe.
    The docs also says the logging configuration file is OIM_HOME/config/log.properties
    It is probably not so, since I've tried to change the line
    log4j.rootLogger=WARN,stdoutto
    log4j.rootLogger=DEBUG,stdoutnothing happened, I still see no messages with INFO severity in my output.
    Regards,
    Vladimir

    How about if you remove the log.properties all together from the location which is specified in the doc? Do you still get logs? Additionally you can do a directory search for all the log.properties on the MWHOME directory and work on the result files? I too think that the location might be pointed out incorrectly in the docs or otherwise this should have worked.
    -Bikash

  • Log4j level inheritance concept doubt

    log.properties file
    log4j.debug=true
    log4j.rootLogger=ERROR, A1
    log4j.appender.A1=org.apache.log4j.ConsoleAppender
    log4j.appender.A1.layout=org.apache.log4j.PatternLayout
    log4j.appender.A1.layout.ConversionPattern=%m%n
    log4j.logger.logging.basics=WARN, cs3
    log4j.appender.cs3=org.apache.log4j.RollingFileAppender
    log4j.appender.cs3.layout=org.apache.log4j.PatternLayout
    log4j.appender.cs3.File=c:\\logas.txt
    log4j.appender.cs3.layout.ConversionPattern=%m%n
    log4j.appender.cs3.MaxFileSize=100KB
    log4j.appender.cs3.MaxBackupIndex=1
    log4j.additivity.com.durasoft.logging=false
    log4j.logger.RAM=INHERITED, B1
    log4j.appender.B1=org.apache.log4j.RollingFileAppender
    log4j.appender.B1.layout=org.apache.log4j.PatternLayout
    log4j.appender.B1.File=c:\\trylog.txt
    log4j.appender.B1.layout.ConversionPattern=%m%n
    log4j.appender.B1.MaxFileSize=100KB
    log4j.appender.B1.MaxBackupIndex=1
    package logging.basics;
    import java.io.FileInputStream;
    import java.io.IOException;
    import java.util.Properties;
    import org.apache.log4j.BasicConfigurator;
    import org.apache.log4j.FileAppender;
    import org.apache.log4j.Logger;
    import org.apache.log4j.PatternLayout;
    import org.apache.log4j.PropertyConfigurator;
    import org.apache.log4j.spi.RootLogger;
    public class LogBasics
         public static void main(String[] args) throws IOException
              Properties prop = new Properties();
              FileInputStream stream = new  FileInputStream("logging\\Resources\\log.properties");
              prop.load(stream);
              PropertyConfigurator.configure(prop);
              Logger temp = Logger.getLogger("RAM");
              RootLogger root = (RootLogger)                     Logger.getRootLogger();
              temp.error("h1i"); 
              temp.warn("hel1lo");
    }Refering to above code and properties file(in bold font), the logger named "RAM" didnt inherit from logging.basics package(which it lies), but inherits only from root, even though level and appenders for logging.basics package is specified in properties file.
    I doubt, because according to level inheritance concept, the logger must inherit from parent level(assuming parent is not null).
    Here parent ,is logging.basics for LogBasics class,so RAM logger must inherit from logging.basics as logging.basics is defined in properties file.
    But,its not happening?Why it is so?
    2) also please explain me what getLogger does when configured using property file
    Thank you.

    phanikrishnait wrote:
    Hai
    I have 3 class class A,B,C in multi level as below the method present in class A should only be accessed in A and B .Should not be visible in C and notaccessible for C class object.Java does not support that in general. In this specific case, if A and B are in the same package, and C is in a different package, and the method in question has package-private access level (not public, private, or protected).
    However, if you're doing this, you almost certainly have a design flaw. My guess is you're trying to use inheritance for code sharing, which is not what it's for.

  • Logger DWR with LOG4J.

    Hello,
    After looking at various forums, we want to use Log4J Logger. We added the following line in the properties of log4j:
    log4j.category.uk.ltd.getahead.dwr=warn,my_appender
    log4j.additivity.uk.ltd.getahead.dwr=false
    We should add a parameter for more Logge Log4J with and not in the System.
    Thank you.

    how can I log the traces from DWR into the filesystem of an application instead of SystemOut.log (WebSphere)?First Google result for "dwr logging" is this: [http://directwebremoting.org/dwr/server/servlet/logging]
    And it says:
    if DWR discovers commons-logging then it will use that in place of servlet logging.So, you need to verify whether [Commons Logging|http://commons.apache.org/logging/] is present in your server, and put it there if it is.
    Then you need to determine the logging level of the DWR messages that you care about. It's probably "info" or "debug" rather than "warn".

  • Log4j: Failed to rename while rolling

    Hi!
    I read a lot about the problem we have but I didn�t get a satisfied answer for my problem. So, maybe you can help me.
    The current situation is that we use a Tomcat which hosts different web applications. Each web application has a log4j.jar in the WEB-INF/lib directory and a logging.ecf which configures log4j and has the following content:
    log4j.rootCategory=warn, F
    log4j.additivity.design.error.logger.gui=FALSE
    log4j.additivity.design.script.logger.gui=FALSE
    log4j.logger.design.error.logger.gui=debug
    log4j.logger.design.script.logger.gui=debug
    log4j.appender.F=org.apache.log4j.RollingFileAppender
    log4j.appender.F.File=${.webapp.dir}/Log/log.txt
    log4j.appender.F.MaxFileSize=1MB
    log4j.appender.F.MaxBackupIndex=10
    log4j.appender.F.layout=org.apache.log4j.PatternLayout
    log4j.appender.F.layout.ConversionPattern=<tr><td class="A">%c</td><td class="B">%d{ISO8601}</td><td class="C">%m</td><td class="D">%p</td></tr>%nWhat happens is that sometimes no backup files are created over night, i.e. log4j seems to have problems with renaming the files and so overwrites them. We got this exception:
    log4j:ERROR Failed to rename [script_logger.txt] to [script_logger.txt.2007-10-05]I read that the problem may be that the current file is locked. Is that right? How can we solve this problem? Can you help me?
    -- jacquipre

    We have a "layout" servlet which programmatically configures log4j and writes script_logger.txt and error_logger.txt (both as DailyRollingFileLogger).
    But the error is also occuring when renaming "log.txt"...

  • Issue with JDeveloper 11.1.1.5.1

    Hi guys,
    I recently installed JDeveloper version 11.1.1.5.1 by reading the chapter 2 of this Fusion Application Developer's Guide [http://download.oracle.com/docs/cd/E15586_01/fusionapps.1111/e15524.pd] and setup up Integrated WebLogic Server accoding the instructions. But since the domain setup of WebLogic Server its throwing several errors and warnings while launching.
    Following is the log
    starting weblogic with Java version:
    <MessageLocalizationHelper> <getLocalizedMessage> The resource for bundle "oracle.apps.fnd.applcore.diagnostics.resource.DiagnosticsBundle" with key "DiagnosticsConfigMXBean.getSpecificValidationStatus" cannot be found.
    <MessageLocalizationHelper> <getLocalizedMessage> The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
    <Sep 30, 2011 5:06:05 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\jdeveloper\ecsf\modules\oracle.ecsf_11.1.1\oracle.ecsf.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:05 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\jdeveloper\ecsf\modules\oracle.ecsf_11.1.1\oracle.ecsf.service.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:07 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\jaxrs-framework-web-lib\829i9k/WEB-INF/web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:07 PM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oracle.bi.integration.adf [LibSpecVersion=1.0,LibImplVersion=11.1.1]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: oracle.bi.integration.adf, Specification-Version: 1, Implementation-Version: 11.1.1.2.0, because of conflicting library Manifest values, and library information registered with the server: [Implementation-Version: 11.1.1.2.0 vs. 11.1.1]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library..
    weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: oracle.bi.integration.adf, Specification-Version: 1, Implementation-Version: 11.1.1.2.0, because of conflicting library Manifest values, and library information registered with the server: [Implementation-Version: 11.1.1.2.0 vs. 11.1.1]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library.
         at weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(LibraryDeploymentFactory.java:113)
         at weblogic.application.internal.library.LibraryDeploymentFactory.createDeployment(LibraryDeploymentFactory.java:48)
         at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:84)
         at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
         Truncated. see log file for complete stacktrace
    >
    <Sep 30, 2011 5:06:10 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\jdeveloper\atgpf\modules\oracle.applcp.model_11.1.1\oracle.applcp.model.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:16 PM IST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.as.scheduler.platform.wls.deploy.ESSApplicationLifecycleListener is ignored because the application ESSAPP is not versioned.>
    <Sep 30, 2011 5:06:19 PM IST> <Warning> <Connector> <BEA-190155> <Compliance checking/validation of the resource adapter C:\Oracle\Middleware\jdeveloper\ess\archives\ess-app\ess-ra.rar resulted in the following warnings:
    The ra.xml <resourceadapter-class> class 'oracle.as.scheduler.adapter.ra.RAImpl' should implement java.io.Serializable but does not.>
    <Sep 30, 2011 5:06:20 PM IST> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract void oracle.as.scheduler.RuntimeService.updateRequestParameter(oracle.as.scheduler.RuntimeServiceHandle,long,java.lang.String,java.lang.Object) throws oracle.as.scheduler.RequestNotFoundException,oracle.as.scheduler.ValidationException,oracle.as.scheduler.RuntimeServiceException' in EJB 'RuntimeServiceBean' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'RuntimeServiceBean' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <Sep 30, 2011 5:06:20 PM IST> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract void oracle.as.scheduler.RuntimeService.setRequestParameter(oracle.as.scheduler.RuntimeServiceHandle,long,java.lang.String,java.lang.Object) throws oracle.as.scheduler.RequestNotFoundException,oracle.as.scheduler.ValidationException,oracle.as.scheduler.RuntimeServiceException' in EJB 'RuntimeServiceBean' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'RuntimeServiceBean' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <Sep 30, 2011 5:06:20 PM IST> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.util.Enumeration oracle.as.scheduler.MetadataService.filterByPermission(oracle.as.scheduler.MetadataServiceHandle,java.util.Enumeration,oracle.as.scheduler.security.MetadataPermission$Action[]) throws oracle.as.scheduler.MetadataServiceException' in EJB 'MetadataServiceBean' contains a parameter of type: 'java.util.Enumeration' which is not Serializable. Though the EJB 'MetadataServiceBean' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <Sep 30, 2011 5:06:24 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.ecsf\dyxwqt/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:24 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.ecsf\dyxwqt/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:24 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.applcp.model\f7pg9o/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:24 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.applcp.model\f7pg9o/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:24 PM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.apps.common.resource, referenced from: C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.webcenter.framework\owur7d]. Make sure the referenced optional package has been deployed as a library.>
    <Sep 30, 2011 5:06:29 PM IST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.as.scheduler.platform.wls.deploy.ESSApplicationLifecycleListener is ignored because the application EssCentralUiApp is not versioned.>
    <JpsDstCredential> <setCredential> Cannot migrate credential folder/key EssCentralUIApp.oracle.apps.applcp.centralui/anonymous#FusionAppsContentRepositoryExtApp_SHARED.Reason oracle.security.jps.service.credstore.CredentialAlreadyExistsException: JPS-01007: The credential with map EssCentralUIApp.oracle.apps.applcp.centralui and key anonymous#FusionAppsContentRepositoryExtApp_SHARED already exists..
    <Sep 30, 2011 5:06:30 PM IST> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract void oracle.as.scheduler.RuntimeService.updateRequestParameter(oracle.as.scheduler.RuntimeServiceHandle,long,java.lang.String,java.lang.Object) throws oracle.as.scheduler.RequestNotFoundException,oracle.as.scheduler.ValidationException,oracle.as.scheduler.RuntimeServiceException' in EJB 'RuntimeServiceBean' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'RuntimeServiceBean' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <Sep 30, 2011 5:06:30 PM IST> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract void oracle.as.scheduler.RuntimeService.setRequestParameter(oracle.as.scheduler.RuntimeServiceHandle,long,java.lang.String,java.lang.Object) throws oracle.as.scheduler.RequestNotFoundException,oracle.as.scheduler.ValidationException,oracle.as.scheduler.RuntimeServiceException' in EJB 'RuntimeServiceBean' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'RuntimeServiceBean' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <Sep 30, 2011 5:06:30 PM IST> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.util.Enumeration oracle.as.scheduler.MetadataService.filterByPermission(oracle.as.scheduler.MetadataServiceHandle,java.util.Enumeration,oracle.as.scheduler.security.MetadataPermission$Action[]) throws oracle.as.scheduler.MetadataServiceException' in EJB 'MetadataServiceBean' contains a parameter of type: 'java.util.Enumeration' which is not Serializable. Though the EJB 'MetadataServiceBean' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <Sep 30, 2011 5:06:31 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\jaxrs-framework-web-lib\829i9k\WEB-INF\web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:40 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\tmp\_WL_user\jaxrs-framework-web-lib\829i9k\WEB-INF\web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Sep 30, 2011 5:06:47 PM IST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application AppsLoggerService is not versioned.>
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.ChangeAwareClassLoader@c54366 finder: weblogic.utils.classloaders.CodeGenClassFinder@8001b annotation: consoleapp@console.
    log4j: Trying to find [log4j.xml] using weblogic.utils.classloaders.GenericClassLoader@11c5bb0 finder: weblogic.utils.classloaders.CodeGenClassFinder@1d021b6 annotation: consoleapp@ class loader.
    log4j: Trying to find [log4j.xml] using ClassLoader.getSystemResource().
    log4j: Trying to find [log4j.properties] using context classloader weblogic.utils.classloaders.ChangeAwareClassLoader@c54366 finder: weblogic.utils.classloaders.CodeGenClassFinder@8001b annotation: consoleapp@console.
    log4j: Using URL [zip:C:/Oracle/MIDDLE~1/WLSERV~1.3/server/lib/consoleapp/webapp/WEB-INF/lib/console.jar!/log4j.properties] for automatic log4j configuration.
    log4j: Reading configuration from URL zip:C:/Oracle/MIDDLE~1/WLSERV~1.3/server/lib/consoleapp/webapp/WEB-INF/lib/console.jar!/log4j.properties
    log4j: Parsing for [root] with value=[WARN, stdout].
    log4j: Level token is [WARN].
    log4j: Category root set to WARN
    log4j: Parsing appender named "stdout".
    log4j: Parsed "stdout" options.
    log4j: Parsing for [org.apache.struts.validator] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category org.apache.struts.validator set to ERROR
    log4j: Handling log4j.additivity.org.apache.struts.validator=[null]
    log4j: Parsing for [com.bea.console.utils.MBeanUtils] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.utils.MBeanUtils set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.utils.MBeanUtils=[null]
    log4j: Parsing for [com.bea.console.utils.ConsoleMessagesBackingFile] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.utils.ConsoleMessagesBackingFile set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.utils.ConsoleMessagesBackingFile=[null]
    log4j: Parsing for [org.apache.beehive.netui.pageflow.internal.AdapterManager] with value=[FATAL].
    log4j: Level token is [FATAL].
    log4j: Category org.apache.beehive.netui.pageflow.internal.AdapterManager set to FATAL
    log4j: Handling log4j.additivity.org.apache.beehive.netui.pageflow.internal.AdapterManager=[null]
    log4j: Parsing for [org.apache] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category org.apache set to ERROR
    log4j: Handling log4j.additivity.org.apache=[null]
    log4j: Parsing for [com.bea.console.actions.BaseConsoleAction] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.actions.BaseConsoleAction set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.actions.BaseConsoleAction=[null]
    log4j: Parsing for [com.bea.console.actions] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.actions set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.actions=[null]
    log4j: Parsing for [com.bea.console.actions.messages.MessagesAction] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.actions.messages.MessagesAction set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.actions.messages.MessagesAction=[null]
    log4j: Parsing for [com.bea.console.utils.MBeanChangeManager] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.utils.MBeanChangeManager set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.utils.MBeanChangeManager=[null]
    log4j: Parsing for [org.apache.beehive.netui.pageflow.scoping.internal] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category org.apache.beehive.netui.pageflow.scoping.internal set to ERROR
    log4j: Handling log4j.additivity.org.apache.beehive.netui.pageflow.scoping.internal=[null]
    log4j: Parsing for [com.bea.console.utils] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.utils set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.utils=[null]
    log4j: Parsing for [com.bea.console.internal] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.internal set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.internal=[null]
    log4j: Parsing for [com.bea.console.utils.MasterControlProgram] with value=[ERROR].
    log4j: Level token is [ERROR].
    log4j: Category com.bea.console.utils.MasterControlProgram set to ERROR
    log4j: Handling log4j.additivity.com.bea.console.utils.MasterControlProgram=[null]
    log4j: Finished configuring.
    <Logger> <error> ServletContainerAdapter manager not initialized correctly.
    <MBeanAttributeInfoMappingMetaData> <<init>> No annotation should be put on attribute mutator parameter "public abstract void oracle.adf.mbean.share.connection.ess.EssConnectionMXBean.setRequestFileDirectory(java.lang.String)".
    <MBeanAttributeInfoMappingMetaData> <<init>> No annotation should be put on attribute mutator parameter "public abstract void oracle.adf.mbean.share.connection.ess.EssConnectionMXBean.setFilePersistenceMode(java.lang.String)".
    <ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    <null> <null> Namespace mapping for "/oracle/webcenter/lifecycle/importexport" is overridden by namespace mapping for "/oracle/webcenter/lifecycle"; the first mapping is not used.
    <null> <null> Namespace mapping for "/oracle/webcenter/lifecycle/importexport" is overridden by namespace mapping for "/oracle/webcenter/lifecycle"; the first mapping is not used.
    <null> <null> Namespace mapping for "/oracle/webcenter/lifecycle/importexport" is overridden by namespace mapping for "/oracle/webcenter/lifecycle"; the first mapping is not used.
    <null> <null> Namespace mapping for "/oracle/webcenter/lifecycle/importexport" is overridden by namespace mapping for "/oracle/webcenter/lifecycle"; the first mapping is not used.
    INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
    INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
    <EclipseLinkLogger> <basicLog> 2011-09-30 17:07:25.272--ServerSession(13572820)--PersistenceUnitInfo ServiceFrameworkPUnit has transactionType RESOURCE_LOCAL and therefore jtaDataSource will be ignored
    <ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    <LoggerHelper> <log> Cannot map nonserializable type "interface oracle.adf.mbean.share.config.runtime.resourcebundle.BundleListType" to Open MBean Type for mbean interface oracle.adf.mbean.share.config.runtime.resourcebundle.AdfResourceBundleConfigMXBean, attribute BundleList.
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/profiles/profileService/}ProfileService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/profiles/profileService/}ProfileService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {oracle/apps/topologyManager/model/applicationModule/common/}TopologyEndPointService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {oracle/apps/topologyManager/model/applicationModule/common/}TopologyEndPointService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/trees/service/}TreeService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/trees/service/}TreeService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmlns.oracle.com/apps/fnd/applcore/common/}ApplSessionService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmlns.oracle.com/apps/fnd/applcore/common/}ApplSessionService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/trees/service/}TreeNodeService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/trees/service/}TreeNodeService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmlns.oracle.com/oracle/apps/fnd/applcore/flex/deployment/service/model/}FlexDeploymentService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmlns.oracle.com/oracle/apps/fnd/applcore/flex/deployment/service/model/}FlexDeploymentService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/trees/service/}TreeStructureService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmnls.oracle.com/oracle/apps/fnd/applcore/trees/service/}TreeStructureService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmlns.oracle.com/topologyManager/endpoint/}TopologyEndPointService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmlns.oracle.com/topologyManager/endpoint/}TopologyEndPointService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmlns.oracle.com/topologyManager/}ProvisionConfigurationService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmlns.oracle.com/topologyManager/}ProvisionConfigurationService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmlns.oracle.com/apps/fnd/applcore/log/service/}AppsLoggerService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmlns.oracle.com/apps/fnd/applcore/log/service/}AppsLoggerService
    <ConnectionsRuntimeMXBeanImpl> <registerBean> Failed to create connection for {http://xmlns.oracle.com/topologyManager/provision/}ProvisionConfigurationService
    <ConnectionsRuntimeMXBeanImpl> <configObjectReloaded> Failed to create connection for {http://xmlns.oracle.com/topologyManager/provision/}ProvisionConfigurationService
    <ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    <ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    <ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    <ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
    <Sep 30, 2011 5:08:10 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Sep 30, 2011 5:08:10 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00012. Log messages will continue to be logged in C:\JDeveloper\system11.1.1.5.37.61.08\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
    <Sep 30, 2011 5:08:10 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Sep 30, 2011 5:08:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Sep 30, 2011 5:08:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Sep 30, 2011 5:08:11 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Sep 30, 2011 5:08:11 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Sep 30, 2011 5:08:11 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:7489:5bb:3c11:f111:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Sep 30, 2011 5:08:11 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:100:7f:fffe:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Sep 30, 2011 5:08:11 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:0:5efe:a0a:a30:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Sep 30, 2011 5:08:11 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.10.10.48:7101 for protocols iiop, t3, ldap, snmp, http.>
    Anybody knows whats wrong with this ? Though the Weblogic Server manages to run its quite slow and even while wokring on the project the JDevleoper randomly throws several exceptions

    Hi,
    sorry, but this forum cannot assist in issues that include Oracle Fusion Applications as we don't have the same JDeveloper version publicly available.
    Frank

  • Filenet connection with java api not working

    I have written the following code to connect content engine and process engine..
    MY content engine is connected fine and good...But process engine is not connecting
    code:
    public String PE_CONNECTION_POINT      = "PEConnection";
    public Connection ceConnection;
    public Domain ceDomain;
    public void testFileNetConnection()
    * Connect to Content Engine and retrieve a list of
    * properties for the base 'Document' document class
    ceConnection =
    Factory.Connection.getConnection(FILENET_URI);
    Subject ceSubject =
    UserContext.createSubject(ceConnection, FILENET_USERNAME, FILENET_PASSWORD, null);
    UserContext.get().pushSubject(ceSubject);
    ceDomain = Factory.Domain.fetchInstance(ceConnection, CE_DOMAIN, null);
    ObjectStore ceObjectStore = Factory.ObjectStore.fetchInstance(ceDomain, CE_OBJECTSTORE, null);
    ClassDefinition classDef =
    Factory.ClassDefinition.fetchInstance(ceObjectStore, "pawan", null);
    PropertyDefinitionList properties = classDef.get_PropertyDefinitions();
    for (Iterator propertyIter = properties.iterator(); propertyIter.hasNext();) {
    PropertyDefinition property = (PropertyDefinition) propertyIter.next();
    System.out.println("Property: " + property.get_DisplayName());
         //this.instantiateFolder(ceObjectStore);
         //this.createFile(ceObjectStore, ceDomain);
    UserContext.get().popSubject();
    * Connect to Process Engine and retrieve a list of
    * Queues for this Connection Point
    VWSession peSession = new VWSession();
    peSession.setBootstrapCEURI(FILENET_URI);
    String[] queueNames = null;
    try
         peSession.logon(FILENET_USERNAME ,FILENET_PASSWORD,PE_CONNECTION_POINT);
         queueNames =
         peSession.fetchQueueNames(VWSession.QUEUE_PROCESS);
    catch(Exception es){es.printStackTrace();}
    for (String queue : queueNames)
    System.out.println("Queue: " + queue);
    The output of above code I have attached part of successful connection of the content engine and the error of process engine
    Property: Ignore Redirect
    Property: Entry Template Object Store Name
    Property: Entry Template Launched Workflow Number
    Property: Entry Template Id
    java.lang.NoClassDefFoundError: com/ibm/CORBA/iiop/ObjectURL
         at filenet.pe.peorb.client.ORBSession.establishORBSession(ORBSession.java:667)
         at filenet.pe.peorb.client.ORBSession.<init>(ORBSession.java:985)
         at filenet.vw.server.PECommandsFactory.getPECommands(PECommandsFactory.java:119)
         at filenet.vw.api.VWSession.logonByDomain(VWSession.java:864)
         at filenet.vw.api.VWSession.logon(VWSession.java:723)
         at FileNetConnectionTest.testFileNetConnection(FileNetConnectionTest.java:97)
         at FileNetConnectionTest.main(FileNetConnectionTest.java:35)
    Caused by: java.lang.NoClassDefFoundError: com/ibm/CORBA/iiop/ObjectURL
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Unknown Source)
         at com.ibm.websphere.naming.WsnInitialContextFactory.init_implClassCtor(WsnInitialContextFactory.java:172)
         at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:112)
         at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
         at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
         at javax.naming.InitialContext.init(Unknown Source)
         at javax.naming.InitialContext.<init>(Unknown Source)
         at filenet.pe.peorb.client.ORBServiceHelper.getORB(ORBServiceHelper.java:442)
         at filenet.pe.peorb.client.ORBServiceHelper.initFromORBRouterInfo(ORBServiceHelper.java:286)
         at filenet.pe.peorb.client.ORBServiceHelper.<init>(ORBServiceHelper.java:873)
         at filenet.pe.peorb.client.ORBSession.establishORBSession(ORBSession.java:653)
         ... 6 more
    Exception in thread "main" java.lang.NullPointerException
         at FileNetConnectionTest.testFileNetConnection(FileNetConnectionTest.java:104)
         at FileNetConnectionTest.main(FileNetConnectionTest.java:35)
    When to remove the above error I add IBMORB.jar in enviroment variable then I get following error
    log4j:WARN The log4j system is not properly configured!
    log4j:WARN All ERROR messages will be sent to the system console until proper configuration has been detected.
    Exception in thread "main" com.filenet.api.exception.EngineRuntimeException: SECURITY_INVALID_CREDENTIALS: Invalid credentials.
         at com.filenet.apiimpl.wsi.ClientOperation.getCredential(ClientOperation.java:303)
         at com.filenet.apiimpl.wsi.ClientOperation.setCallContext(ClientOperation.java:194)
         at com.filenet.apiimpl.wsi.ClientOperation.start(ClientOperation.java:102)
         at com.filenet.apiimpl.wsi.ClientOperation.run(ClientOperation.java:69)
         at com.filenet.apiimpl.wsi.ServiceSession.getObjects(ServiceSession.java:242)
         at com.filenet.apiimpl.util.SessionHandle.getObjects(SessionHandle.java:334)
         at com.filenet.apiimpl.core.Session.callGetObjects(Session.java:121)
         at com.filenet.apiimpl.core.Session.executeGetObject(Session.java:325)
         at com.filenet.apiimpl.core.Session.getObject(Session.java:339)
         at com.filenet.apiimpl.core.IndependentObjectImpl.getObject(IndependentObjectImpl.java:154)
         at com.filenet.apiimpl.core.IndependentObjectImpl.refresh(IndependentObjectImpl.java:161)
         at com.filenet.api.core.Factory$Domain.fetchInstance(Factory.java:1543)
         at FileNetConnectionTest.testFileNetConnection(FileNetConnectionTest.java:69)
         at FileNetConnectionTest.main(FileNetConnectionTest.java:35)
    Plz help me out..Thank you

    I'm having the same problem.. I think there's something wrong with it. [fast weight loss tips|http://www.weightlossgidiet.com]

  • Log.properties

    below is the log.properties file but this is not able to generate new log file every hour.
    so please help me to point out what modification should be needed.
    # This file is to configure the logs that xellerate produces via log4j.
    # this file is used by Websphere and Weblogic. If JBoss is used
    # to host Xellerate, the file that needs to be modified is jboss-log4j.xml under
    # the JBoss directory: <jboss_home>/server/default/conf. Since
    # this file is used for the whole JBoss log configuration, a Xellerate
    # tag is used to define the level to log:
    # <category name="XELLERATE">
    # <priority value="WARN"/>
    # </category>
    # That is equivalent to the line below:
    # log4j.logger.XELLERATE=WARN
    # If specific categories need to be logged as in the case of the commented
    # categories below, a new category can be added after the "XELLERATE" category
    # in the jboss-log4j.xml file for JBoss. For instance "XELLERATE.ACCOUNTMANAGEMENT"
    # as below, would be like the following in jboss-log4j.xml:
    # <category name="XELLERATE.ACCOUNTMANAGEMENT">
    # <priority value="DEBUG"/>
    # </category>
    # In the case of Weblogic or Weblogic, uncommenting the category below would
    # be enough.
    # Any changes to the log configuration need to be follow by a restart of the
    # Application Server.
    # For more information about log4j, please refer to http://logging.apache.org/log4j/docs/
    # The below configuration sets the output of the log to be to the
    # standard output. In the case of JBoss it is to the console and
    # for Websphere and Weblogic to the log file.
    # Commentted below is "logfile" in addition to stdout. If you want
    # the output to be sent to a specific file un-comment the line below
    # and comment the one without the "logfile" entry.
    log4j.rootLogger=WARN,stdout,logfile
    #log4j.rootLogger=WARN,stdout
    # Console Appender
    # The configuration below is to configure the way the log will be formatted
    # when it is output to the console.
    log4j.appender.stdout=org.apache.log4j.ConsoleAppender
    log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
    log4j.appender.stdout.layout.ConversionPattern=%5p,%d{dd MMM yyyy HH:mm:ss,SSS},[%c],%m%n
    # File Appender
    # Uncomment if you want to output to a file and change the file name and path
    log4j.appender.logfile=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.logfile.DatePattern='.'yyyy-MM-dd-HH
    log4j.appender.logfile.File=F:/OIM/oimserver/logs/OIMLOG.log
    log4j.appender.logfile.MaxBackupIndex=20
    log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
    log4j.appender.logfile.layout.ConversionPattern=%p %t %c - %m%n
    # Below are the different categories supported by Xellerate
    # commented out. The Root Category, .XELLERATE, is not commented
    # out and it's set to WARN. This means that every category is set
    # to WARN level unless specifically changed. Each category can be
    # uncommented and the level can be changed individually while
    # the root is still on WARN (for all other categories with log level
    # not defined).
    # The following are the accepted levels:
    # DEBUG - The DEBUG Level designates fine-grained informational events
    # that are most useful to debug an application.
    # INFO - The INFO level designates informational messages that highlight
    # the progress of the application at coarse-grained level.
    # WARN - The WARN level designates potentially harmful situations.
    # ERROR - The ERROR level designates error events that might still allow
    # the application to continue running.
    # FATAL - The FATAL level designates very severe error events that will
    # presumably lead the application to abort.
    # Special Levels:
    # ALL - The ALL Level has the lowest possible rank and is intended to turn on all logging.
    # OFF - The OFF Level has the highest possible rank and is intended to turn off logging.
    # XELLERATE #
    log4j.logger.XELLERATE=WARN
    # We would like to have DDM operations at the DEBUG level
    # as we may not have a second chance to perform the same
    # operation if something fails
    log4j.logger.XELLERATE.DDM=DEBUG
    #log4j.logger.XELLERATE.ACCOUNTMANAGEMENT=DEBUG
    #log4j.logger.XELLERATE.SERVER=DEBUG
    #log4j.logger.XELLERATE.RESOURCEMANAGEMENT=DEBUG
    #log4j.logger.XELLERATE.REQUESTS=DEBUG
    #log4j.logger.XELLERATE.WORKFLOW=DEBUG
    #log4j.logger.XELLERATE.WEBAPP=DEBUG
    #log4j.logger.XELLERATE.SCHEDULER=DEBUG
    #log4j.logger.XELLERATE.SCHEDULER.Task=DEBUG
    #log4j.logger.XELLERATE.ADAPTERS=DEBUG
    #log4j.logger.XELLERATE.JAVACLIENT=DEBUG
    #log4j.logger.XELLERATE.POLICIES=DEBUG
    #log4j.logger.XELLERATE.RULES=DEBUG
    #log4j.logger.XELLERATE.DATABASE=DEBUG
    #log4j.logger.XELLERATE.APIS=DEBUG
    #log4j.logger.XELLERATE.OBJECTMANAGEMENT=DEBUG
    #log4j.logger.XELLERATE.JMS=DEBUG
    #log4j.logger.XELLERATE.REMOTEMANAGER=DEBUG
    #log4j.logger.XELLERATE.CACHEMANAGEMENT=DEBUG
    #log4j.logger.XELLERATE.ATTESTATION=DEBUG
    #log4j.logger.XELLERATE.AUDITOR=DEBUG
    #log4j.logger.XELLERATE.PERFORMANCE=DEBUG
    # SPML Webservice #
    log4j.logger.SPMLWS=WARN
    log4j.logger.SPMLWS.OIMEvent=DEBUG
    # Nexaweb #
    log4j.logger.com.nexaweb.server=WARN
    # OSCache #
    log4j.logger.com.opensymphony.oscache=ERROR

    Why are you expecting to generate a new log file every hour ? It will keep updating the same log file and archive it ...
    Thanks
    Suren

  • Exception thrown kodo.util.OptimisticVerficationException

    I am working with Kodo Jdo,
    I trying to set the properties of a user objt and set it in the session
    object to work with it in the different pages.
    I have a UI form to modify the User properties and then call the
    respective action update method.
    public ActionForward update(ActionMapping mapping, ActionForm form,
    HttpServletRequest request,
    HttpServletResponse response) throws NoUserSessionException {
    ActionMessages messages = new ActionMessages();
    PersistenceManager pm =
    Utils.getPersistenceManagerFactory().getPersistenceManager();
    User user = sessionUtils.getUser(pm, request); // get user from
    the session object
    if (validateFields(form, user, messages)) {
    Transaction tx = pm.currentTransaction();
    tx.begin();
    form2model(form, user, pm); // move the values from form
    to the user object
    refreshUserSession(request, user); // update the session
    with the user values.
    tx.commit();
    messages.add("success", new
    ActionMessage("userPreferencesForm.message.operation.successfully"));
    saveMessages(request, messages);
    model2form(pm, user, form,request);
    pm.close();
    return mapping.findForward("form");
    it work fine a couple of times , but once in the while when i try to get
    the user in the session from the other pages I get a Exception when it
    reach the excecution between the tx.begin and tx.commit of the update
    method (above).
    kodo.util.PtimisticVerificationException : There was 1 optimistic locking
    error when flushing to the data store. This indicates that an object was
    concurrently modified in another transaction. the exception in the nested
    throwables array contains a failed object representing a concurrently
    modified object.
    can someone could tell me what can I do to solve the problem...
    thanks in advance.

    Hi Marc,
    I wasnt able to enable trace-level for SQL and JDBC
    I added to jdo.properties the following:
    # kodo.Log: SQL=TRACE, JDBC=TRACE
    #kodo.Log: DefaultLevel=WARN, Runtime=INFO, Tool=INFO, SQL=TRACE
    #kodo.Log: /tmp/kodo.log , DefaultLevel=WARN, Runtime=INFO, Tool=INFO,
    #SQL=TRACE
    kodo.Log: SQL=TRACE
    also I tried using log4J by adding to jdo.properties
    kodo.Log: log4j
    and adding a log4j.properties file with the following:
    log4j.rootCategory=WARN, console
    log4j.category.kodo.jdbc.SQL=TRACE
    log4j.category.kodo.jdbc.JDBC=TRACE
    log4j.appender.console=org.apache.log4j.ConsoleAppender
    could you advice me.
    Marc Prud'hommeaux wrote:
    Emmanuel-
    An OptimisticVerficationException means that you are trying to update an
    instance in the database, but that instance has been changed in between
    the time when your instance was first obtained and the time at which you
    try to commit the changes.
    In order to track down why this is happening, you will usually do the
    following:
    1. Determine the failed object by calling
    OptimisticVerficationException.getFailedObject. Printing this object out
    in a debugging statement helps identify which instance has failed.
    2. Enable TRACE-level SQL and JDBC logging and watch for other processes
    that update that instance in the database.
    3. Examine the SQL log for the last failed statement that was executed:
    this will usually contain the lock column (e.g. "JDOVERSION") that is
    being validated.
    If you would like our assistance in determing exactly where the problem
    is, please post the log with SQL and JDBC channels set to "TRACE", as
    well as the complete stack trace from the exception.
    In article <[email protected]>, Emmanuel wrote:
    I am working with Kodo Jdo,
    I trying to set the properties of a user objt and set it in the session
    object to work with it in the different pages.
    I have a UI form to modify the User properties and then call the
    respective action update method.
    public ActionForward update(ActionMapping mapping, ActionForm form,
    HttpServletRequest request,
    HttpServletResponse response) throws NoUserSessionException {
    ActionMessages messages = new ActionMessages();
    PersistenceManager pm =
    Utils.getPersistenceManagerFactory().getPersistenceManager();
    User user = sessionUtils.getUser(pm, request); // get user from
    the session object
    if (validateFields(form, user, messages)) {
    Transaction tx = pm.currentTransaction();
    tx.begin();
    form2model(form, user, pm); // move the values from form
    to the user object
    refreshUserSession(request, user); // update the session
    with the user values.
    tx.commit();
    messages.add("success", new
    ActionMessage("userPreferencesForm.message.operation.successfully"));
    saveMessages(request, messages);
    model2form(pm, user, form,request);
    pm.close();
    return mapping.findForward("form");
    it work fine a couple of times , but once in the while when i try to get
    the user in the session from the other pages I get a Exception when it
    reach the excecution between the tx.begin and tx.commit of the update
    method (above).
    kodo.util.PtimisticVerificationException : There was 1 optimistic locking
    error when flushing to the data store. This indicates that an object was
    concurrently modified in another transaction. the exception in the nested
    throwables array contains a failed object representing a concurrently
    modified object.
    can someone could tell me what can I do to solve the problem...
    thanks in advance.
    Marc Prud'hommeaux
    SolarMetric Inc.

  • Problem in using log4j..i'm getting warning!!!

    i have been using log4j without any porblems. i have placed the log4j.properties file under classes folder under WEB-INF and it worked.
    but now i'm asked to place it under a folder named properties under CatalinaHome. And i came to know tht there is no problem in doing so and i just changed the path in my code.
    but now i'm getting the following warnings.. but logging is also going well..
    what could be the reson for this warning.
    log4j:WARN No appenders could be found for logger (com.servlet.Search
    Profile).
    log4j:WARN Please initialize the log4j system properly.

    Hi
    Have not come across a situation to limit the number of records in APD while processing, we have several DTP's extracting quite high volume of data and processing it further. (Including Cumulative & Non-cumulative key figures)
    However please be informed that the processing will fail if the query execution runs out of memory due to high volume of data.
    Based on the above screen shot it seems to be a warning message but will process the data.
    Regards
    Ashish 

  • Log4j:WARN No appenders could be found

    We are using weblogic 10.0.1 and JDK 1.6.
    We are using Log4j for logging, if I pass -Dlog4j.configuration=log4jconfig.xml in the startup script as a command line parameter weblogic console is displaying following warning messages. However, system properly initializes Log4j properly.
    Looks like beehive loggers are not initialized properly. In our log4jconfig.xml we have added appender for org.apache.
    log4j:WARN No appenders could be found for logger (org.apache.beehive.netui.pageflow.internal.AdapterManager).
    log4j:WARN Please initialize the log4j system properly.
    Please advise

    I've the same problem on weblogic 10.0.
    When the application code calls commons LogFactory for the first time, I see the following error messages.
    log4j:WARN No appenders could be found for logger (com.xxx.TestClass).
    log4j:WARN Please initialize the log4j system properly.
    Can someone explain why the same config file/setup works with Weblogic 8.1 but not with Weblogic 10.
    Thanks
    Kambiz
    Here is my folder structure
    -webroot
    +
    +-WEB-INF
    +classes
    | |--log4j.properties
    +lib
    +commons-logging.jar
    +log4j-1.2.15.jar                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Server Startup - log4j:WARN Failure in post-close rollover action

    Hi,
    Could anyone kindly help me to fix this issue??
    We are Migrating Weblogic from 11g 10.3.2 to 10.3.6
    After starting the server and checking the log, it keeps on prints "log4j:WARN Failure in post-close rollover action" in the log for several time.
    It would be very helpful if you give me a solution to solve this issue.
    Thanks
    Janes

    Hi,
    Still i didn't get any solution to resolve this issue.
    It would be very kind if someone help me.
    Thanks in advance.
    Regards,
    Janes

  • Log4j warning . i am getting this warning

    log4j: WARN No appenders could be found for category (org.apache.struts.util.PropertyMessageResources).
    log4j:WARN Please initialize the log4j system properly.
    i am getting this warning while starting the tomcat.please help me on this.

    This is not a Log4J forum check here: http://logging.apache.org/site/mailing-lists.html

  • Getting error as :  log4j : WARN No appenders could be found for logger

    Hi all,
    I am using IBM - Rational Application Developer (RAD) for the development of my project service task.
    I am trying to use log4j to log various events like errors and warnings and so on ....
    But I am getting following errors in console window of RAD :
    {color:#ff0000}
    [8/5/08 10:12:18:001 IST] 00000038 SystemErr R log4j:WARN No appenders could be found for logger (VINValidationService).
    [8/5/08 10:12:18:001 IST] 00000038 SystemErr R log4j:WARN Please initialize the log4j system properly.{color}
    If you have any clue regarding how to get out of this then it would be of great help to me .... please reply soon ....!
    (Please note that I have tried all the ways of setting CLASSPATHS and BUILDPATHS in the RAD) .
    --- Thanking you in advance ...
    Akshay_L.

    You could read these to get some hints [http://www.google.co.uk/search?q=%22Please+initialize+the+log4j+system+properly.%22]
    The first reply to the first hit on google says "log4j.properties needs to be on the classpath where log4j can find it.".
    You can set the system property if you wish but the classpath approach is the easiest in my opinion.

Maybe you are looking for