Log4j and commons logging
Hi,
My application is using log4j, I get my logger as follows:
private static Logger sLogger = Logger.getLogger(Neolyser.class);My problem is that Im using a library thats using commons logging and writes all its logging onto my logger, which I dont want. I want only to see my log statements, I'm happy enough with exceptions and stack traces from the library. So how can I turn off the commons logging? Or at least get it to write to another logger? Thanks in advance,
Ste
Hi thanks for your reply, Im pretty new to log4j so I dont know how to do that. I configure my looger as follows:
BasicConfigurator.resetConfiguration();
ConsoleAppender lCAppender = new ConsoleAppender(new PatternLayout(lPattern));
lCAppender.setThreshold(Level.toLevel(lLevel));Are there other settings I can use to turn off the library logging? Thanks
Similar Messages
-
Can any one get me the difference between Log4j and commons-logging.
Or, if both are same which one compliments the other.
Thankls
- Java Buddy.Can any one get me the difference between Log4j and
commons-logging. Both are logging mechanisms.
Or, if both are same which one compliments the
other.Commons logging can be configured to internally use Log4J.
http://jakarta.apache.org/commons/logging/guide.html#Configuration -
Cant use log4j or commons logging with ease in OC4J/OAS 10g
Hi,
I have a simple JEE 5 app which just uses Log4J for logging. I have a log4j.properties at the right place. But deploying an EAR with this config fails
Operation failed with error: Lorg/apache/log4j/Logger;
or if i move to commons logging this...
Operation failed with error: Lorg/apache/commons/logging/Log;
Things as simple as using logging, I feel, shouldnt be any complex than what is inferred. Atleast there should more error detailing to it than a bozo message like the above.
Anyone used logging in just a ejb jar app???We've run into this recently and were surprised to find out that Oracle not only "recommends" OAS over OC4J in a production environment, they require it. If you look at the license agreement that you accepted when you downloaded OC4J (you know, the thing that you never read) you'll find that Oracle expressly says that you are not allowed to use OC4J in anything other than a development environment.
So, after years of using it for several applications, we now have to switch to OAS. Actually, we are doing this not only to stay legal, but also to take advantage of mod_oc4j for reverse proxy. We could not get this to work under OC4J so we started poking around with OAS and then found out that we were not licensed for either in production.
If you are using OC4J in production, read the not-so-fine print. You are in violation of their license agreement.
-Bruce Altner
NASA HQ -
Taskflow based on human task and commons logging error
Hi,
Is the logging changed after the soa update. When I deploy the humantask taskflow to the soa-infra I got .the following error
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
I had to remove the commons logging library from the project and add this to the orion-application.xmlI don't use log4j , I just created a fusion webapp where I add taskflow based on a human task that's it.
If I remove the commons logging then deployment fails. -
Cluster and commons-logging jar LogConfigurationException
Hi,
My configuration:
-OAS 10.1.3.1 on 2 machines with oracle cluster configuration (discovery).
My app:
-ear which includes simple ejb3 module with commons-logging-1.1.jar lib (Jakarta commons logging)
-clustering and replication is configured (in orion-application.xml):
<cluster allow-colocation="false">
<replication-policy trigger="onSetAttribute" scope="allAttributes" />
<flow-control-policy enabled="false" />
<protocol>
<peer>
<opmn-discovery />
</peer>
</protocol>
</cluster>
When I'm trying to deploy my application I always get an error during deployment:
[19-Jun-2007 16:46:44] Initializing ClassLoader(s)
[01-Jan-1970 01:00:00] Error deserializing return-value: org.apache.commons.logging.LogConfigurationException; nested exception is: java.lang.ClassNotFoundException: org.apache.commons.logging.LogConfigurationException
It doesn't matter if I try to deploy it on one or both machines. The exception is always the same on each machine.
When I get rid of clustering/replication configuration (from orion-application.xml or during deployment) application is deployed without any problem.
Also when I remove commons-logging-1.1.jar application is deployed.
I know that there is already apache.commons.logging 1.0.4 in OAS shared libraries by it's not selected in "Configure Class Loading" by default.
I also tried use the same version (1.0.4) in my app - didn't help.
I can also deploy without any problem war file or ear file with web module, which has commons-logging-1.1.jar. But not ejb!
Any advice?
Thanks
darekHey Darek -- I just gave it a quick try -- the ListQueries query works as expected.
This is how I executed it and the results it returned.
d:\java\oc4j-10131-prod\j2ee\home>java -Doc4j.start.query=ListQueries+Exit -jar oc4j.jar
07/06/25 00:51:41 Shutting down OC4J...
AuditLoader - Performs various diagnostics on the contents of the speci
fied loader(s).
Callers - List all classes that call the specified method(s).
ClassLoadMetrics - Report metrics from specified loader(s) or all if none specified.
ClassPath - List the code-sources in use.
Dependencies - List the dependencies of the specified class.
Depends - List all classes that depend on the specified class(s).
DuplicateClasses - List duplicate classes, both loaded and in code-sources.
DuplicateCodeSources - List code-sources that have more than 1 subscriber, or the same name.
Exit - Exits the process (does shutdown if system is running).
FindResource - List the code-sources containing the specified resource.
GetResource - Call getResource() or getResources() on a specified loader and report the results.
HttpSessions - View summary of active HttpSessions for deployed applications.
LeakedLoaders - Control detection of class loader leaks and inspect results.
ListQueries - List built-in subclasses of the "oracle.classloader.query.Query" class.
LoadClass - Call loadClass() or Class.forName() using a specified loader and report the results.
LoadedClasses - List the names of all loaded classes (if available).
LoaderTree - List the class loader tree.
Packages - List the package names contained within the specified code-source(s).
SharedLibraries - List shared-libraries and the loaders that have imported them.
SystemProperties - List or set System properties.
ThreadPools - List application server related thread for the current VM.
Threads - List thread info for the current VM.
UnusedCodeSources - List any code-sources from which no classes or resources have been loaded.
Uptime - Report how long the system has been running.
VMStat - List statistic info for the current VM.
Specify the query name for a full description, or use the '-l' option to see ful
l descriptions for all. -
Hello all,
Is there anyway to redirect log4j logging to WAS loggers.
For example, axis needs log4j and may need to log to some appenders.
Can we safely use SAP logging and how?
Is there an example somewhere?
AntoineThere's an article "Integrating 3rd party logging Frameworks into SAP NetWeaver" (https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36085e78-0801-0010-678d-8b4e89ddff3c)
It mentions sample code and a tutorial for a "Log4j bridge", but I couldn't locate that. I have posted a separate question for that.
Hope this helps,
Michael -
Hi,
When i start WL 9.1 server, i get the following error. My application uses log4j-1.2.8 and commons-logging-1.0.4.jar. I wasnt getting this in WL 8.1.4. is there any in-compatibilities(Looking at the error message, i looks like that).Is there anything that needs to be done for WL 9.1?
<Mar 22, 2006 10:23:30 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[
1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, http.>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default"
is now listening on 10.173.194.102:7001 for protocols iiop, t3, ldap, http.>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <WebLogicServer> <BEA-000331> <Started W
ebLogic Admin Server "AdminServer" for domain "coretest_oracle" running in Devel
opment Mode>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to RUNNING>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server st
arted in RUNNING mode>
java.lang.NoSuchMethodError: org.apache.log4j.Category.log(Ljava/lang/String;Lor
g/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V
at org.apache.commons.logging.impl.Log4JCategoryLog.debug(Log4JCategoryL
og.java:94)
at com.bea.console.preferences.spi.FilePreferencesProvider.<init>(FilePr
eferencesProvider.java:70)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at com.bea.portlet.prefs.spi.ProviderFactory.createInstance(ProviderFact
ory.java:79)
at com.bea.portlet.prefs.spi.ProviderFactory.setDefaultProviderClass(Pro
viderFactory.java:47)
at com.bea.portlet.prefs.spi.IPreferenceStore$Factory.registerDefaultPro
vider(IPreferenceStore.java:128)
at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServ
let.java:113)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:
94)
at weblogic.servlet.internal.WebAppServletContext$AsyncInitRequest.run(W
ebAppServletContext.java:1641)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkMan
agerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)Hi,
When i start WL 9.1 server, i get the following error. My application uses log4j-1.2.8 and commons-logging-1.0.4.jar. I wasnt getting this in WL 8.1.4. is there any in-compatibilities(Looking at the error message, i looks like that).Is there anything that needs to be done for WL 9.1?
<Mar 22, 2006 10:23:30 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[
1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, http.>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default"
is now listening on 10.173.194.102:7001 for protocols iiop, t3, ldap, http.>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <WebLogicServer> <BEA-000331> <Started W
ebLogic Admin Server "AdminServer" for domain "coretest_oracle" running in Devel
opment Mode>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to RUNNING>
<Mar 22, 2006 10:23:30 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server st
arted in RUNNING mode>
java.lang.NoSuchMethodError: org.apache.log4j.Category.log(Ljava/lang/String;Lor
g/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V
at org.apache.commons.logging.impl.Log4JCategoryLog.debug(Log4JCategoryL
og.java:94)
at com.bea.console.preferences.spi.FilePreferencesProvider.<init>(FilePr
eferencesProvider.java:70)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at com.bea.portlet.prefs.spi.ProviderFactory.createInstance(ProviderFact
ory.java:79)
at com.bea.portlet.prefs.spi.ProviderFactory.setDefaultProviderClass(Pro
viderFactory.java:47)
at com.bea.portlet.prefs.spi.IPreferenceStore$Factory.registerDefaultPro
vider(IPreferenceStore.java:128)
at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServ
let.java:113)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:
94)
at weblogic.servlet.internal.WebAppServletContext$AsyncInitRequest.run(W
ebAppServletContext.java:1641)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkMan
agerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) -
Hi,
I'm using RollingFileAppender to append log4j and log4cxx logs in a common log file. This works only for the first log file. But, the subsequent log files which got created when the size exceeds the specified range, does not getting appended the log4cxx logs.
I have referred http://www.dreamcubes.com/blog/?itemid=59#nucleus_cf
Here is my config settings
log4j:
log4j.rootLogger=debug,console,file
log4j.category.com.company.project=debug
# File Appender
# file is set to be a RollingFileAppender.
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.File=project.log
log4j.appender.file.MaxFileSize=100KB
# Keep one backup file
log4j.appender.file.MaxBackupIndex=100
# file uses PatternLayout.
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss,SSS} - %m%nlog4cxx:
<?xml version="1.0" encoding="UTF-8" ?>
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
<!-- Output the log message to system console.
-->
<appender name="MyConsoleAppender" class="org.apache.log4j.ConsoleAppender">
<param name="Target" value="System.out"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%-5p %c{1} - %m%n"/>
</layout>
</appender>
<!-- On application startup, a log file named "project.log" will be create if not exist.
When the log file reach beyond 100KB, it will be renamed "project.log.1", when the log
index reach "project.log.5", the next rename will be back to "project.log.1" and
overite the old log.
-->
<appender name="MyRollingAppenderSize" class="org.apache.log4j.RollingFileAppender">
<param name="file" value="project.log"/>
<param name="append" value="true"/>
<param name="MaxFileSize" value="100KB"/>
<param name="MaxBackupIndex" value="100"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
</layout>
</appender>
<!-- Setup the root category, add the appenders and set the default level
5 level of logging, ALL < DEBUG < INFO < WARN < ERROR < FATAL
The root level is set with INFO, which mean any message greater or same
as INFO will be log down, in this case, DEBUG is not logged.
To log all regardless of logging level, set <priority value="ALL">
-->
<root>
<priority value="all" />
<appender-ref ref="MyRollingAppenderSize"/>
<appender-ref ref="MyConsoleAppender"/>
</root>
</log4j:configuration>Logger experts,
First of all, trying to point a common logging file from two different log configuration file is possible?
If this is not at all possible, Keeping the two different log file would work, but it is cumbersome on debugging..
Thanks and Regards,
Ramesh -
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(MGuten 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 -
Struts, log4j, commons-logging problems in 9.0.4 too??
ok... I have a J2EE project that uses struts, log4j, a couple ejbs. I can successfully deploy and run on JBoss. However, our client insists that we use the 10g App Server, so I tried to deploy on 10g v10.1.2 (after making the appropriate changes to the deployment descriptors); the ear file deployed without problems, but when using the application, I encountered the following error when the app got to part of my code that tries to create a log file using the commons-logging framework:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
I see from these forums that there is a known problem regarding commons-logging and log4j with v10.1.2 (Help: 10g, struts, commons-logging and log4j doesn't work in 10g!? 9i fine! )..... so, I installed v9.0.4 of the 10g AppServer, deployed and ...... drum roll please.... I get the same error.
The commons-logging.jar file IS in the [application dir]/WEB-INF/lib directory so the app should be finding the org.apache.commons.logging.LogFactory class file. And - struts is working based on page navigation prior to hitting the error (which I've heard indicates that the commons-logging.jar library is being invoked at some point).
So... am I missing something? or does v9.0.4 also have the bug (related to classloaders)???
sure hope someone can help....
ScottI don't know why it's not working either, unless it's related to that classloader issue.... I have the following files in my WEB-INF/lib directory:
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-logging.jar
commons-validator.jar
jakarta-oro.jar
log4j-1.2.9.jar
struts.jar
ScottsTester-ejb.jar (my ejb classes)
ScottsTester-web.jar (my struts-related classes)
I'm running into problems when the app tries to create an instance of my ejb (which has as a member variable an org.apache.commons.logging.Log object which is created by the org.apache.commons.logging.LogFactory object - the Oracle App Server is telling me it can't find the LogFactory class despite the fact that the commoons-logging.jar file is in the WEB-INF/lib directory.... and, as other postings have noted, this appears to be a problem with the classloaders. Unfortunately, the workaround suggesting by Qiang causes problems with my ejbs - when I try to get a home object, I encounter a ClassCastException somewhere in the PortableRemoteObject.narrow(o, DbConnectionHome.class); call..... maybe Oracle should stick to databases..... -
How to use commons.logging in weblogic (8.1)?
Greetings,
I'm trying to use commons.logging framework to manage the logs of my
application. With Weblogic I will use an implementation that works with
weblogic.logging package but with other J2EE products I'll use another
native log implementations or frameworks (for instance, for jboss I will
use log4j).
1) I created a class WeblogicLogger which implements the Log interface::
public final class WeblogicLogger implements Log {
I packaged this class in a jar file with a properties file,
commons-logging.properties, which has the property setting my class
below has the default logger:
org.apache.commons.logging.Log=pt.ptinovacao.weblogic.logging.WeblogicLogger
2) My sample code has the following code:
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
private static final Log log = LogFactory.getLog(
LogTimeStartHandler.class.getName());
something(){
log.info(this.getClass()+" test log");
3) I added the commons-logging jars and my jar with my custom wrapper
weblogic logger in ${WL_HOME}/common/bin/commEnv.sh:
WEBLOGIC_CLASSPATH=
(...)${CLASSPATHSEP}${WL_HOME}/server/lib/weblogiclogger.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging-api.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging.jar
However, my loggings still not appear in my weblogic server. Did I miss
something?
thanks,
Pedro SalazarDid you manage to get this working?
If yes ... what did you do?
I am having the same problem implementing commons-logging with log4j -
Greetings, all!
I've searched this forum and the OC4J forum and have not found any clues to help with my log4j woes. I'm hoping someone may have encountered similar issues and can share their thoughts.
I am developing a web application and would like to use log4j. I have successfully integrated it in my development environment (JDev 10.1.2.1.0/Standalone OC4J 10.1.2.0.2) by placing the log4j jar (log4j-1.2.14) in WEB-INF/lib. I have not been successful in moving it to our staging OAS environment, however. We are running 10gR2 OAS (10.1.2.0.2) on Windows 2003.
Since I read in the docs (http://download-west.oracle.com/docs/cd/B14099_19/web.1012/b14017/jkosfram.htm#sthref698)that the log4j jar should not be put in the applib directory of the OAS_HOME I have been trying to deploy the application with the jar file within the WEB-INF/lib location. Every time I try to deploy, I get the following error complaining that it cannot find the correct classes.
Base Exception:
com.evermind.server.rmi.OrionRemoteException
Class not found: org.apache.commons.logging.LogConfigurationException; nested exception is:
java.lang.ClassNotFoundException: org.apache.commons.logging.LogConfigurationException. Class not found: org.apache.commons.logging.LogConfigurationException; nested exception is:
java.lang.ClassNotFoundException: org.apache.commons.logging.LogConfigurationException
I understand it is probably a classloader issue, but using an orion-web.xml file with the search-local-classes-first set to true does not work either. I was successful in deploying the app and writing to a log when the log4j jar was in the applib directory, but since the docs state that this could cause conflicts with OEM, I removed the jar. I have also been able to log to the application.log file by using context.log() statements, but this is less than optimal.
I know 10.1.3 may solve this issue, but we are not planning on that version for some time. How are others using log4j in the OAS? Should I just place the jar in the applib and hope for the best?
TIA for any help or insight,
Dixie.I resolved the problem and wanted to post the solution in case anyone had similar problems. The issue was related to the commons.logging package used by JSF. I had version 1.0.4 in the applib directory of the OAS_HOME along with the other jars needed for JSF. Once I upgraded to the 1.1 version of commons-logging I was able to deploy the app and use log4j. I received this metalink reference from a colleague and it helped me solve the problem: Note:413981.1
Dixie. -
Replace commons-logging.jar with another version
Hi all,
I'm using CR4E version 2 Update 4(v. 12.2.205) and I would use instead of
commons-logging.jar (v. 1.1.1) provided, the version used in my application
(v. 1.0.4). Is possible without errors?
I specify that I not use the provided log4j.jar in CR4E v.2.
Thanks a lotThe versions that we provide with our product is the version that we expect to be using when using our product. Any other version may or may not work and there would be no way to fix an issue specific to using a different version than what we provide.
-
EJBC error when using Commons Logging API
All,
I am using weblogic 7.0 and Commons with log4j.When I run the
ejbc I get the following error.
There is no package called Lorg in my classpath.
Any suggestions on why this is happening?
Thanks in Advance,
Chandrav
[java] ERROR: Error from ejbc: Class not found: Lorg/apache/commons/logging/Log;
[java] <Apr 23, 2003 1:59:58 PM PDT> <Warning> <EJB> <010054> <EJB Deploym
ent: ServiceProviderInterfaceEntityBean has a class com.wisor.validator.servicep
rovidermanagement.entitybean.ServiceProviderInterfaceEntityLocal which is in the
classpath. This class should only be located in the ejb-jar file.>
[java] [EJBCompiler] : Recompiling because no previous hashes found
[java]
[java] java.lang.NoClassDefFoundError: Class not found: Lorg/apache/commons
/logging/Log;
[java] at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBCompl
ianceChecker.java:282)
[java] at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymen
tInfo(EJBComplianceChecker.java:227)
[java] at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompile
r.java:923)
[java] at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.j
ava:879)
[java] at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:23
2)
[java] at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:3
96)
[java] at weblogic.ejbc20.runBody(ejbc20.java:459)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:126)
[java] at weblogic.ejbc.main(ejbc.java:21)
[java]
[java]
[java] ERROR: ejbc found errors
[java]
BUILD FAILEDmake sure you have defined the commons logging jar as a Class-Path entry in
your ejb jar META-INF\manifest.mf file
\"Chandrasekaran.V" <[email protected]> wrote in message news:<3ea75721$[email protected]>...
All,
I am using weblogic 7.0 and Commons with log4j.When I run the
ejbc I get the following error.
There is no package called Lorg in my classpath.
Any suggestions on why this is happening?
Thanks in Advance,
Chandrav
[java] ERROR: Error from ejbc: Class not found: Lorg/apache/commons/logging/Log;
[java] <Apr 23, 2003 1:59:58 PM PDT> <Warning> <EJB> <010054> <EJB Deploym
ent: ServiceProviderInterfaceEntityBean has a class com.wisor.validator.servicep
rovidermanagement.entitybean.ServiceProviderInterfaceEntityLocal which is in the
classpath. This class should only be located in the ejb-jar file.>
[java] [EJBCompiler] : Recompiling because no previous hashes found
[java]
[java] java.lang.NoClassDefFoundError: Class not found: Lorg/apache/commons
/logging/Log;
[java] at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBCompl
ianceChecker.java:282)
[java] at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymen
tInfo(EJBComplianceChecker.java:227)
[java] at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompile
r.java:923)
[java] at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.j
ava:879)
[java] at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:23
2)
[java] at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:3
96)
[java] at weblogic.ejbc20.runBody(ejbc20.java:459)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:126)
[java] at weblogic.ejbc.main(ejbc.java:21)
[java]
[java]
[java] ERROR: ejbc found errors
[java]
BUILD FAILED -
Weblogic admin console fails to start when commons logging is used.
I have an application that requires commons logging.
I followed the instructions as per the documentation and other forum entries such as How to use log4j into weblogic 10.3 to add the commons logging jar from apache and the weblogic jar specified. Plus I set the system property for the LogFactory.
When I start up the application server I see messages as expected from my application. But when I start up the weblogic Admin console I get and exception and the console fails to start. I even tried to put the jars in my applicaiton instead of the domain/lib directory to try to iscolate the issue but still got issues with starting the Console.
Any ideas on why this is occuring?
See the error below:
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <----------------------------------------Retention Init()---------------------------------------->
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <Thu May 20 05:00:00 EDT 2010>
####<May 19, 2010 4:16:06 PM EDT> <Info> <Health> <TE001XU-CATOR1> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1274300166060> <BEA-310002> <81% of the total memory in the server is free>
####<May 19, 2010 4:35:03 PM EDT> <Info> <WorkManager> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301303146> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<May 19, 2010 4:35:17 PM EDT> <Error> <HTTP> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301317582> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl cannot be cast to org.apache.commons.logging.LogFactory)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:574)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:254)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.<clinit>(MBeanUtilsInitSingleFileServlet.java:23)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)Thank you for replying. Yes that is the first place we looked and tried. Actually to be more specific we followed the instrcutions under: "How to Use the Commons API with WebLogic Logging Services" of the same link.
Are you thinking that maybe we are we missing a step somewhere else within the site?
Not sure if I was clear before but we are using Weblogic 10.3 and also tried up to version 10.3.3. And we get the same results.
We prefer to use the method with commons logging for our application.
One more specific here what we did on our last attempt.
1. added this to the startWeblogic script JAVAOPTIONS -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
2. we put the WebLogic-specific Commons classes, $BEA_HOME/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar, together with the commons-logging.jar file in one of the following locations: APP-INF/LIB or WEB-INF/LIB directory or DOMAIN_NAME/LIB directory server CLASSPATH
We are still not able to get the Weblogic admin console to start
Any other ideas?
Edited by: user13094648 on May 21, 2010 10:29 AM
Edited by: user13094648 on May 21, 2010 10:37 AM
Maybe you are looking for
-
Issues Consuming ADF portlet in Webcenter
Hi, We created an ADF page in the portlet producer and created a portlet entry. We used a webcenter consumer to consume the ADF portlet from the portlet producer. On running the webcenter consumer the page is displayed as desired but on performing an
-
Itunes will not launch on Windows Vista no error code
Itunes will not launch on my computer. I have windows vista. I have uninstalled and downloaded itunes repeatedly. I have also tried all of the troubleshooting tips available on the apple support site. But none of them worked. Quicktimes works fine. I
-
Cannot uninstall older version of bonjour
When installing itunes update 10.4 on my pc using windows xp. Error message cannot uninstall older version of bonjour. I cannot delete this file manually using add delete programme either. Any ideas?
-
SVM - "Unavailable" devices, destroyed SVM config
I have a Solaris 10 host with mirrored SVM volumes that seems to have destroyed its SVM config. We rebooted and all the metadbs on two of the disks came up bad, and none of the DBs were online so the system came up in single user mode due to insuffic
-
Recently updated to osx 4.6 and system keeps freezing????
If anybody has any suggestions, please try to walk me thru process of troubleshooting problem ... I'm not all that mac savy! Thanks in advance!