Configure commons-logging formatting
I've managed to configure commons-logging to work with WebLogic but now I'd like to configure the log-output format.
Does anyone know how to change the output format?
Yes, but the simplest thing to do is to not include
log4j.jar
If you don't want to use it, don't inlcude it.It's not possible. Our client wants a callendar. We have purchased dotj library which has a calendar. Unfortunately their library includes log4j.
But the application I have written uses commons logging and it should use jdk 1.4 logging otherwise logging doesn't work properly with SUN AS.
Similar Messages
-
Using extended common log format
Hello
I wanted to set up access log file format to capture referer and user-agent info.
After reading the docs I added the 2 variables via admin console.
So HTTP Service ->Access Log -> Format contains following:
%client.name% %auth-user-name% %datetime% %request% %status% %response.length% %header.referer% %header.user-agent%After saving and restarting the domain, I am still not getting the referrer and user agent.
There is not even a "-" indicating that the info was unavailable....
Any thoughts?
Z....Can someone please help me with this issue.
Our company needs extensive web metric reports and the only way to do so is by adding more info in the logs.
Again, following is my Configuration->HTTP Service->Access Log setup from the admin console.
Rotation: Enabled
Rotation Policy: time
Rotation Interval: 1440
Rotation Suffix: %YYYY;%MM;%DD;-%hh;h%mm;m%ss;s
Format: %client.name% %auth-user-name% %datetime% %request% %status% %response.length% %header.referer% %header.user-agent% %cookie.value%Again, the log does not record last 3 values....There are not even "-" indicating missing values.
Much appreciated.
Z -
Hello,
I am rather new to BEA, and I am experiencing a little bit of a problem here. I am trying to configure the access logs in order for them to generate output concerning Browser information. I have gone through and was successfully able to change the configuration to extended. The browser information is now displayed.
I have one MAJOR problem. When using the common log format, the usernames are logged just fine. But when I changed to the extended format, I only get a value of '-'. I believe all of my configuration is correct according to w3c standards, as I am using 'cs-username' in the '#Fields' directive. I have been searching all over for information reguarding how this field can be documented, but I cannot find anything.
I have even gone out and tried to configure our apache logs to read this field, and yet I get the same '-' value there as well.
If anyone could PLEASE help me in this matter, I would greatly appreciate it, as I am going down a river without a paddle on this one.
Thanks in advance,
Garret<p>Hello,</p>
<p>Have you read through common log format doc and Enabling and Configuring HTTP Access Logs? Oddly they don't mension cs-username in the supported field identifiers section. You could try the common log format field name: auth_user. Or a custom identifier. I would also raise a support case with BEA if you don't get anywhere to make sure they do actually support this field.</p>
<p>
Hussein Badakhchani</br>
</p> -
How to direct commons-logging to jdev console instead of DefaultServer.log
Hi,
I have configured commons-logging in my adf 11g application. I added the following line to the commons-logging.properties file:
org.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
I have added the JDev11.1.1.1.0/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar as library to my project. If in my weblogic server i set the correct logger settings for my classes i see al log messages in the DefaultServer.log file. How can i make these appear in the JDeveloper console instead?
Kind Regards,
AndreHi,
Found it out by myself so for everybody that wants to do the same.... In the weblogic console logging tab i needed to set the Severity level of Message Destination Standard Out to Debug. Since i now can see all logging in the JDev console i set the Message Destination Log File to warning so the log file does not get to big.
Kind Regards,
Andre -
Is there a way to control the format of weblogic's logging?
I'm logging to Weblogic's log using Java code that looks something like:
T3Services.getT3Services().log().log( "Foo..." );
This results in log messages that look something like:
Wed Jan 17 15:57:03 CST 2001:<I> <T3Services> Foo...
I'd like to be able to modify, replace or even suppress the date, time, <I> and/or <T3Services>.
For example, my log subsystem is capable of generating the following message which I'd prefer to send to WL's log:
01-17-2001 15:57:03 <TRACE> <GUI> Foo...
Does WL5.1 support the level of log format customization I'm looking for, and if so where can I find information about configuring the logging format?Owen Horne <[email protected]> wrote in message
news:3a663105$[email protected]..
>
Is there a way to control the format of weblogic's logging?No. The format of the logfiles is fixed in 5.1 and 6.0 release.
>
I'm logging to Weblogic's log using Java code that looks something like:
T3Services.getT3Services().log().log( "Foo..." );
This results in log messages that look something like:
Wed Jan 17 15:57:03 CST 2001:<I> <T3Services> Foo...
I'd like to be able to modify, replace or even suppress the date, time,<I> and/or <T3Services>.
>
For example, my log subsystem is capable of generating the followingmessage which I'd prefer to send to WL's log:
01-17-2001 15:57:03 <TRACE> <GUI> Foo...
Does WL5.1 support the level of log format customization I'm looking for,and if so where can I find information about configuring the logging format? -
Commons-logging error when starting Flex2 in JRun
Created new JRun Server and deployed Flex2 to this server.
Receiving this error when starting up this server instance.
Starting Macromedia JRun 4.0 (Build 92909), logicerm2 server
07/13 22:23:28 info JRun Naming Service listening on *:2911
07/13 22:23:28 warning No sessionSecret has been specified in
jrun.xml. Installi
ng a self generated sessionSecret.
07/13 22:23:28 info No JDBC data sources have been configured
for this server (s
ee jrun-resources.xml)
07/13 22:23:28 info JRun Web Server listening on *:8102
07/13 22:23:28 info Deploying enterprise application
"default-ear" from: file:/C
:/JRun4/servers/logicerm2/default-ear/
07/13 22:23:28 info Deploying web application "JRun Default
Web Application" fro
m: file:/C:/JRun4/servers/logicerm2/default-ear/
07/13 22:23:29 info Web Services in default-ear#default-war:
07/13 22:23:29 info AdminService
07/13 22:23:29 warning default-war web application has
'reload' as true in jrun-
web.xml. Consider setting it false if the application is
running in production e
nvironment.
07/13 22:23:29 warning default-war web application has
'compile' as true in jrun
-web.xml. Consider setting it false if the application is
running in production
environment.
07/13 22:23:29 user JSPServlet: init
07/13 22:23:29 info Deploying web application "Flex Data
Services" from: file:/C
:/JRun4/servers/logicerm2/flex/
07/13 22:23:29 user JSPServlet: init
07/13 22:23:29 user FlexMxmlServlet: init
07/13 22:23:29 INFO Loading configuration file
C:\JRun4\servers\logicerm2\flex\W
EB-INF\flex\flex-webtier-config.xml
07/13 22:23:30 INFO Loading configuration file
C:\JRun4\servers\logicerm2\flex\W
EB-INF\flex\flex-config.xml
07/13 22:23:30 user FlexMxmlServlet: Starting Adobe Flex Web
Tier Compiler
07/13 22:23:30 user FlexMxmlServlet: Adobe Flex Web Tier
Compiler Build: 143451
07/13 22:23:30 user MessageBrokerServlet: init
07/13 22:23:31 user FlexSwfServlet: init
07/13 22:23:31 user FlexInternalServlet: init
07/13 22:23:31 info Deploying web application "Flex Admin Web
Application" from:
file:/C:/JRun4/servers/logicerm2/flex-admin/
07/13 22:23:31 user JSPServlet: init
07/13 22:23:31 user MessageBrokerServlet: init
07/13 22:23:31 info Deploying web application "Flex Data
Services Samples" from:
file:/C:/JRun4/servers/logicerm2/samples/
07/13 22:23:31 user JSPServlet: init
07/13 22:23:31 user FlexMxmlServlet: init
07/13 22:23:32 INFO Loading configuration file
C:\JRun4\servers\logicerm2\sample
s\WEB-INF\flex\flex-webtier-config.xml
07/13 22:23:32 INFO Loading configuration file
C:\JRun4\servers\logicerm2\sample
s\WEB-INF\flex\flex-config.xml
07/13 22:23:32 user FlexMxmlServlet: Starting Adobe Flex Web
Tier Compiler
07/13 22:23:32 user FlexMxmlServlet: Adobe Flex Web Tier
Compiler Build: 143451
07/13 22:23:32 user MessageBrokerServlet: init
07/13 22:23:32 error Could not pre-load servlet:
MessageBrokerServlet
[1]org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logg
ing.LogConfigurationException:
org.apache.commons.logging.LogConfigurationExcept
ion: Invalid class loader hierarchy. You have more than one
version of 'org.apa
che.commons.logging.Log' visible, which is not allowed.
(Caused by org.apache.co
mmons.logging.LogConfigurationException: Invalid class loader
hierarchy. You ha
ve more than one version of 'org.apache.commons.logging.Log'
visible, which is n
ot allowed.) (Caused by
org.apache.commons.logging.LogConfigurationException: or
g.apache.commons.logging.LogConfigurationException: Invalid
class loader hierarc
hy. You have more than one version of
'org.apache.commons.logging.Log' visible,
which is not allowed. (Caused by
org.apache.commons.logging.LogConfigurationExc
eption: Invalid class loader hierarchy. You have more than
one version of 'org.
apache.commons.logging.Log' visible, which is not allowed.))
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:543)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:235)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:209)
at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at
org.apache.commons.httpclient.params.DefaultHttpParams.<clinit>(Defau
ltHttpParams.java:53)
at
flex.messaging.services.http.HTTPProxyAdapter.<init>(HTTPProxyAdapter
.java:111)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Sou
rce)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
flex.messaging.util.ClassUtil.createDefaultInstance(ClassUtil.java:71
at
flex.messaging.Destination.createAdapter(Destination.java:277)
at
flex.messaging.Destination.initDestination(Destination.java:103)
at
flex.messaging.services.HTTPProxyService.createDestination(HTTPProxyS
ervice.java:78)
at
flex.messaging.services.AbstractService.createDestinations(AbstractSe
rvice.java:82)
at
flex.messaging.config.MessagingConfiguration.createServices(Messaging
Configuration.java:187)
at
flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
gConfiguration.java:84)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
5)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
java:1242)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
ice.java:789)
at
jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
va:291)
at
jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
ce.java:242)
at
jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
ce.java:179)
at
jrun.deployment.DeployerService.run(DeployerService.java:891)
at
jrunx.scheduler.SchedulerService.invokeRunnable(SchedulerService.java
:223)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
Caused by:
org.apache.commons.logging.LogConfigurationException:
org.apache.comm
ons.logging.LogConfigurationException: Invalid class loader
hierarchy. You have
more than one version of 'org.apache.commons.logging.Log'
visible, which is not
allowed. (Caused by
org.apache.commons.logging.LogConfigurationException: Inval
id class loader hierarchy. You have more than one version of
'org.apache.common
s.logging.Log' visible, which is not allowed.)
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:397)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:529)
... 30 more
Caused by:
org.apache.commons.logging.LogConfigurationException: Invalid class
l
oader hierarchy. You have more than one version of
'org.apache.commons.logging.
Log' visible, which is not allowed.
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:385)
... 31 more
[0]flex.messaging.config.ConfigurationException: Unable to
create service 'flex.
messaging.services.HTTPProxyService' for 'proxy-service' due
to the following er
ror: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.lo
gging.LogConfigurationException: Invalid class loader
hierarchy. You have more
than one version of 'org.apache.commons.logging.Log' visible,
which is not allow
ed. (Caused by
org.apache.commons.logging.LogConfigurationException: Invalid cla
ss loader hierarchy. You have more than one version of
'org.apache.commons.logg
ing.Log' visible, which is not allowed.) (Caused by
org.apache.commons.logging.L
ogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
Invalid class loader hierarchy. You have more than one
version of 'org.apache.c
ommons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commons
.logging.LogConfigurationException: Invalid class loader
hierarchy. You have mo
re than one version of 'org.apache.commons.logging.Log'
visible, which is not al
lowed.)).
at
flex.messaging.config.MessagingConfiguration.createServices(Messaging
Configuration.java:202)
at
flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
gConfiguration.java:84)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
5)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
java:1242)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
ice.java:789)
at
jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
va:291)
at
jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
ce.java:242)
at
jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
ce.java:179)
at
jrun.deployment.DeployerService.run(DeployerService.java:891)
at jrunx.scheduler.SchedulerS07/13 22:23:33 user
FlexSwfServlet: init
ervice.invokeRunnable(SchedulerService.java:223)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
PLEASE Help!!!
BernieFigured this one out:
Searched thru instance of JRun that flex was installed in and
removed all the additional commons-logging jar files I
found. -
How to configur log4j logging for weblogic 10.1
Hi,
I am tried to set log4j logging for my application running in weblogic 10.1. I set a log4j.properties file and loaded the properties by a servlet. Where its load the properties files and configure it by PropertyConfigurator.
The same logic has worked out in websphere. But in weblogic, it is not working. I set the server logging and domain logging to Log4j in Admin console. Now it is writing all the log statements.
If i write a property for a package to Error level and root level is Debug. Its not working, all debug statements are getting written.
Can you please tell me the steps to configure log4j logging in weblogic 10.1.
Thanks & Regards,
Nasrin.NDid you manage to get this working?
If yes ... what did you do?
I am having the same problem implementing commons-logging with log4j -
Hello,
I am trying to use castor beans in a back end java
application that I instantiate from within a cold fusion page using
the cfobject tag. Castor beans has a dependency on a newer version
of apache commons logging than is shipped with Cold Fusion. I found
the following knowledgebase article that describes the issue, but I
can't seem to get it to work. The first thing is that I don't have
a WEB-INF/cfusion/lib directory, and secondly, if I create it (to
put the thirdparty directory in it) then I can no longer access my
applications main web page (this page is a simple cfm file with no
java calls or anything). Any help is appreciated.
knowledge base article:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=98b79ee8
thanks.after looking into this further it appears that the solution
outlined in the knowledgebase article is geared toward the
multi-server configuration rather than in the self contained
configuration. Since I have ColdFusion Standard edition, it isn't
an option for me to use the multi-server configuration. Does anyone
know how to accomplish the same thing in Cold Fusion MX7 Standard
Edition?
thanks. -
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. -
Hi DBAs,
I have 2 Archive destination. My archive log format is ARC%S_%R.%T
But In my 1 location E:\app\Administrator\product\11.1.0\db_1\RDBMS format shows ARC00025_0769191639.001
2 location shows E:\app\Administrator\flash_recovery_area\BASKAR\ARCHIVELOG\2011_12_08\O1_MF_1_25_7G15PVYX_.ARC
SQL> select destination from v$archive_dest;
DESTINATION
E:\app\Administrator\product\11.1.0\db_1\RDBMS
USE_DB_RECOVERY_FILE_DEST
My Question is that, I am using this format only ARC%S_%R.%T
but it shows different format in each location. May i know what 's the reason behind this?
Thanks in AdvanceIf you are using other archive destination other than FRA it will creates as per LOG_ARCHIVE_FORMAT,
and the FRA configured then the archive format for FRA is O1_MF_1_25_7G15PVYX_.ARC
from your query it is clear that there are two destinations are configured, So if you dont want *.ARC* files, you have to disable FRA.
But recommended to use FRA easy to manage. -
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 -
Commons-logging Error when starting JRun with Flex
Created new JRun Server and deployed Flex2 to this server.
Receiving this error when starting up this server instance.
Starting Macromedia JRun 4.0 (Build 92909), logicerm2 server
07/13 22:23:28 info JRun Naming Service listening on *:2911
07/13 22:23:28 warning No sessionSecret has been specified in
jrun.xml. Installi
ng a self generated sessionSecret.
07/13 22:23:28 info No JDBC data sources have been configured
for this server (s
ee jrun-resources.xml)
07/13 22:23:28 info JRun Web Server listening on *:8102
07/13 22:23:28 info Deploying enterprise application
"default-ear" from: file:/C
:/JRun4/servers/logicerm2/default-ear/
07/13 22:23:28 info Deploying web application "JRun Default
Web Application" fro
m: file:/C:/JRun4/servers/logicerm2/default-ear/
07/13 22:23:29 info Web Services in default-ear#default-war:
07/13 22:23:29 info AdminService
07/13 22:23:29 warning default-war web application has
'reload' as true in jrun-
web.xml. Consider setting it false if the application is
running in production e
nvironment.
07/13 22:23:29 warning default-war web application has
'compile' as true in jrun
-web.xml. Consider setting it false if the application is
running in production
environment.
07/13 22:23:29 user JSPServlet: init
07/13 22:23:29 info Deploying web application "Flex Data
Services" from: file:/C
:/JRun4/servers/logicerm2/flex/
07/13 22:23:29 user JSPServlet: init
07/13 22:23:29 user FlexMxmlServlet: init
07/13 22:23:29 INFO Loading configuration file
C:\JRun4\servers\logicerm2\flex\W
EB-INF\flex\flex-webtier-config.xml
07/13 22:23:30 INFO Loading configuration file
C:\JRun4\servers\logicerm2\flex\W
EB-INF\flex\flex-config.xml
07/13 22:23:30 user FlexMxmlServlet: Starting Adobe Flex Web
Tier Compiler
07/13 22:23:30 user FlexMxmlServlet: Adobe Flex Web Tier
Compiler Build: 143451
07/13 22:23:30 user MessageBrokerServlet: init
07/13 22:23:31 user FlexSwfServlet: init
07/13 22:23:31 user FlexInternalServlet: init
07/13 22:23:31 info Deploying web application "Flex Admin Web
Application" from:
file:/C:/JRun4/servers/logicerm2/flex-admin/
07/13 22:23:31 user JSPServlet: init
07/13 22:23:31 user MessageBrokerServlet: init
07/13 22:23:31 info Deploying web application "Flex Data
Services Samples" from:
file:/C:/JRun4/servers/logicerm2/samples/
07/13 22:23:31 user JSPServlet: init
07/13 22:23:31 user FlexMxmlServlet: init
07/13 22:23:32 INFO Loading configuration file
C:\JRun4\servers\logicerm2\sample
s\WEB-INF\flex\flex-webtier-config.xml
07/13 22:23:32 INFO Loading configuration file
C:\JRun4\servers\logicerm2\sample
s\WEB-INF\flex\flex-config.xml
07/13 22:23:32 user FlexMxmlServlet: Starting Adobe Flex Web
Tier Compiler
07/13 22:23:32 user FlexMxmlServlet: Adobe Flex Web Tier
Compiler Build: 143451
07/13 22:23:32 user MessageBrokerServlet: init
07/13 22:23:32 error Could not pre-load servlet:
MessageBrokerServlet
[1]org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logg
ing.LogConfigurationException:
org.apache.commons.logging.LogConfigurationExcept
ion: Invalid class loader hierarchy. You have more than one
version of 'org.apa
che.commons.logging.Log' visible, which is not allowed.
(Caused by org.apache.co
mmons.logging.LogConfigurationException: Invalid class loader
hierarchy. You ha
ve more than one version of 'org.apache.commons.logging.Log'
visible, which is n
ot allowed.) (Caused by
org.apache.commons.logging.LogConfigurationException: or
g.apache.commons.logging.LogConfigurationException: Invalid
class loader hierarc
hy. You have more than one version of
'org.apache.commons.logging.Log' visible,
which is not allowed. (Caused by
org.apache.commons.logging.LogConfigurationExc
eption: Invalid class loader hierarchy. You have more than
one version of 'org.
apache.commons.logging.Log' visible, which is not allowed.))
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:543)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:235)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:209)
at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at
org.apache.commons.httpclient.params.DefaultHttpParams.<clinit>(Defau
ltHttpParams.java:53)
at
flex.messaging.services.http.HTTPProxyAdapter.<init>(HTTPProxyAdapter
.java:111)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Sou
rce)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
flex.messaging.util.ClassUtil.createDefaultInstance(ClassUtil.java:71
at
flex.messaging.Destination.createAdapter(Destination.java:277)
at
flex.messaging.Destination.initDestination(Destination.java:103)
at
flex.messaging.services.HTTPProxyService.createDestination(HTTPProxyS
ervice.java:78)
at
flex.messaging.services.AbstractService.createDestinations(AbstractSe
rvice.java:82)
at
flex.messaging.config.MessagingConfiguration.createServices(Messaging
Configuration.java:187)
at
flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
gConfiguration.java:84)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
5)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
java:1242)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
ice.java:789)
at
jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
va:291)
at
jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
ce.java:242)
at
jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
ce.java:179)
at
jrun.deployment.DeployerService.run(DeployerService.java:891)
at
jrunx.scheduler.SchedulerService.invokeRunnable(SchedulerService.java
:223)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
Caused by:
org.apache.commons.logging.LogConfigurationException:
org.apache.comm
ons.logging.LogConfigurationException: Invalid class loader
hierarchy. You have
more than one version of 'org.apache.commons.logging.Log'
visible, which is not
allowed. (Caused by
org.apache.commons.logging.LogConfigurationException: Inval
id class loader hierarchy. You have more than one version of
'org.apache.common
s.logging.Log' visible, which is not allowed.)
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:397)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:529)
... 30 more
Caused by:
org.apache.commons.logging.LogConfigurationException: Invalid class
l
oader hierarchy. You have more than one version of
'org.apache.commons.logging.
Log' visible, which is not allowed.
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:385)
... 31 more
[0]flex.messaging.config.ConfigurationException: Unable to
create service 'flex.
messaging.services.HTTPProxyService' for 'proxy-service' due
to the following er
ror: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.lo
gging.LogConfigurationException: Invalid class loader
hierarchy. You have more
than one version of 'org.apache.commons.logging.Log' visible,
which is not allow
ed. (Caused by
org.apache.commons.logging.LogConfigurationException: Invalid cla
ss loader hierarchy. You have more than one version of
'org.apache.commons.logg
ing.Log' visible, which is not allowed.) (Caused by
org.apache.commons.logging.L
ogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
Invalid class loader hierarchy. You have more than one
version of 'org.apache.c
ommons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commons
.logging.LogConfigurationException: Invalid class loader
hierarchy. You have mo
re than one version of 'org.apache.commons.logging.Log'
visible, which is not al
lowed.)).
at
flex.messaging.config.MessagingConfiguration.createServices(Messaging
Configuration.java:202)
at
flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
gConfiguration.java:84)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
5)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
java:1242)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
ice.java:789)
at
jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
va:291)
at
jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
ce.java:242)
at
jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
ce.java:179)
at
jrun.deployment.DeployerService.run(DeployerService.java:891)
at jrunx.scheduler.SchedulerS07/13 22:23:33 user
FlexSwfServlet: init
ervice.invokeRunnable(SchedulerService.java:223)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
PLEASE Help!!!
BernieThis can happen if you have the default-ear that JRun creates
and you install the /samples files for Flex Data Services installed
together.
The problem is with the commons-logging.jar. If you copy the
commons-logging.properties file from the
samples\WEB-INF\flex\jars\commons-logging.properties directory to
the samples\WEB-INF\classes\commons-logging.properties directory,
it will resolve the problem.
This is listed as Adobe FDS bug: 179227 -
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 -
I am trying to use apache commons logging in wls 9.2 as described in the documentation, ref
http://edocs.bea.com/wls/docs92/logging/config_logs.html#wp1015132
However, I get the following stacktrace
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)
Does anybody know the reason of this unexpected behavior?
/PeterOne small problem - Commons-Logging isn't listed under the available libraries. I looked through the entire list for anything that mightly remotely similar but found nothing. I thought that the commons-logging library was available as part of the struts library. Do I need to set it up as a user defined library?
Thanks for your input.
Chris -
Integration of Commons Logging framework with Weblogic
Hi,
We are trying to use Apache commons logging framework and trying to publish log mesages in Weblogic so that messages can be seen through console and all the Logging configurations can be managed from Admin console. I tried using the below steps:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/logging/config_logs.html#using_commons
But these does not seems to be working for User defined handlers. I am able to see the logs in the default odl-handler file but not able to log the messages through the handlers defined by me.
Can anyone help me on this.
Regards,
AnujHi,
We are able to see reports through Workspace. We are facing problem after
integrating Hyperion Interactive Reporting with Weblogic Portal. we are able to see the sections like Query,Report,Results but we are not able to see the content after selecting any one of the section mentioned above.
System Configuration:
Hyperion Interactive Reporting 9.3.1
App Server: Weblogic server 9.2
Web Server: Apache 2.0.52
Database: Oracle 9.0.1.
Operating System: Windows 2003 with SP1
Browser: I.E 6.0
With Workspace everything is working fine. After Integration we are facing problem.
Regards,
S.Suresh.
Maybe you are looking for
-
I have a C309a All in One, how do I use the CD/DVD component to print on a CD?
PRODUCT/SYSTEM: C309a All in One Printer; Windows 7 64-bit;
-
Best practice question re. importing and scratch drive
Hello: Will be editing .mov files primarily (Panasonic TM900 files wrapped as ProRes 422HQ - via ClipWrap). I'm using an external scratch drive. Questions: 1. is it best to "copy" the files to the project as is the default check mark or uncheck and
-
How come my mini ipad retina does not have sound suddenly ?
After I updated my mini ipad 2 to iOS.7, the sound in my ipad suddenly was not functioning!
-
Re: Portege A600-13Y: BIOS update 1.50 to 2.00-WIN - How risky it is?
Hi there, My Portege A600-13Y BIOS is version 1.50: - should I upgrade to 2.00WIN? - I found this source for the biso upgrade 2.0 but there is no indication that this file is authentic TOSHIBA bios. No checksums, no ssl certificate, nothing. Is it po
-
3rd party install Vista over XP, Return to factory default?
3rd party installed Vista over XP on a T60. Is there a way to return to factory default through ThinkVantage? Tried holding down ThinkVantage button at startup, but only gets me into Bios, no thinkvantage software. Ideas?