Log4j.properties or log4j.xml Not Reading

Hello,
I am trying to use log4j in jsp.
I have added log4j.properties in /WEB-INF/log4j.properties.
And in jsp page, I added like
Logger logger = Logger.getLogger("test1.jsp");When I run jsp page, I get
log4j:WARN No appenders could be found for logger (test1.jsp).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.Is this the right place to keep log4j.properties file? Does java classes can read if I put under /WEB-INF folder?
If I am using log4j.xml where to keep this file?
Regards
Edited by: Chackochen on Aug 14, 2010 1:19 AM
Edited by: Chackochen on Aug 14, 2010 1:20 AM

Here is what I figured:
add properties to the workspace/WEIB-INF/directory.xml and then read them from the PAPI code using
String myProp = DirectoryConfigurationManager.getRuntime("default").getConfigurationProperty("categoryName", "propKey");

Similar Messages

Cost involved in changing the code using log4j.properties to log4j.xml

i have finished my application, and it was done in such a way that logging is done using log4j but it was using log4j.properties file.
now i need to change it to log4j.xml. i need to do this at the earliest. so i need to know the cost involved in it?. do i need to change a lot on my app to read the log4j.xml?. In my app there is a function named getProperties, which actually reads the log4j.properties file.
this is the code of that function
public static Properties getProperties(String filename,String path) throws myException
//InputStream is = null;
FileInputStream is=null;
        Properties props = new Properties();
        //ClassLoader classLoader = ResourceUtil.class.getClassLoader();
        //is = classLoader.getResourceAsStream(filename);
        File catalinaHome = new File(System.getProperty("catalina.home"));
        try {
is=new
FileInputStream(catalinaHome.getCanonicalFile()+path + filename);
} catch (IOException e) {
        if(is == null)
            String message = "Cannot locate property file " + filename + " in the classpath";
            log.error(message);
        throw new myException(message);
        try
            props.load(is);
        catch (IOException e)
            String message = "Error reading property file " + filename;
            log.error(message);
        throw new myException(message, e);
        finally
            try
                is.close();
            catch(Throwable t)
                t.printStackTrace();
        if(props.isEmpty())
            String message = "No properties are defined in " + filename;
            log.error(message);
        throw new myException(message);
        return props;
}and my initialize function is
public static void initialize()
Properties properties=null;
try {
String path="/properties/";
properties=ResourceUtil.getProperties("log4j.properties",path);
} catch (myException e2) {
e2.printStackTrace();
PropertyConfigurator.configure(properties);
}Message was edited by:
xema
Message was edited by:
xema
Message was edited by:
xema

>
1. Restructure log4j.properties into log4j.xml.
thats done
2. Move log4j.xml into a directory that's in the
classpath.
actually i donot understand what does it mean to move in a directory thats in classpath means. i have to use logging in my webapplication running in tomcat. and my log4j.xml has to reside in catalina.home/properties/. My log4j.properties have been residing here and it had worked well woth the previous function. Now what i did is placed the log4j.xml under properties folder. Now tell me what modifications should i make in the above code.
3. Remove any code that explicitly configures log4j
(i.e. the initialize() method) because log4j will
configure itself from any properties file it finds in
the classpath, automatically, the first time it is
called.I prefer not remvoing this function as this function is being called in many of my classes... and we don't have time to edit all...
please help... and excuse me if i asked some blunders.!!!

Open Dataset for XML not reading the XML file, Returning Code 8.

Dear all,
Im trying to open an XML file using Open Dataset, since i have to execute this report in background and GUI_upload doesnt work in background.
The XML file is available in my C:\, say, C:\xmlfile.xml.
But the open dataset is not reading any value into the g_xml_line . it is returning sy-subrc = 8.
Below is my code for that, can anybody help me out to resolve.
DATA : lv_filename LIKE rlgrap-filename.
CLEAR: lv_filename.
lv_filename = p_input.
OPEN DATASET lv_filename FOR INPUT IN BINARY MODE.
IF sy-subrc ne 0.
    WRITE:/ 'invalid file'.
