Db2diag.log Severe msg db2fmp, common communication sqlccipcdarihandshake

I am new to SAP and DB2 as a Netweaver Administrator of a new project.  We do not have anyone who has experience on the following messages on the db2dialog.log.
Is is normal to see lots of the following messages during a DB2 offline backup on the ECC server?
2006-11-18-22.00.49.xxxxxx-480 I457336A288        LEVEL: Severe
PID     : xxxxxx               TID  : 1           PROC : db2fmp (idle) 0
INSTANCE: db2dss               NODE : 000
FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3
RETCODE : ZRC=0x83000024=-2097151964
There is a warning message before these messages:
2006-11-18-22.00.49.422496-480 I456932A403        LEVEL: Warning
PID     : 421914               TID  : 1           PROC : db2sysc 0
INSTANCE: db2dss               NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE270 : 0000 0000
Thanks a lot.                                 ....

Hi,
I assume you have scheduled the offline backup in the SAP system.
Because the application servers are connected permanently to the database offline backups cannot be done without forcing of all connected appliations. On SAP systems this is achived by a db2stop force call before performing the offline backup.
The call to db2stop force is the reason for the errors and warnings you see during an offline backup of a SAP system.
As an alternative to offline backups you should evaluate the usage of online backup or online backups include log files.
Best regards, Jens

