Logging with log4j

I'm having a problem doing logging. The problem lies in my log4j.properties file. I want to the log to be in the WEB-INF directory. Here's a log file that works
log4j.rootLogger=info, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=${catalina.home}/logs/clprservicing.log
log4j.appender.R.MaxFileSize=10MB
log4j.appender.R.MaxBackupIndex=10
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
log4j.logger.org.apache.catalina=INFO, RThis properties file is in WEB-INF/classes where it should be. When I change the location of the log to WEB-INF in the following log file
log4j.rootLogger=info, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.logfile.File=${clpr-servicing.root}/WEB-INF/clprservicing.log
log4j.appender.R.MaxFileSize=10MB
log4j.appender.R.MaxBackupIndex=10
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
log4j.logger.org.apache.catalina=INFO, Rit doesn't work! The webapplication is called clpr-servicing. Is there something wrong with the key ${clpr-servicing.root}? Does it have to be defined somewhere?

Never mind. I found the solution.

Similar Messages

Want to Generate custom logs with Log4J within Java Embedding activity

Hi Gurus,
i want to Generate custom logs with Log4J within Java Embedding activity. For that i have performed some steps, but the log file has not been created.
ServerSide Configuration:
*===============*
1. I have copied the log4j-1.2.15.jar file to the "oracle.soa.ext_11.1.1" location and recreate the oracle.soa.ext.jar file using an-script, which appends the log4j.jar file to the classpath.( That was created successfully)
2. Specify a File location in log4j.xml for creating the log file. (e.g. (<middleware_home>/config/customLog.log)
3. Then create a folder and add log4j.xml and log4j.dtd file under the folder.
4. Modify the startManagedWeblogicServer by adding JAVA_OPTIONS="-Dlog4j.configuration=<middleware_home>/config/log4j.debug.xml”
5. Then restart the SOA server.
log4j.xml :
I have used fileAppender.
DevelopmentSide Configuration:
*===================*
1. Create synchronous BPEL process and Add "JAVA Embedding Activity" inbetween receiveInput and replyOutput activity.
2.Import the log4j-1.2.15.jar to the project libs
3.In the BPEL source code, import the Logger class.
4.Insert the code in the JAVA Embedding Activity
Logger logger = Logger.getLogger("CustomLog");
logger.info("CustomeLog " + getTitle());
Compile and deploy the project into the SOA_server and test it. Test status is completed but log is not created in the mentioned location.
Ref: http://blog.andrade.inf.br/search/label/Log4j
Is there any other way to achieve this requirement. Please suggest.
Thanks in Advance,
Sharmistha

You can try this.
http://veejai24.blogspot.co.uk/2008/04/simple-way-to-implement-log4j-in-your.html
Thanks,
Vijay

Application specific logging with Log4j on weblogic 8.1

Hi,
For a few days now, I have been trying to implement application specific logging using Log4j (1.2.x) for my 3 applications running on the same server (8.1.6). All three application war files are generated from same source. I followed the example of Jboss in setting up the Hierarchy for logging using RepositorySelector. In my case Java class which implements RepositorySelector is loaded through ServletContextListener from jar file placed in WEB_INF/lib folder and log4j.properties file is in WEB-INF folder of each application.
Independent logging of each application takes place correctly, if the applications are deployed from console. However logging fails if weblogic is shutdown and restarted, in this case logging takes place from 2 classes only implementing filters of each application. Logging from other classes is not taking place. I am spinning my wheels on this and can't seem to figure out what the issue is.
Thanks for any help...below is the snippet of code
Sohan
public static synchronized void init(ServletContext config, String strLogProperties, String webAppName)
throws ServletException {
if( !initialized ) // set the global RepositorySelector
defaultRepository = LogManager.getLoggerRepository();
RepositorySelector theSelector = new MyRepositorySelector();
LogManager.setRepositorySelector(theSelector, guard);
initialized = true;
Hierarchy hierarchy = new Hierarchy(new RootCategory(Level.DEBUG));
loadLog4JConfig(config, hierarchy, strLogProperties, webAppName);
ClassLoader loader = Thread.currentThread().getContextClassLoader();
repositories.put(loader, hierarchy);
config.setAttribute("hierarchy", hierarchy );
public LoggerRepository getLoggerRepository() {
ClassLoader loader = Thread.currentThread().getContextClassLoader();
LoggerRepository repository = (LoggerRepository)repositories.get(loader);
if (repository == null) {
return defaultRepository;
} else {
return repository;
public void LogInit(ServletContext ctx) throws ServletException {
System.out.println("\n\n---------------Log4jInit---------------\n\n");
String strLogProperties = ctx.getInitParameter("Log4JProperties");
System.out.println("Log4j properties " + strLogProperties);
String webAppName = ctx.getInitParameter("LogFileName");
System.out.println("App log File name " + webAppName);
if (webAppName == null ) {
webAppName = getWebAppName(ctx);
System.out.println("Application name = " + webAppName);
MyRepositorySelector.init(ctx, strLogProperties, webAppName);
LOG = Logger.getLogger(this.getClass());
LOG.info("Log message from Log4jInit ServletContextListener");
System.out.println("\n\n---------------Log4jInit: Complete---------------\n\n");
}

Has anyone been able to get around the "Export of object xxx barred" error when
trying to access the object?
Thanks,
Kevin
"Koua" <[email protected]> wrote:
>
I have the same problem when adding listener for COM events. I think
it's a bug
in Weblogic. It seems that no one can help.
Teresa Canales <[email protected]> wrote:
Hi,
I am getting the following error. I am not sure how to fix this. I
looked in everywhere on the admin console and couldn't find anything.
The following is what I am getting....
BEA-210000 Apr 14, 2004 11:05:42 AM EDT servicelayertrain
Error COM Export of object: com.symphonyhealth.user.facade.ejb.User_eecm3e_HomeImpl@2ba3e4
barred
Any help would be greatly appreciated.
Teresa

Logging with log4j in a Web app that uses TopLink

The deployment engineer in my company is reporting problems with our first Web app that uses both log4j and TopLink. Apparently TopLink is failing to initialize correctly when log4j-1.2.8.jar is deployed to the WEB-INF/classes directory within the Web app.
I know that 9iAS's Enterprise Manager uses an older version of log4j and I wonder if TopLink uses an older version too.
Are there any known problems when using log4j 1.2.8 with TopLink 9.0.3?
Thanks,
Al Margheim

Unfortunately, when I asked the deployment engineer for more information on the problem, he couldn't provide any, and since he moved the log4j library out of the application's WEB-INF\classes directory he can't reproduce the problem (whatever it was).
Based on a variety of factors (including your response) I suspect that the people who encountered the problem misinterpreted the cause.
If I can get him to put the log4j library back in WEB-INF\classes and get more specific information about the problem, and it still looks like a conflict between TopLink and log4j, I'll post the errors here.
Thanks,
Al Margheim

Separate logging with log4j for web applications deployed on one server

I have been trying to get web applications to write to separate log files.
Log4j.jar is loaded through classpath once during weblogic startup. In each web application, I have Log4j.xml or Log4j.properties configuration files under WEB-INF folder. I hava java class in the application extending HttpServlet and loads the log4j.xml file, In web.xml they have load-on-startup set to 1. Two java class files both extending write the log to the specified log file but other java class files are not logging information, some implement filter, some are action classes (Struts 1.2.9). If the java class has a static method then the log from the method is being written but the log from instance methods is not being written. I tried declaring the variable both as static and non-static
private Logger log = Logger.getLogger(LoginFilter.class);
What could be causing some java class files not to log?
Another issue, For Log4j.xml, Doctype as SYSTEM property set to lookup Log4j.dtd, weblogic complains as Log4j.dtd file not found, tried adding this file in WEB-INF folder, same location as LOg4j.xml and WEB-INF/lib folder and even in classpath, weblogic still complains of log4j.dtd file being not found. For now, I removed SYSTEM entry but need to put it back for parser to validate xml file.
I am using WLS 8.1.6, struts 1.2.9 and Log4j 1.2.8 versions.
Any help is appreciated.
thanks,
SK

How we can implement thisBy implementing an SSO product of your choice.

Logging with WSS4j

Hello ,
I'm using Tomcat6 + Axis 1+wss4j.
I have to modify something in wss4j's source code but I can't test its results...but I couldn't enable logging with log4j..
How should I do that???
I could be able to do log with log4j for axis..using the following properties file , placed in folder \Tomcat\webapps\axis\WEB-INF\classes.
log4j.properties :
# Set root logger level to WARN and its only appender to A1.
log4j.rootLogger=WARN, A1
# show DEBUG for SOAPPart method
log4j.logger.org.apache.axis.SOAPPart=DEBUG
# A1 is set to be a ConsoleAppender.
# log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1=org.apache.log4j.FileAppender
log4j.appender.A1.File=axis.log
# A1 uses PatternLayout.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
How do I enable logging with wss4j?
I tried putting the properties file included with wss4j's source but with no luck..
Thanks in Advance

If you are deploying via the WebLogic admin console, here's the reference to configure logging level:
Administration Console Online Help - [View and configure logs|http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/logging/ConfigureAndViewLogs.html]
If deploying from command line, try including the -debug flag?
(weblogic.Deployer Command-Line Reference - [Common Arguments|http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/wldeployer.html#wp1010461])

Getting empty log files with log4j and WebLogic 10.0

Hi!
I get empty log files with log4j 1.2.13 and WebLogic 10.0. If I don't run the application in the application server, then the logging works fine.
The properties file is located in a jar in the LIB folder of the deployed project. If I change the name of the log file name in the properties file, it just creates a new empty file.
What could be wrong?
Thanks!

I assume that when you change the name of the expected log file in the properties file, the new empty file is that name, correct?
That means you're at least getting that properties file loaded by log4j, which is a good sign.
As the file ends up empty, it appears that no logger statements are being executed at a debug level high enough for the current debug level. Can you throw in a logger.error() call at a point you're certain is executed?

Need help with log4j logging tool (org.apache.log4j.*) to log into database

Hi,
I need help with log4j logging tool (org.apache.log4j.*) to log into database using JDBCAppender. Have look at my logger code and corresponding log4j.properties file stated below. I'm running this program using Eclipse IDE and it's giving me the following error (highlighted in red) at the end:
log4j: Parsing for [root] with value=[debug, stdout, Roll, CRSDBAPPENDER].
log4j: Level token is [debug].
log4j: Category root set to DEBUG
log4j: Parsing appender named "stdout".
log4j: Parsing layout options for "stdout".
log4j: Setting property [conversionPattern] to [%x %d{HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n].
log4j: End of parsing for "stdout".
log4j: Parsed "stdout" options.
log4j: Parsing appender named "Roll".
log4j: Parsing layout options for "Roll".
log4j: Setting property [conversionPattern] to [%x %d{yyyy.MM.dd HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n].
log4j: End of parsing for "Roll".
log4j: Setting property [file] to [HelloWorld.log].
log4j: Setting property [maxBackupIndex] to [10].
log4j: Setting property [maxFileSize] to [20KB].
log4j: setFile called: HelloWorld.log, true
log4j: setFile ended
log4j: Parsed "Roll" options.
log4j: Parsing appender named "CRSDBAPPENDER".
{color:#ff0000}
Can't find class HelloWorld{color}
import org.apache.log4j.*;
public class HelloWorld {
static Logger log = Logger.getLogger(HelloWorld.class.getName());
public static void main(String[] args) {
try{
// Now, try a few logging methods
MDC.put("myComputerName", "Ravinder");
MDC.put("crsServerName", "ARNDEV01");
log.debug("Start of main()");
log.info("Just testing a log message with priority set to INFO");
log.warn("Just testing a log message with priority set to WARN");
log.error("Just testing a log message with priority set to ERROR");
log.fatal("Just testing a log message with priority set to FATAL");
catch(Exception e){
e.printStackTrace();
------------------------- log4j.properties file ------------------------------
#### Use three appenders - log to console, file and database
log4j.rootCategory=debug, stdout, Roll, CRSDBAPPENDER
log4j.debug=true
# Print only messages of priority WARN or higher for your category
# log4j.category.your.category.name=WARN
# Specifically inherit the priority level
# log4j.category.your.category.name=INHERITED
#### stdout - First appender writes to console
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%x %d{HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n
#### Roll - Second appender writes to a file
log4j.appender.Roll=org.apache.log4j.RollingFileAppender
##log4j.appender.Roll.File=${InstanceName}.log
log4j.appender.Roll.File=HelloWorld.log
log4j.appender.Roll.MaxFileSize=20KB
log4j.appender.Roll.MaxBackupIndex=10
log4j.appender.Roll.layout=org.apache.log4j.PatternLayout
log4j.appender.Roll.layout.ConversionPattern=%x %d{yyyy.MM.dd HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n
#### CRSDBAPPENDER - third appender writes to the database
log4j.appender.CRSDBAPPENDER=org.apache.log4j.jdbc.JDBCAppender
log4j.appender.CRSDBAPPENDER.Driver=net.sourceforge.jtds.jdbc.Driver
log4j.appender.CRSDBAPPENDER.URL=jdbc:jtds:sqlserver:/arncorp15:1433;DatabaseName=LOG
log4j.appender.CRSDBAPPENDER.USER=sa
log4j.appender.CRSDBAPPENDER.PASSWORD=p8ss3doff
log4j.appender.CRSDBAPPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.CRSDBAPPENDER.sql=INSERT INTO LOG (computername, crsservername, logtime, loglevel, threadname, filename, linenumber, logtext) VALUES ('%X{myComputerName}', '%X{crsServerName}', '%d{dd MMM yyyy HH:mm:ss,SSS}', '%p', '%t', '%F', '%L', '%m')
#log4j.appender.CRSDBAPPENDER.sql=INSERT INTO LOG(COMPUTERNAME,CRSSERVERNAME,LOGTIME,LOGLEVEL,THREADNAME,FILENAME,LINENUMBER,LOGTEXT) select host_name(),'${CRSServerName}${InstanceName}','%d','%5p','%t','%F','%L','%m%n'
#log4j.appender.CRSDBAPPENDER.sql=INSERT INTO LOG (computername, crsservername, logtime, loglevel, threadname, filename, linenumber, logtext) VALUES ("%X{myComputerName}", "%X{crsServerName}", "%d{dd MMM yyyy HH:mm:ss,SSS}", "%p", "%t", "%F", "%L", "%m")
------------------------------- end of log4j.properties file ------------------------------
Here is the directory structure of my program. My log4j.properties file and HelloWorld.class file are residing in folder HelloWorld\bin.
HelloWorld\bin
HelloWorld\lib
HelloWorld\src
Please note - The same program works fine for console and file appender when I comment the database appender part in my properties file.
Thanks
Ravinder

try this :
log4j.appender.PROJECT.Append=false

Getting error with Log4j

Hi,
Not sure if this is the right place to post this as it is a problem with log4j really and not java. Let me know if this needs moving.
Here goes:
I have a servlet in tomcat that uses log4j to log details, this works fine on all the systems at home and work, but I get the following error when it is run on our customers site:
log4j: No appenders could be found for category (some.category.name).
log4j: Please initialize the log4j system properly.
I have looked this up on log4j's website, they give the following advice:
Log4j does not have a default logging target. It is the user's responsibility to ensure that all categories can inherit an appender. This can be easily achieved by attaching an appender to the root category.
This works fine off site? I have the following log4j.properties in the WEB-INF/classes dir in tomcat:
log4j.rootCategory=DEBUG, dest1
log4j.appender.dest1=org.apache.log4j.FileAppender
log4j.appender.dest1.file=/rmx.log
log4j.appender.dest1.layout=org.apache.log4j.PatternLayout
log4j.appender.dest1.layout.ConversionPattern=%-5p %l %x: %m%nAny ideas?
Thanks in advance.
Phil Maskell

I have added code similar to what you suggested,
being deployed on Tomcat I get the following:
java.class.path=C:\Program Files\Apache Group\Tomcat
5.5\bin\bootstrap.jar
Is this what I should get? This is on my working
system.That was probably not a good test (in hindsight). Tomcat's classpath is evidently not where its servlet classloader looks for classes.
My log4j code uses a logFactory, in a final class,
will this have any effect on the class path?The fact that the class is final will have no effect on any classloading. I doubt whether a logfactory will either, but I don't know what that is.
P.S I could post my Logger.java, but stupid thing is
it works fine on all my systems, just not on the
customers :(I put my log4j.properties in the web app's WEB-INF/classes directory, just like you did. If your customer's system is not working the same as yours then you are probably wasting your time looking at Java code. The two systems are not configured the same and you need to find the difference.

Logging with whereabouts using open source and freeware

You can find the html version of this at:
http://www.acelet.com/whitepaper/loggingWithWhereabouts.html
Logging with whereabouts using open source and freeware
The purpose of logging is to find out what had happened when needed. When the
time comes to read log messages, you want to know both the log message and its
whereabouts (class name, method name, file name and line number). So you need
to hard code whereabouts.
But hard coded whereabouts are very difficult to maintain: when you modify your
source code, line number changes; when you copy and paste a line, its class name
and method name change. If whereabouts are wrong, you introduce bugs in your logging
logic and the log messages are useless at the best.
This article shows you an example of using freeware Redress tool to rectify whereabouts
programmatically in your Makefile or Ant build file. So your whereabouts are always
correct for both Java and JSP source file.
Redress tool is part of SuperLogging at http://www.ACElet.com. SuperLogging also
provides an open source wrapper Alog.java, which redirects log method calls to
your favorite logging package. Redress tool can rectify whereabouts information
on all Alog's method calls in your application. So, if you call Alog's log methods,
these calls will be rectified by Redress.
JDK 1.4 introduces a new utility package java.util.logging. The example in this
article is based on JDK logging. Log4J is a cousin of JDK logging. Log4J users
should have no difficulties to modify this example for Log4J. Both JDK logging
and Log4J are excellent logging software for single JVM.
Note: Redress tool rectifies method calls on Alog, not JDK logging. You need to
call Alog instead of JDK logging in your application.
Source code of Alog.java
The following is the source code of Alog's JDK logging version. It serves as an
library file and should be on your CLASSPATH:
* Copyright Acelet Corp. 2000. All rights reserved
* License agreement begins >>>>>>>>>> 
* This program (com.acelet.opensource.logging.Alog) ("Software") is an
* open source software. 
* LICENSE GRANT. The Software is owned by Acelet Corporation ("Acelet").
* The Software is licensed to you ("Licensee"). You are granted a
* non-exclusive right to use, modify, distribute the Software for either
* commercial or non-commercial use for free, as long as: 
* 1. this copyright paragraph remains with this file. 
* 2. this source code (this file) must be included with distributed
* binary code. 
* NO WARRANTY. This comes with absolutely no warranty. 
* <<<<<<<<<< License agreement ends 
* The purpose of releasing this open source program is to prevent vendor
* lock in. 
* You can code your program using this class to indirectly use Acelet
* SuperLogging (com.acelet.logging). If later you want to swith to other
* logging package, you do not need to modify your program. All you have
* to do is: 
* 1. modify this file to redirect to other logging packages. 
* 2. replace existing com.acelet.opensource.Alog with your modified one. 
* 3. you may have to reboot your EJB server to make the changes effect. 
* 
* This program is just a wrapper. For detail information about the methods
* see documents of underline package, such as com.acelet.logging.Logging.
* 
* Visit http://www.ACElet.com for more information.
* 
* This file is a modified for using JDK logging as an EXAMPLE.
* 
* You can use Redress tool to keep your whereabouts information
* always correct. See http://www.ACElet.com/freeware for detail.
* 
* Please see http://www/ACElet.com/opensource if you want to see the
* original version.
package com.acelet.opensource.logging;
import java.util.logging.*;
public final class Alog {
* Log level value: something will prevent normal program execution.
public static int SEVERE = 1000;
* Log level value: something has potential problems.
public static int WARNING = 900;
* Log level value: for significant messages.
public static int INFO = 800;
* Log level value: for config information in debugging.
public static int CONFIG = 700;
* Log level value: for information such as recoverable failures.
public static int FINE = 500;
* Log level value: for information about entering or returning a
* method, or throwing an exception.
public static int FINER = 400;
* Log level value: for detail tracing information.
public static int FINEST = 300;
static Logger logger;
static {
logger = Logger.getLogger("");
public Alog() {
public static void alert(String subject, String message) {
public static void error(String text, int level, String fullClassName,
String methodName, String baseFileName, int lineNumber) {
String[] para = {lineNumber + "", baseFileName};
logger.logp(getLevel(level), fullClassName, methodName, text, para);
public static Level getLevel(int levelValue) {
if (levelValue == SEVERE)
return Level.SEVERE;
else if (levelValue == WARNING)
return Level.WARNING;
else if (levelValue == INFO)
return Level.INFO;
else if (levelValue == CONFIG)
return Level.CONFIG;
else if (levelValue == FINE)
return Level.FINE;
else if (levelValue == FINER)
return Level.FINER;
else if (levelValue == FINEST)
return Level.FINEST;
else
return Level.ALL;
public static void log(String text, int level, String fullClassName,
String methodName, String baseFileName, int lineNumber) {
String[] para = {lineNumber + "", baseFileName};
logger.logp(getLevel(level), fullClassName, methodName, text, para);
public static void sendMail(String to, String from, String subject,
String text) throws Exception {
public static void sendMail(String to, String cc, String bcc, String from,
String subject, String text) throws Exception {
Test program
The simple test program is Test.java:
import com.acelet.opensource.logging.Alog;
public class Test {
public static void main(String argv[]){
Alog.log("Holle world", Alog.SEVERE, "wrongClassName", "wrongMethod",
"wrongFileName", -1);
How to run the test program
1. Compile Alog.java (JDK 1.4 or later, not before):
javac Alog.java
2. Download freeware Redress tool from http://ACElet.com/freeware.
3. Run Redress tool:
java -cp redress.jar Test.java
4. Check Test.java. The Alog.log method call should be rectified.
5. Run test program:
java Test
You should see log message with correct class name and method name.

Hi;
I found this code and would like to share it with you :
JCoDestination destination = JCoDestinationManager
.getDestination(DESTINATION_NAME2);
JCoFunction function = destination.getRepository().getFunction(
"RFC_FUNCTION_SEARCH");
if (function == null)
throw new RuntimeException("RFC_FUNCTION_SEARCH not found in SAP.");
function.getImportParameterList().setValue("FUNCNAME", "*");
function.getImportParameterList().setValue("GROUPNAME", "*");
try {
function.execute(destination);
JCoTable funcDetailsTable = function.getTableParameterList()
.getTable("FUNCTIONS");
int totalNoFunc = funcDetailsTable.getNumRows();
if (totalNoFunc > 0) {
for (int i = 0; i < totalNoFunc; i++) {
System.out.println("Function Name: "
+ funcDetailsTable.getValue(i));
} catch (AbapException e) {
System.out.println(e.toString());
return;
System.out.println("RFC_FUNCTION_SEARCH finished");
It is working and retrieving FM.
Regards
Anis

Utilize Apache Commons Logging and Log4J

Hello Forum,
I have some questions regarding the usage of Apache Commons Logging in combination
with Log4J. As wer're doing cross platform development for JBoss and NetWeaver I
can't rely on SAP Logging facilities.
The information I used to set up the logging are written down in the Article:
"Integrating 3rd Party Logging Frameworks into SAP NetWeaver".
I created the package "util" within my testing project and placed the .java classes
"SapLogAppender.java" and "SapLogJclImpl.java" into it.
After that I created a log4j.xml configuration file with the following content:
[code]
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
<appender name="STDOUT" class="org.apache.log4j.ConsoleAppender">
 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="%-5p %C (Line %L) - %m%n"/>
 </layout>
</appender>
<appender name="FILE_LOG" class="org.apache.log4j.FileAppender">
 <param name="File" value="${user.dir}/log/myTestLogFile.log"/>
 <param name="append" value="false"/>
 <param name="ImmediateFlush" value="true"/>
 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="%d %-5p %C (Line %L) - %m%n"/>
 </layout>
</appender>
<appender name="SAP_LOG" class="de.collogia.util.SapLogAppender">
 <param name="categoryName" value="sapmon"/>
</appender>
<category name="de.collogia" additivity="false">
 <priority value="debug" />
 <appender-ref ref="FILE_LOG"/>
 <appender-ref ref="SAP_LOG"/>
</category>
<root>
 <priority value="error" />
 <appender-ref ref="STDOUT"/>
</root>
</log4j:configuration>
[/code]
After that I created the file "commons-logging.properties" with the following content:
[code]
org.apache.commons.logging.Log=de.collogia.util.SapLogJclImpl
[/code]
I put the configuration files in the root of the classes folder, created the .jar in the
EJB-Project, created the .ear in the EAR-Project and deployed the application.
The application contains just a simple session bean with a remotable method that
shall do some logging using the following statements:
[code]
LOG.trace("Testing log trace level");
LOG.debug("Testing log debug level");
LOG.info("Testing log info level");
[/code]
The only logging output I'm able to find is located in file:
C:\NWAS_JAVAEE5\JP1\JC00\j2ee\cluster\server0\log\applications.0.log
and it logs the info level logging message.
If I understood the afore mentioned paper right the debug and trace level logging
mesages shall go to file:
C:\NWAS_JAVAEE5\JP1\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc
Unfortunately there isn't logged anything. I looked through the log facility
in SAPMMC but there isn't anything to.
The most inconvenient behaviour of the NetWeaver is that since the my stateless
session beans class contains the logging code I'm only able to deploy once.
A second deplyoment fails with a large Exception I will append below. The problem
is definitely related to logging - after removing the line:
[code]
 /** The <code>Log</code> object for this class. */
 private static final Log LOG = LogFactory.getLog(TravelAgentBean.class);
[/code]
from the stateless session bean I'm able to deploy as often I like to.
The line re-enabled, deployed the ear, invoking the remotable method once and every
subsequent deplyoment fails with:
[code]
[EXCEPTION]
#1#com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: java.io.IOException: Cannot delete file: C:
NWAS_JAVAEE5
JP1
JC00
j2ee
cluster
apps
sap.com
test2Ear
orpersistence
jars
test2Ejb.jar
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:188)
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:184)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:149)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:151)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
#1.5 #0007E97510B5000E00000039000001A8005B19B7C7A8358A#1174557303064#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#/System/Server/Services/Deploy#Plain#Exception in operation startInitiallyApp with application sap.com/test2Ear.###
#1.5 #0007E97510B5000E0000003A000001A8005B19B7C7A8358A#1174557303064#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error##Java###Exception in operation startInitiallyApp with application sap.com/test2Ear.
Reason : Exception in operation startInitiallyApp with application sap.com/test2Ear.
[EXCEPTION]
#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startInitiallyApp with application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:485)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:382)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while downloading files of application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:642)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 ... 31 more
Caused by: com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: java.io.IOException: Cannot delete file: C:
NWAS_JAVAEE5
JP1
JC00
j2ee
cluster
apps
sap.com
test2Ear
orpersistence
jars
test2Ejb.jar
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:188)
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:184)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:149)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:151)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 ... 35 more
#1.5 #0007E97510B5000E0000003C000001A8005B19B7C7A8358A#1174557303079#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#/System/Server/Services/Deploy#Plain#Exception in operation startApp with application sap.com/test2Ear.###
#1.5 #0007E97510B5000E0000003D000001A8005B19B7C7A8358A#1174557303079#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error##Java###Exception in operation startApp with application sap.com/test2Ear.
Reason : Exception in operation startApp with application sap.com/test2Ear.
[EXCEPTION]
#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:485)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:382)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while downloading files of application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:642)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 ... 27 more
Caused by: com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: java.io.IOException: Cannot delete file: C:
NWAS_JAVAEE5
JP1
JC00
j2ee
cluster
apps
sap.com
test2Ear
orpersistence
jars
test2Ejb.jar
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:188)
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:184)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:149)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:151)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 ... 35 more
#1.5 #0007E97510B5000E0000003F000001A8005B19B7C7A8358A#1174557303095#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#/System/Server/Services/Deploy#Plain#Exception while downloading files of application sap.com/test2Ear.###
#1.5 #0007E97510B5000E00000040000001A8005B19B7C7A8358A#1174557303095#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error##Java###Exception while downloading files of application sap.com/test2Ear.
Reason : Exception while downloading files of application sap.com/test2Ear.
[EXCEPTION]
#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while downloading files of application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:642)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: java.io.IOException: Cannot delete file: C:
NWAS_JAVAEE5
JP1
JC00
j2ee
cluster
apps
sap.com
test2Ear
orpersistence
jars
test2Ejb.jar
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:188)
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:184)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:149)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:151)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 ... 35 more
#1.5 #0007E97510B5000E00000041000001A8005B19B7C7A8358A#1174557303095#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error##Plain###
Operation startApp over application sap.com/test2Ear finished with errors on server 2564250. For more detailed information see traces of Deploy Service.#
#1.5 #0007E97510B5000E00000042000001A8005B19B7C7A8358A#1174557303095#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error##Plain###
Error occurred on server 2564250 during startApp sap.com/test2Ear : com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while downloading files of application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:642)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: java.io.IOException: Cannot delete file: C:
NWAS_JAVAEE5
JP1
JC00
j2ee
cluster
apps
sap.com
test2Ear
orpersistence
jars
test2Ejb.jar
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:188)
 at com.sap.engine.services.orpersistence.model.builders.FileUtils.deleteDirectory(FileUtils.java:184)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:149)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
 at com.sap.engine.services.orpersistence.container.util.FileUtils.deleteDirectory(FileUtils.java:151)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ConfigurationsExtractor.execute(ConfigurationsExtractor.java:59)
 at com.sap.engine.services.orpersistence.container.deploy.ContainerAdapter.downloadApplicationFiles(ContainerAdapter.java:248)
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:627)
 ... 35 more
#1.5 #0007E97510B5000E00000044000001A8005B19B7C7A8358A#1174557303111#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#8#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#/System/Server/Services/Deploy#Plain#Clusterwide exception: server ID 2564250:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while downloading files of application sap.com/test2Ear.
 at com.sap.engine.services.deploy.server.editor.impl.second.DIReaderImpl2.bootstrapApp(DIReaderImpl2.java:642)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.bootstrapApplication(ApplicationTransaction.java:763)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.bootstrapApplication(StartInitiallyTransaction.java:228)
 at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:132)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:430)
 at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:418)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:192)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:639)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:630)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
 at com.sap.engine.services.cross.fca.MessageReader.run(M

Guten Tag Henning
> adjusting the logging severity like outlined in this
> thread
> <a href="/thread/2 [original link is broken]
> 34301">Thread</a> helped.
> I'm able to see more logging messages within the log
> files now.
Good to hear
> But am I right with my assumption that though I'm
> using my LOG object it's
> not really using the logging frameworks? Every
> logging out put contains the word
> "plain" as pefix:
>
>
> stateless.TravelAgentBean#Plain###Testing info level
> logging#
>
>
> So it's not really using the logging system?
Well, yes - and no. The output you see is from the SAP Logging framework. But behind it still uses log4j / commons logging. And that's not surprising at all. That is exactly what the article describes - a bridge (routing) to SAP Logging, right? This is useful when you are porting existing apps (potentially using several logging frameworks) to the SAP NetWeaver Application Server and adapt them to use the SAP Logging framework thus achieving a unified logging experience. However, if you want to simply use log4j, I'd suggest that you just follow the steps described in Logging Questions isn't really
> clear to me - What is meant by:
>
> >The re-deployment fails because your file-system
> resources are locked by the
> >class loader of the previous application version and
> the this classloader is still in use ( >not GC-ed ).
> >Please check if your application uses registration
> pattern involving the application >classloader.
>
> I googled a bit on "registration pattern" but didn't
> find anything really useful.
> I'm not dealing with the classloader manually - any
> other tips/ further explanations
> on this?
OK, it was not actually meant to serve as a solution, but more as an explanation for the error you experienced. But you're right, maybe I had to elaborate a bit. You already spotted the culprit:
LogFactory.getLog(TravelAgentBean.class)
With this line of code you hand the TravelAgentBean class to the Commons Logging library which then keeps (eternally) that reference and hence the classloader of your application. This prevents from deleting the jars on the next deployment since the resources are locked by the classloader.
Unfortunately, I'm not aware of any real solution right now. I just have the strong feeling that if you pack the logging frameworks together within your app (as opposed to as a separate library), this error should not occur at all.
HTH!
-Vladimir

Problems with Log4j/commonslogging

I'm having some weird problems with log4j or commons/logging. I'm not at all
excluding that they may be my own fault, but I can't get to the actual
problem. Hope someone can help me out. I'm getting an exception at startup
of the VM. The exception is below. The problem seems to be version related I
think, but I can't figure it out exactly, since the versions of both logging
and log4j I have in my path seem to be exactly equal to those in my 2.5 RC1
distrib.
Hope you can help out,
Martin van Dijken
PS: This isn't the entire excep, hope it's enough
1652 ERROR [main] kodo.Runtime -
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:555)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:289)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.<init>(MetaDataParser.
java:32)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.<init>(CFMetaDataPar
ser.java:39)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.<init>(JDOMetaDataParser.java:61
at
com.solarmetric.kodo.meta.ClassMetaData.getInstance(ClassMetaData.java:223)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassIn
ternal(JDBCPersistenceManagerFactory.java:444)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(J
DBCPersistenceManagerFactory.java:334)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListen
er.java:53)
at javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at
com.madocke.mirakel.forum.ForumMessage.<clinit>(ForumMessage.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:217)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.resolveClass(MultiLoaderC
lassResolver.java:85)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.canResolveClass(MultiLoad
erClassResolver.java:143)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:231)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:180)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:165)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.startClass(JDOMetaDataParser.jav
a:122)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.startElement(CFMetaD
ataParser.java:53)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.startElement(MetaDataP
arser.java:238)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno
wn Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

What is probably happening is a class loader issue... I would put
jakarta's logging jar in the same place as log4j and be sure that they
aren't extraneously in the classpath (such as in an EAR or WAR). Java
can be pretty funky about classloaders and interfaces.
On Fri, 16 May 2003 11:02:40 -0400, Alex Roytman wrote:
Are you running it standalone or under lets say tomcat 4?
"Martin van Dijken" <[email protected]> wrote in message
news:[email protected]...
I'm having some weird problems with log4j or commons/logging. I'm not atall
excluding that they may be my own fault, but I can't get to the actual
problem. Hope someone can help me out. I'm getting an exception at startup
of the VM. The exception is below. The problem seems to be version relatedI
think, but I can't figure it out exactly, since the versions of bothlogging
and log4j I have in my path seem to be exactly equal to those in my 2.5RC1
distrib.
Hope you can help out,
Martin van Dijken
PS: This isn't the entire excep, hope it's enough
1652 ERROR [main] kodo.Runtime -
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:555)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:289)
atorg.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.<init>(MetaDataParser.
java:32)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.<init>(CFMetaDataPar
ser.java:39)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.<init>(JDOMetaDataParser.java:61
at
com.solarmetric.kodo.meta.ClassMetaData.getInstance(ClassMetaData.java:223)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassIn
ternal(JDBCPersistenceManagerFactory.java:444)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(J
DBCPersistenceManagerFactory.java:334)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListen
er.java:53)
atjavax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at
com.madocke.mirakel.forum.ForumMessage.<clinit>(ForumMessage.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:217)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.resolveClass(MultiLoaderC
lassResolver.java:85)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.canResolveClass(MultiLoad
erClassResolver.java:143)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:231)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:180)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:165)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.startClass(JDOMetaDataParser.jav
a:122)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.startElement(CFMetaD
ataParser.java:53)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.startElement(MetaDataP
arser.java:238)
atorg.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno
wn Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(UnknownSource)
at org.apache.xerces.parsers.DTDConfiguration.parse(UnknownSource)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(UnknownSource)
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Not sure how to configure Weblogic with log4j.xml

