Should clients of long-running processes wait for a response?

I am a bit confused by the worklist tutorial where the client waits around for
a response from the worklist process that blocks on human input. This may be okay
for the sample application, but is it a realistic scenario? Have you designed
any practical worklist processes this way? I would have thought that the client
of a worklist process would simply trigger the process and go away. Eventually
when the human involved in the process would take some action, the process would
then, for example, send a message to some application. What do you think? I would
be interested in your opinions and perhaps some real examples of how you are using
worklists.
Thanks.
P.S. Is it even possible for a worklist client to trigger the process and go away?
Would the process die because the client has gone out of scope?

I agree with your comments. In being honest as well, we unfortunately do have SRs that get behind or missed. It's very frustrating on our side as well when we have these come up. We have implemented a number of technologies and also human touch to help us catch these and continue to focus on ways to overcome these delays. I know it's frustrating for you as well.
Our customer satisfaction is very high and actually continues to increase each Qtr. Our data shows us our three key satisfaction areas are; speed of response, speed of resolution and followup.
Chat support helps us in response time, but sometimes may hinder us in resolution times. Especially with more complex issues. Our goals were not to totally replace the phones with chats, but to use chat to allow us to respond more quickly, which it has done. We're now focusing our folks to realize it's still ok to call you when the Chat is hindering resolution and it would be quicker to talk live about the issue.
We resolve over half of the SRs on the first day. We continue to focus on speeding up the resolution of those that go beyond the first day. A couple things we've implemented are we call you back at least every 2 days when the SR is in Novell's court and at least every 5 days when it's in your court. We've also implemented timed escalation for SRs and are now looking at also escalating when progress is not being made after a certain number of days (rather that just time open). The goal is to get you in the hands of the right person asap to speed up the resolution time.
We're also having Managers call you on more and more SRs before being closed to double check your satisfaction with the SR.
Our dream is to never have you need to ask us for attention on a SR. We continue to make progress on it.
I look forward to your thoughts and other ideas you may have to help us improve,
-Todd
Todd Abney
Technical Support Director
Novell

Similar Messages

Long running Process chain for less Number of records

Hello Experts,
I have a problem with a process chain which is taking very long time ( To load around 20 records)
Problem Description:
1) I have one base ODS and First level ODS and the data uo to this point is loaded with out any problem.
2) When the data is moving from First level ODS to the Cube to load 20 records it is taking around 5 hrs of time and the load is successful.
3) If I see the DTP monitor the exraction step from DSO to Cube is taking around 4.50 min
4) The remaining stpes are like Error handling, transformations, updation are taking normal times (Around 5 secs).
Could any one please help me to find out where the exact problem lies to make this extraction step so long time.
Regards,

Please check for start routines, field level routines. From DSO to Cube check for transformation. How each and every field is getting updated and you will be able to track the time taken for the load.
thanks,

How long do I wait for a response?

I opened an SR on June 9th, some trouble with ZCM. The technician escalated the call. Today is June 17th, and I have ZERO response on it. Someone remind me why I pay for support each year? We've opened 2 ZCM related SR's this year, neither of which have been resolved. It's just ridiculous.

I agree with your comments. In being honest as well, we unfortunately do have SRs that get behind or missed. It's very frustrating on our side as well when we have these come up. We have implemented a number of technologies and also human touch to help us catch these and continue to focus on ways to overcome these delays. I know it's frustrating for you as well.
Our customer satisfaction is very high and actually continues to increase each Qtr. Our data shows us our three key satisfaction areas are; speed of response, speed of resolution and followup.
Chat support helps us in response time, but sometimes may hinder us in resolution times. Especially with more complex issues. Our goals were not to totally replace the phones with chats, but to use chat to allow us to respond more quickly, which it has done. We're now focusing our folks to realize it's still ok to call you when the Chat is hindering resolution and it would be quicker to talk live about the issue.
We resolve over half of the SRs on the first day. We continue to focus on speeding up the resolution of those that go beyond the first day. A couple things we've implemented are we call you back at least every 2 days when the SR is in Novell's court and at least every 5 days when it's in your court. We've also implemented timed escalation for SRs and are now looking at also escalating when progress is not being made after a certain number of days (rather that just time open). The goal is to get you in the hands of the right person asap to speed up the resolution time.
We're also having Managers call you on more and more SRs before being closed to double check your satisfaction with the SR.
Our dream is to never have you need to ask us for attention on a SR. We continue to make progress on it.
I look forward to your thoughts and other ideas you may have to help us improve,
-Todd
Todd Abney
Technical Support Director
Novell