Similar Messages

  • Error Database DB2 (db2diag.log)

    Hi, I nedd help.
    The log db2diag.log show message error, and database colapse every 48 hours.
    2011-08-01-08.59.46.316326-300 I30710990A559      LEVEL: Warning
    PID     : 14564                TID  : 427         PROC : db2sysc 0
    INSTANCE: db2epd               NODE : 000         DB   : EPD
    APPHDL  : 0-94                 APPID: 10.20.0.61.53713.110801135412
    AUTHID  : SAPEPDDB
    EDUID   : 427                  EDUNAME: db2agent (EPD) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgWaitForLrecBufferLimit, probe:410
    MESSAGE : ZRC=0x870F0151=-2029059759=SQLO_WP_TERM
              "The waitpost area has been terminated"
    DATA #1 : String, 10 bytes
    Ignore rc.
    please help.

    Hi I would like to have more informations. In db2diag, do you  have any LEVEL : Error or Severe messages ?.  The log you put is a warning
    thanks

  • Configuration of logging severity

    Hello everyone,
    I am trying to use the weblogic Admin console to modify the logging severity at runtime. I have an application deployed on the AdminServer.
    In the web console, I go to the AdminServer Settings page and navigate to the Logging tab. I click the "Advanced" link to show the "Logger severity properties". In this box I have tried entering many different values. I save. There is no change to the logs. I restart the server, there is still no change to the logs.
    Some values I've attempted to use:
    com.mycompany.level=Trace
    com.mycompany.level=Debug
    com.mycompany=Trace
    com.mycompany=Debug
    .level=Trace
    .level=Debug
    I am using weblogic 10.3.2.0 with jdk logging.
    Does anyone know if these configuration changes are supposed to affect the log files? Am I using this configuration parameter incorrectly?
    Note that I have found a way to configure the logging severity using a logging.properties file, by calling:
    LogManager.getLogManager().readConfiguration(EventDAOEJBImpl.class.getResourceAsStream("/logging.properties"));
    However, this does not allow me to configure the application from the weblogic console. Is there a way to configure the logging severity using the weblogic console?

    You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.
    I asked them to reply to this message.

  • I get an error message when trying to email photos. It says "The email server didn't recognize your username/password combination." Yet I have reset my password and was able to log in to this Support Community. Can anybody help me?

    I get an error message when trying to email photos. It says "The email server didn't recognize your username/password combination." Yet I have reset my password and was able to log in to this Support Community. Can anybody help me?

    See my answer to your previous duplicate question. What happened when you tried my answers?
    LN

  • Common communication channel

    Hi ,
    We have a scenerio which will be rollout to different countries.
    In most of the cases common communication channel can used We are using different Bussiness System for all countries, now creating channel all roulout under different BS will incerese unnecessary objects.
    Is there any way we can define common channel , which can be used in different BS.If  anyone aware of  any kind  approach , please share.
    Regards,
    Vikrant

    If there are multiple scenarios connecting to the same Business System (or Service), then it is recommended to use a common channel....however since you have different Business System you will have to define CC for those Systems as the data mentioned in the channels will be different.
    Suppose you are sending IDOCs to the SAP systems, then the end-system details will be different for the systems involved and hence you have to maintain different channels.
    Regards,
    Abhishek.

  • Fast growing db2diag.log (FP4 V9.5)

    Does anyone have experiences with V9.5 FP4SAP?
    We have implemented this FP4 last week (from FP2a). Since this a db2diag.log of about 1MB were written (and the system usage is really low).
    We have another system on FP2a which is used heavier (as a productive system) and the db2diag.log is about 2,5 MB within two months.
    We have checked SAP note 1086130 for DB parameters and did not find a required change (from FP2a to FP4).
    Any idea is welcome!
    Best regards.

    db2diag.log extract 2009-08-02 23:00-23:59
    2009-08-02-23.24.20.577179+120 I1019336A362       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0001678.LOG.
    2009-08-02-23.24.21.914535+120 I1019699A422       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0001678.LOG to TSM chain 0 from
              /db2/MES/log_dir/NODE0000/.
    2009-08-02-23.28.53.621596+120 I1020122A483       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Locklist" From: "3712" <automatic>  To: "3552" <automatic>
    2009-08-02-23.28.53.627724+120 I1020606A545       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, access plan manager, sqlra_resize_pckcache, probe:150
    CHANGE  : APM : Package Cache : FROM "5208760" : TO "4191641" : success
    IMPACT  : None
    DATA #1 : String, 29 bytes
    Package Cache Resized (bytes)
    2009-08-02-23.28.53.629400+120 I1021152A485       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Pckcachesz" From: "1311" <automatic>  To: "1055" <automatic>
    2009-08-02-23.28.54.510395+120 I1021638A507       LEVEL: Info
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90
    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "19552" <automatic> To:
              "15648" <automatic>
    2009-08-02-23.29.24.543188+120 I1022146A494       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Database_memory" From: "205060" <automatic>  To: "185520" <automatic>
    2009-08-02-23.29.54.555357+120 I1022641A483       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Locklist" From: "3552" <automatic>  To: "3392" <automatic>
    2009-08-02-23.29.54.559234+120 I1023125A545       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, access plan manager, sqlra_resize_pckcache, probe:150
    CHANGE  : APM : Package Cache : FROM "4191641" : TO "3937361" : success
    IMPACT  : None
    DATA #1 : String, 29 bytes
    Package Cache Resized (bytes)
    2009-08-02-23.29.54.560050+120 I1023671A484       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Pckcachesz" From: "1055" <automatic>  To: "991" <automatic>
    2009-08-02-23.29.55.097984+120 I1024156A507       LEVEL: Info
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90
    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "15648" <automatic> To:
              "13914" <automatic>
    2009-08-02-23.30.25.137828+120 I1024664A494       LEVEL: Event
    PID     : 602270               TID  : 3342        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000         DB   : MES
    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318
    AUTHID  : MESADM 
    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB MES: "Database_memory" From: "185520" <automatic>  To: "176480" <automatic>
    2009-08-02-23.41.12.098793+120 I1025159A362       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0001679.LOG.
    2009-08-02-23.41.13.334331+120 I1025522A422       LEVEL: Warning
    PID     : 602270               TID  : 4114        PROC : db2sysc 0
    INSTANCE: db2mes               NODE : 000
    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0001679.LOG to TSM chain 0 from
              /db2/MES/log_dir/NODE0000/.

  • Set logging severity level for clustered servers

    How can I set the logging severity level for clustered servers just once at the cluster level rather than one at a time at the server level?

    I know the logging is server by server, but surely there is a way to configure the multiple servers with one change rather than one by one. We have 40 some servers in the cluster.

  • Automatic archiving of db2diag.log

    Good Morning everyone,
    I have a question regarding the db2diag.log. After a couple of month this logfile could increase dramatically. In order to make root cause analysis easier I would like to archive the file every month and clean it up to get a better overview in it.
    Is there a possibility do to this via DB2 (Alertlog archiving) or should I realize this with a planned Batchjob every month.
    Greetings
    Marco

    Hello Marco,
    You can archive the db2diag.log using the db2diag tool. You can specify the -A or -archive <dirname> option:
    http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0011728.html
    -A | -archive dirName
    Archives a diagnostic log file. When this option is specified, all other options are ignored. If one or more file names are specified, each file is processed individually. A timestamp, in the format YYYY-MM-DD-hh.mm.ss, is appended to the file name.
    You can specify the name of the file and directory where it is to be archived. If the directory is not specified, the file is archived in the directory where the file is located and the directory name is extracted from the file name.
    If you specify a directory but no file name, the current directory is searched for the db2diag.log file. If found, the file will be archived in the specified directory. If the file is not found, the directory specified by the DIAGPATH configuration parameter is searched for the db2diag.log file. If found, it is archived in the directory specified.
    If you do not specify a file or a directory, the current directory is searched for the db2diag.log file. If found, it is archived in the current directory. If the file is not found, the directory specified by the DIAGPATH configuration parameter is searched for the db2diag.log file. If found, it is archived in the directory specified by the DIAGPATH configuration parameter.
    Regards,
    Adam Wilson
    SAP development Support

  • Db2diag.log issue in DB2

    Hi All,
    We are repetitively getting severe error message in DB2  database. Please advise on this.
    2014-08-07-10.45.03.030954+060 I14065240A184      LEVEL: Severe
    PID:10944994 TID:74889 NODE:000 Title: **** DRDA CMNMGR CB ****
    Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
    2014-08-07-10.45.03.032407+060 I14065425A181      LEVEL: Severe
    PID:10944994 TID:74889 NODE:000 Title: **** DSS SEGMENT ****
    Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
    2014-08-07-10.45.03.033169+060 I14065607A184      LEVEL: Severe
    PID:10944994 TID:74889 NODE:000 Title: **** RECEIVE BUFFER ****
    Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
    2014-08-07-10.45.03.033957+060 I14065792A238      LEVEL: Severe
    PID:10944994 TID:74889 NODE:000 Title: **** SEND BUFFERS ****
    Dump File: /db2/fmp/db2dump/10944994.74889.000.dump.bin
    Dump with error: Error 65706 occurred. ( rc = 0x100aa )
    1833 Aug 07 07:04 db2locktimeout.0.3856.2014-08-07-07-04-58
    -rw-r--r--    1 db2fmp   dbfmpadm     250773 Aug 07 07:05 10944994.221612.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm    1733457 Aug 07 07:05 10944994.279501.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm     512284 Aug 07 07:10 10944994.189348.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm    1666934 Aug 07 07:15 10944994.251255.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm    1456576 Aug 07 07:15 10944994.220776.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm     716526 Aug 07 07:15 10944994.186209.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm     226391 Aug 07 07:20 10944994.202921.000.dump.bin
    -rw-r-----    1 db2fmp   dbfmpadm       1833 Aug 07 07:20 db2locktimeout.0.3856.2014-08-07-07-20-03
    -rw-r--r--    1 db2fmp   dbfmpadm     427893 Aug 07 07:20 10944994.258979.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm    1250050 Aug 07 07:30 10944994.234475.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm    1188238 Aug 07 07:30 10944994.90388.000.dump.bin
    -rw-r--r--    1 db2fmp   dbfmpadm    1274291 Aug 07 07:35 10944994.259795.000.dump.bin
    Regards,
    Raja

    Hi,
    Also getting below error message.
    2014-08-07-10.55.01.768463+060 I14131030A1270     LEVEL: Severe
    PID     : 10944994             TID  : 186209      PROC : db2sysc 0
    INSTANCE: db2fcp               NODE : 000
    APPHDL  : 0-51945
    EDUID   : 186209               EDUNAME: db2agent (idle) 0
    FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
    MESSAGE : ZRC=0x81360010=-2127167472=SQLZ_RC_CMPARM, SQLT_SQLJC
              "CM parameter bad"
    DATA #1 : String, 11 bytes
    CCI Error:
    DATA #2 : unsigned integer, 8 bytes
    68
    CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
      [0] 0x090000000D21AFB0 pdLog + 0xE0
      [1] 0x090000000B9AA2DC sqljcLogCCIError__FP10sqljCmnMgrPCcP12SQLCC_COND_TUclN35 + 0x234
      [2] 0x090000000B9AB5AC sqljcLogCCIError__FP10sqljCmnMgrPCcP12SQLCC_COND_TUclN35@glueDAC + 0x78
      [3] 0x090000000A594B84 sqljcReceive__FP10sqljCmnMgr + 0x278
      [4] 0x090000000D2D859C @63@sqljsRecv__FP8sqeAgentP13sqljsDrdaAsCb + 0x100
      [5] 0x090000000D2D8370 @63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x254
      [6] 0x090000000D2D7E60 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0xEC
      [7] 0x090000000D2540B0 RunEDU__8sqeAgentFv + 0x2F4
      [8] 0x090000000D2502EC EDUDriver__9sqzEDUObjFv + 0xE4
      [9] 0x090000000D25C4B0 sqloEDUEntry + 0x260
    Rgards,
    Raj

  • System Log Error Msgs

    Hi
    How to check System Log for error messages in BI 7.0

    Hi,
    T-code to see system logs is : SM21.
    Go through following links which are helpful.
    http://help.sap.com/saphelp_nw04s/helpdata/en/c7/69bcbaf36611d3a6510000e835363f/frameset.htm
    /thread/321122 [original link is broken]
    Thanks and Regards,
    Ramki.

  • FTP communication channel generating logs in NWA Logs and Traces

    Dear all
    Wishihg you all a very happy new year. I have a peculiar issue, where I am using a FTP adapter, and files are deposited in an FTP location. This processing is runnign succesfully. However, my NWA logs says that there is communication issues while putting htis file in the server.
    Whenever there is a transaction happening this error gets generated in NWA log.
    Does any one have any idea why this is happening.
    Many thanks & Regards : Bobby Bal
    Below mentioned is the error message.
    Message:   Error during disconnect from ftp server ediftp-pw09.colpal.com, ignored: com.sap.aii.adapter.file.ftp.FTPEx: 421 Unexpected reply codeTerminating connection.
    Severity:   Error
    Date:   2012-01-10
    Time:   09:18:12:191
    Category:   /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File
    Location:   com.sap.aii.adapter.file.File2XI.disconnectFTPServer
    Application:   
    Thread:   XI File2XI[XXX_WMS_SENDER_CC/SYS321/XX_ChinaWMS]_34877
    Data Source:   j2ee/cluster/server1/log/applications_01.log
    Arguments:   
    Passport User Activity ID:   7f0f0ddd38fd11e1b099c68806a4be02
    Message ID:   com.sap.SOA.apt_file.0058
    Session:   0
    Transaction:   
    User:   J2EE_GUEST
    Time Zone:   0-500
    Customer Message Component:   BC-XI-CON-AFW
    Runtime Component:   com.sap.aii.af.lib
    Correlation ID:   144518351000001784
    Passport Session:   7F0F0DDD38FD11E1B099C68806A4BE02
    Passport Connection:   7f0f0ddd38fd11e1b099c68806a4be02
    Passport Connection Counter:   0
    Log ID:   C000A7E404320DFE00000000013600A4
    Host:   xppapp14
    System:   XPP
    Instance:   DVEBMGS14
    Node:   server1

    Hi Bobby,
    1. Check whether the user you are using has access control i.e Read/Write Access from the folder in FTP server..
    2. Check it at OS level by directly pasting or pick the files..
    3. From SAP end check the user credientials provided in the file adapter i.e username of the FTP server and the Password of the FTP server it is case-sensitive.
    4. Try to give the exact path from where the file is to be picked and reactivate the scenario.
    5. what is the file size of the file that is going to be picked from the ftp server.
    6. Then finally check in Communication channel monitoring detailed log what is the error it was coming and check the log in XI server you can clearly notice the error.
    Even some times it will access at OS level but not through the server for this reactivate the adapter and provdie the user credentials and the path once again..
    Regards,
    Ravi

  • How to prevent java.util.logging from displaying pop-up dialog on SEVERE?

    Hi,
    I'm new to using java.util.logging. I notice that whenever I try to make a call to logger.SEVERE(msg) or logger.WARNING(msg), not only does it write the output to file (which I want), but it also pops up a dialog box displaying the exception. I don't want this pop up to appear. How do I prevent the logger from doing this?

    What are you talking about?
    Hello,
    In order to better assist you with your issue please provide us with a screenshot. If you need help to create a screenshot, please see [[How do I create a screenshot of my problem?]]
    Once you've done this, attach the saved screenshot file to your forum post by clicking the '''Browse...''' button below the ''Post your reply'' box. This will help us to visualize the problem.
    Thank you!

  • Utilize Apache Commons Logging and Log4J

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

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

  • Common log file name for ESB

    What is the log file name which is logging all the informations of ESB?

    There are several
    The most common ones are :
    $OH$\soa\j2ee\home\log\home_default_group_1\oc4j\log.xml
    and
    $OH$\soa\bpel\domains\default\logs\domain.log

  • Commons Logging with embeded OC4J

    Hey people,
    I suppose this is a basic question, but haven't been able to figure it out yet. We have a BC4j/Struts web application built with Jdevloper 10.1.2.0.0. My query is with regards to the logging. Logging is performed by commons-logging. When I deploy my application to the server in production with an ear and run it, all seems well. However, when I run the application directly from Jdeveloper (that would be the embedded OC4j?), I'm unable to enable the logger. Here's a sample bit of code I use:
    (class declaration)
    private static Log log = LogFactory.getLog(EmpSearchAction.class);
    (sample code)
    if (log.isInfoEnabled()) {
    LogInfo message = new LogInfo(profile.getLogId(),
    LogConstants.ACCESS_OPR,
    LogConstants.WEBURL_TYPE, "" , "",
    "empsearch.do",
    profile.getLoginPrefix());
    log.info(message);
    I wanted to know if I run my web app directly from Jdeveloper without the ear, how would I have the Log enabled, I.e currently with existing settings when I debug in Jdeveloper it never enters the if loop I.e log isInfo is always disabled. Could anyone be kind enough to let this ignorant one what config needs to be tweaked to get this to start working when running directly from Jdeveloper.
    help much appreciated.

    hello,
    Common loggings uses a properties file to read what should be logged and what not.
    This file is named:
    commons-logging.propertiesI believe the file the internal OC4J uses is in:
    $JDEV_HOME$\jdk\jre\libthis will have a line like this:
    .level= SEVEREThis is the root level, meaning nothing below severe will be logged anywhere, which for you should be set to INFO or ALL I guess.
    Now you need to set which gets logged to the console and what not, by default this should be on INFO which is good enough I presume.
    java.util.logging.ConsoleHandler.level = INFOHope this helps,
    -Anton

Maybe you are looking for

  • Hi does anyone know how i can copy my videos from Google   to my iMac desktop so I can burn them to a dvd?

    Hi, I am trying to figure out if I can "rip" my videos from Google+ and then save and brun them to a dvd can anyone help me please? Thanks

  • Windows doesn´t recognize ipod error 1415

    iPod prior Mac recognized now intended for Windows can´t be updated, it shows error 1415, When I connect this windows xp Averatec shows there is a new device, but then it fails to recognize it. some help please, Thank you

  • Require coding for purchase requisation outstanding aging report

    Hi Gurus,                 I got a requirment to develop  purchase requisation outstanding aging report.Please provide me the coding for purchase requisation outstanding aging report. Points will be rewarded  for every reply. Regards , Sonali.

  • The grey bar on safari?

    sometimes when i open a new safari page on the very bottom of it there is a grey bar that tells me the url or the name of the site when my mouse is over a link or clickable item.. it usually isnt there and my question is how do i get it to stay there

  • OutOfMemory Exception. Please Help!

    Hi, We are deploying our application on Oracle10g AS , version 10.1.3. Very frequently we get OutOfMemory error even for a single user. We are using the default settings for Java Options. Please suggest a solution ASAP. Regards, Subhashini