I tried something VERY similar to this. I wasn't sure where to put this code below. I figured in a Servlet environment, it should probably go in a Listener. I found an existing class inside of Spring that does exactly that: org.springframework.web.util.Log4jConfigListener
I put my log4j configuration file into an entry in the classpath and configured web.xml as follows:

 <context-param>
 <param-name>log4jConfigLocation</param-name>
 <param-value>classpath:gov/pa/dep/formu/resources/log4j.properties</param-value>
 </context-param>
 <context-param>
 <param-name>log4jRefreshInterval</param-name>
 <param-value>30000</param-value>
 </context-param>
 
 <listener>
 <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
 </listener>The server admin placed the actual log4j.properties file into an AppFileOverrides folder instead of under WEB-INF\classes. I don't know if this caused the problem or not. Since I also was using the DailyRollingFileAppender and running into problems LOSING my log entries each day because he file didn't get renamed, I followed Metalink BUG# 8459807, and used the datedFileAppender available at http://minaret.biz/tips/datedFileAppender.html.
When the application started, the server log showed that log4j was being configured but none of my logging statements were going into the logs. It wasn't until the server admin placed a copy of log4j.properties (a different log4j.properties with a rolling file appender) that the log statements started going into the file that was configured based on web.xml.
Surely, things can't be this difficult with log4j, and commons logging under WebLogic.
All I want is APPLICATION LEVEL LOGS that are specific to the day.
Can someone else elaborate on how they got this working?
thanks a bunch,
Eric