else.
DO.
    READ DATASET lv_filename INTO g_xml_line.
    IF sy-subrc EQ 0.
      APPEND g_xml_line TO g_xml_table.
    ELSE.
      EXIT.
    ENDIF.
ENDDO.
CLOSE DATASET lv_filename.
   ENDIF.
TYPES: BEGIN OF t_xml_line,
        data(256) TYPE x,
      END OF t_xml_line.
DATA: g_xml_table       TYPE TABLE OF t_xml_line,
      g_xml_line        TYPE t_xml_line,
      g_xml_table_size TYPE i.
GET REFERENCE OF gt_person INTO gs_result_xml-value.
gs_result_xml-name = 'IPIX'.
APPEND gs_result_xml TO gt_result_xml.
Perform the XSLT stylesheet
TRY.
      CALL TRANSFORMATION zaum_manh_sync_rpt
      SOURCE XML g_xml_table
      RESULT (gt_result_xml).
    CATCH cx_root INTO gs_rif_ex.
      gs_var_text = gs_rif_ex->get_text( ).
      MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
Kindly suggest me a solution. Points assured
regs,
raja

After saving the file , below is the code i wrote, but it gives a runtime error with message
No roll storage space of length 3788808 available for internal storage.
***Coding****
PARAMETERS: p_file TYPE pathintern LOWER CASE DEFAULT '/usr/sap/DEV/SYS/global/XMLABAP2.XML'.
DATA : lv_filename LIKE rlgrap-filename.
CLEAR: lv_filename.
lv_filename = p_file.
DATA: l_fname TYPE filename-fileintern. " File name
*GET THE FILENAME FROM THE APPLICATION SERVER
CALL FUNCTION '/SAPDMC/LSM_F4_SERVER_FILE'
    EXPORTING
      directory        = p_file
      filemask         = '*'
    IMPORTING
      serverfile       = l_fname
    EXCEPTIONS
      canceled_by_user = 1
      OTHERS           = 2.
IF sy-subrc NE 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
*/usr/sap/DEV/SYS/global/substanc
lv_filename = l_fname.
OPEN DATASET lv_filename FOR INPUT IN BINARY MODE.
IF sy-subrc NE 0.
    WRITE:/ 'invalid file'.
ELSE.
    DO.
      READ DATASET lv_filename INTO g_xml_line.
   IF sy-subrc EQ 0.
      APPEND g_xml_line TO g_xml_table.
   ELSE.
     EXIT.
   ENDIF.
    ENDDO.
    CLOSE DATASET lv_filename.
ENDIF.

Log4j.properties location for ant and kodo tools

Greetings all
Is it possible to configure the kodo ant tasks,
such as jdoc (kodo.ant.JDOEnhancerTask) to use
a log4j.properties file that is not in the
classpath?
We generally have our log4j.properties
file in a separate location away from the classpath
and for standard junit and java ant targets we can
set it's location via a jvmarg...
Version: 3.0.0
Thanks
droo.