ORABPEL-05002 for long running process

Hi everybody,
My question is related with a long running process I have designed and which, after running for a couple of days, ends by reporting the ORABPEL-05002 error:
===============================================================
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
===============================================================
Looking in the Manual Recovery screen, I can see an Activity I can recover. It's about an assign Activity where I'm doing a single boolean assignation.
Of course, together with the ORABPEL-05002 error I got also the 'Transaction was rolled back: time out' message. Note that I have modified the transaction-timeout value to 180000. The error occurs during the night, with no heavy load of the server.
Recovering the assign activity brings back the process in the running state.
My process pattern:
while (1 == 1) {
do activity;
wait_timeout();
So, I have the following questions:
1. Which is cause of this error?
2. How may I automatically recover this lost activity? RecoveryAgent?
Any suggestion is appreciated.
Regards,
amo
P.S: the full stack of error messages reported in domain.log:
===============================================================
<2006-09-18 08:08:34,101> <ERROR> <SRH.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:873)
     at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1479)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: No Exception - originate from:
     at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:871)
     ... 10 more
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1479)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:08:34,129> <ERROR> <SRH.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,236> <ERROR> <SRH.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
ORABPEL-02094
Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
     at com.collaxa.cube.engine.core.ScopeContext.getScope(ScopeContext.java:213)
     at com.collaxa.cube.engine.core.WorkItem.setCubeInstance(WorkItem.java:259)
     at com.collaxa.cube.engine.core.WorkItemFactory.init(WorkItemFactory.java:68)
     at com.collaxa.cube.engine.core.WorkItemFactory.create(WorkItemFactory.java:58)
     at com.collaxa.cube.engine.adaptors.common.BaseWorkItemPersistenceAdaptor.load(BaseWorkItemPersistenceAdaptor.java:147)
     at com.collaxa.cube.engine.data.WorkItemPersistenceMgr.load(WorkItemPersistenceMgr.java:75)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5185)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5173)
     at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2136)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
     at IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
     at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,274> <ERROR> <SRH.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
ORABPEL-02094
Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
     at com.collaxa.cube.engine.core.ScopeContext.getScope(ScopeContext.java:213)
     at com.collaxa.cube.engine.core.WorkItem.setCubeInstance(WorkItem.java:259)
     at com.collaxa.cube.engine.core.WorkItemFactory.init(WorkItemFactory.java:68)
     at com.collaxa.cube.engine.core.WorkItemFactory.create(WorkItemFactory.java:58)
     at com.collaxa.cube.engine.adaptors.common.BaseWorkItemPersistenceAdaptor.load(BaseWorkItemPersistenceAdaptor.java:147)
     at com.collaxa.cube.engine.data.WorkItemPersistenceMgr.load(WorkItemPersistenceMgr.java:75)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5185)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5173)
     at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2136)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
     at IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
     at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,275> <ERROR> <SRH.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
===============================================================