Hi,
The configuration wizard (config.sh) lets you create a WebLogic Domain, however and depending on others "Oracle Middleware" products installed on the same "Oracle Home" (directory where weblogic has been installed) the configuration wizard allows you create the new weblogic domain to support the others middleware products such as WebCenter.
When I say support It means that Configuration Wizard allows you to create the weblogic resources like JDBC connections, JMS services, and deploys all applications that integrates another product such as WebCenter.
I suggest create your domain with support for WebCenter and then from Admin Console create the JDBC resource to connect to other database such as JD Edwards database.
I hope this help.

Open task sequence log with cmtrace on error

Hi,
Is there a way to make an SCCM 2012 R2 task sequence automatically open the smsts.log (with cmtrace) when an error occurs?
J.
Jan Hoedt

I would agree with Torstren. The difficult piece would be determining where the smsts.log is, based on where its at in the task sequence. Once you have that it wouldn't be too difficult to place those steps in the
Gather Logs and StateStore on Failure group. The catch will be, even if CMTrace is open, the machine will still reboot after 15 minutes unless the cmd prompt is also open.

Can't update software because a message appears that I have to log with the same Apple ID that was used to purchase them: iMovie, Garage Band

I can't update software because a message appears that I have to log with the same Apple ID that was used to purchase them: iMovie, Garage Band, iPhoto, but those apps came with OSX Lion.
How can I get the "original" Apple ID?

Support Downloads
http://support.apple.com/downloads/
Luckily, there is always more than one way to update software.

Logging with log4j

Similar Messages

Maybe you are looking for