Ok thanks for the help.
Perhaps I could suggest for a future version that the
Kodo Ant Tasks include the ability to specify a "jvmarg"
like you can for java and junit targets now, for example:
<taskdef
name="jdoc"
classname="kodo.ant.JDOEnhancerTask"
classpathref="compile.path" />
<jdoc>
<fileset refid="all.jdo.files" />
<classpath refid="other.path" />
<config propertiesFile="${kodo.properties}"/>
<jvmarg value="-Dlog4j.properties=file:///my/log4j/config" /
>
<jvmarg value="-Djava.compiler=NONE" />
<jvmarg value="-Dfred=mary" />
</jdoc>
But if not then it's ok too :) Thanks again.
droo.
Droo-
I'm not aware of an ant task to set system properties. You could
specify it on the command line. E.g.,:
ant -Dlog4j.configuration=/my/log4j/config mytarget
You could also install beanshell and use the beanshell target to set
it. E.g.:
<target name="setlog4jproperty">
<script language="beanshell"><![CDATA[
System.setProperty ("log4j.configuration", "/my/log4j/config");
]]> ]]></script>
</target>
See the ant documentation for more on the required dependencies for
beanshell.
In article <[email protected]>, droo wrote:
Yes of course, but the real question is...
How do I specify a system property for a
kodo ant task?
Sorry if this question is too stupid!
Here is what I have...
<taskdef
name="jdoc"
classname="kodo.ant.JDOEnhancerTask"
classpathref="compile-path" />
<jdoc>
<fileset refid="all-jdo-files" />
<classpath refid="post-compile-path" />
<config propertiesFile="${nf.kodo.properties}"/>
</jdoc>
In <[email protected]> Marc Prud'hommeaux wrote:
Droo-
I think you can specify the "log4j.configuration" system property.
Take a look at:
http://jakarta.apache.org/log4j/docs/manual.html
In article <[email protected]>, droo wrote:
Greetings all
Is it possible to configure the kodo ant tasks,
such as jdoc (kodo.ant.JDOEnhancerTask) to use
a log4j.properties file that is not in the
classpath?
We generally have our log4j.properties
file in a separate location away from the classpath
and for standard junit and java ant targets we can
set it's location via a jvmarg...
Version: 3.0.0
Thanks
droo.

How to load log4j.properties

how to load log4j.properties file in my java code ?
i have put log4j.properties in c:\property\log4j.properties directory.
how do i load this properties file ?

Normally you don't have to load it explicitely at
all. Just place it in your classpath and use log4j,
it should be loaded automagically.so, at run time i should use
java -classpath .;c:\property\log4j.properties;c:\log4j.jar; MyClass
is this the syntax ?

Configuring directory path for fileappender in log4j.properties

I want to write log data to a file where the directory path of the file should be picked from a unix environmental variable. How can you configure this in log4j.properties?
log4j.rootLogger=INFO, A
# A is set to be a FileAppender.
log4j.appender.A=org.apache.log4j.FileAppender
# A uses PatternLayout.
log4j.appender.A.File=$UNIX_ENV_VARIABLE/A.log <= This is what I want. The dir path should be picked from some env path
log4j.appender.A.layout=org.apache.log4j.PatternLayout
log4j.appender.A.layout.ConversionPattern=%d{HH:mm:ss,SSS} [%t] %-5p %c %x - %m%n
Or if this should be done in code, then please guide me on that.
Thanks in advance

Hi,
i am facing one problem,
where today's log and yesterday log has log statements for today with same date.. but different data. any one pls help.
this is the properties i configured
# Logger for A messages
log4j.logger.A=debug, A_R1
log4j.appender.A_R1=org.apache.log4j.DailyRollingFileAppender
log4j.appender.A_R1.File=/var/opt/wmeaidata/app_data/log4j/logs/eai_a.log
log4j.appender.A_R1.MaxFileSize = 5MB
log4j.appender.A_R1.MaxBackupIndex = 3
log4j.appender.A_R1.layout=org.apache.log4j.PatternLayout
log4j.appender.A_R1.layout.ConversionPattern=%d{MMM dd, yyyy hh:mm:ss a}|%c-%X{host}|%m%n
Thanks
venkat

Some columns not read from db on EntityManager.find

We are working with glassfish 2.1 and toplink-essentials 2.0.1-b09d-fcs. Our db vendor is Mysql.
Sometimes when we call em.find we get a not fully read object. It has a correctly set primerykey, version field but its properties seem to been not read from the database. They are nulls. Sometimes em.refresh is a good solution, sometimes even this is not enough and restart of glassfish only helps.
I appreciate any help... This is causing many problems as we are in production alreadt...
We cannot use a newer version of toplink-essentials because we get some problems with merging our objects then and have no resources to investigate the problem for a while.

