Data Request remains in yellow status after RSAPO_CLOSE_TRANS_REQUEST

Dear all,
I am working on BI 7.0 and I need to load data from a Real-Time Cube (in planning mode) to a Standard Cube. I am using a Process Chain with a program which calls function module RSAPO_CLOSE_TRANS_REQUEST providing the technical name of the Real-Time cube to this function module. I see that this function module works in general, because afterwards I see the number of data records transferred and added appearing in the data request. However, the status of the data request is still yellow. In order to load the data from this cube to another it has to be in green. It is not acceptable to do this manually, it has to be automated. Data entry on the Planning Cube is via a BI-IP Query. The data arrives correctly in the cube, when checking the InfoCube content the data appears to be fine.
I have used this function module in many projects without such a problem. Does anyone have an idea why the data request is not set in green status?
I have also tried to use the function modules RSAPO_SWITCH_TRANS_TO_BATCH and RSAPO_SWITCH_BATCH_TO_TRANS to convert from Planning mode to normal mode and then back from normal to planning mode. The result is the same, data request remains yellow.
Many thanks for your help
Claas

Thanks Rishi,
I have tried this with the standard Process Chain steps to switch the mode, but the issue remains. It first switches the Cube to Load-Mode, I see data records in the request being added to the cube, the next step tries to switch the cube back into Planning mode, This step now gives an error because the data request is in yellow status, so the cube cannot be switched back to planning.
Error Message:
Request APO_R4EX2HO4TYDLBCNQPQY82K8ZOJ(0000020181) is yellow or red in InfoCube DRI_P301; cannot switch to planning
Message no. RSM068
The Problem is that after the Cube was switched to Load-mode the request is still yellow.
I do not understand why data records get added to the cube but the request does not get turned into green status. Any more ideas?
Cheers
Claas
Edited by: Claas Bartels on Aug 29, 2009 10:29 PM