These are the possible cause to the problem and their solutions:
Poor performance of the dehydration database If you are using Oracle Lite as dehydration store, please switch to use Oracle 9i or 10g. If Oracle 9i/10g is already in use, check the database parameter 'process' and 'session' to make sure it can handle the expected throughput.
OC4J has too few available connections to the dehydration database. Increase the maxConnection number of the BPELServerDataSource at the BPEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml (for developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/data-sources.xml (mid-tier installation).
Size of message is too big Two ways to deal with this problem:
Increase the transaction timeout at PEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/server.xml (developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/server.xml (mid-tier installation)
Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.
Cheers
Anirudh Pucha

ProgressIndicator and hourglass for long running processes

Hi all,
Iam using Oracle ADF 10g with EJBs.
I have a long running process for which I want to give the user an indication of its progress. The process is run upon clicking a submit button.
I have tested the use of the combination of progressIndicator + poll according to the example of Gerger consulting( http://gergerconsulting.blogspot.com/2007/04/adf-faces-progressindicator-example-for.html) but it did not work. The problem is that my long running process hangs the page and the progress bar does not work until the process has finished.
I have seen a similar post in this foum (Re: How to run long background jobs in ADF applications where a user complains that there is not an Oracle method for running asynchronous processes from Oracle ADF.
I've tested to isolate my asynchronous process with the progressIndicator + poll in a single ADF page. The process is being activated from an invokeAction from the executables of the pagedef file. But again the process hangs the page and the progressIndicator does not display at all.
So I have abandoned the idea of the progress indicator and Iam thinking of using an hourglass.
Is there an example or guidelines of how I can do it?

Thanks John for your reply,
Iam still working on the progressIndicator. I have read the discussion thoroughly quite many times.
One thing I have not yet figured out from your discussion is how you manage to create the long-running-process thread within an action method within the managed bean and make the thread still be active, while the parent action method has finished.
Usually the managed beans attached to a .jspx pages has request scope. So a commandButton's action method (that will spawn the long running thread) will finish much earlier than the thread and it will kill the thread.
Thanks,
Dimitris

Question : Scheduling a Long Running Process in BPEL

Hi All,
I have a doubt regarding deployment and scheduling of a Long Running Process in BPEL console like the way we schedule a concurrent program in Oracle Apps.
Business Scenario:
We have developed a BPEL process to pull data from the Database, do the required transformation and then enqueue the transformed data in a queue present in another database.
Then a Java program will pick the data from the queue and then generate an XML file and send it to FTPserver of the Trading Partners(TP's).
We have two Trading Partners and hence the generated XML will be put into the appropriate FTP servers of the TP's.
The BPEL processing for both the Trading Partners is identical. Only the generated XML is put in different FTP servers.
My question here is:
1. Since the processing is same for both the TP's, how can we use the same process for both the Trading Partners.Can we handle it in the BPEL process itself ?
2. Is there any way to schedule the same process in BPEL console, to first run for Trading Partner TP1 and wait for say 15 mins and then run for another Trading Partner TP2 and this cycle should continue since we will be deploying it in production environment and continuous updation of the transactions will be happening in the database.
So far my knowledge in BPEL goes, i could not find any way to schedule a process in BPEL console. If any one has come across similar scenario, please post your updates/approach which will help us in defining the architecture for our client.
Thanks In Advance,
Cheers
Dibya

Hi Marc,
Thanks a Lot for ur inputs.
Need some more clarification for quetsion no.1 in my previous post.
From our BPEL process we are calling a package which takes the Trading Partner name as the input and some other parameters. Our BPEL process will be run for both the Trading Partners since the processing is identical.
If we develop two different processes for both Trading Partners, then there will be locking issues in the database since both the processes will refer to the same table.
Hence we were looking for an option where we can use the same process for both the Trading Partners. Is there any way to handle it in BPEL process.
Your inputs will be really helpful.
Thanks In Advance,
Dibya

Correlating to long running process

I'm trying to set up a long running process that handles item-storage. For handling of the BPEL I have a process which needs to tell the long running process which item is stored in that particular storage. For example: i have 200 bins, which can contain up to 100 items. As the bins are handled individually (when filled), I need the 100 bpels that handle the items to wait until the long running process is finished.
So, I figured to make a BPEL that accepts 2 messages: 'initiate' and 'addItem'. Initiate sets up the bin and waits until filled before handling the bin.
The addItem is placed in a onMessage branch. This branch should be 'create Instance = no", as the instance is created when the bin is initiated. I get one initiate message and 100 addItem messages. Initiate & additem are correlated, so I should only receive the messages for this particular bin. However, when I try to compile this process, I get the following message:
Error(36): [Error ORABPEL-10050]: no create instance activity [Description]: in line 36 of "L:\workspaces\MyTests\LongRunningProcess\LongRunningProcess.bpel", There is not an activity (receive/pick) to start the process. [Potential fix]: You might want to set createInstance="yes" for this <receive> / <pick>.
Well, the 'fix' is not quite what I had in mind. I cannot have a createInstance='yes' here, as the instance is already created when I started handling the bin. Besides, I have to handle 100 incoming messages, not just 1.
I have a need for this kind of pattern, as I have a lot of converging & diverging messages in our processing. Diverging is easy, converging is giving me a lot of headaches.
Anyone has ideas how to help me find a solution for this? Thanks in advance!

Hi,
1) You could use conversation for the first issue which are designed for this usecase.
Conversations are essential for any web service involved in asynchronous communication. This includes web services that communicate with clients using callbacks or polling interfaces, and web services that use controls with callbacks.
More info at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/converse/navMaintainingStatewithConversations.html
Thanks
Vimala

HTTP Server Hangs on Long Running Process

Hi,
We are having an issue with our production environment where long running processes i.e. > 5 mins will cause the client application to stop responding. We notice that this is only affecting forms which has no activity during the busy period i.e. forms which call a back end DB procedure or function and waits for a response from the DB to say that the process is done.
Checking on the process itself from the DB shows that the process has completed successfully but somehow there's no response back to the client to say that it's completed. As a result, the client will be in busy status forever.
We are sure that the issue originates from the HTTP server because when we by-pass the HTTP server i.e. send the request directly to the Apps server, this behaviour is not happening.
By thew way, we are running on Oracle Forms 11g using Weblogic.
Changes made so far but to no effect:
maxBlockTime=1800000 (web.xml)
keepAlive=Off (httpd.conf)
Timeout=1800 (httpd.conf)
FORMS_TIMEOUT=60 (formsweb.cfg)
heartbeat=4 (formsweb.cfg)
Session-Timeout=30 (web.xml)
Can this be related to network configuration? If yes, what are the things to look for?
Thanks.

as the response came from the server your httpd service is not getting active for that you
need to keep the httpd service alive so that the response can be obeyed
just try this
keepAlive=On (httpd.conf)
..

Call long running process and return immediately

Hi everyone,
Here' my problem : I am calling an onDemand application process when clicking on a button. It's a very long running process; and while waiting for the response my browser stops responding (white page).
So, is there a way to call a process and return immediately to the javascript. The process will set a field to a given value when it finishes. In javascript side, I can then check in a while boucle the value of this field to know if the process has ended.But I dont know how to return just after the application process call ...
Thanks and best regards,
Othman

I presume that you can achieve that by means of a batch job.
You can use an automatic page reload every X seconds until a certain "flag" (or similar mechanism) changes state and check it in a before header process. In the meanwhile you can display some animated GIF for instance.
Once the processing is completed you remove the reload timer from the header or you branch to a different page using a programmatic technique like procedure owa_util.redirect_url.
Bye,
Flavio
http://www.oraclequirks.blogspot.com/search/label/Apex

In forms how to cancel long running process or query in 10g

We have application which is hosted on 10g AS. Some forms has lot of processing to be done and sometimes user wants to cancel the processing in between maybe because he wants to change some value and refire processing.
Based on the search on net 'Esc' key was used in earlier version of forms to function as User requested Cancel operation. How can same be done in 10g. Do we have to do anything in fmrweb.res for this. Is there some setting to be done in forms or in AS for this functionality.
Does this matter on whether JInitiator is used or JPI is used for running the application?
Edited by: suresh_mathew on May 21, 2013 1:36 AM

Hi,
Exit can be used to cancel query mode i.e. in case you go into query mode by Exit you can cancel query mode. Suppose you went into query mode and you have fired query which will take some time to fetch how can I abort it.
In earlier version of form there was 'Cancel' facility wherein if triggered it used to fire an error message 'Ora--01013 user requested cancel of current operation"
With this facility you can abort any query which is executing or any long running process which forms is currently performing.
fmrweb.res would have entry like
27 : 0 : "Esc" : 1001 : "Cancel"
The above entry I picked from OPN
Java Function Numbers And Key Mappings For Forms Deployed Over Web [ID 66534.1]
Unfortunately this is not working for us even if I put this in frmweb.res of 10g AS
Basically I want ability to Abort/Cancel a long running process be it query execution or standard process triggered in the form.
Any advise or help is highly appreciated.
Suresh

GF 3.1.1 Admin Console Freeze -- A long-running process has been detected

I installed Glassfish 3.1.1 on both sparc and intel servers for solaris 10 & 11 platform. All my servers have the same symptom when I access the admin console. The console freezed and pop-up a message "A long-running process has been detected". There is nothing I can do at this point. I've tried accessing from different PC with different browsers (IE, Firefox 5, Chrome and Safari), but nothing is working including clearing the cache. Also, tried uninstall and install again (with and without updatetool) many times. Any idea how do I stop the popup message? Am I the only one has this problem? I'm using JDK 1.7 (GF 3.1.1 support JAVA 7). I need help!!!!!
Thanks,
- Johnny

The only fix I know of for this issue is to reboot the host.
If there is another fix someone please let me know as I have users who run into this often.
Thanks
Bonnie.Partridge

Handling long running processes in APEX

Hello Experts,
I need your help!
I would like to call a long running PL-Proc from an Apex-App. So I build a page for the parameters with the wizzard - all fine.
Pressing the button starts the pl-proc - thats also fine.
Problem: While the PL-Proc is running, there is no activity signaled in the browser. There is no way to see, that something is running in the background.
After the pl-proc is finished, the branch to an other site took place - so the "after process" action is working as desired.
I tried "javascript:html_Submit_Progress(this);" - but this is not a solution because there is only a very short time to reload the page itself. The PL-Proc need much more time.
Is there a way to show the user, that background action is running?
Any Ideas?
Thanks for your help!
Kind regards,
Frank

A few things to keep in mind. The animated gif solutions don't show a true progress bar indicator, it's just an animation on a loop. If the process takes too long, you will hit the session timeout value defined for Oracle HTTP Server.
Another thought is this. In the code that is the long running process, make calls to [dbms_application_info.set_session_longops|http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28419/d_appinf.htm#i996999] that indicate the real progress in the code. Then have a page that queries v$session_longops and refreshes every x (say 5 seconds). That page could even have an animated gif on it to indicate there is still activity.
Tyler Muth
http://tylermuth.wordpress.com
[Applied Oracle Security: Developing Secure Database and Middleware Environments|http://www.amazon.com/gp/product/0071613706?ie=UTF8&tag=tylsblo-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0071613706]

Long running process/query

One of my after submit processes involves a lot of processing, temp tables, sorting, aggregating, etc.
When this process is invoked from a page, is there a way to put up a generic 'Processing...' page that auto refreshes and when my back-end process is done, takes me to my results page?
Thanks

Let me see if I understand you...
So, the first page (that would have invoked the long running process) branches to the "processing page". That page has a onload that does doSubmit(). The after submit process on this processing page calls my long running process via dbms_job. When the long running process ends, the branch on the processing page takes me back to the first page (or whereever).
But then as far as the browser is concerned, the processing page never "finishes loading". IE's progress bar would creep ahead sloooowly and it would appear as if the page is loading for a looong time!
Wouldnt it be cleaner to use the META refresh tag like John was suggesting?
Also, using either of your approaches, how would I allow the user to "Cancel" the long running process and go back to the first page?
Could you please put up a quick sample of this in action on htmldb.oracle.com?
Thanks

Context when Invoking Long Running Processes

When I use a long running process to invoke another long running process, the creator of the second long running process is always "System Context Account".
Is it possible to invoke one long running process using another long running process using the context of the workspace user? The primary need here is to be able to track the process in the audit tab.

Hi gary,
Thanks for the update.
I have just tried your "Run As" approach which is also not working.
My testing scenario:
I have created two processes (a Parent and a Child)
I have enabled RunAs option with 'Invoker' for the Child process.The parent process is configured to invoke the Child internally.
I am, as a user, invoking the Parent process from Workspace. The Child process is being invoked; However, the process's creator name still shows 'System Context Account'. I do remember that this issues was exist in previous release as well ES (8.0).
Is this a bug? or am I missing something in between?
Please advise.
Thanks,
Nith

How do you keep a VI running while waiting for user input?

I have a VI that:
1. The user enters set points.
2. The user starts the VI and the VI sends the set points to an external process via a serial interface.
3. The VI stops running.
4 The user waits for the external process to complete.
5. Repeat sequence. Go to Step 1.
This works well except for one small problem. Starting the VI in step 2 causes an external micro controller to reset. During the reset it will ignore set point commands. To get around this problem a delay has been added between when the VI opens the serial port and when the VI sends the set points to the external process Is it possible to keep a VI running continuously in this type of application, thereby eliminating the start up and shut down of the serial interface?
If yes, how do you keep a VI running while waiting for user input?
Howard

The ones for the event structure specifically. I'm posting from my phone. Look at the basic ones for user input. even a simple while loop with a boolean and a case statement would work.

Should clients of long-running processes wait for a response?

Similar Messages

Maybe you are looking for