WS12300111 starts in status Ready
Hi.
I have a problem when triggering WS12300111.
The workflow is created, but it goes into status 'READY', meaning that it doesn't run. I would expect it to go into status 'STARTED'.
Customizing in SPRO looks fine, and SWU3 - Maintain Runtime Environment is all green.
If i find the workflow in SWIA and "execute" it, it goes into status 'STARTED' and workitem for approval is created.
What am I missing to get get the workflow started automatically?
Thanks for your input.
Best Regards
Poul Steen Hansen.
Hi,
Well the workflow starts with a dialog step, so you want this to be background?
Or what is the problem here.
I think in one case some workflow wasnt exactly starting automatically, I solved it by changing the agent assignment of the workflow template to general.
Kind regards, Rob Dielemans
Similar Messages
-
Hi All
I have set up a simple custom HCM process and Form regarding Infotype TO CREATE AND CHANGE POSITION. I have checked the process and form consistency and it seems fine. Now when I run the process from HRASR_DT it generates a process number but it also gives an error workflow could not start.I get following error (SWIA log - Step history)
Executing flow work item - Transaction brackets of the workflow has been damaged
Exception occurred - Error when starting work item 000000007031
PROCESS_NODE - Error when processing node '0000000014' (ParForEach index 000000)
CREATE - Error when creating a component of type 'Step'
CREATE_WIM_HANDLE - Error when creating a work item
CREATE_VIA_WFM - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event CREATED and (target) status
EVENT_RAISED - Error updating the process object
Executing flow work item - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY->ERROR
EVENT_RAISED - Error updating the process object
Executing flow work item - Transaction brackets of the workflow has been damaged
Executing flow work item - Work item 000000007031: Object FLOWITEM method EXECUTE cannot be executed
Executing flow work item - Error when processing node '0000000014' (ParForEach index 000000)
Points to be noted:
1) I have searched few SAP notes such as 1384961(Notes for 6.0.4) but our system is in higher level patch 6.0.5
2) WF-BATCH have SAP_NEW and SAP_ALL authorization.
Appreciate your valuable suggestions.
Thanks
RagavHi Ragav
did you try to debug this? maybe something is missing in config of P&F?
Since you are on 605, the following note would be there in your system....use it to debug:
1422496 - Debugging background workflow tasks in HCM P&F
This will help you find the root cause.
regards,
modak -
Dear Experts,
I have a workitem (activity step) in status ready. I have bind a webdynpro java application for this in SWFVISU tcode. So once user clicks workitem from portal dynpro java application will open. But workitem in R/3 remains in status ready even after user clicks submit from the java application. So on action submit I need to complete that workitem. Is there any FM to complete a workitem which is in status ready. This workitem is from a task of activity step. This is just a dummy workitem that is I have given a BO method inside it that does not have any code. I use this to start the dynpro java appln alone.
First i will be using sap_Wapi_write_container FM. Then I will complete the workitem. Then using sap_wapi_read_container I will read the written values. If i use sap_wapi_workitem_complete FM then the written values change back to old values again.
KR,
Bharath
Edited by: bharath padmanabhan on Dec 29, 2009 10:06 AM
Edited by: bharath padmanabhan on Dec 29, 2009 10:28 AMDear All,
Thanks a lot for your replies. I have solved the problem. First I set the status of workitem to started and then completed it. Please find the code below.
CALL FUNCTION 'SAP_WAPI_SET_WORKITEM_STATUS'
EXPORTING
workitem_id = lv_wi_id " workitem id
status = 'STARTED'
USER = SY-UNAME
LANGUAGE = SY-LANGU
DO_COMMIT = 'X'.
CALL FUNCTION 'SAP_WAPI_DECISION_COMPLETE'
EXPORTING
workitem_id = lv_wi_id " workitem id
LANGUAGE = SY-LANGU
USER = SY-UNAME
decision_key = '0001'
DO_COMMIT = 'X'.
KR,
Bharath -
Backgroud task of a workflow set to status "ready"
Hi all, We have a worflow working since some years ago and now suddenly one problem has started to ocurr...
sometimes, one of the backgroud steps of this workflow is not processed in backgroud by WF-BATCH as expected but it remain in status "READY"....this is not intended and what we are expecting is that this task is processed in background without any user input inmediately after the previous task....
Until today, this task has worked without problems but now we got this task not processed but waiting in status "ready"...this only occurs sometimes, not with all instances of this workflow but only sometimes in a random way....
I can´t see anything wrong in the template...only thing I see is that this background task is executed right after a "dialog task" where user need to aprove or reject the document in workflow. this "dialog step" use the standard task "TS00008267" (generic decission task) as base and this standard task has "latest end" setted (I don´t know if this can be the problem or always has been in this way with this "latest end" active...)
any tips???? someone with same problems????
Thanks in advance....hi Rob, first at all, thanks for your fast reply, much appreciated mate....
surfing this forum I just found this post () , I think, is same problem, related to RSWERRE program jobs....
I´ve seen that all of those background workitems in status "ready" that we expected to be processed automatically are from same day, and in that day we suffered a problem related to jobs system so I think that is the key of my problem....no wrong workitems in status "ready" others days than that one when we suffered that problem with jobs systems so pretty sure this is my case...
anyway, thanks a lot for your tips...if I found that my problem continues I will be sure of check what you are pointing me...
Thanks.
Miguel. -
SMWMQUEUES - what does status "ready" mean
SMWMQUEUES lists all outbound queues by name in CRM. All my queues are in status NOSEND . They currently can not conntrans so I am wondering if this is some indication that their site is not correctly identified. Does anyone know why all the othere queues are in status NOSEND and this one is READY ?
Many thanks MMPlease have a look at the note below and <b>reward points if it helps</b>
Basically, if the initial load is not successful, you should analyze queues and restart them if required. It makes sense to restart the initial load of an individual object if the analysis did not result in problems. Always log on to the CRM/EBP server in English to see the error texts. For notes on the delta data supply from the R/3 Backend system into the CRM server and the other way round, see the attached notes.
Error Detection - Tool Monitoring in the Middleware Menu:
a) Transaction R3AM1: Initial load monitor: After a successful initial load, all traffic lights should be "green".
b) Transaction SMWP: 'Middleware Portal':Under 'Runtime Information' -> 'Adapter Status Information' -> 'Initial Load Status', you can investigate the inbound and outbound queues and branch to the qRFC transactions from there. Below, the error analyses with access via the CRM Middleware Portal are described.
c) Transaction SMW01: Analysis of errors in the BDoc flow, in particular CRM/EBP application Customizing errors during the initial load into the CRM Server.
d) Transaction SMWT: Middleware trace with trace environment 'I':Display of additional information for each data block transferred.
Analysis
1. Ensure that the highest available plug-in (PI) Support Package plus Core Support Package is installed in the R/3 back-end system. The same applies to the CRM/EBP Server.
2. Transaction SM30:In the R/3 Back-end System, the correct RFC destination must be entered in table CRMRFCPAR for CONSUMER CRM. For this, see the documentation on the CRM Adapter Framework.
3. Transaction SM59:Test RFC connection - 'Remote login' from CRM/EBP to R/3 Back end and vice versa.
4. Transaction SMOEAC (Administration Console): Check the sites for R/3 systems. Have the RFC destinations been entered correctly and do the additional attributes exist? For this, see the documentation on the CRM Adapter Framework.
5. Transaction SMWP:Menu item 'Runtime information' -> 'Adapter Status Information' -> 'Initial Load Status':The subitems for the monitoring of the different inbound and outbound queues must each be evaluated in a similar way:
Double-click a queue entry to display the status of a queue (for example, READY, RUNNING, SYSFAIL). If you double-click again, you can see the cause of the error from the status text in the case of an error (SYSFAIL). Note: In case of temporary errors, it often helps to restart the queue (F6).
In general, a short dump occurs for status SYSFAIL. For the outbound queues, this short dump exists in the target system and not in the system in which the queue is. For inbound queues, the short dump exists in the same system as the inbound queue. For the initial data transfer between CRM and CDB or CRM and XML/ALE sites, the source and the target system are the same.
a) Menu option 'Load from OLTP systems:Start outbound queues in the CRM server':Status SYSFAIL in these outbound queues displays that a program termination occurred during the selection or the sending of data from an R/3 source system.If the program termination occurs in programs SAPLCRM0, SAPLCXML, SAPLCXMP, SAPLCTRK, SAPLCRMD, SAPLCGEN, SAPLCGNR, SAPLCFIL, SAPLCRMR, SAPLCRMS, SAPLCRMC and if you cannot solve the problem with the help of this note, send a customer message to component CRM-MW-ADP.In all other cases, choose the corresponding application component.
b) Menu item 'Load from CRM: Start outbound queues in the CRM server': Status SYSFAIL displays that a program termination occurred during the selection of data from the CRM for the CDB or a different site (for example, XML). Apart from that, the same applies as under the previous point.
c) Menu item 'Outbound queues in OLTP-R/3 System(s)':In general, these queues are only temporary because they are converted into inbound queues on the CRM Server. Consequently, they only exist if network errors, incorrect RFC connection parameters or database problems occur on the CRM server. If a restart of the queue is not successful, a short dump has occurred on the receiving side, the cause of which you must first correct. If the status of the queue is 'NOSENDS', the sending of data was blocked by mistake. This should never be set during live operation. To solve the problem, ensure that the HOLD_DATA field is initial in the CRMRFCPAR table. You can use Transaction SM30 to check or change this. In this transaction, it is the entry for the 'Save data' text. You must trigger existing queues with the status 'NOSENDS' manually. Afterwards, the processing of the outbound queue will occur automatically again.
d) Menu item 'Inbound queues on CRM server': In these queues, you find the data from the initial data transfer from an R/3 System. A SYSFAIL is by far the most frequent item in these queues. The reasons for this can be manifold. Program terminations in the CRM application due to missing or incorrect Customizing are the most frequent reason. To see detailed information on the errors which occurred, call Transaction SMW01 for the corresponding BDoc type. This is also required if there is no queue with errors that you can use to determine and analyze errors in any type of data transport. Short dumps may also occur due to real program errors. In this case, there is a corresponding short dump on the same system. If the error occurs in the SAPLSMOUTIL, SAPLSMO0 or SAPLSMOXML programs and if you cannot correct the error yourself, create a message for component CRM-MW-ADP. In all other cases, create a message for the corresponding component.
A possible error text in the inbound queue is "Error in Mapping (Details: Transaction SMW01)" (SMOF078). To correct this error, proceed as follows: Analyze and correct the error which is displayed in Transaction SMW01 at the error segments. You can find the correct BDoc message with the aid of the date and the time of the entry in the queue as well as with the BDoc status which is 'F05'. After you have corrected this problem, restart the inbound queue in order to process the entry. You can request help for correcting the error displayed in Transaction SMW01 in the corresponding application component.
e) Menu item 'Inbound queue on CRM server from CRM': These queues contain the data from the initial data transfer from the CRM Server to the CDB or other linked sites (for example, XML). For the error analysis, the same applies as for the previous menu item.
6. Logical system maintained in the CRM/EBP Server and in the R/3 Back end?
7. Transaction SMW01: Incorrect settings in the CRM/EBP application.In the selection screen, restrict the relevant period and, if required, the BDoc type.In the result of the selection, select the incorrect message and choose 'Display errors/error segments'.Here, you find notes on CRM/EBP application Customizing problems.
8. Transaction ST22: Short dumps on OLTP CRM/EBP Server
9. Transaction SE80:Syntax check for generated functions in development class $SAP_MSAGEN, for example function group /1CRMG0/PRDCT_OBJECT for product master. If a function group has syntax errors, it is often useful to regenerate it by using Transaction SMOGGEN.
Typical error messages and their solution:
Error 1654, for example for table space PSAPBTABI: Solution: add SAPDBA to the table space.
Timeout in R/3 back-end system during the initial download: Solution:See Note 162956
General performance problems during the initial download:See Note 350176
Inbound queue (SMQ2) on the CRM/EBP Server has status 'READY', but it is not processed. Solution:Restart the queue and check the registration of R3A, CRI in Transaction SMQR
The outbound queue in the R/3 Back-end System has status 'SYSFAIL', the detailed message is: Solution:shut down the CRM/EBP Server and restart it.If other SYSFAIL messages occur, restart the queue and analyze the short dumps.
RSQL error 13 when accessing table SMOTCURR:you should convert the data exchange between the R/3 Back end and the CRM Server to the XML format (see Note 333008).Then delete the inbound queue (in SMQ2, for example, R3AI_DNL_CUST_CURREN) and restart the object.
The number of data records between an R/3 Back-end table or a CRM table and the corresponding CRM CDB table do not match. Solution:Check the following:
Was the initial load completed successfully?
Are filters set for the object?
Note:Filters that are defined in the CRM Server must be defined in the form in which the data is stored in the source system in the database. For example, the filter for date 20010215 corresponds to a filter for February 15, 2001 (format YYYYMMDD).Make sure that the filter criteria are entered with leading digits, for example 10-digit customer numbers, 18-digit material numbers with leading zeros.
Are there error messages in Transaction SMW01 indicating rejections by the CRM server application?
Is the table a child table and are the excessive records orphaned child records that are not selected as well?
Should this delta data only be in the Customizing tables after the compare?
After you start the initial load using Transaction R3AS, the started object remains in status WAIT in Transaction R3AM1, and the initial download is not started. This is not an error.
The following causes are possible:
Too many objects already have status RUNNING or too many requests have been started or too many DIMa instances have been started and not completed. The number of running initial loads plus the number of running requests is the total number of all running initial-like processes. Therefore, this object must wait for the initial load or request of a different object to be completed. After an object is completed, a different object in status 'WAIT' is started automatically. If the initial load/request of the other objects is not completed, you can use this note to analyze why these are not completed and trigger their processing. You can change the maximum number of parallel initial loads using the MAX_PARALLEL_PROCESSES parameter in the SMOFPARSFA table. The standard value in the 'Param. Value' field is 5.
The object has a parent object whose initial load was not completed successfully. You can see from flag 'P' in Transaction R3AM1 whether an object has a parent object. You can see from table SMOFOBJPAR which objects these are.
No entry exists in one of the queues, but the status in R3AM1 remains 'Running':
This is probably because after the data selection in the source system, no reply was sent to the CRM system. If this is the case for one adapter object but not for others, contact the respective application component, which can analyze why the source system does not send a reply and correct the problem.
If this system response occurs for all adapter objects, create a message for component CRM-MW-ADP.
During the start of the initial load, the system displays the message "No initial load if COMPARE is active" or "No Initial Load if data distribution is active. Use Synchron. Load" (SMOF162):
In this case, start a synchronization load for the respective Adapter Object. -
Server0 doesnot start and stalls at "starting apps" status
The Server0 was running fine and suddenly started stalling at "starting apps" status. The SDM and Dispatcher are running fine. The Java_Home variable is set correctly and the System has 2GB RAM . The Developer Trace file is showing these errors after
"starting frameworks" step
[Thr 2440] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 2440] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
Fri Jan 12 13:49:07 2007
Full thread dump Java HotSpot(TM) Server VM (1.4.2_09-b05 mixed mode):
"SAPEngine_TREXRefreshCache_0" prio=10 tid=0x00fd0e90 nid=0x1674 waiting on condition [6caf000..6cafd90]
at java.lang.Thread.sleep(Native Method)
at com.sapportals.trex.util.cache.CacheFactory$RefreshThread.run(CacheFactory.java:522)
"SAPEngine_System_Thread[impl:5]_94" prio=5 tid=0x00fbe120 nid=0x166c in Object.wait() [6c5f000..6c5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590118> (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 <0x15590118> (a com.sap.engine.services.log_configurator.archive.Buffer)
at com.sap.engine.services.log_configurator.archive.ArchivingThread.run(ArchivingThread.java:34)
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]_93" prio=10 tid=0x00fbee00 nid=0x1670 in Object.wait() [6c1f000..6c1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"Timeout Service Integrity Watcher Thread" prio=10 tid=0x00fbd8c0 nid=0x1660 in Object.wait() [6bdf000..6bdfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590378> (a com.sap.engine.services.timeout.TimeoutIntegrityWatcher)
at com.sap.engine.services.timeout.TimeoutIntegrityWatcher.run(TimeoutIntegrityWatcher.java:69)
- locked <0x15590378> (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]_91" prio=10 tid=0x00fbc6d0 nid=0x1668 in Object.wait() [6b9f000..6b9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590458> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590458> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"Timeout Service Synchronous Internal Thread" prio=5 tid=0x00fbc980 nid=0x165c in Object.wait() [6b5f000..6b5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590610> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:589)
- locked <0x15590610> (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]_89" prio=5 tid=0x00fbce90 nid=0x1664 in Object.wait() [6b1f000..6b1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_88" prio=5 tid=0x00fba520 nid=0x1654 in Object.wait() [6adf000..6adfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_87" prio=10 tid=0x00fbae90 nid=0x1658 in Object.wait() [6a9f000..6a9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_86" prio=10 tid=0x00fb80e0 nid=0x1650 in Object.wait() [6a5f000..6a5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_85" prio=10 tid=0x00fb8760 nid=0x1638 in Object.wait() [6a1f000..6a1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590ad8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x15590ad8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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]_84" prio=10 tid=0x00fb7600 nid=0x164c in Object.wait() [69df000..69dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_83" prio=10 tid=0x00fb7c30 nid=0x1644 in Object.wait() [699f000..699fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_82" prio=10 tid=0x00fb6980 nid=0x1648 in Object.wait() [695f000..695fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590e98> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x15590e98> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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:105)
"Timeout Service Integrity Watcher Thread" prio=10 tid=0x00fb5490 nid=0x1640 in Object.wait() [691f000..691fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590fe8> (a com.sap.engine.services.timeout.TimeoutIntegrityWatcher)
at com.sap.engine.services.timeout.TimeoutIntegrityWatcher.run(TimeoutIntegrityWatcher.java:69)
- locked <0x15590fe8> (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]_80" prio=5 tid=0x00fb3950 nid=0x163c in Object.wait() [68df000..68dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (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=10 tid=0x00fb2770 nid=0x1630 in Object.wait() [689f000..689fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_78" prio=10 tid=0x00fb14b0 nid=0x1634 in Object.wait() [685f000..685fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591270> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591270> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_77" prio=10 tid=0x00fb0170 nid=0x161c in Object.wait() [681f000..681fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591400> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591400> (a com.sap.engine.core.service630.container.ServiceWrapper)
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=10 tid=0x00faf230 nid=0x1624 in Object.wait() [67df000..67dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591590> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x15591590> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_75" prio=5 tid=0x00fafcb0 nid=0x1628 in Object.wait() [679f000..679fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_74" prio=10 tid=0x00faea90 nid=0x162c in Object.wait() [675f000..675fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591740> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591740> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_73" prio=10 tid=0x00fad620 nid=0x1618 in Object.wait() [671f000..671fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155918e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155918e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_72" prio=10 tid=0x00fac460 nid=0x1620 in Object.wait() [66df000..66dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_71" prio=10 tid=0x00fab1d0 nid=0x1610 in Object.wait() [669f000..669fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_70" prio=10 tid=0x00faa150 nid=0x1614 in Object.wait() [665f000..665fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591c70> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591c70> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_69" prio=5 tid=0x00faad30 nid=0x1604 in Object.wait() [661f000..661fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (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=10 tid=0x00fa99f0 nid=0x160c in Object.wait() [65df000..65dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
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=10 tid=0x00fa8760 nid=0x15fc waiting on condition [659f000..659fd90]
at java.lang.Thread.sleep(Native Method)
at com.sap.caf.mp.core.svc.CAFMPCoreServiceFrame.initializePermissions(CAFMPCoreServiceFrame.java:502)
at com.sap.caf.mp.core.svc.CAFMPCoreServiceFrame.initializeService(CAFMPCoreServiceFrame.java:183)
at com.sap.caf.mp.core.svc.CAFMPCoreServiceFrame.start(CAFMPCoreServiceFrame.java:306)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
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:105)
"SAPEngine_System_Thread[impl:5]_65" prio=10 tid=0x00fa7430 nid=0x1608 in Object.wait() [655f000..655fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_66" prio=10 tid=0x00fa61a0 nid=0x1600 in Object.wait() [651f000..651fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591c70> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591c70> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_64" prio=5 tid=0x00fa6d50 nid=0x15f8 in Object.wait() [64df000..64dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (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=10 tid=0x00fa59f0 nid=0x15d8 in Object.wait() [649f000..649fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591270> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591270> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_62" prio=10 tid=0x00fa46a0 nid=0x15f4 in Object.wait() [645f000..645fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_61" prio=10 tid=0x00fa3410 nid=0x15c0 in Object.wait() [641f000..641fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155925e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155925e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_59" prio=10 tid=0x00fa2230 nid=0x15d0 in Object.wait() [63df000..63dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155925e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155925e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_60" prio=5 tid=0x00fa2cb0 nid=0x15e8 in Object.wait() [639f000..639fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (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=10 tid=0x00fa1a90 nid=0x15e0 in Object.wait() [635f000..635fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_57" prio=10 tid=0x00fa0590 nid=0x15c8 in Object.wait() [631f000..631fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155918e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155918e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_56" prio=10 tid=0x00f9f520 nid=0x15f0 in Object.wait() [62df000..62dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_55" prio=10 tid=0x00f9fe90 nid=0x15ec in Object.wait() [629f000..629fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_54" prio=10 tid=0x00f9ecb0 nid=0x15e4 in Object.wait() [625f000..625fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155918e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155918e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_53" prio=10 tid=0x00f9c0f0 nid=0x15dc in Object.wait() [621f000..621fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_52" prio=10 tid=0x00f9c7c0 nid=0x15d4 in Object.wait() [61df000..61dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15592fe8> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15592fe8> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_51" prio=10 tid=0x00f9b490 nid=0x15cc in Object.wait() [619f000..619fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_50" prio=10 tid=0x00f9be90 nid=0x15c4 in Object.wait() [615f000..615fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15593268> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15593268> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_49" prio=10 tid=0x00f9ad10 nid=0x15bc in Object.wait() [611f000..611fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_48" prio=10 tid=0x00f999f0 nid=0x15b8 in Object.wait() [60df000..60dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15593718> (a com.sap.engine.core.configuration.impl.cache.ConfigurationCache)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:856)
- locked <0x15593718> (a com.sap.engine.core.configuration.impl.cache.ConfigurationCache)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:694)
- locked <0x15593790> (a com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.createRedirConfig(P4ObjectBrokerServerImpl.java:313)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.postInit(P4ObjectBrokerServerImpl.java:254)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.postInit(P4ObjectBrokerServerImpl.java:1077)
at com.sap.engine.services.rmi_p4.P4ObjectBroker.<init>(P4ObjectBroker.java:298)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.<init>(P4ObjectBrokerServerImpl.java:110)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at com.sap.engine.services.rmi_p4.P4ObjectBroker.loadInstance(P4ObjectBroker.java:264)
- locked <0x50bc8c58> (a java.lang.Class)
at com.sap.engine.services.rmi_p4.P4ObjectBroker.init(P4ObjectBroker.java:159)
at com.sap.engine.services.rmi_p4.P4ObjectBroker.init(P4ObjectBroker.java:141)
at com.sap.engine.services.rmi_p4.server.ClusterOrganizer.<init>(ClusterOrganizer.java:69)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.<init>(P4SessionProcessor.java:80)
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.start(P4ServiceFrame.java:79)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
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]_47" prio=5 tid=0x00f98760 nid=0x15b0 in Object.wait() [609f000..609fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_45" prio=10 tid=0x00f82960 nid=0x15b4 in Object.wait() [605f000..605fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:117)
- locked <0x155928f8> (a com.sap.engine.core.service630.container.InterfaceWrapper)
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]_46" prio=5 tid=0x00f972f0 nid=0x15ac in Object.wait() [601f000..601fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_44" prio=10 tid=0x00f97880 nid=0x15a4 in Object.wait() [5fdf000..5fdfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_43" prio=10 tid=0x00f97ca0 nid=0x159c in Object.wait() [5f9f000..5f9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15593e88> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15593e88> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_42" prio=10 tid=0x00f962a0 nid=0x15a8 in Object.wait() [5f5f000..5f5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_41" prio=10 tid=0x00f96660 nid=0x1598 in Object.wait() [5ddf000..5ddfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594110> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15594110> (a com.sap.engine.core.service630.container.ServiceWrapper)
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:105)
"SAPEngine_System_Thread[impl:5]_40" prio=10 tid=0x00f96970 nid=0x15a0 in Object.wait() [5d9f000..5d9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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)
"SAPJarResourceCloseTimeoutThread" daemon prio=5 tid=0x00f92e90 nid=0x1588 in Object.wait() [5d5f000..5d5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594348> (a com.sap.engine.frame.core.load.res.JarThread)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.frame.core.load.res.JarThread.run(JarThread.java:32)
- locked <0x15594348> (a com.sap.engine.frame.core.load.res.JarThread)
"Thread-14" daemon prio=5 tid=0x00f80b30 nid=0x1488 in Object.wait() [5f1f000..5f1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155943e0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <0x155943e0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at com.sap.engine.cache.util.ReferenceQueueRunnable.run(ReferenceQueueRunnable.java:43)
at java.lang.Thread.run(Thread.java:534)
"Background Jobs Internal Thread" daemon prio=5 tid=0x00f7d5a0 nid=0x148c in Object.wait() [5edf000..5edfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594450> (a java.lang.Object)
at com.sap.engine.cache.job.impl.BackgroundExactImpl.run(BackgroundExactImpl.java:134)
- locked <0x15594450> (a java.lang.Object)
at java.lang.Thread.run(Thread.java:534)
"Timeout Service Integrity Watcher Thread" daemon prio=10 tid=0x00f7d220 nid=0x146c in Object.wait() [5e9f000..5e9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594500> (a com.sap.engine.cache.job.impl.IntegrityWatcher)
at com.sap.engine.cache.job.impl.IntegrityWatcher.run(IntegrityWatcher.java:54)
- locked <0x15594500> (a com.sap.engine.cache.job.impl.IntegrityWatcher)
at java.lang.Thread.run(Thread.java:534)
"Background Jobs Internal Thread" daemon prio=5 tid=0x00f7cc90 nid=0x1460 in Object.wait() [5e5f000..5e5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594588> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.cache.job.impl.BackgroundExactImpl.run(BackgroundExactImpl.java:115)
- locked <0x15594588> (a java.lang.Object)
at java.lang.Thread.run(Thread.java:534)
"Timeout Service Integrity Watcher Thread" daemon prio=10 tid=0x00f78310 nid=0x1450 in Object.wait() [5e1f000..5e1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594618> (a com.sap.engine.cache.job.impl.IntegrityWatcher)
at com.sap.engine.cache.job.impl.IntegrityWatcher.run(IntegrityWatcher.java:54)
- locked <0x15594618> (a com.sap.engine.cache.job.impl.IntegrityWatcher)
at java.lang.Thread.run(Thread.java:534)
"SeedGenerator Thread" daemon prio=2 tid=0x00f74330 nid=0x12e8 in Object.wait() [5d1f000..5d1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155946a0> (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 <0x155946a0> (a sun.security.provider.SeedGenerator$ThreadedSeedGenerator)
at java.lang.Thread.run(Thread.java:534)
"SAPEngine_EnquReader" prio=5 tid=0x00f65e90 nid=0x120c runnable [5cdf000..5cdfd90]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.sap.bc.krn.enqu.EncomiHandle.ReceiveMessage(EncomiHandle.java:483)
- locked <0x15594748> (a java.lang.Object)
at com.sap.bc.krn.enqu.EnccliMultiplexHandle.receive(EnccliMultiplexHandle.java:771)
at com.sap.bc.krn.enqu.ReadRunnable.run(EnccliMultiplexHandle.java:958)
at java.lang.Thread.run(Thread.java:534)
"SAP J2EE Engine|MS Ping Thread" prio=5 tid=0x00f638f0 nid=0x11c0 waiting on condition [5c9f000..5c9fd90]
at java.lang.Thread.sleep(Native Method)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection$MSPingRunner.run(MSRawConnection.java:2383)
at java.lang.Thread.run(Thread.java:534)
"SAPEngine_System_Thread[impl:5]_39" prio=10 tid=0x00f59460 nid=0x1160 in Object.wait() [5c5f000..5c5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15592fe8> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15592fe8> (a com.sap.engine.core.service630.container.ServiceWrapper)
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)
"Timeout Service Internal Thread" prio=5 tid=0x00f59e90 nid=0x115c in Object.wait() [5c1f000..5c1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594970> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.services.timeout.TimeoutManagerImpl.multiThreadRun(TimeoutManagerImpl.java:476)
- locked <0x15594970> (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]_37" prio=5 tid=0x00f57180 nid=0x1158 in Object.wait() [5bdf000..5bdfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_36" prio=10 tid=0x00f56090 nid=0x1154 in Object.wait() [5b9f000..5b9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15594ad0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15594ad0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_35" prio=10 tid=0x00f56690 nid=0x1150 in Object.wait() [5b5f000..5b5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_34" prio=10 tid=0x00f552f0 nid=0x114c in Object.wait() [5b1f000..5b1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590c28> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_33" prio=10 tid=0x00f55e00 nid=0x1148 in Object.wait() [5adf000..5adfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_32" prio=5 tid=0x00f54810 nid=0x1144 in Object.wait() [5a9f000..5a9fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
- locked <0x15590748> (a com.sap.engine.lib.util.WaitQueue)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:127)
"SAPEngine_System_Thread[impl:5]_31" prio=10 tid=0x00f520b0 nid=0x1140 in Object.wait() [5a5f000..5a5fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15591400> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15591400> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_30" prio=10 tid=0x00f523c0 nid=0x113c in Object.wait() [5a1f000..5a1fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155925e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155925e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_29" prio=10 tid=0x00f52e90 nid=0x1138 in Object.wait() [59df000..59dfd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x15590868> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_28" prio=10 tid=0x00f519d0 nid=0x1134 in Object.wait() [599f000..599fd90]
at java.lang.Object.wait(Native Method)
- waiting on <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
at java.lang.Object.wait(Object.java:429)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:92)
- locked <0x155901e0> (a com.sap.engine.core.service630.container.ServiceWrapper)
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]_27" prio=10 tid=0x00f50510 nid=0x1130 in Object.wait()Hi ,
We are facing the same kind of problem in our PI 7.0 Development system.
Its J2EE Server node got stuck into a server starting loop.
The error message is as follows.
[Thr 3372] JLaunchISetState: change state from [Starting (2)] to
[Starting applications (10)]
[Thr 6208] JLaunchIExitJava: exit hook is called (rc = 666)
[Thr 6208]
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 6208] JLaunchCloseProgram: good bye (exitcode = 666)
Is anybody having solution for this problem?
Regards,
Nilesh -
Logical drive 1 status = Ready for recovery ml350 g5
Hi,
I have a problem with a HP Proliant ML350 G5, 2 weeks ago the server did shutdown unexpectedly i looked in the ACU and saw that the controller had a battery problem. I replaced the battery but the server keeps once or twice a day shutting down. I made a report from the ACU but i don't know what this all means.
Here is a part of the report, i hope someone can lead me to the right solution,
Thanks in advance.
Array Diagnostic Utility Version 7.85.16.0
Array Diagnostic Utility Inspection Report Version 7.85.16.0
Date/Time: Friday, June 27, 2014 3:43:11PM
Computer Model: HP Server
SLOT SUMMARY:
Slot Num Slot Type Array Controllers and Host Adapters Detected
SLOT 0 PCI Smart Array E200i Controller
SLOT 0 Smart Array E200i Controller ERROR REPORT:
Logical drive 1 status = Ready for recovery
SUBSYSTEM INFORMATION:
Chassis Serial Num: GB87494LT1
This Controller
Array Serial Number: QT79MU6382
Cache Serial Number: P9A3A0B9SV00ST
Other Controller
Array Serial Number: Not Available
Cache Serial Number: Not Available
CONTROLLER IDENTIFICATION:
Configured Logical Drives: 1
Configuration Signature: 0xa00004c9
Controller Firmware Rev: 1.66
Controller ROM Revision: 1.66
Controller Hardware Rev: 0x00
Boot Block Version: 1.66
Board ID: 0x3211103c
Cable or Config Error: 0x00 (No)
Invalid Host RAM Address: No
CPU Revision: 0x00
CPU to PCI ASIC Rev: 0x00
Cache Controller ASIC Rev: 0x00
PCI to Host ASIC Rev: 0x00
Marketing Revision: 0x41 (Rev A)
Expand Disable Code: 0x01
Protocol Chip Count: 1
Enclosure Count: 3
Max SCSI IDs per Bus: 0
Big Drive Map: 0x000c 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Ext Drive Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Non-Disk Drive Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Fibre Chip Count: 0
Recovery ROM Inactive
Image Revision:
Recovery ROM Active Image
Flags Status: 0x10
Battery PIC Rev: 0x20
NCQ: Not Supported
LOGICAL DRIVE IDENTIFICATION:
Logical Drive 1:
Sector Size: 512
Sectors Available: 143305920
Fault Tolerance Mode: Mirroring
Logical Param Table: cyl=17562 heads=255 sec/track=32 xlate sig=0x0
BIOS Disabled: No
Logical Drive Ident: 0x 0
Logical Drive Label: A00004C9QT79MU6382 678E
LOGICAL DRIVE CONFIGURATION:
Logical Drive 1:
Configuration Signature: 0xa00004c9
Mapping Scheme: Multiple Block
Physical Drives: 2 (number not valid after drive movement)
This Logical Drive: 2 (excluding spare drives)
Fault Tolerance Mode: Mirroring
Logical Param Table: cyl=17562 heads=255 sec/track=32 xlate sig=0x0
Distribution Factor: 256
Operating System: 64768
Controller Order: 0
Additional Information: 0
Offset to Data: 0
Int 13h Support Enabled: Yes
Sectors on Volume: 143305920
Sectors per Drive: 143305920
Big Drive Assignment Map: 0x000c 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Spare Assignment Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Array Accelerator is enabled for this logical drive.
LOGICAL DRIVE STATUS:
Logical Drive 1:
Drive Status: Ready for recovery
Blocks to Rebuild: 0
Blocks Re-mapped:
Spare Status Flags: 0x00
Spare to Replaced Map: See Big Spare to Replace Map:
Media Was Exchanged: No
Cache Failure: No
Expand Failure: 0x00
Unit Flags: 0x00
Big Remap Count: All Counts Zero
Big Drive Failure Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Replacement Drive Map: 0x0004 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Active Spare Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Spare to Replace Map: No spares have replaced any drives
Big Spare Marked OK Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
MONITOR AND PERFORMANCE DATA:
Port 1I, Box 1, Bay 2
Factory: Serial #, Firmware Rev, and Mfg/Model #:
33 4e 50 32 34 36 59 30 30 30 30 30 39 38 31 36 3NP246Y000009816
51 35 58 4e 48 50 44 37 00 00 00 00 48 50 20 20 Q5XNHPD7....HP
20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20 DG072ABAB3
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Since Power: Serial #, Firmware Rev, and Mfg/Model #:
33 4e 50 32 34 36 59 30 30 30 30 30 39 38 31 36 3NP246Y000009816
51 35 58 4e 48 50 44 37 00 00 00 00 48 50 20 20 Q5XNHPD7....HP
20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20 DG072ABAB3
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Serial Number Control: 0x0054
Firmware Revision Control: 0x0248
Mfg/Model Number Control: 0x0268
Factory Since Power Threshold Control
Serv. Time 00341415 000001d4 00000000 2104
Read Blks 0000001788c34d46 00000000000002b1 0108
Hrd Read 00000485 00000000 00000000 2104
Rtry Read 00000000 00000000 00000000 2104
ECC Read 000000000000000d 0000000000000000 0000000000000000 2108
Write Blks 00000006c04e371c 0000000000ffcf08 0108
Hrd Write 00000000 00000000 00000000 2104
Rtry Write 00000006 00000000 00000000 2104
Seeks 0000000000000000 0000000000000000 0808
Seek Errs 0000000000000000 0000000000000000 0000000000000000 0808
Spin Cyls 00000000 00000000 00000000 2104
Spin Time 0000 0000 0000 2202
Test 1 0000 0000 0000 0802
Test 2 0000 0000 0000 0802
Test 3 0000 0000 0000 0802
Test 4 0000 0000 0000 0802
Spare Blks ffffffff ffffffff 0a04
Re-mapped 0000009b 00000000 00000000 2504
DRQ Tmots 0000 0000 0000 0802
Timeouts 0000 0000 0000 2102
Rebuilds 0002 0000 0000 2102
Spn Retrs ffff ffff 0000 2902
Fl Rd Recv 0000 0000 0000 2102
Fl Wt Recv 0000 0000 0000 2102
Format Err 0000 0000 0000 2102
POST Err 0000 0000 0000 0802
Drv Nt Ry 00000000 00000000 00000000 2104
Reallc Abt 00000000 00000000 00000000 0804
IRQ Gltchs 00000000 00000000 00000000 0804
Bus Flts 00000054 00000001 00000000 2104
Hot Plgs 00000000 00000000 00000000 2104
Tk Rwt Err ffff ffff 0000 2902
Rmp Wt Err 0000 0000 0000 2102
Bg Fw Rev 0000000000000000 0000000000000000 0848
Med Flrs 0000 0000 0000 2102
Hrdw Errs 0007 0000 0000 2102
Abt Cmd Fl 0000 0000 0000 2102
Spn Up Fl 0000 0000 0000 2102
Bd Tgt Cnt 0000 0000 0000 2102
Pred Fails 00000000 00000000 00000000 2104
DRIVE ERROR LOG:
Error Log Header:
Parameter Length = 0x14
Entry Size = 0x0040
Current Entry = 0x1c
Total Errors Logged = 0x0000021c
Error Log Data:
SCSI CAM Sense Sense
Stat Stat Key Code Qual Block(Vl) Time Op Info
02 04 06 29 02 00000000(0) 002f200b 00 0000
02 04 06 29 02 00000000(0) 002f477e 00 0000
02 04 06 29 02 00000000(0) 0030a78b 00 0000
02 04 06 29 02 00000000(0) 00311fd3 00 0000
02 04 06 29 02 00000000(0) 00316ebf 00 0000
00 0a 00 00 00 00000000(0) 00317117 00 0000
02 04 06 29 02 00000000(0) 0032043a 00 0000
02 04 06 29 02 00000000(0) 00329e1f 00 0000
02 04 06 29 02 00000000(0) 0032c9aa 00 0000
02 04 06 29 02 00000000(0) 0033b5c4 00 0000
00 0a 00 00 00 00000000(0) 0033e304 00 0000
00 0a 00 00 00 00000000(0) 0033e430 00 0000
00 22 00 00 00 3f000000(0) 0033e509 5a 0000
00 0a 00 00 00 00000000(0) 0033eec2 00 0000
00 0a 00 00 00 00000000(0) 0033f285 00 0000
00 0a 00 00 00 00000000(0) 0033f4f2 00 0000
00 0a 00 00 00 00000000(0) 0033f6d2 00 0000
00 0a 00 00 00 00000000(0) 0033fe90 00 0000
00 0a 00 00 00 00000000(0) 0034003c 00 0000
00 0a 00 00 00 00000000(0) 003402d0 00 0000
Port 1I, Box 1, Bay 1
Factory: Serial #, Firmware Rev, and Mfg/Model #:
33 4e 50 32 46 41 57 38 30 30 30 30 39 38 33 30 3NP2FAW800009830
32 39 41 52 00 00 00 00 00 00 00 00 48 50 20 20 29AR........HP
20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20 DG072ABAB3
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Since Power: Serial #, Firmware Rev, and Mfg/Model #:
33 4e 50 32 46 41 57 38 30 30 30 30 39 38 33 30 3NP2FAW800009830
32 39 41 52 48 50 44 43 00 00 00 00 48 50 20 20 29ARHPDC....HP
20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20 DG072ABAB3
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Serial Number Control: 0x0054
Firmware Revision Control: 0x0248
Mfg/Model Number Control: 0x0268
Factory Since Power Threshold Control
Serv. Time 00055b43 000001d4 00000000 2104
Read Blks 000000029c28733f 0000000001e70b56 0108
Hrd Read 00000000 00000000 00000000 2104
Rtry Read 00000000 00000000 00000000 2104
ECC Read 0000000000000000 0000000000000000 0000000000000000 2108
Write Blks 00000000c7b62ee8 0000000000ffcf36 0108
Hrd Write 00000000 00000000 00000000 2104
Rtry Write 00000000 00000000 00000000 2104
Seeks 0000000000000000 0000000000000000 0808
Seek Errs 0000000000000000 0000000000000000 0000000000000000 0808
Spin Cyls 00000000 00000000 00000000 2104
Spin Time 0000 0000 0000 2202
Test 1 0000 0000 0000 0802
Test 2 0000 0000 0000 0802
Test 3 0000 0000 0000 0802
Test 4 0000 0000 0000 0802
Spare Blks ffffffff ffffffff 0a04
Re-mapped 00000000 00000000 00000000 2504
DRQ Tmots 0000 0000 0000 0802
Timeouts 0000 0000 0000 2102
Rebuilds 0001 0000 0000 2102
Spn Retrs ffff ffff 0000 2902
Fl Rd Recv 0000 0000 0000 2102
Fl Wt Recv 0000 0000 0000 2102
Format Err 0000 0000 0000 2102
POST Err 0000 0000 0000 0802
Drv Nt Ry 00000000 00000000 00000000 2104
Reallc Abt 00000000 00000000 00000000 0804
IRQ Gltchs 00000000 00000000 00000000 0804
Bus Flts 00000004 00000001 00000000 2104
Hot Plgs 00000000 00000000 00000000 2104
Tk Rwt Err ffff ffff 0000 2902
Rmp Wt Err 0000 0000 0000 2102
Bg Fw Rev 0000000000000000 0000000000000000 0848
Med Flrs 0000 0000 0000 2102
Hrdw Errs 0000 0000 0000 2102
Abt Cmd Fl 0000 0000 0000 2102
Spn Up Fl 0000 0000 0000 2102
Bd Tgt Cnt 0000 0000 0000 2102
Pred Fails 00000000 00000000 00000000 2104
DRIVE ERROR LOG:
Error Log Header:
Parameter Length = 0x14
Entry Size = 0x0040
Current Entry = 0x1f
Total Errors Logged = 0x0000001f
Error Log Data:
SCSI CAM Sense Sense
Stat Stat Key Code Qual Block(Vl) Time Op Info
02 04 06 29 02 00000000(0) 00000000 00 0000
02 04 06 29 02 00000000(0) 00000001 00 0000
02 04 06 29 02 00000000(0) 00006731 00 0000
02 04 06 29 02 00000000(0) 00008ea4 00 0000
02 04 06 29 02 00000000(0) 0001eeb1 00 0000
02 04 06 29 02 00000000(0) 000266f9 00 0000
02 04 06 29 02 00000000(0) 0002b5e5 00 0000
02 04 06 29 02 00000000(0) 0002b83d 00 0000
02 04 06 29 02 00000000(0) 00034b60 00 0000
02 04 06 29 02 00000000(0) 0003e545 00 0000
02 04 06 29 02 00000000(0) 000410d0 00 0000
02 04 06 29 02 00000000(0) 0004fcea 00 0000
02 04 06 29 02 00000000(0) 00052a2a 00 0000
02 04 06 29 02 00000000(0) 00052b56 00 0000
00 22 00 00 00 3f000000(0) 00052c2f 5a 0000
02 04 06 29 02 00000000(0) 000535e8 00 0000
02 04 06 29 02 00000000(0) 000539ab 00 0000
02 04 06 29 02 00000000(0) 00053c18 00 0000
02 04 06 29 02 00000000(0) 00053df8 00 0000
02 04 06 29 02 00000000(0) 000545b6 00 0000Hi QUANT,
Your Proliant server is a commercial product and to get your issue more exposure I would suggest posting in the commercial forums. Here is a link to the Commercial Notebook forum.
Thank you,
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP -
Hello All,
I have created a control step to trigger alert for success condition in BPM after send step.
When i executed the BPM status ready is showing for the control step in workflow logs.
Will it get executed? Otherwise is there anything else to be added for this to get executed.
Thanks in Advance
RajeshHi Rajesh,
That means it is still waiting for condition to be met. Try checking the technical details of the same. you can use Goto->technical details and check where it is waiting.
Else you can add a switch step in BPM and put the control step in one branch and cancel in the other . So, in that case atleast one of them will execute and you will come to know what the error is?
Regards,
Sachin -
Mail stuck in wf_notification_out with status = ready
Hi All,
Please help on workflow mailer .
EBS R12 12.1.3 DB:11GR2 OS: OUL5X64
when sending a test mail and verify with this script below , i could see the message was in wf_notification_out table with status READY
BUT IT JUST SAT THERE AND NEVER GOES ANYWHERE.
SELECT n.begin_date,
n.status,
n.mail_status,
n.recipient_role,
de.def_enq_time,
de.def_deq_time,
de.def_state,
ou.out_enq_time,
ou.out_deq_time,
ou.out_state
FROM applsys.wf_notifications n,
(SELECT d.enq_time def_enq_time,
d.deq_time def_deq_time,
TO_NUMBER((SELECT VALUE
FROM TABLE(d.user_data.parameter_list)
WHERE NAME = 'NOTIFICATION_ID')) d_notification_id,
msg_state def_state
FROM applsys.aq$wf_deferred d
WHERE d.corr_id = 'APPS:oracle.apps.wf.notification.send') de,
(SELECT o.deq_time out_deq_time,
o.enq_time out_enq_time,
TO_NUMBER((SELECT str_value
FROM TABLE(o.user_data.header.properties)
WHERE NAME = 'NOTIFICATION_ID')) o_notification_id,
msg_state out_state
FROM applsys.aq$wf_notification_out o) ou
WHERE n.notification_id = &NOTIFICATION_ID
AND n.notification_id = de.d_notification_id(+)
AND n.notification_id = ou.o_notification_id(+);
Here was the result.
BEGIN_DATE STATUS MAIL_STATUS RECIPIENT_ROLE DEF_ENQ_T DEF_DEQ_T DEF_STATE OUT_END_TIME OUT_DEQ_TIME OUT_STATE
11-JUN-12 OPEN MAIL TEST.USER 11-JUN-12 11-JUN-12 PROCESSED 11-JUN-12 READY
Please advise it i miss anything. This was working before.
Thanks in advance.Please advise it i miss anything. This was working before.Can you find any errors in the Database and Workflow log files?
Troubleshooting Workflow Java Notification Mailer - Technical Reference [ID 1191125.1]
A Guide For Troubleshooting Workflow Notification Emails - Inbound and Outbound [ID 831982.1]
How To Troubleshoot Java-based Workflow Notification Mailer [ID 242941.1]
Troubleshooting Inbound & Outbound Email Notifications [ID 1184846.1]
OWF H Diagnostics, Solutions and Information [ID 332152.1]
Oracle Workflow Release 12 Diagnostics [ID 469822.1]
Thanks,
Hussein -
Workflow problem with status Ready
HI,
I have a problem with the workflow not getting completed.
The workflow is for the employee attendace 20000081 .
After the manager of the employee accepts the leave application posted by employee , The workflow is in the following state: -
ID 000000340552 Work item type Background step
Work Item text Find Employee .
Status <b>Ready</b>
Now the question is there any background job which needs to be scheduled for changing the all the workitem with status 'Ready' to be executed .
since once I execute this step manually then the workflow again goes in the ready status with the next step and the next step in this case is 'Create attendance/absence' This stpe of the workflow is in again status 'Ready'.
Please let me know if some know about this problem.
Thanks in advance .
AnkurHi ,
Thanks for the prompt reply.
I have tried the auto customizing and I am geeting the following log generated :
Auto-Customizing: General tasks
E WZ:119 Instances for task TS60001307 already exist
Task TS60001307 not classified as general task
E WZ:119 Instances for task TS70008037 already exist
Task TS70008037 not classified as general task
E WZ:119 Instances for task TS70008125 already exist
Task TS70008125 not classified as general task
And while checking the customizing setting in SWU3 the folling entires exists but as I understand the seeting is proper, please have alook below:
An active plan version exists
Workflow administrator maintained
RFC destination: User locked
Generic decision task classified completely
Tasks for document generation fully classified
T77* tables all available
Monitoring job for missed deadlines is scheduled
Monitoring job for work items with errors is scheduled
Sending to objects and HR objects activated
Entries missing in PD control tables
Default Domain for Internet Mail Maintained
Workflow development environment
Customizing incomplete
Prefix numbers for standard object types maintained
An active plan version exists
T77* tables all available
Number range defined for customer tasks
Entries missing in PD control tables
Please let me know if this is not proper .
Thanks and Regards,
Ankur -
hi experts
we are experimenting an strange situation when the crm - internet sails receive an order. If there are any inbound queue in status ready (R3AD_*), the order is not received in the erp system.
if the queue R3AD_ (number of customer) is unlocked, the BDOC can be processed.
additionally, these queues (R3AD*) remains in the same status ready indefinitely unless are unlocked by hand
any suggestion?
thanks in advanceHi Chan
The queue R3A* is already registered.
When we have a internet sales order, there is a bdoc in yellow.( bdoc type Bus_trans_msg and the queue name is CSA_ORDER_....)
The queue CSA* is registered too.
At the same time, a new queue entry in the smq2 (CRM). this queue is R3AD_00... (the account number who makes the internet order)
This queue is in status ready.
If I try to process the Bdoc. A message says "R3 adapter is called". The order doesn´t distribute to R3.
I active manually the queue R3AD_000(account number), and then I can process the bdoc.
Why this queue is in status ready and doesn´t process automatically?
Thanks -
Application install starts but status is failed
Hi guys,
I'm running into an issue where I'm deploying Microsoft Office 2010 Pro and although the install starts the status in Software Center is "Failed". Once application finishes installing and I click on "Reply" button status changes to "Installed".
This seems to happen only with this software.
The fail error code is: 0x87D00324(-2016410844).
Doing a search on the forums I see that people are suggesting to try a different detection methods for my deployment and I have tried different ones but to no luck. I also tried starting the install by launching .exe and .msi but that didn't make a difference.
Do you guys have any suggestions?
Steve+++ Starting Install enforcement for App DT "Microsoft Office 2010 Pro" ApplicationDeliveryType - ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision - 2, ContentPath - C:\Windows\ccmcache\1, Execution Context - System AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
A user is logged on to the system. AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Performing detection of app deployment type Microsoft Office 2010 Pro(ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, revision 2) for system. AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
+++ Application not discovered. [AppDT Id: ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision: 2] AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
App enforcement environment:
Context: Machine
Command line: setup.exe
Allow user interaction: Yes
UI mode: 1
User token: null
Session Id: 2
Content path: C:\Windows\ccmcache\1
Working directory: AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Prepared working directory: C:\Windows\ccmcache\1 AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Prepared command line: "C:\Windows\ccmcache\1\setup.exe" AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Executing Command line: "C:\Windows\ccmcache\1\setup.exe" with user context AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Working directory C:\Windows\ccmcache\1 AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Post install behavior is BasedOnExitCode AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Waiting for process 4340 to finish. Timeout = 120 minutes. AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Process 4340 terminated with exitcode: 0 AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Looking for exit code 0 in exit codes table... AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Matched exit code 0 to a Success entry in exit codes table. AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
Performing detection of app deployment type Microsoft Office 2010 Pro(ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, revision 2) for system. AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
+++ Application not discovered. [AppDT Id: ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision: 2] AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
++++++ App enforcement completed (0 seconds) for App DT "Microsoft Office 2010 Pro" [ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977], Revision: 2, User SID: ] ++++++ AppEnforce 9/4/2014 10:33:53 AM 1576 (0x0628)
+++ Starting Uninstall enforcement for App DT "Microsoft Office 2010 Pro" ApplicationDeliveryType - ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision - 2, ContentPath - C:\Windows\ccmcache\1, Execution Context - System AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
A user is logged on to the system. AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Performing detection of app deployment type Microsoft Office 2010 Pro(ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, revision 2) for system. AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
+++ Discovered application [AppDT Id: ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision: 2] AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
App enforcement environment:
Context: Machine
Command line: msiexec /x "x86\ProPlus.WW\ProPlusWW.msi"
Allow user interaction: Yes
UI mode: 1
User token: null
Session Id: 2
Content path: C:\Windows\ccmcache\1
Working directory: AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Prepared working directory: C:\Windows\ccmcache\1 AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Prepared command line: "C:\Windows\system32\msiexec.exe" /x "x86\ProPlus.WW\ProPlusWW.msi" AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Executing Command line: "C:\Windows\system32\msiexec.exe" /x "x86\ProPlus.WW\ProPlusWW.msi" with user context AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Working directory C:\Windows\ccmcache\1 AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Post install behavior is BasedOnExitCode AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Waiting for process 2688 to finish. Timeout = 120 minutes. AppEnforce 9/4/2014 11:11:30 AM 4496 (0x1190)
Process 2688 terminated with exitcode: 1603 AppEnforce 9/4/2014 11:11:47 AM 4496 (0x1190)
Looking for exit code 1603 in exit codes table... AppEnforce 9/4/2014 11:11:47 AM 4496 (0x1190)
Unmatched exit code (1603) is considered an execution failure. AppEnforce 9/4/2014 11:11:47 AM 4496 (0x1190)
++++++ App enforcement completed (16 seconds) for App DT "Microsoft Office 2010 Pro" [ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977], Revision: 2, User SID: ] ++++++ AppEnforce 9/4/2014 11:11:47 AM 4496 (0x1190)
+++ Starting Uninstall enforcement for App DT "Microsoft Office 2010 Pro" ApplicationDeliveryType - ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision - 2, ContentPath - C:\Windows\ccmcache\1, Execution Context - System AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
A user is logged on to the system. AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Performing detection of app deployment type Microsoft Office 2010 Pro(ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, revision 2) for system. AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
+++ Discovered application [AppDT Id: ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977, Revision: 2] AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
App enforcement environment:
Context: Machine
Command line: msiexec /x "x86\ProPlus.WW\ProPlusWW.msi"
Allow user interaction: Yes
UI mode: 1
User token: null
Session Id: 2
Content path: C:\Windows\ccmcache\1
Working directory: AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Prepared working directory: C:\Windows\ccmcache\1 AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Prepared command line: "C:\Windows\system32\msiexec.exe" /x "x86\ProPlus.WW\ProPlusWW.msi" AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Executing Command line: "C:\Windows\system32\msiexec.exe" /x "x86\ProPlus.WW\ProPlusWW.msi" with user context AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Working directory C:\Windows\ccmcache\1 AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Post install behavior is BasedOnExitCode AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Waiting for process 1544 to finish. Timeout = 120 minutes. AppEnforce 9/4/2014 11:11:55 AM 4496 (0x1190)
Process 1544 terminated with exitcode: 1618 AppEnforce 9/4/2014 11:12:06 AM 4496 (0x1190)
Looking for exit code 1618 in exit codes table... AppEnforce 9/4/2014 11:12:06 AM 4496 (0x1190)
++++++ App enforcement completed (11 seconds) for App DT "Microsoft Office 2010 Pro" [ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_390a03d8-32b9-4622-88ce-d3e201274977], Revision: 2, User SID: ] ++++++ AppEnforce 9/4/2014 11:12:07 AM 4496 (0x1190)
+++ Starting Install enforcement for App DT "CMTrace" ApplicationDeliveryType - ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_355e20a1-4f9d-443a-8a6d-7e0c9df56fc6, Revision - 1, ContentPath - C:\Windows\ccmcache\2, Execution Context - User AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
A user is logged on to the system. AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Performing detection of app deployment type CMTrace(ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_355e20a1-4f9d-443a-8a6d-7e0c9df56fc6, revision 1) for user. AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
+++ Application not discovered. [AppDT Id: ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_355e20a1-4f9d-443a-8a6d-7e0c9df56fc6, Revision: 1] AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
App enforcement environment:
Context: User
Command line: "install.bat"
Allow user interaction: Yes
UI mode: 1
User token: not null
Session Id: 2
Content path: C:\Windows\ccmcache\2
Working directory: AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Prepared working directory: C:\Windows\ccmcache\2 AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Prepared command line: "C:\Windows\ccmcache\2\install.bat" AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Executing Command line: "C:\Windows\ccmcache\2\install.bat" with user context AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Working directory C:\Windows\ccmcache\2 AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Post install behavior is BasedOnExitCode AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Waiting for process 5028 to finish. Timeout = 120 minutes. AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Process 5028 terminated with exitcode: 0 AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Looking for exit code 0 in exit codes table... AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Matched exit code 0 to a Success entry in exit codes table. AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
Performing detection of app deployment type CMTrace(ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_355e20a1-4f9d-443a-8a6d-7e0c9df56fc6, revision 1) for user. AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
+++ Discovered application [AppDT Id: ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_355e20a1-4f9d-443a-8a6d-7e0c9df56fc6, Revision: 1] AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
++++++ App enforcement completed (0 seconds) for App DT "CMTrace" [ScopeId_352419C3-121B-4F48-A71E-DAC7E1D9A151/DeploymentType_355e20a1-4f9d-443a-8a6d-7e0c9df56fc6], Revision: 1, User SID: S-1-5-21-1792559092-1865782889-1767051203-1000] ++++++ AppEnforce 9/4/2014 11:14:12 AM 4596 (0x11F4)
The weird thing is that the Failed status is as soon as the application starts installing. I just run setup.exe in the command line. -
Queues, not processed automatically they are status Ready
Hi Experts ,
Queues in outbound(smq2), not processed automatically they are status Ready from long time, RFC is working fine
i tried to process maually one by one ,but they are many.
how can i execute this , need your inputs.
thanks in advance
vamsiCheck that the scheduler is running in SMQR
Read,
http://help.sap.com/saphelp_nw04s/Helpdata/EN/e4/df5f3c8dde1c67e10000000a114084/content.htm
Regards
Juan -
Hi
I am replicating campaigns from CRM to PS. Now as I release the campaign BDOC is triggered and goes to backend ECC system. But after replication BDOC comes and stops in inbound queue of CRM with status ready. When I goto SMQ2 and unlock it, it flows through.
This problem I am facing for all campaigns transfered not for any specific one.
Please help me in resolving this issue.
Thanx in advance.
Cheers
HitsHi,
This happens because the Queues are not registered.
In SMQ2, note the first 3 cahracters of the queue, e.g, R3A or CSA.
Now goto SMQR and see if any Queue exists with this name like R3A* or CSA*.
If it does, then select the Queue and press button Registration.
If it does not, tehn create a new entry by pressing the same registration button and entering the following value:
Queue name CSA*
EXEMODE D
MAXTIME 60
USERDEST
NRETRY 30
TDELAY 300
Doing this is sufficient for your Queue to get executed automatically.
Kindly reward with points in case helpful.
Sharif. -
SMQ2 - Many entries status "ready"
Hi experts,
we have many entries in transaction SMQ2 with status "ready".
Can someone post a guide or explain what this means please?
Would be great.
I've also checked SMQR and there I found the status "inactive" byHi,
Because of this messages all the remaining were in READY status. due to the error you mentioned above, this message was stuck and blocked all the remaining messages. were all the remaining messages processed now?
BDoc Conversion is not completed successfully
Execute report CRM40_MW_BDOC_TADIR_CONVERSION to finish the upgrade.
No generation performed. Call transaction GN_START.
Middleware stopped.
As mentioned above I think you need to execute the report. As I am BASIS guy, I can suggest you on how to clear the queue.
regarding any functional issue, please wait for functional experts suggestions.
Regards,
Venkata S Pagolu
Edited by: Venkata Pagolu on Feb 21, 2012 12:49 PM
Maybe you are looking for
-
Download Firefox4 but keep getting told I am only running 3.6. Why
Several times I have downloaded Firefox 4 but I still get a message saying I am only operating on Firefox 3.6. I don't know why this should be4
-
event s schedule to repeat every week between sept and december, show fine in my iCal, but my new iPod copies it for EVERY DAY for that time period, rather then once a week, as it correctly shows in the iCal. I tried deleting and re-entering - same t
-
OS and databas time setting with sysdate value
Hi Experts: Oracle claims "SYSTIMESTAMP returns the system date, including fractional seconds and time zone, of the system on which the database resides. The return type is TIMESTAMP WITH TIME ZONE." Last week on this site, I got the confirmation tha
-
Calling portal screen from workflow and required two level approvals to approve in portal
Hello Experts, I have a requirement that, I would trigger a process order approval workflow from SRM SUS portal. Agent when he clicks the link in the attached mail, it has to take him to the portal screen to approve and it has to go to next level man
-
Stop quicktime playing downloaded video files
Hi How do I stop QuickTime from automatically playing video files that I have downloaded in Safari? I'm sure it's simple but just haven't found it out yet Thx