Similar Messages

  • PSA load remains in yellow status.

    Hi Gurus,
    I have created a generic datasource based  on function module.
    I have replicated the datasource in  SAP BI dev instance.
    I have even checked the extractor checker in R/3 and it shows 381 records.
    On BI side I am loading data upto PSA.When I execute the infopackage for full load in the monitor screen I could see
    "381 out of 0 records".The request remains in yellow status.
    The idoc status in source system side is 03 and on BI side is 53.
    I dont get any error message.Even I am not seeing idocs with red status in SM58 tcode.No logs are seen in sm21.
    I even asked the basis team to check for RFC connection SM59 and partner profile.Every thing looks fine .
    This loading issue is only happening with this specific datasource(ie datasource created on function module).
    For other datasources load are carried out fine.
    Has anybody faced a similar issue?.Please help in this regard.

    seems the load is hung bcoz of thehung IDOCs.
    Process the idocs manually. after
    check the below things
    --> Check weather the source system job finished or not?
    If the job is finished check the TRFCs are processed or not?
    In the monitor screen - menu bar --environment -->job overview (to check the job) -->TRFcs - to check the TRFCs.
    Check for short dumps using transaction ST22.
    -->Check for the Idocs in BD87 and if there are any IDOCs got stuck process them manually.
    To process Idocs first change the status of request to red and try to process them in the background.

  • PSA request is in yellow status

    Hi
    We got the problem when loading the 2LIS_03_BF data into cube. We have around 4 cubes and 2 ods.
    The data got loaded into all the cubes and ods except on Cube. There was a problem of table space and now it is solved.
    Now the request is in yellow status in PSA. It cube it shows no of records added and transferred but the status is in red color.
    How can i upload the delta data into the cube from PSA when PSA request is in yellow color.
    I feel strange that when the request is in yellow color how come the data is loaded into all other cubes.
    REgards
    Annie

    You should be able to load request from PSA to data target using the option available in PSA. When you manage on Datasource, you see all requests. You can select that PSA request and use Scheduler option in that screen to update that particular request.  It will run infopackage as usual. It will execute all the routines if there are any in update rules.
    When you say you have some programs running in process chain, they must be after this failed load right?
    If that is the case, all you need to do is push process chain further. Below are steps to push process chain further if you any step is stuck in yellow or if mually carry out any red step in process chain. In you case, load that failed step manually using scheduler form PSA manage tab and then push PC further using these steps. That will continue PC further and run any programs that run after load.
    Execute in SE38 -> RSPC_PROCESS_FINISH
    Fill the following parameters on screen and rest all can be left blank.
    1. LOGID - you will find this when you do monitor of your process chain. Every time you run process chain, unique LOGID is created.
    2. TYPE - If step is ODS activation then TYPE wud be ODSACTIVAT and if it is infopak loading TYPE wud be LOADING and if it is DTP Load TYPE wud be LOAD. In your case it will be LOADING.
    3. VARIANT - In the process chain monitor mode, right click on step which you executed manually -> Display Messages. Go to chain tab and there you will find VARIANT
    4. INSTANCE - In the process chain monitor mode, right click on step which you executed manually -> Display Messages. Go to chain tab and there you will find INSTANCE
    5. STATE - Value wud be G
    After entering above parameters, click execute. It will be done in fraction of second and wont give any popup. Now when you will check process chain monitor, you will see that step 4 is green and next step has started executing.
    Abhijit

  • Datasource 0UC_SWTMSGDATA - request remains in yellow state

    hi all,
    we are using the datasource 0UC_SWTMSGDATA to extract message data for the switch documents.
    every time we scheduled the infopackage to load data into sap bi, the datasource extracts all data records to the bi.
    but at the end, when all records arrived at bi, the request remains in yellow state.
    do you have the same problem? what's the reason?
    we are already using the datasource 0UC_SWTDOC, it works fine.
    kind regards,
    phil
    Edited by: Philipp Südfeld on Jul 8, 2011 4:49 PM

    Hi,
    You have to check  the job status in SM37 in R/3 system. If it shows "Active mode", then you will be getting Yellow color in BW. You may have to wait till the job gets finished in R/3.
    Sometimes, transferring I-Docs take time.
    Regards,
    Suman

  • Request shows in Red status after extraction of Data from Planning area

    Hi Experts,
    I am extracting data from DP planning area to APO BW Info Cube. It was working fine but from last few days after extraction we are getting Red status of that request. However whatever data packages we are extracting we are getting same in to Info Cube also. But only status of that request is in Red.
    I gone through step by step analysis I found "Data selection succesfully finished?" statement in Red status & rest are in green. When I gone through the details of this statement then I found Missing "Message:Selection Completed" in yellow status.
    Any Idea? How do i resolve this issue?
    Please advise..
    Regards
    Sujay

    Hi Sujay,
    Check the logs obtained after the extraction.
    This only will tell you fare idea for you to proceed further
    to resolve the error that has happened.
    Also check whether the extracted data is correct by
    random sampling of extracted data
    Regards
    R. Senthil Mareeswaran.

  • Data Loading is in Yellow Status

    Hi All,
    I have scheduled  the data using info package.I have Checked in RSMO and after long time, the job is in the yellow status. I have checked the job in SM37 in R/3 side and found the status as "Released".
    And data is not pulling into BW.
    Can you provide how to rectify this.
    Thanks,
    Siva.

    Hi there,
    Your job is stucked on the R/3 side (probably no more process available on R/3 side).
    Normally I could "force" that job, but I don't actually remember all of the steps.
    Try this:
    go to sm37 and for that particular job that is in the released state, select it and in the Menu choose Job->Released->Schedule
    This will start your job, if not, you can still find it in sm37 with the status "Schedule". Select it again and choose Release. This will or start your job immediatly or prompt to when you want to start your job. Select immediatly and this will start your job.
    Diogo.

  • Yellow status after "No database operations necessary, data unchanged"

    Hi,
    I am loading master data (full) and for some packages I get the message "No database operations necessary, data unchanged" the processing remains with status yellow (no "processing end" message comes for those packages). In the end, I get a red status because it times out.
    Has anyone encountered this problem before? Any idea appreciated
    Thanks!
    Andreea

    Hi,
    In case of master data, the update option for infoobject is overwrite. So if u are trying to load the same data again and again or if no changes are there in the new request at that time u may get this type of error. i am not sure about it. Check once more.
    Hope this helps u a lot.........
    <REMOVED BY ADMIN - DO NOT ASK FOR POINTS>
    Regards
    Ramakrishna Kamurthy
    Edited by: Craig Cmehil on Jul 17, 2008 9:24 AM

  • Mailbox move requests remain in Queued status

    My server is part of a two member DAG.  DAG shows to be healthy.  I have turned logging up to Expert level but no useful data is generated (only shows that the move request was created; no problems are indicated)
    Server is Exchange 2010 SP 3 

    Hi,
    Please check the database copy status under management tab on source database and target database. This can be that one or more of those databases you are moving mailboxes to has a failed or suspended copy and its failing the DataMoveReplicationConstraint
    check.
    Refer to this blog about Exchange 2010 Mailbox Moves and Mailbox Resiliency
    http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
    In addition, please check the event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
    Best Regards.

  • Data Load- 0 records yellow status

    Hi ,
    While loading data to BW 3.5 where the number of records is 0, it takes a very long time (more than one day) for the status to become GREEN. The data source is based on a custom FM. The extraction in RSA3 is working fine.
    I have changed the evaluation setting in the monitor screen to GREEN. However the problem still continues.
    Is their any exception which needs to be defined in the FM code?
    Thanks
    Priyya

    Are you raising NO_MORE_DATA when there is no records? See FM RSAX_BIW_GET_DATA_SIMPLE as an example.

  • DTP load in Yellow status forever

    All,
    The DTP load to this particular remains in Yellow status forever even though the transferred records are just 5000. After observing  the dump, it shows problem where a select query to a table is done in the end routine of the transfroamtion. 
    The select is on a big master data table (material) but when I gave the selection by itself in SE16, there were not many records - just 3000. then why would the trace say that all the time is being spent querying this database table?
    This was all working in D but not in q
    Another important note is that there was no scuh change to the material table. however, there were four attributes to which we had enabled 'conversion' in the transfer structure
    Would this be an issue if not the code itself?
    Thanks

    Any updates please?
    MORE iNFORMATION:
    The dtp loads from one DSO to another. I checked a similar scenario in the same system - things look fine.
    I have an end routine in the transformation. when I look at the dtp monitor for the status, it says:
    Extract. from DataStore xxxx: 4709 Data Records ---status GREEN
    Filter Out New Records with the Same Key : 5000 -> 5000 Data Records------status GREEN
    ODSO xxxxx-> ODSO yyyyy-----status YELLOW
    -Transformation Start---status GREEN
    -Rules---status GREEN
    -End Routine---status GREEN
    No Message: Transformation End
    No Message: Update to DataStore Object yyyyyy
    No Message: Set Technical Status to Green
    No Message: Set Overall Status to Green
    Thanks!

  • Dataload Yellow Status in DSO

    Hi All,
    We are having an issue with Infopackage request (QM Status) remains in Yellow status in the Target Admin of DSO but in fact it actually has failed (Red in Process Monitor). This happens when the Integrity Check is turned ON for infoobjects in the Transfer Rules and the records doesnu2019t exist in the master data. The Status should turn into Red instead of remaining in Yellow.
    Due to this, the triggered Process Chain will skip this request and shows Green status (zero records transferred to upper layer DSO). The user might think that the data is available for reporting because the Process Chain is in Green status.
    The reason why we are using an Infopackage/3.x Datasource/ Transfer Rules (instead of DTP/ Transformation) is because the source system is BODI. (BO Data Services)
    I tried changing some setting i.e. the Error Handling and Traffic Light setting of the Infopackage but it still wouldnu2019t work.
    My take is that the referential integrity checking in 3.5 Transfer Rule may have some bugs compared to 7.0 Transformation. I did a test using 7.0 Tansformation and DTP (from flat file source) and it works fine. But we canu2019t use this method because our source system is BODI. (3.x Datasource)
    Any help appreciated and thanks in advance.

    maybe it's bug, maybe not...but you can however mix 3.5 and bi7 within the same flow. you can load in 3.5 to a first layer dso (edwl) and then do a bi7 load to the next level. you can do the integrity check at this level.
    M.

  • 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

  • SM13 - Error in Collect.Run - Yellow status update records.

    Hello,
    After some problems with update queues in R/3, we have some update records in yellow status "Error in collective run" in sm13 t-code.
    If we run collective run, new records are pushed into rsa7, but this yellow status records won't move, and we actually need them.
    Does anyone know how to process this errors?

    Hi,
    There is no problem with background process, the new update records are being processed with no problem.
    These update records remain in yellow status since yesterday, but new records are being processed.

  • Status remains as Yellow, for no data

    hi ,
    in our master data load process chain, a datasource which has 0 records in the sourcesystem returns 0 records in BI. but the status remains as yellow , instead of green.
    since the status is yellow the next process is not getting triggered. only if we manually change the status to green, the process chain continues. wht shall we do to change the status to green automatically.

    Hi DOLLY,
    you need to cofigure  a small setting at Infopackage for this.
    RSA1-> infopackage -> scheduler -> Trafic light color for Empty request -> select green and save it.
    for 0 to 0 records load will show as Green.
    Regards
    Daya Sagar

  • FM to read yellow status requests from transactional InfoCube

    Hi,
    I am using the FM RSDRI_INFOPROV_READ to read data from the transactional InfoCube. My problem is that my code using this FM should be able to read data requests that have the yellow status for the transactional InfoCube.
    My code using this FM is able to read data from the green requests only but not the yellow requests. I was told in BPS, the yellow requests should turn green automatically after 50K of records have been queue up and ready to be turned green by itself.
    Has anyone come across this and help me solve this issue of reading data using FM RSDRI_INFOPROV_READ to read yellow request data. Is there another FM to read both the green and yellow requests?
    Please advise. Thanks
    RT

    Hi Rob,
    The function module mentioned by you is correct and it will read the yellow requests please try this, by default the parameter i_rollup_only is set as true set it to false (blank) while calling the function module.
    Please see the attached code
    CALL FUNCTION 'RSDRI_INFOPROV_READ'              
       EXPORTING                                      
         i_infoprov             = p_infocube          
         i_th_sfc               = t_sfc               
         i_th_sfk               = t_sfk               
         i_t_range              = lt_range            
         I_PACKAGESIZE          = p_pksize            
         i_rollup_only          = rs_c_false          
       IMPORTING                                      
         e_t_data               = <fsl_data_read>     
         e_end_of_data          = w_end_of_data       
       CHANGING                                       
         c_first_call           = l_first_call        
       EXCEPTIONS                                     
         illegal_input          = 1                   
         illegal_input_sfc      = 2                   
         illegal_input_sfk      = 3                   
         illegal_input_range    = 4                   
         illegal_input_tablesel = 5                   
         no_authorization       = 6                   
         ncum_not_supported     = 7                   
         illegal_download       = 8                   
         illegal_tablename      = 9                   
         trans_no_write_mode    = 10                  
         inherited_error        = 11                  
         x_message              = 12                  
         OTHERS                 = 13.                 
    Hope this was helpful.
    thanks

Maybe you are looking for

  • Video camera - Need to shoot in Black and White

    We need to shoot video in black and white, We have tried to shoot in night  mode.  But the result is the colors being brighter and not lighter.  We need to do video coding with these so the colors being too bright is not working out.  any imput on a

  • Import into SQL Server db from Sybase 7 data source - SQL Server 2008 R2/2012

    Hi, I need to import Sybase 7 data into a SQL Server 2008 R2 or 2012 database. Has anyone any experiences about this import? Thanks

  • Temp tables and deferred updates

    Does anyone know why the following update to #test and #test1 is deferred, but the same update to the permanent table inputtable is direct? I haven't found any documentation that would explain this. @@version is Adaptive Server Enterprise/15.7.0/EBF

  • InDesign CS5 crashing on launch due to font auto-activator issue

    I was having a problem where all the jobs I had been collecting would no longer open in InDesign CS5 without crashing on startup. Just found out today it has to do with the new feature in CS5 that reads fonts from your "Document Fonts" folder. Once I

  • Connection driving me mad.. Please help

    So to say I'm frustrated at my connection would be an understatement. Moved address so went from a 20meg connection to what was nearly 5meg... I have been downloading my backup from livedrive for weeks now. Anyway no extension sockets are here just t