BDocs stay yellow - status I02 Written to qRFC Queue (intermediate state)

We upgraded our system from SAP CRM 7.0 EHP3 SP3 to SP4.
Now all the BDocs in smw01 stay yellow. I can manually reprocess them, then they become green. There is no error message and there are no dumps in st22.
The CSA* queues are registered. The scheduler says "inactive" (and briefly goes to active when saving a business partner, product or transaction, as it should).
The CSA* queues relevant for each "stuck" business partner, transaction or product is in status "STOP".
There's a note, 1593693 - BDoc's in state I02, but it doesn't help. We don't have a problem with the number or load of the RFC processes (as far as I can tell), there is very little going on on the system, right now I am the only one logged on) and the queues are not in status READY, either.
MW_CHECK says "All post-processing steps are done."
GENSTATUS counts 0 errors or waiting.
MW_MODE is on, of course.
smw3_00 is empty (which it was before the SP installation, too).
The CRM is not connected to an ERP system, it sends búsiness partner and transactional data via the XIF adapter (via web services). Which, up to now, worked just fine.

I was given the solution: Use transaction smq2, search for CSA*, click on the queue, click the unlock button. That worked.

Similar Messages

  • BUPA_MAIN stays in Intermediate state Function Module missing

    We noticed that on our Productive system, since yesterday most
    of the BUPA_MAIN BDOCs status are in yellow "After qRFC step (intermediate
    state)" since last two days on PRM. Before it was working fine.
    We got o SMW01 & re-process it, then we get a short dump which says:
    " Function module "/1CRMGC/CGBUPA_MAIN_RRR" not found."
    We compared in th eTxn: SBDM the BUPA_MAIN on Production & Test systems.
    We found that the Module "/1CRMGC/CGBUPA_MAIN_RRR" is not there in Production but it
    is there on other systems where its working.
    Please let us know how we can generate this,
    Is it the normal process to Generate on the dsired system in our case production directly? or do we do it in Development & then Transport it.
    We have this bug in Production and fix this asap.
    Thanks
    Regards
    Rahul
    Edited by: Rahul Kumar Lal on Sep 2, 2010 1:50 PM

    Hi Rahul,
    Goto Trxn. GNRWB -
    Generator Group : REPLI
    Industry : Consumer Goods
    Select BUPA_MAIN on L.H.S. and all Generators on the R.H.S.
    Click on Generate/Check icons.
    or you can goto trxn . SMOGGEN and select BUPA_MAIN.
    Tnx,
    Rohit

  • BDOC Error : "BDoc stored before update task (intermediate state)"

    Hi Experts,
    I have stuck BDOCs under BDOC type "BUS_TRANS_MSG" and the error msg as "BDoc stored before update task (intermediate state)". The error occurs when BDoc Message was not written to qRFC queue. I checked the update tasks in transaction
    SM13 and could find the entries there. I opened one of the entry and was able to spot the error in one of the function module.
    The error was encountered at some later point in time and is been fixed. I now want to re-send the update so that the new update is written and the BDOCs are processed.
    Kindly guide me through the steps that need to be performed in order to re-process the BDOCS.
    Thanks,
    Chaudh

    Hi,
    BDocs were stuck at time when we really had a problem; now the problem is re-solved. I have checked SM13 we have entries highlighting the problem, but i really don't know how to re-update the error entries in SM13.
    I believe once that is done then i might possibly be able to re-process the BDOCs in SMW01.
    Thanks,
    Chaudh

  • In the MMC, the dispatcher stays yellow, with the status

    Hi all,
    In My Solution Manager system, In the MMC, the dispatcher stays yellow, with the status 'Dialog Queue Info unavailable'.
    However, the system continues to run. Can you please help on this.
    Thanks
    suman

    Hi,
    for this problem, check SAP note 396309 and 72248.
    Thanks
    Sunny

  • BDOC BUS_TRANS_MSG is in yellow status.

    Hi all,
    When I am creating a sales order in CRM system the order is getting replicated in R/3 system but the BDOC is still in Yellow status.
    When I am trying to use the TA /nVA02 and give the order number it is giving the error message "Sales document XXXXXXX is currently being processed (by user RFCUSER)".
    When I am reprocessing the BDOC it is giving the error "Inconsistent update flags" which is technically correct and the status is in Green.
    Can some one pls help me why the BDOC is not completly process in the first time itself. Why R/3 is not sending confirmation to the CRM system.
    Thanks in advance.
    Best regards,
    Vikash.

    Hi Michael,
    Thanks for your reply. I checked all three points mentioned by you.
    - There is no entry in transaction SM12 (lockings) on the R/3 side.
    - There is nothing in the inbound/outbound queues on CRM or on R/3.
    - There is no dumps in transaction ST22 (CRM or R/3).
    Still the BDOCs are in yellow status. Kindly suggest how to resolve this issue.
    Best regards,
    Vikash.

  • Request Status stays yellow after successful load

    We recently started loading two infocubes from the same data source. 
    - The Monitor shows that the load completed normally with no errors. 
    - Manage on the first cube shows that the status is green and the data available for reporting. 
    - Manage on the second cube shows the data is not avaialble and the status is yellow. 
    There seems to be no problems with the load. I can manualy force the status from yellow to green and the data is available for reporting.  But I don't want to have to manully change the status after each load.  Any ideas on why the status stays yellow?  Any thoughts on what I can do?
    Thanks,
    Chris

    Nagesh,
    Looks like your suggestion will solve this.  It was not checked for the one that was staying yellow.  It was checked for the cube that would go to green.  I'll run a test then come back and award points.
    Thanks,
    Chris

  • Request Status Stay Yellow

    Hi Expets,
    I am using load 0HR_PT_2.
    Because the load gets warning in the source system the request stay in status yellow
    (HR say all the data is good)
    In the Details tab of the monitor under Extraction i see the warning
    "warnings have appeared when extracting data" (message R3 401)
    And i have to change it to green every morning (because all the data is in received in to the BW)
    how can ignore the warnings or chagne it to green automaticly?
    Or what else can i do?
    Thanks and BR,
    Or.

    Hi,
    In the DTP on the extraction tab you can set the DTP extraction mode to ignore warning and make the request status as green. Once you do this setting your request will become green automatically.
    But I don't know if there is any similar setting in BI 3.5.
    Regards,
    Durgesh.

  • BI PSA stays on status Yellow

    Hi Experts
    We are trying to integrate BW and XI. We can successfully send the data from Oracle to BW via XI.  A webservice type of data source is used in BW and the problem we are having now is that once the data is sent, the PSA (corresponding to the Info Package with webservice data source) does not close. (It stays yellow).  This results in a repeat of the send data process appending data to the same PSA, i..e if I have 10 records in Oracle, I end up with 20, 30 or even 7000 (which is our case) on the BW info Package because the PSA is still open, i.e. data is appended and not Delta Uploaded.
    Put simple, how do you close a PSA belonging to an info Package of a data source of type Web service?  (I have specified 1 hour), but this is not working.
    Thanks for the help.
    Kind Regards
    Ronny

    Hi,
    in the monitor is all the data processed successfully? I mean all datapackets have been updated in your IObj right?
    if yes then you can set the QM status to green manually.
    However the issue still remains; I could think of a warning coming from the source system datasource in conjunction with your settings of "evaluation of requests" :in the monitor / menu settings / evaluation of requests / if warning arise during processing....  you have to set the status to successful...
    Can't you use 0ART_PLANT_* datasources instead of 0MAT_PLANT; indeed 0ART datasources have replaced 0MAT* sources some time ago and they're more reliable...
    hope this helps...
    Olivier.
    Message was edited by:
            Olivier Cora

  • My BDOCs(transaction smw01) are all waiting with yellow status

    I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?

    Hi Kaushal,
    I am also facing the similar problem as Prakash, I don't know why my Bdocs are all waiting with yellow status in smw01.I followed your steps but in SMOHQUEUE the status of the queue demon is Hold because of this the status of Bdocs are yellow.If yes would you pls tell me the steps to turn it to green.If i manually do(Reprocess or register that queue in smqr) everything is working fine but is there any way we can turn Bdocs from yellow to green automatically.I appreciate it in advance. If you find any doc. pls fwd it to [email protected]
    Thanks a lot
    With Regards
    Nagamani.

  • My BDOCs in CRM are all waiting with yellow status

    I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?
    Message was edited by: Prakash  Singh

    hi Prakash,
    again oss note 692195-FAQ: Sales Analytics and CRM-BW data Extraction ?
    bwa5 and bwa7, delta is activated ?
    and initialization performed in bw ?
    626214 619122
    3. If there are queues in SMQ1 with erroneous status then activate
       these queues.
       In Transaction SMQ1 if there are Queues existing with
       names beginning with CRM_BWAn (n is number) then
       activate these queues in the same transaction.
    4.a)If required activate the datasource
        Go to transaction BWA5   > select the required datasource and
        activate.
    4 b) The Delta may not be active ,activate the delta in BWA7 by
      selecting the name of the datsource and pressing the candle icon for
      'activate delta'.
    Symptom
    There may be problems or issues related to data tranfer from CRM to BW.
    Other terms
    CRM-BW extraction,upload,initial,delta,full upload ,Sales Analytics,
    Reason and Prerequisites
    There could be errors in customization or program errors due to which
    data may not be transferred or incorrectly transferred to BW.
    Solution
    Question 1 : The Extraction from CRM to BW takes a very long time. What
    can be done? (Performance Issues)
    Question 2 : On executing transaction RSA3 I get records but I find 0
    records when I load data from BW request.(No Data Available).
    How can I extract data in this case?
    Question 3 : The Deltas for my data source are not extracted . What can
    I do?
    Question 4: How can I extract the fields, which are not provided in the
    standard  data source extraction ?
    Question 5: I am unable to extract  user status correctly.What should I
    do?
    Question 6 : What can I  do when the activity/Opportunity/Complaint
    reasons(Code,CodeGruppe,Katalogart)  are not extracted?
    Question 7: What can I do if the deleted opportunities
    are not reflected in BW?
    Question 8: How do I activate the metadata?
    Question 9: I donot get any records for the delta upload of my attribute
    datasource(s).What is to be done?
    Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0
    and various other BW status mean ?
    Solutions
    Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues)
    Suggestion 1: Please implement notes  653645 (Collective note) and
    639072(Parallel  Processing).
    The performance could be slow because of the wrong control parameters
    used for packaging.
    You can change the package size for the data extraction.
    Also note that changing the package size in the transaction SBIW
    would imply a change for all the extractors. Instead, you could
    follow the path in the bw system.
    Infopackage (scheduler)    > Menu 'Scheduler'   > 'DataS. default data
    transfer'   > maintain the value as 1500 or 1000(This value is variable)
    The package size depends on the Resources available at the customer side
    (The no of parallel processes that could be assigned =
    1.5 times the no of CPU's available approx.)
    Question 2 : On executing transaction RSA3 I get records but I find 0
    records when I load data from BW request.(No Data Available)
    Suggestion 2: First check if there are any entries in the table
    CRMD_ORDER_INDEX.Only if there are entries in this table you can
    extract records.
    If this is not the case then,
    It is possible that the user does not have sufficient
    authorities for extraction of  the relevant objects.
    Additionally, please review and implement the following notes
    615670
    161570
    150315
    618953
    If you are in the release 4.0 then
    To do BW extraction with the user please see that the following
    authorization object exists(display mode is enough):
    CRM_ACT, CRM_OPP, CRM_LEAD, CRM_SAO, CRM_SEO, CRM_CO_SE, CRM_CO_SC
    CRM_CO_SA, CRM_CON_SE, CRM_CMP, CRM_ORD_OP, CRM_ORD_LP, CRM_ORD_PR
    CRM_ORD_OE, CRM_CO_PU, CRM_CO_PD, CRM_ORD_PO
    (all these objects are linked to transaction crmd_order).
    Question 3 : The Deltas for my data source are not extracted . What can I do?
    Suggestion 3: Please check the following.
    Please Check if the services have been generated in transaction GNRWB.
    If they are not active(not marked 'X' before their names) then activate
    the services following the steps here.
    Go to transaction GNRWB
    Select BUS_TRANS_MSG
    Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
    Press Generate.
    Also check  for the following:
    1. The delta should have been initialized successfully.
    2. Confirm that all Bdocs of type BUS_TRANS_MSG
       are processed with success in SMW01.
    3. If there are queues in SMQ1 with erroneous status then activate
       these queues.
       In Transaction SMQ1 if there are Queues existing with
       names beginning with CRM_BWAn (n is number) then
       activate these queues in the same transaction.
    4.a)If required activate the datasource
        Go to transaction BWA5   > select the required datasource and
        activate.
    4 b) The Delta may not be active ,activate the delta in BWA7 by
      selecting the name of the datsource and pressing the candle icon for
      'activate delta'.
    5. In BW system
       Go to transaction RSA1   > modeling   > infosources   > select the
       infosource   > right mouse click on the selected
       infosource   > choose option replicate datasource
        Activate the infosource.
    6. Go to the scheduler for the infosource   > select delta  in the
        update  >choose the option PSA only (in the Processing tab)
        > start immediately
    Check the entry in the RSA7 in the OLTP(CRM system)
    Question 4: How can I extract the fields, which are not provided in the standard  data source extraction .
    Suggestion 4: Follow the steps mentioned below.
    1. Enhance Extract Structure with the required fields. (Create & include
       an append structure to the extract structure via transaction RSA6).
    2.a) Release the fields of the append  for usage. (  To do this, double
       click on the Datasource and remove the flags in the column 'Hide
       Field' for all fields of Append. )
    2.b)If the new fields cannot be seen in the extract structure of
        the transaction BWA1 then change and save the datasource, and then
        activate it in RSA6.
    3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields.
    Goto SPRO .
    Follow the path ->
    SAP Implementation guide ->Implementation with other mySAP components ->
    Data transfer to the Business Information Warehouse->
    Settings for the application specific datasources (CRM)->
    Settings for BW adapter->
    Badi :BW adapter :Enhancement of datasources in messaging flow.
    4. Replicate the new Datasource to BW.
    5. Expand the Communication Structure in BW.
    6. Maintain transfer Rules for the new Datasource.
    7. Activate the trasfer rules and perform the upload.
    Question 5:  I am unable to extract  user status correctly.What should I
    do?
    Suggestion 5 :Check the following notes
    531875
    616062
    713458
    700714
    765281
    Question 6 : What can I  do when the activity/Opportunity/Complaint
    reasons(Code,CodeGruppe,Katalogart)  are not extracted.
    Suggestion 6 :Check the following notes
    481686
    516820
    603609
    617411
    711146
    Question 7:Deleted opportunities are not reflected in BW.
    Suggestion 7: Check the note 706327.
    Question 8: How do you  activate the metadata?
    Suggestion 8:CRM BW adapter meta data has to be activated first before
    it is available in the system. You can use Transaction BWA5 to copy the
    meta data for selected DataSources. You can reach the transaction via
    the IMG maintenance 'SAP Reference IMG -> Settings for SAP Business
    Information Warehouse -> Activate BW Adapter Meta Data'. For more
    information, see the documentation on the IMG activity 'Activate BW
    Adapter Meta Data'.  (Note 432485)
    Question 9: I donot get any records for the delta upload of my attribute
    datasource(s).What is to be done?
    Suggestion 9: In case of attribute datasources, it is possible that the
    entry for the GUID is missing in the table SMOXAFLD.
    If , for example the datasource 0CRM_OPPT_ATTR is not giving deltas
    then you can follow the steps:
    1)If Delta process is active for the attribute datasource e.g.
         0CRM_OPPT_ATTR,  then stop the delta process in the BW
         system 
    2) In the CRM system, Make the entry in the table SMOXAFLD
       for the datasource with the Key
       as  0CRM_OPPT_ATTR     GUID 3) Save the entry.Activate the datasource                           4) Check that the above entry is replicated in smoxafld_s also    after this.               5) Create a transport request manually for the following    object             R3TR   SMO4   0CRM_OPPT_ATTR    
    Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ?
    Suggestion 10: The BW status are used to extract system and user defined
    status.
    The BW status are defined in the customization settings in SPRO.
    Check for-> Status Concept for BP/Product/CRM objects
    Here goto-> Process user status You will find the documentation attached here for the user status. Going inside the transaction you will find the status groups USS0, ZIOP,ZMOP etc. The names of the various BW status are derived from this For ex. BW + ST+ One + USS0 gives the name of the field BWSTONEUSS0 or BWST + ONE + ZMOP = BWSTONEZMOP (Master opportunity values) (which means BWST + (status group name) + status object group name) Double clicking on any of the object groups will take you to the values that these status can have . For ex. BWSTONEUSS0 in your system can have values E001 ,E002,E003,E007 which will be shown in RSA3 as BW status values 1,2,3,7, respectively.
    Similarly we have Goto -> Process system status (in SPRO). Here you can get the values for the system status in exactly the same way as BWSTONESYS0(Lifecycle status) , BWSTTECSYS2 (Error) etc. In RSA3 you get the names as BW status, To know which corresponds to which status here,Goto the record list in RSA3 . Here goto Settings - Layout -Current . Right click -> Press Show technical field names . You will be able to see the BW status names and will be able to adjust the layout accordingly.

  • J2EE Server stays in Yellow status saying "Starting Apps"

    Dear Experts,
    In our BI system, the J2EE server SERVER0 is not coming to running state. After I stop and start the sap instance of the BI system it remains in yellow status showing starting apps. I could not find any error message in dev_server0, std_server0.out and server.0.log, please find below log of dev_server0
    dev_server0
    trc file: "F:\usr\sap\B23\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID6587850
    pid         : 1384
    system name : B23
    system nr.  : 00
    started at  : Thu Sep 18 12:42:53 2008
    arguments       :
           arg[00] : F:\usr\sap\B23\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
           arg[02] : -DSAPINFO=B23_00_server
           arg[03] : pf=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=4600
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=B23
           arg[08] : -DSAPMYNAME=bidq001_B23_00
           arg[09] : -DSAPPROFILE=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 2412] Thu Sep 18 12:42:53 2008
    [Thr 2412] *** WARNING => INFO: Unknown property [instance.box.number=B23DVEBMGS00bidq001] [jstartxx.c   841]
    [Thr 2412] *** WARNING => INFO: Unknown property [instance.en.host=bidq001] [jstartxx.c   841]
    [Thr 2412] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2412] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : bidq001
    -> ms port    : 3901
    -> OS libs    : F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : bidq001
    -> ms port    : 3901
    -> os libs    : F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID6587800  : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID6587850  : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID6587800            : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID6587850            : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 2412] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 2412] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 2752] JLaunchRequestFunc: Thread 2752 started as listener thread for np messages.
    [Thr 4064] WaitSyncSemThread: Thread 4064 started as semaphore monitor thread.
    [Thr 2412] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 2412] CPIC (version=700.2006.09.13)
    [Thr 2412] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_16-x64
    [Thr 2412] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\B23\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID6587850]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_16-x64
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : F:\usr\sap\B23\DVEBMGS00\exe\jstartup.jar;F:\usr\sap\B23\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 2412] JLaunchISetDebugMode: set debug mode [no]
    [Thr 3380] JLaunchIStartFunc: Thread 3380 started as Java VM thread.
    [Thr 3380] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dsys.global.dir=F:\usr\sap\B23\SYS\global
    -> arg[ 24]: -Dapplication.home=F:\usr\sap\B23\DVEBMGS00\exe
    -> arg[ 25]: -Djava.class.path=F:\usr\sap\B23\DVEBMGS00\exe\jstartup.jar;F:\usr\sap\B23\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 26]: -Djava.library.path=C:\j2sdk1.4.2_16-x64\jre\bin\server;C:\j2sdk1.4.2_16-x64\jre\bin;C:\j2sdk1.4.2_16-x64\bin;F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs;D:\oracle\B23\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\j2sdk1.4.2_16-x64\bin;F:\usr\sap\B23\SYS\exe\uc\NTAMD64
    -> arg[ 27]: -Dmemory.manager=1024M
    -> arg[ 28]: -Xmx1024M
    -> arg[ 29]: -Xms1024M
    -> arg[ 30]: -DLoadBalanceRestricted=no
    -> arg[ 31]: -Djstartup.mode=JCONTROL
    -> arg[ 32]: -Djstartup.ownProcessId=1384
    -> arg[ 33]: -Djstartup.ownHardwareId=Z1382384873
    -> arg[ 34]: -Djstartup.whoami=server
    -> arg[ 35]: -Djstartup.debuggable=no
    -> arg[ 36]: -Xss2m
    -> arg[ 37]: -DSAPINFO=B23_00_server
    -> arg[ 38]: -DSAPSTART=1
    -> arg[ 39]: -DCONNECT_PORT=4600
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=B23
    -> arg[ 42]: -DSAPMYNAME=bidq001_B23_00
    -> arg[ 43]: -DSAPPROFILE=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
    -> arg[ 44]: -DFRFC_FALLBACK=ON
    -> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 46]: -DSAPSTARTUP=1
    -> arg[ 47]: -DSAPSYSTEM=00
    -> arg[ 48]: -DSAPSYSTEMNAME=B23
    -> arg[ 49]: -DSAPMYNAME=bidq001_B23_00
    -> arg[ 50]: -DSAPDBHOST=bidq001
    -> arg[ 51]: -Dj2ee.dbhost=bidq001
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 3380] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 2604] Thu Sep 18 12:42:58 2008
    [Thr 2604] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 2604] Thu Sep 18 12:43:07 2008
    [Thr 2604] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 2604] JLaunchISetClusterId: set cluster id 6587850
    [Thr 2604] Thu Sep 18 12:43:08 2008
    [Thr 2604] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 2604] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5780] Thu Sep 18 12:43:48 2008
    [Thr 5780] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5780] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 5780] Thu Sep 18 12:43:52 2008
    [Thr 5780] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
    [Thr 1764] Thu Sep 18 12:44:02 2008
    [Thr 1764] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 2604] Thu Sep 18 12:44:24 2008
    [Thr 2604] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 2752] Tue Sep 23 14:16:00 2008
    [Thr 2752] JLaunchRequestFunc: receive command:17, argument:0 from pid:5616
    [Thr 2752] JLaunchIShutdownInvoke: set shutdown interval (stop:1222159560/end:1222159680/TO:120)
    [Thr 2752] JLaunchProcessCommand: Invoke VM Shutdown
    [Thr 2752] JHVM_FrameworkShutdownDirect: invoke direct shutdown
    [Thr 6268] Tue Sep 23 14:16:20 2008
    [Thr 6268] JLaunchISetState: change state from [Starting applications (10)] to [Waiting for stop (4)]
    [Thr 6268] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
    trc file: "F:\usr\sap\B23\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID6587850
    pid         : 4116
    system name : B23
    system nr.  : 00
    started at  : Tue Sep 23 14:18:06 2008
    arguments       :
           arg[00] : F:\usr\sap\B23\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
           arg[02] : -DSAPINFO=B23_00_server
           arg[03] : pf=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=4600
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=B23
           arg[08] : -DSAPMYNAME=bidq001_B23_00
           arg[09] : -DSAPPROFILE=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 5340] Tue Sep 23 14:18:06 2008
    [Thr 5340] *** WARNING => INFO: Unknown property [instance.box.number=B23DVEBMGS00bidq001] [jstartxx.c   841]
    [Thr 5340] *** WARNING => INFO: Unknown property [instance.en.host=bidq001] [jstartxx.c   841]
    [Thr 5340] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 5340] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : bidq001
    -> ms port    : 3901
    -> OS libs    : F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : bidq001
    -> ms port    : 3901
    -> os libs    : F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID6587800  : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID6587850  : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID6587800            : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID6587850            : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 5340] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5340] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5460] JLaunchRequestFunc: Thread 5460 started as listener thread for np messages.
    [Thr 5580] WaitSyncSemThread: Thread 5580 started as semaphore monitor thread.
    [Thr 5340] Tue Sep 23 14:18:07 2008
    [Thr 5340] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5340] CPIC (version=700.2006.09.13)
    [Thr 5340] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_16-x64
    [Thr 5340] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\B23\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID6587850]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_16-x64
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\B23\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : F:\usr\sap\B23\DVEBMGS00\exe\jstartup.jar;F:\usr\sap\B23\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 5340] JLaunchISetDebugMode: set debug mode [no]
    [Thr 3176] JLaunchIStartFunc: Thread 3176 started as Java VM thread.
    [Thr 3176] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dsys.global.dir=F:\usr\sap\B23\SYS\global
    -> arg[ 24]: -Dapplication.home=F:\usr\sap\B23\DVEBMGS00\exe
    -> arg[ 25]: -Djava.class.path=F:\usr\sap\B23\DVEBMGS00\exe\jstartup.jar;F:\usr\sap\B23\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 26]: -Djava.library.path=C:\j2sdk1.4.2_16-x64\jre\bin\server;C:\j2sdk1.4.2_16-x64\jre\bin;C:\j2sdk1.4.2_16-x64\bin;F:\usr\sap\B23\DVEBMGS00\j2ee\os_libs;D:\oracle\B23\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\j2sdk1.4.2_16-x64\bin;F:\usr\sap\B23\SYS\exe\uc\NTAMD64
    -> arg[ 27]: -Dmemory.manager=1024M
    -> arg[ 28]: -Xmx1024M
    -> arg[ 29]: -Xms1024M
    -> arg[ 30]: -DLoadBalanceRestricted=no
    -> arg[ 31]: -Djstartup.mode=JCONTROL
    -> arg[ 32]: -Djstartup.ownProcessId=4116
    -> arg[ 33]: -Djstartup.ownHardwareId=Z1382384873
    -> arg[ 34]: -Djstartup.whoami=server
    -> arg[ 35]: -Djstartup.debuggable=no
    -> arg[ 36]: -Xss2m
    -> arg[ 37]: -DSAPINFO=B23_00_server
    -> arg[ 38]: -DSAPSTART=1
    -> arg[ 39]: -DCONNECT_PORT=4600
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=B23
    -> arg[ 42]: -DSAPMYNAME=bidq001_B23_00
    -> arg[ 43]: -DSAPPROFILE=F:\usr\sap\B23\SYS\profile\B23_DVEBMGS00_bidq001
    -> arg[ 44]: -DFRFC_FALLBACK=ON
    -> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 46]: -DSAPSTARTUP=1
    -> arg[ 47]: -DSAPSYSTEM=00
    -> arg[ 48]: -DSAPSYSTEMNAME=B23
    -> arg[ 49]: -DSAPMYNAME=bidq001_B23_00
    -> arg[ 50]: -DSAPDBHOST=bidq001
    -> arg[ 51]: -Dj2ee.dbhost=bidq001
    Tue Sep 23 14:18:09 2008
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 3176] Tue Sep 23 14:18:10 2008
    [Thr 3176] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 6368] Tue Sep 23 14:18:26 2008
    [Thr 6368] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 6368] Tue Sep 23 14:18:35 2008
    [Thr 6368] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 6368] JLaunchISetClusterId: set cluster id 6587850
    [Thr 6368] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 6368] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6696] Tue Sep 23 14:19:11 2008
    [Thr 6696] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 6696] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 6696] Tue Sep 23 14:19:12 2008
    [Thr 6696] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
    [Thr 6376] Tue Sep 23 14:19:20 2008
    [Thr 6376] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 6368] Tue Sep 23 14:19:41 2008
    [Thr 6368] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 5460] Wed Sep 24 12:20:46 2008
    [Thr 5460] JLaunchRequestFunc: receive command:10, argument:0 from pid:5616
    [Thr 5460] JLaunchProcessCommand: caught dump stack trace
    Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.4.2_16-b05 mixed mode):
    "SeedGenerator Thread" daemon prio=2 tid=0x00000000092d0900 nid=0x1b80 in Object.wait() [0x0000000072b7f000..0x0000000072b7fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590070> (a sun.security.provider.SeedGenerator$ThreadedSeedGenerator)
         at java.lang.Object.wait(Object.java:429)
         at sun.security.provider.SeedGenerator$ThreadedSeedGenerator.run(SeedGenerator.java:282)
         - locked <0x0000000015590070> (a sun.security.provider.SeedGenerator$ThreadedSeedGenerator)
         at java.lang.Thread.run(Thread.java:534)
    "DSR_Write_Rate_Monitor: bidq001.tvse.int_B23_6587850" prio=5 tid=0x000000006de58420 nid=0x1ac0 waiting on condition [0x000000007297f000..0x000000007297fb80]
         at java.lang.Thread.sleep(Native Method)
         at com.sap.engine.services.dsr.DSRComponentImpl0$SubmitRateMonitor.run(DSRComponentImpl0.java:1505)
    "Thread-35" prio=5 tid=0x000000006de58190 nid=0x5f0 in Object.wait() [0x000000007277f000..0x000000007277fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590198> (a com.sap.engine.services.shell.processor.ShellWrapper)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.services.shell.core.ServerShellProcessor.run(ServerShellProcessor.java:118)
         - locked <0x0000000015590198> (a com.sap.engine.services.shell.processor.ShellWrapper)
         at java.lang.Thread.run(Thread.java:534)
    "Thread-33" prio=10 tid=0x00000000092d2530 nid=0x1b6c waiting on condition [0x000000007257f000..0x000000007257fb80]
         at java.lang.Thread.sleep(Native Method)
         at com.sap.caf.mp.base.caching.MemoryCache$ValidationThread.run(MemoryCache.java:144)
    "Thread-32" daemon prio=10 tid=0x00000000092d1d80 nid=0x1b0c in Object.wait() [0x0000000071aff000..0x0000000071affb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590378> (a java.util.TaskQueue)
         at java.util.TimerThread.mainLoop(Timer.java:429)
         - locked <0x0000000015590378> (a java.util.TaskQueue)
         at java.util.TimerThread.run(Timer.java:382)
    "JCoRequestDispatcher" daemon prio=5 tid=0x00000000092d2010 nid=0x1b08 runnable [0x00000000720bf000..0x00000000720bfb80]
         at com.sap.mw.rfc.driver.CpicDriver.nativeSAP_CMLISTEN(Native Method)
         at com.sap.mw.rfc.driver.CpicDriver.SAP_CMLISTEN(CpicDriver.java:1126)
         at com.sap.mw.rfc.driver.RfcTypeRegisterCpic.waitForRequest(RfcTypeRegisterCpic.java:593)
         at com.sap.mw.rfc.api.RfcApi.RfcWaitForCpicRequest(RfcApi.java:1261)
         at com.sap.mw.jco.MiddlewareJRfc.waitForRequest(MiddlewareJRfc.java:580)
         at com.sap.mw.jco.RequestDispatcher$DispatcherWorker.run(RequestDispatcher.java:157)
         at java.lang.Thread.run(Thread.java:534)
    "SAPEngine_CCMSCommandConsumer_0" prio=10 tid=0x00000000092d1af0 nid=0x1a90 in Object.wait() [0x0000000071cff000..0x0000000071cffb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x00000000155904f8> (a java.lang.Object)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.concurrent.LinkedQueue.take(LinkedQueue.java:104)
         - locked <0x00000000155904f8> (a java.lang.Object)
         at com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer.run(CCMSCommandConsumer.java:38)
         at java.lang.Thread.run(Thread.java:534)
    "SAPDSR_updater" prio=10 tid=0x00000000092d15d0 nid=0x1b88 waiting on condition [0x00000000718ff000..0x00000000718ffb80]
         at java.lang.Thread.sleep(Native Method)
         at com.sap.jdsr.writer.DsrPortUpdater.run(DsrPortUpdater.java:55)
    "SAPDSR_watcher" prio=10 tid=0x00000000092d1340 nid=0x1b78 runnable [0x00000000716ff000..0x00000000716ffb80]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
         - locked <0x0000000015590700> (a java.net.PlainSocketImpl)
         at java.net.ServerSocket.implAccept(ServerSocket.java:448)
         at java.net.ServerSocket.accept(ServerSocket.java:419)
         at com.sap.jdsr.writer.DsrListener.run(DsrListener.java:748)
    "Thread-24" prio=10 tid=0x00000000092d0e20 nid=0x1b30 in Object.wait() [0x00000000714ff000..0x00000000714ffb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590cb8> (a com.sap.jmx.provider.ProviderConnectionTimer)
         at com.sap.jmx.provider.ProviderConnectionTimer.run(ProviderConnectionTimer.java:31)
         - locked <0x0000000015590cb8> (a com.sap.jmx.provider.ProviderConnectionTimer)
         at java.lang.Thread.run(Thread.java:534)
    "Thread-23" prio=10 tid=0x00000000092d10b0 nid=0x1ab4 in Object.wait() [0x00000000712ff000..0x00000000712ffb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590d50> (a com.sap.jmx.provider.LazyMBeanLoader)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.jmx.provider.LazyMBeanLoader.run(LazyMBeanLoader.java:133)
         - locked <0x0000000015590d50> (a com.sap.jmx.provider.LazyMBeanLoader)
         at java.lang.Thread.run(Thread.java:534)
    "_keystore_managed_system_thread_" prio=10 tid=0x00000000092d0b90 nid=0x1ab0 in Object.wait() [0x00000000710ff000..0x00000000710ffb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590e00> (a java.lang.Object)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.services.keystore.impl.security.SystemThreadWorker.run(SystemThreadWorker.java:56)
         - locked <0x0000000015590e00> (a java.lang.Object)
         at java.lang.Thread.run(Thread.java:534)
    "R3RoleDataSource_UpdateThread[114603123]" daemon prio=10 tid=0x00000000092d0670 nid=0x1af4 waiting on condition [0x0000000070eff000..0x0000000070effb80]
         at java.lang.Thread.sleep(Native Method)
         at com.sap.security.core.persistence.datasource.imp.R3RoleDataSource$1.run(R3RoleDataSource.java:661)
         at java.lang.Thread.run(Thread.java:534)
    "JarmCondense" daemon prio=10 tid=0x00000000092d03e0 nid=0x1af8 in Object.wait() [0x000000006cb7f000..0x000000006cb7fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015590f30> (a java.lang.Object)
         at com.sap.util.monitor.jarm.CondenseThread.threadShouldContinue(CondenseThread.java:217)
         - locked <0x0000000015590f30> (a java.lang.Object)
         at com.sap.util.monitor.jarm.CondenseThread.run(CondenseThread.java:196)
         at java.lang.Thread.run(Thread.java:534)
    "JCO.TimeoutChecker" daemon prio=10 tid=0x00000000092d0150 nid=0x1b60 in Object.wait() [0x000000006c80f000..0x000000006c80fb80]
         at java.lang.Object.wait(Native Method)
         at com.sap.mw.jco.JCO$PoolManager$TimeoutChecker.run(JCO.java:5672)
         - locked <0x0000000015590fd0> (a com.sap.mw.jco.util.ObjectList)
         at java.lang.Thread.run(Thread.java:534)
    "ConnectionSetCleaner Thread (UNMANAGED)." prio=10 tid=0x00000000092cf9a0 nid=0x1b8c in Object.wait() [0x000000006c60f000..0x000000006c60fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015591028> (a com.sap.engine.services.connector.jca.ConnectionHashSet$ConnectionSetCleaner)
         at com.sap.engine.services.connector.jca.ConnectionHashSet$ConnectionSetCleaner.run(ConnectionHashSet.java:682)
         - locked <0x0000000015591028> (a com.sap.engine.services.connector.jca.ConnectionHashSet$ConnectionSetCleaner)
    "SAPEngine_TREXRefreshCache_0" prio=10 tid=0x00000000092cf710 nid=0x196c waiting on condition [0x000000006a40f000..0x000000006a40fb80]
         at java.lang.Thread.sleep(Native Method)
         at com.sapportals.trex.util.cache.CacheFactory$RefreshThread.run(CacheFactory.java:522)
    "SAPEngine_System_Thread[impl:5]_87" prio=5 tid=0x00000000092cf480 nid=0x894 in Object.wait() [0x000000006a20f000..0x000000006a20fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_86" prio=5 tid=0x00000000092cf1f0 nid=0x68c in Object.wait() [0x000000006a00f000..0x000000006a00fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_85" prio=5 tid=0x00000000092cef60 nid=0x61c in Object.wait() [0x0000000069e0f000..0x0000000069e0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_84" prio=5 tid=0x00000000092cecd0 nid=0x270 in Object.wait() [0x0000000069c0f000..0x0000000069c0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_83" prio=5 tid=0x00000000092cea40 nid=0x1b18 in Object.wait() [0x0000000069a0f000..0x0000000069a0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_82" prio=5 tid=0x0000000008b92530 nid=0x1afc in Object.wait() [0x000000006980f000..0x000000006980fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_81" prio=5 tid=0x0000000008b922a0 nid=0x4b8 in Object.wait() [0x000000006960f000..0x000000006960fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000001af2a070> (a com.sap.engine.services.log_configurator.archive.Buffer)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.services.log_configurator.archive.Buffer.getTask(Buffer.java:38)
         - locked <0x000000001af2a070> (a com.sap.engine.services.log_configurator.archive.Buffer)
         at com.sap.engine.services.log_configurator.archive.ArchivingThread.run(ArchivingThread.java:37)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_80" prio=5 tid=0x0000000008b92010 nid=0x1ad0 in Object.wait() [0x000000006940f000..0x000000006940fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_79" prio=5 tid=0x0000000008b91d80 nid=0x1aac in Object.wait() [0x000000006920f000..0x000000006920fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x00000000155910b0> (a java.lang.Object)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.jms.server.destinationcontainer.AgentThreadSystem.run(AgentThreadSystem.java:148)
         - locked <0x00000000155910b0> (a java.lang.Object)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_78" prio=5 tid=0x0000000008b91af0 nid=0x1b00 in Object.wait() [0x000000006900f000..0x000000006900fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "Timeout Service Internal Thread" prio=5 tid=0x0000000008b91860 nid=0x1448 in Object.wait() [0x0000000068e0f000..0x0000000068e0fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000001af2a3f8> (a java.lang.Object)
         at com.sap.engine.services.timeout.TimeoutManagerImpl.multiThreadRun(TimeoutManagerImpl.java:483)
         - locked <0x000000001af2a3f8> (a java.lang.Object)
         at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:20)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_76" prio=5 tid=0x0000000008b915d0 nid=0x1960 in Object.wait() [0x0000000068c0f000..0x0000000068c0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "Timeout Service Integrity Watcher Thread" prio=10 tid=0x0000000008b91340 nid=0x1ab8 in Object.wait() [0x0000000068a0f000..0x0000000068a0fb80]
         at java.lang.Object.wait(Native Method)
         at com.sap.engine.services.timeout.TimeoutIntegrityWatcher.run(TimeoutIntegrityWatcher.java:69)
         - locked <0x000000001af2a6a0> (a com.sap.engine.services.timeout.TimeoutIntegrityWatcher)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_74" prio=5 tid=0x0000000008b910b0 nid=0x1a9c in Object.wait() [0x000000006880f000..0x000000006880fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_73" prio=5 tid=0x0000000008b90e20 nid=0x1aa0 in Object.wait() [0x000000006860f000..0x000000006860fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_72" prio=5 tid=0x0000000008b90b90 nid=0x1a94 in Object.wait() [0x000000006840f000..0x000000006840fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "Timeout Service Synchronous Internal Thread" prio=5 tid=0x0000000008b90900 nid=0x1a98 in Object.wait() [0x000000006820f000..0x000000006820fb80]
         at java.lang.Object.wait(Native Method)
         at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:596)
         - locked <0x000000001af2aa40> (a java.lang.Object)
         at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:18)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_70" prio=5 tid=0x0000000008b90670 nid=0x1aa8 in Object.wait() [0x000000006800f000..0x000000006800fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "Timeout Service Integrity Watcher Thread" prio=10 tid=0x0000000008b903e0 nid=0x19b8 in Object.wait() [0x0000000067e0f000..0x0000000067e0fb80]
         at java.lang.Object.wait(Native Method)
         at com.sap.engine.services.timeout.TimeoutIntegrityWatcher.run(TimeoutIntegrityWatcher.java:69)
         - locked <0x000000001af2ac60> (a com.sap.engine.services.timeout.TimeoutIntegrityWatcher)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_68" prio=5 tid=0x0000000008b90150 nid=0x1a04 in Object.wait() [0x0000000067c0f000..0x0000000067c0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_67" prio=5 tid=0x0000000008b8fec0 nid=0x18dc in Object.wait() [0x0000000067a0f000..0x0000000067a0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_66" prio=5 tid=0x0000000008b8fc30 nid=0x19e4 in Object.wait() [0x000000006780f000..0x000000006780fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_65" prio=5 tid=0x0000000008b8f9a0 nid=0x1a78 in Object.wait() [0x000000006760f000..0x000000006760fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_64" prio=5 tid=0x0000000008b8f710 nid=0x1a38 in Object.wait() [0x000000006740f000..0x000000006740fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_63" prio=5 tid=0x0000000008b8f480 nid=0x1a60 in Object.wait() [0x000000006720f000..0x000000006720fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_62" prio=5 tid=0x0000000008b8f1f0 nid=0x1a64 in Object.wait() [0x000000006700f000..0x000000006700fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_61" prio=5 tid=0x0000000008b8ef60 nid=0x1a8c in Object.wait() [0x0000000066e0f000..0x0000000066e0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_60" prio=5 tid=0x0000000008b8ecd0 nid=0x19f8 in Object.wait() [0x0000000066c0f000..0x0000000066c0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_59" prio=5 tid=0x0000000008b8ea40 nid=0x19dc in Object.wait() [0x0000000066a0f000..0x0000000066a0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_58" prio=5 tid=0x0000000008656ce0 nid=0xdbc in Object.wait() [0x000000006680f000..0x000000006680fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0000000015591210> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
         - locked <0x0000000015591210> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
         at com.sap.engine.lib.util.cache.CacheGroup.run(CacheGroup.java:76)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    "SAPEngine_System_Thread[impl:5]_57" prio=5 tid=0x0000000008656a50 nid=0x1a0c in Object.wait() [0x000000006660f000..0x000000006660fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_56" prio=5 tid=0x00000000086567c0 nid=0x1a28 in Object.wait() [0x000000006640f000..0x000000006640fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_55" prio=5 tid=0x0000000008656530 nid=0x1a54 in Object.wait() [0x000000006620f000..0x000000006620fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_54" prio=5 tid=0x00000000086562a0 nid=0x1a4c in Object.wait() [0x000000006600f000..0x000000006600fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_53" prio=5 tid=0x0000000008656010 nid=0x1a48 in Object.wait() [0x0000000065e0f000..0x0000000065e0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_52" prio=5 tid=0x0000000008655d80 nid=0x18e8 in Object.wait() [0x0000000065c0f000..0x0000000065c0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_51" prio=5 tid=0x0000000008655af0 nid=0x1a68 in Object.wait() [0x0000000065a0f000..0x0000000065a0fb80]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000001ab100a8> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
    "SAPEngine_System_Thread[impl:5]_50" prio=5 tid=0x0000000008655860 nid=0x1a74 in Object.wait() [0x000000006580f000..0x000000006580fb80]

    Could you please send the default trace.Default trace will contain the detailed description of the error message , but you will have to search a lot in that .The trace file is BIG!!!
    This trace can be found in .../DV**/j2ee/cluster/server0/log.
    Check for the latest File.
    Regards,
    Yogesh

  • Reprocess Bdoc with status I04 (Intermediate state)

    Hi All,
    I have problems to reprocess Bdoc's with status I04 (Intermediate state).
    In a batchprogram I created businesstransactions. But when a central blockade was set on the businessparter, no businesstransaction appear.
    In the SM13 I have Update-errors (SAPSQL_ARRAY_INSERT_DUPREC).
    In the SMW01 I have Bdoc's (BUS_TRANS_MSG) with status I04.
    I'm having problems to reprocess the Bdoc's.
    After uncheck all central blockades, the reprocess of the bdoc failed.
    After changing the status of the Bdoc from I04 to I01, the bdoc will be reprocessed (green), but the data in the Bdoc will not be written to the database (CDB).
    What could be a solution to reprocess the Bdoc's with an update of the CDB (and the businesstransaction appear)?
    Thanks!

    Hi G. van Doom,
    You got a system error: <b>SAPSQL_ARRAY_INSERT_DUPREC</b>, this means that the running process tried to insert to the DB a records that is already existing. Hence it raised this system error.
    Reprocessing the BDoc won't solve the issue since you will again try to insert record that already exist.
    I would suggest you to maybe check the <b>task</b> you set in the BDoc from your batchprogram, if the records was already existing then you should rather do an update, by using Task = 1. Therefore you must have a logic in your program which can find if the record exist or not in order to set the appropriate task.
    Task:
    1 - Update
    2 - Insert
    3 - Delete
    Hopping this help.
    Sincerely,
    Alain Gauthier

  • Request stays yellow

    Hi all,
    a DTP request with an attribute InfoObject target (time-independent) that has to handle duplicate record keys stays in yellow status. Only non-duplicate entries are transferred and nothing happens anymore. Why?
    Many thanks in advance.
    Best regards
    Tobias

    After a while the request turned to green status.

  • Bdoc intermediate state( I02)

    Hi,
      I am creating bdoc thru report program. When i execute the program Bdoc is creating as a Intermediate state ( I02) and it is stored in SMQ2(Inbound queue) level. In the queue level it is showing status like RETRY.
    Please help me in this.
    Regards
    Srinu

    Hi,
    have you already successfully created the replication object, publication and subscription in the administration console (transaction SMOEAC)?
    Maybee this hind helps.
    Best regards
    Manfred

  • Statndard S_TCODE object in unmaintained (yellow) status

    Hi Experts,
    I came across a role in which standard S_TCODE object is in unmaintained(yellow) status.
    Is there any limit to number of Tcodes which can be added under S_TCODE object?
    Please help me out to find the reaon.
    Thanks,
    Mohit

    Hi Julius,
    Its new to me too Thanks for sharing the notes. I didn't guess and hence said as per my knowledge Limiting the guess to my knowledge.
    Thanks agian!!
    Rgds,
    Raghu

Maybe you are looking for