Hello,
Strange problem, especially if em.refresh still won't allow you to get the data from the database - is your application using any custom options? If objects are not fully populated when they are read, it means that the cache is becoming corrupted somehow. This is common when the application does not maintain both sides of bidirectional relationships, and can also occur when an application uses stub objects for existing objects instead of reading them in. My first suggestion is to try to reproduce this in a test environment, and then isolate a particular scenario the issue occurs under - following a particular incomplete object to see how it got created and stored in the cache. Explaining the issue you have upgrading might also help determine what might be going on in the application that could cause your current issue (assuming the problems might be related, which is likely, since merge issues generally can cause cache corruptions)
In the mean time, you might try to turn off the shared cache and use an isolated cache in production to see if this helps reduce the problem.
http://weblogs.java.net/blog/guruwons/archive/2006/09/understanding_t.html describes caching in TopLink Essentials and how to turn off the shared cache in this case.
Best Regards,
Chris

File not found error with log4j.properties

Hi,
I'm writing a web service on weblogic 8.1 with weblogic workshop.I have to use log4j-1.2.7 supplied by client with my application.I cannot write ant script manually.Also I cannot change server start script or cannot put any command line argument when the server starts.
Now I require this logger in my EJB.I have kept log4j.properties in the same path where my EJB's are.But the final ear produced does not contain this log4j.properties and subsequently I get the error "log4j:ERROR Could not read configuration file [log4j.properties]."
Please help me to resolve this problem so that log4j.properties goes with the final .ear file and the ejb code finds the logger.
thanks,
pratim

Hello,
I am having a similar problem. Did you find a solution?
Thank you,
Melissa
"arunak" <[email protected]> wrote:
>
Hi Pratim,
I am also facing the same problem. can u please let me know whenever
u get the
solution for this.
Regards,
Arunak
Pratim <[email protected]> wrote:
Hi,
I'm writing a web service on weblogic 8.1 with weblogic workshop.Ihave
to use log4j-1.2.7 supplied by client with my application.I cannot write
ant script manually.Also I cannot change server start script or cannot
put any command line argument when the server starts.
Now I require this logger in my EJB.I have kept log4j.properties inthe
same path where my EJB's are.But the final ear produced does not contain
this log4j.properties and subsequently I get the error "log4j:ERROR
Could not read configuration file [log4j.properties]."
Please help me to resolve this problem so that log4j.properties goes
with the final .ear file and the ejb code finds the logger.
thanks,
pratim

Could not read Log4j configuration file when I run jar file

Hi,
I'm using Log4J in my application..
I configure the log4j, as follows;
PropertyConfigurator.configure("properties/logging.properties");and then go on to use it.
The .properties is in the root when I jar my source. I use Ant to Jar the file. It all works good when I run the jar file from ant.
The problem is when I run the jar file by double clicking on it, I get an error
" Could not read configuration file [properties/logging.properties]."
I tried the following options;
PropertyConfigurator.configure("/logging.properties");
PropertyConfigurator.configure("./logging.properties");
PropertyConfigurator.configure("../logging.properties");But in all cases, I get corresponding errors on running the jar file through Ant:
log4j:ERROR Could not read configuration file [logging.properties].
log4j:ERROR Could not read configuration file [./logging.properties].
log4j:ERROR Could not read configuration file [../logging.properties].
I want to be able to run the Jar by double clicking on it or through Ant.. Would any one know how to fix this issue so that I can use both methods..

Keep your properties file inside the root folder of your application.It is working fine

Very weird issue with server logging when using log4j.properties file

