How to wait for events to happen without using sleeps.

hi,
I am basically doing Thread.sleep() for waiting the events to complete.
For example, when i click on query button, it takes sometime to process in the background & then populate the data in my table.
So i am using the sleep method for this event to finish.
I feel this is not the correct approach, can anyone suggest just me a way to wait for the event to finish without actually using sleep method.
Thanks & Regards,
Vishal

Hi,
Firstly thanks for your valuable suggestion. But i would like to mention one thing, actually i am using JFCunit framework for doing Unit Testing for our Swing based client. So here i am not looking into Swing code that is being developed but rather i am concentrating on writing unit tests to whatever that is been developed.
So when i click on the query button automatically, it is taking sometime to process (few seconds) & then its populating the data in a table. So in this case if i have to use the progress bar for the event to finish, i guess i have to modify the source code which is not advisable when you are doing unit testing. So i would appreciate if there is any other alternative that you could suggest me apart from using the progress bar.
Thanks & Regards,
Vishal

Similar Messages

  • If we dont want to use sleep/wakeup button for dissconnect the call so there is any other option for dissconnect the call without using sleep/wakeup button in ios 8.1.3. kindly suggest

    if we dont want to use sleep/wakeup button for dissconnect the call so there is any other option for dissconnect the call without using sleep/wakeup button in ios 8.1.3 . kindly suggest..!

    Hello kumar kalptaru, 
    Thank you for participating in the Apple Support Communities. 
    It sounds like you're wondering how to hang up a call besides using the Sleep/Wake button. 
    Other than this, you can tap the red hang up button on the Phone app. See the iPhone User Guide for more help:
    While on a call - iPhone
    End a call. Tap  or press the Sleep/Wake button.
    Best Regards,
    Jeremy 

  • How to "kill" AWT Event Queue thread without using System.exit()?

    When I run my program and the first GUI window is displayed a new thread is created - "AWT-Event Queue". When my program finishes, this thread stays alive and I think it causes some problems I have experienced lately.
    Is there any possibility to "kill" this thread without using System.exit() (I can't use it for some specific reasons)

    All threads are kept alive by the JVM session. When you use System.exit(int) you kill the current session, thus killing all threads. I'm not sure, though...
    What you could do, to make sure all threads die, is to make ever thread you start member of a thread group. When you want to exit you app, you kill all the threads in the thread group before exit.
    A small example:
    //Should be declared somewhere
    static ThreadGroup threadGroup = new ThreadGroup("My ThreadGroup");
    class MyClass extends Thread {
    super(threadGroup, "MyThread");
    Thread thread = new Thread(threadGroup, "MySecondThread");
    void exit() {
    //Deprecated, seek alternative
    threadGroup.stop();
    System.exit(0);
    }

  • Error while completing Wait for event step

    Hi Gurus,
    I have a Workflow developed which has a "Wait for Event" step.
    In that step,I am facing a problem .It seems the step is not getting completed properly.
    When I check in SWEL it shows the Event is triggered.But the next which is a 'Send Mail' step is not getting executed.
    The Event shows action status as "Receiver started correctly".
    When i executed "Complete Manually " in SWIA,it executed correctly and also the further steps got executed.
    What could be the issue ?
    Many Thanks in advance !
    Regards,
    Ameya Kulkarni

    Hello Ameya !
                     To one of my replies to this thread you have stated that no container elements are configured to wait for event step.
                     Without business object,event and container element with object reference, wait for event will not fire.
                     When the user changes the status in KO02, event fires and is seen in SWEL.But, if it should reflect in workflow, afore- mentioned details needs to be configured in wait for event step.
                    Have you configured this wait for event step with event 2 ?
    Regards,
    S.Suresh

  • Error in wait for event activity

    hi all,
    i am gettin gfollowing error when i am using wait for event activity in my WF.
    wait step 0000000088: No valid object ID in container element 'EVENT_BOR'
    'EVENT_BOR' is my container element of type BOR object which contain event.
    please tell me correct way to use wait for event step.
    i am using this on one parallel branch of Fork.
    thanks.

    Hi,
    check the event in SWO1 if there is an import parameter defined. If there is one you have to define the binding in the task waiting for event. You have to bind the relevant object type from workflow to containerelement &_WI_OBJECT_ID& of the event container.
    reagrds,
    Steffen

  • Wait for Event in Fork - How to terminate the wortkflow in leg 2

    Hi Experts,
    My scenario is that there is a fork with 2 branches. 1 has a change Doc method. In this I have raised an enent when a action is performed which in turn calls a wait for event in other leg. The problem is that the other loop is executing but the workflow is not coming out of leg 1. The work item remains in the agents workplace.
    How to correct this?
    Thanks,
    Dinesh

    in the FORK step you have an option of mentioning the "necessary steps".
    it defines the minimum number of legs of the FORK step that must be completed before proceeding to the next step in the WF.
    mention the necessary step as 1 for your case.

  • How to use wait for event step

    Hi,
    I need to trigger wait for event step for my workflow but I am not able to trigger that .
    Can anyany one of you tell me in detail what are the necessary config.and bindings i need to do for that .
    Also i need to pass data from my report program(where i am triggering the event for the wait activity) to the workflow through event triggering for the wait step.
    Please tell me how can I do that .
    Thanks in advance.
    Anand

    Hi,
    I think you can use the function module "SAP_WAPI_CREATE_EVENT" to trigger an event. Make sure that the instance data is same in both ends. To send data from your report, you can populate the event container using the container related macros.
    Check this link for more information
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c5/e4af4a453d11d189430000e829fbbd/frameset.htm
    Regards
    <i><b>Raja Sekhar</b></i>

  • Wait for event step without callback

    Hi All,
    In 4.6C I have the following problem:
    We have a workflow that has a fork with 2 branches, with 1 necessary for continuing the fork.
    One of the branches has a dynamic parallel processing step on a multiline container element, where each parallel process is a wait for event step. For example if the multiline element has 5 records, than there will be 5 parallel wait for event steps on this branch, and if all 5 are completed, then the workflow continues after the fork and the other branch should be logically deleted (normal behaviour).
    The other branch has a single wait for event step, if this event is received, the other branch's parallel wait for event steps should be deleted to continue.
    The problem is that when the event for the latter single wait step is received, the step gets completed, but sometimes the parallel wait for event steps on the other branch are not deleted and the wokflow does not continue. The completed wait for event step shows that the callback is not completed yet.
    I tried to fix these steps in SWPC, but in 4.6C it does not work for wait for event steps w/o callback. There's an OSS note for higher releases where this is fixed to enable SWPC for wait for events, so I copied it to a custom program and use that right now.
    First question is why does the system not continue these workflow's when the event is received? My guess is that the tRFC calls get stuck and when the tRFC job reprocesses the entries, it does not do it correctly. For example lately we had a tablespace problem that caused some tRFC calls to go into error. The waiting steps in the instances were completed w/o callback. I reprocessed the tRFC entries, which created new entries in the Workflow logs showing that the events are received, but the workflows still hang.
    Second question, it takes a lot of time to logically delete those parallel wait for event steps. When the event for the single wait for event is received and the workflow continues w/o problem, it may take tens of minutes from the receipt of the event until the parallel wait for event steps get deleted and the WF continues. Why does it take so long?
    Thanks,
    KK

    Hi,
    Regarding the delay and the hundreds of thousand SWW_CONT updates... the main workflow on one branch does a dynamic parallel processing of a subworkflow using a multiline container element that can have 50 or even 100 elements. So we can have 50 or even 100 subworkflows waiting for their event to be triggered.
    The main workflow container contains many elements, some multiline with long structures, so in one instance the main flow had 8000 entries in SWW_CONT (each field of a structure is a separate record in SWW_CONT).
    Now if I do the math, when this workflow loads all the container elements of the main flow into the 100 waiting subflows before deleting them and continuing along the other branch, it creates 100 times 8000 entries in SWW_CONT, that is 800.000 inserts!
    And this was ONE single workflow.. Imagine when we have just a few hundred and they all want to continue at the same time...
    Anyway, the beauty comes now....
    I created a simple main flow with a single multiline import parameter USERS of object USER. It has a fork with 2 branches, 1 enough to continue. One branch is a user decision with 1 option: Continue. The other branch has a subworkflow and it does dynamic parallel processing with the multiline element USERS.
    The subworkflow has one single import element USER of object USER. It has only one step, a wait for event, waiting for the DELETED event of the USER object.
    That's the scenario.
    When I start the main flow, filling the USERS parameter with two user objects, on the first branch it starts the two parallel waiting subflows with one user each, and I get the decision step on the other branch. If I check the subflow containers this time, they only have one USER object each.
    Now if I complete the user decision, the workflow continues, logically deletes the subflows and completes. If I check the subflow containers after this, they all include the USERS multile container element with all the USERS I started the main flow with!
    So this time it was a different main flow, different subflow, different events. I guess there can't be any custom code doing this, unless there's some generic workflow user exit somewhere.
    Feel free to test this yourselves if you have 4.6C, quite easy scenario. Guess I'll try in ECC 6.0 too just to see...
    And I'll report to SAP for sure.
    Regards,
    Krisztian Klausz

  • Wait for event - workflow 4.7

    Hi, not sure if this is the correct forum for workflow or not but here is the problem.  I have a custom BOR with 2 key fields, both character.  The BOR has some some events one of these events is 'submitforapproval' and another is 'reviewed'.  The 'submitforapproval' event is raised by an external R/3 program and is used to trigger the workflow in question.  This works well.  The 'reviewed' event is also raised by an external program and is used in a 'wait for event' step inside the same workflow. Once this event is raised the workflow continues. This happens sometimes without error and other times it can't find a receiver.  I have looked at the event linkage through SWEINST when there is an error and while the receiver key is correct the object key holds incorrect information causing the 'receiver not entered' error.  Why is this happening?  When the workflow is triggered the event manager should set up the linkage for waiting event from the BOR key in question, why is this not happening?  What can I do?
    Any help will be appreciated,
    Kevin

    Thanks for the reply Gareth.
    My WF C has a normal step in it that calls the A workflow.
    I've tried numerous combinations, but as it is now, I have the WFINITIATOR, WFPRIORITY, ATTACHOBJECTS, and an object reference parameter being passed into workflow A.
    Basically, that task just references the WS workflow object to kick it off.
    WF A doesn't have any triggering events.  It was previously manually initiated through the SWW_WI_START function in a custom transaction.
    After the process has trickled through C->A->B and is at the wait step, I'm using another external custom transaction that initiates an event (for the wait step in WF B) using the SWE_EVENT_CREATE function.  I'll be doing some more testing here today...  but I have a feeling there's something wrong with the object key I'm passing through.
    I'm not new to WF...  but I've only really ever maintained existing workflows.  We'll say I'm still learning the complexities.  There is a pretty good chance that I'm just missing something really obvious or stupid.
    Thanks for your help so far...

  • AP01: warning -- apply server waiting for event (since 1602 seconds)

    Hi,
    in the alert log I see a message "AP01: warning -- apply server 2, sid 449 waiting for event (since 1602 seconds):" without any other information...
    How can I troubleshoot this situation?
    Edited by: Insaponata on Feb 24, 2011 8:51 AM

    APPLY SERVER:
    select SID from V$STREAMS_APPLY_SERVER;
    With above SIDs, query V$PROCESS to get the PIDs:
    select a.pid, b.sid
    from v$process a, v$session b
    where a.addr=b.paddr and b.sid in(the list of sids from above);
    With the PIDs found:
    $ sqlplus /nolog
    connect / as sysdba
    oradebug setorapid <PID>
    oradebug unlimit
    oradebug Event 10046 trace name context forever, level 12
    wait for 10-15 mins
    oradebug tracefile_name -- gives pathname / filename to file being written to
    oradebug Event 10046 trace name context off

  • Error in Workflow wait for event node

    Hello Experts,
    I am working on one QM notification. I shall explain the scenario first:
    1) User will take the usage decision on inspection lot in QA11. When user will take decision and save inspection lot BUS2045 event USAGEDECISIONMADE will be triggered and initiate my workflow here.
    2) After workflow initiation system will create notification and send to approver, but here i have wait step in my workflow for BUS2078 - Created (Notification).
    wait for Event step
    BO: BUS2078
    EV: CREATED
    I am posting error below:
    Error when starting work item 000000294361
    Error when processing node '0000000060' (ParForEach index 000000)
    Error when creating a component of type 'Wait Step'
    Error when creating an event item
    Error within method CL_SWF_RUN_WIM_EVENT->_CREATE_WORKITEM_CONTAINER
    Error within method CL_SWF_RUN_WIM_EVENT->_GET_INIT_WORKITEM_CONTAINER
    Workflow 000000294361 wait step 0000000060: No valid object ID in container element 'Notification
    Node 60 - wait for event step.
    Re.,
    Guri

    Hi,
    Based on your description what I felt is you are making use  of a wait step in which you have choose to wait till BUS2078 event CREATED is occured ... right.. Now can you please clear me that where and how this event will triggered.
    or is it some thign like you are making use of event creator step and in this case, When ever you are making use of the eventcreator  step and a BOR object inside it make sure that specific BOR object is already instatitaed in the workflow container , if it is instantiated then only it will try to identify the instance  or the BOR and it will try to rasie the event.
    Regards
    Pavan

  • Bpm:message being sent and wait for event

    Hi,gurus:
    My scenario is about BPM.In the integration process I used a loop and correlation.The scenario worked successfully yesterday,but after I changed some thing,it did not work.The outbound status of the message in sxi_monitor said "message being sent".And when I clicked PE to see the workflow log, it said " wait for event".
    Thanks in advance.

    Could you tell me how to reimport the integration progress in ID?
    reimport means...delete the already imported BPM from ID.....this would affect the corresponding ID objects....save and activate....and then again run the import Integration Process wizard....create the objects once again.....seems time consuming.....hence mentioned it as the last option in the list:(
    Also from SWWL delete only the instance with status as ERROR.
    Edited by: abhishek salvi on May 20, 2009 9:30 AM

  • Problem with wait for event

    Hi everyone,
    I'm using wait for event step in my workflow of a custom event called zevent2.
    I'm not using the event as a start event of the workflow.The event is getting triggered at a certain point of the workflow programmatically.
    So for that what should be the entry in SWE2? I've maintained the following entry for zevent2 at swe2 tcode.
    Object type: BUS2000126
    Event: ZEVENT2
    Receiver type:
    Receiver function module: SWW_WI_CREATE_VIA_EVENT_IBF
    In swel I'm finding out that event got triggerd but it is giving error "No Receiver Entered".
    And the workflow is getting stuck at 'wait for step event'.
    So can anybody please tell me what is the step am I missing? is the swe2 correct?
    Thanks & Regards,
    Anirban

    HI....
    you have to specify RECIEVER TYPE without which you will be getting this error
    goto SWE2 and give the value and your problem will be done
    regards
    Edited by: Mohit Kumar on Feb 20, 2009 10:50 AM

  • NiDCPower Wait For Event

    Hello,
    I am using the PXIe-4139 SMU to source a current sequence that starts when a trigger is received and takes about 40 seconds to complete.
    After the niDCPower Initiate VI I have inserted the niDCPower Wait For Event VI with a timeout set to 300 seconds to allow for enough time to receive the trigger and complete the sequence. This VI waits for the Sequence Engine Done Event.
    Now this works fine, however, when the user wishes to stop the programm for whatever reasons, they have to wait the full 300 seconds until the Wait For Event VI produces a timeout error and stops the programm. This is rather inconvenient. How can I change the programm so that the user can stop it even when the Wait For Event VI hasn't reached its timeout?
    I tried this:
    But this doesn't work. For some reason, I get a timeout error with code -200474 but the boolean operator returns FALSE.
    Any other ideas?

    If there an output on the wait for event VI that flags a timeout? If so, set the timeout short (like 100 msec) and wait for 3000 timeouts before continuing on.
    Oh, and use an event structure. Timeout event (timeout=0) checks the wait for event, value change event for button breaks out of loop.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Need help on Wait for Event.

    Hello all.
    I faced an issue with wait for event step,Which goes like this.
    For a workflow one of the fork branches there is a wait for event step(wait for manual release) . On development server when ever that event is fired (manual release) , the wait for event is capturing and completing the workflow ( This is the correct process).(PO release procedure)
    On production system, this event is not been caught(after manual release is done) and and the workflow is not  complete and still in progress. (even po is released manually) Which should not happen.
    So what all the things i need to verify in the production to fix this. I cannot simulate any kind of event on production ryt. so please suggest.
    please suggest.
    Cheers
    PRASAD.

    Hi Prasad
    i doubt that in Production the event trace would be on. Check SWELS to see if you see the "OFF" button (this means the trace is on). If it is On, check SWEL to see if any event is there for rejection. You will have to ask example of the PO and search using the Key (PO number).
    Also, check the workflow instance which is supposed to complete when the rejection happens (which did not complete). Check the technical WF log. Look for the Business Object container element which should hold the runtime instance. Check if it has a value and the same is bound from the event to the workflow in the wait for event step's binding. (_EVT_OBJECT to Workflow Container element of same type). This WF container element should have an instance and should not be empty for the wait step to work.
    Regards,
    Modak

Maybe you are looking for