I'm using log4j logging. In log4j.properties the root logger is set up to use the ServerLoggingAppender class so that all our application logs go to the main server logfile. In addition, there are several appenders defined for specific components, with output going to specific per-component log files. Everything is going fine until I launch the server console. At this point all of those per-component log files get wiped out (zero length) and some non-ASCII lines are written to at least one of these files, after which the logs appear to be fine. The main server log file does not appear to be affected (because the root logger is set to "warn" level, while component-specific loggers are set to trace, the contents in these files is different; however I tried disabling all the other appenders and turning the root logger up to trace, and that still did not re-create the problem in the main server log file.
And here's the really weird part -- if I use the same configuration, but in a log4j.xml file, the problem does not happen.

Figured it out.
We were passing in the configuration for log4j as -Dlog4j.configuration=file:/<properties file> and this was added to the command line for both the managed and admin servers. Problem is that the console app starts its own instance of log4j, and when it reads the configuration for the appenders it initializes or rolls over the files. At some point we have two JVMs accessing the same files, so some corruption is bound to happen.
I'm not clear why the .xml file made a difference, but earlier we had been passing the log4j configuration as a jar file placed in the domain/lib folder, so perhaps the designer reverted to that (placed the log4j.xml file in a jar in lib, and not simply changed the -Dlog4j.configuration=file:/ option.

Log4j.properties with OAF R12

I am writing OAF R12 components that integrate/extend existing R12 pages.
I need to deploy a log4j.properties file for logging. I have a dependent jar file that uses log4j. This file is usually placed on the classpath in WEB-INF/classes for a servlet application.
Where should I place this log4j.properties file so that the OAF R12 container (oc4j) reads this file when processing. I tried to add it to the CLASSPATH. I edited orion_application_xml_1013.tmp and placed the log4j.properties in $JAVA_TOP and added lines for the <library path> as
<library path="$JAVA_TOP/log4j.properties" /> or
<library path="%s_javatop%/log4j.properties" />
and restarted the server.
However, the log file defined in log4j.properties is not created when running the OAF framework and exercising the integrated code that includes log4j logging.
What is the best way to integrate this properties file?
Thanks,
Ken

gday Ken --
If you are OAF R12 wouldn't there be an Oracle standard for logging you should be using? I'd be asking the OAF team for more details.
Then I'd ask whether using log4j is worth the extra effort over using the Java standard logging API -- the container itself is using Java standard logging API, for which we have the ability to dynamically adjust log levels, view the logs, etc.
Here are some links to some notes I wrote up recently on using log4j with OC4J (and also using Java standard logging API) :
http://buttso.blogspot.com/2007/09/directing-log-messages-into-oc4j.html
http://buttso.blogspot.com/2007/09/directing-log4j-logs-into-oc4j-logging.html
http://buttso.blogspot.com/2007/09/using-shared-libraries-to-configure.html
-steve-

Security hotfix APSB11-04 - CF8 and log4j.properties

Hi,
I have been reviewing the Tech Notes for the security hotfix at http://kb2.adobe.com/cps/890/cpsid_89094.html which for CF 8.01 talks about backing up and replacing the log4j.properties file. I can't locate this on any of our CF 8.01 servers, so wondering if this is a mistake in the tech note and should have only applied to CF 9. Can I skip the step all together or do I still need to copy the file from the downloaded hotfix to the suggested location?
Thanks
Meint

Hi Meint,
My CF8.0.1 does not have log4j.properties file either tho CF9.0.1 has.
HTH, Carl.

Problem with log4j.properties and level DEBUG

Hi,
I need some log4j help.
I create 2 different appenders in the log4j.properties file
and it works.
This is my complete log4j.properties:
log4j.logger.log1=DEBUG, log1
log4j.logger.log2=DEBUG, log2
log4j.appender.log1=org.apache.log4j.DailyRollingFileAppender
log4j.appender.log1.File=${StandardLogPath}
log4j.appender.log1.DatePattern='.'yyyy-MM-dd
log4j.appender.log1.Append=true
#log4j.appender.log1.Threshold=DEBUG
log4j.appender.log1.layout=org.apache.log4j.PatternLayout
log4j.appender.log1.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} [%-5p] %-25c{1} %m%n
log4j.appender.log2=org.apache.log4j.DailyRollingFileAppender
log4j.appender.log2.File=${StandardLogQueryPath}
log4j.appender.log2.DatePattern='.'yyyy-MM-dd
log4j.appender.log2.Append=true
log4j.appender.log2.layout=org.apache.log4j.PatternLayout
log4j.appender.log2.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} [%-5p] %-25c{1} %m%nAnd here's my logging code:
import org.apache.log4j.Logger;
Logger log = Logger.getLogger("log1");
Logger logQuery = Logger.getLogger("log2");
log.debug("loggerDebug");
logQuery.debug("loggerDebug");
log.info("loggerInfo");
logQuery.info("loggerInfo");The problem is that "loggerDebug" is not written to all appenders (only "loggerInfo").
In fact if I print:
System.out.println( log.getEffectiveLevel().toString() );result that the level is INFO and I known that if level is INFO then DEBUG is disable.
But why the level is INFO????
Someone can suggest me a solution?
Thank you very much

You're so over-sensitive you: when an OP doesn't respond anymore
to your last reply it implies that you've solved the problem and
(implicitly) that the OP is very grateful to you. Why do you always
have to be so explicit about matters? ;-)
Because I'm not one of those Dutch people ;-)Yes, that's us, the Dutch: mysteriously smiling and keeping silent all the
time. That's why they call us the Asians of Western Europe ;-)
ps. There are nice exception to the rule sometimes though.
Yes, and unfortunately they do seem to be the exception rather than
the rule. It would be nice to catch one a bit more often.True; that's the internet generation: grab all the information that you can
and don't give a f*ck about the guy who supplied the information. It's sad
indeed.
Maybe we should start a support group where we could thank each
other now and then 'on behalf' of those little spoiled brats and complain
about all those bad manners nowadays ;-)
kind regards,
Jos

Log4j works in local tomcat, not in the remote one.

hi,
actually i have this in log4j.properties:
log4j.appender.R.File=${catalina.home}/log/logging.logand it works in local tomcat but it doesn't on remote one.
I have to get it to work on a remote server. I doesn't know where catalina.home is set on the remote server and i don't have a shell to check it out.
I can only see the WEB-INF dir under public_html directory.
I tried already:
log4j.appender.R.File=/public_html/logging.logbut no luck. No files created.
Is there a way to point to WEB-INF dir, that is the only dir of tomcat i can see in the remote ftp?
Something like ${WEB-INF} ?
Thanks in advance.

we ran into a similar problem at work yesterday with no logging appearing when adding a log4j config file to an application but logging appearing in the server config when it wasn't there.
Answer: the app server (JBoss in this case) uses log4j itself and the 2 config files were in conflict so nothing was logged at all.
Removing the application specific config cured the problem.
You probably have something similar going on, with the remote server having its own log4j logging already in place and conflicting with yours.
You might have to switch to another logging system or get in contact with the server admins and have them set things up so the server generates your logs where you can access them.

JMS Appender in log4j.properties ??

Hie Experts,
I have setup a logging mechanism to log messages asynchronously using JMS queue.
Currently, I am doing this as a call to a method.
Inside the method, I am
- creating a JNDI context,
- retrieve queue connection factory,
- create a queue session, create a queue sender and
- associate to the retrieved queue.
- Finally I send the message and close the queue.
I do not think that this is the best strategy because:
1. Queue gets initialized for all logging (making it slower)
2. I believe that there must be a simpler way such as adding a JMS appender in log4j.properties
Please advise if there is a better strategy.
Thanks,
V Chitkara

Hi Vishal,
You are correct in your assumption that there is a simpler way to perform logging using JMS.
The Log4J project already contains a JMS appender. Take a look at this page:
http://logging.apache.org/log4j/docs/manual.html
And search it for "JMS".
Hope this helps,
Tom Jenkinson
Arjuna Technologies Limited

Log4j.properties or log4j.xml Not Reading

Similar Messages

Maybe you are looking for