Process instance fails to terminate.

I start a process instance programmatically through a web service call, passing a couple of parameters to the starting instance. But then, when the last activity is completed and the end event is reached, there is a failure. As a consequence, the instance is not ended. The failure is the following:
com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_Approvazione_Vie_Aeree:END_CONTROL_EVENT_End(
      com.sap.glx.adapter.BPMNAdapter:Token_0_Approvazione_Vie_Aeree_84bb2f9ca021a18a7f0398d219d89556 token,
      com.sap.glx.adapter.BPMNAdapter:Instance_0_Approvazione_Vie_Aeree_84bb2f9ca021a18a7f0398d219d89556 parent){
  exit=new com.sap.glx.adapter.BPMNAdapter:Exit();
  exit:addParameter(token);
  exit:addParameter(parent);
  exit:onActivation("4B55B53890073FD304FF11DFCE9002004C4F4F50", parent, token);
  delete exit;
  controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController();
  controller:setContext(token);
  delete controller;
  kicker=parent:kicker;
  grampa=parent:parent;
  response=new com.sap.glx.adapter.BPMNAdapter:Response("sysdat.it/vieaeree_bpm/Pool/Approvazione_Vie_Aeree_e9c5b1215494d058c64477dc6840a7ee", "avvioVieaeree", grampa, kicker);
  scope_business=new com.sap.glx.adapter.internal.TypeRegistry:Scope_8_Approvazione_Vie_Aeree_84bb2f9ca021a18a7f0398d219d89556(parent);
  document=scope_business:instantiate("http://www.w3.org/2001/XMLSchema", "anyType");
  delete scope_business;
  mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
  yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
  yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
  yves_out:setData("http://sysdat.it/StartProcess/", "$http://sysdat.it/StartProcess/:avvioVieaereeResponse", document, "7E86E4BE818B213CFC42A775F27707D9");
  mapper:map("4B55B53890073FD604FF11DFA74702004C4F4F50_84bb2f9ca021a18a7f0398d219d89556", yves_in, yves_out);
  document=yves_out:getData("http://sysdat.it/StartProcess/", "$http://sysdat.it/StartProcess/:avvioVieaereeResponse", "7E86E4BE818B213CFC42A775F27707D9");
  delete yves_in;
  delete yves_out;
  delete mapper;
  response:setData(document);
  delete token;
com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:69)
com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:241)
com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:125)
com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:116)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAs(Subject.java:337)
com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:114)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169)
Any help will be appreciated.
Regards,
Livio.

Hi Oliver,
thank you for your kind reply.
The stack trace I posted is all what is available from the place where I got it (Operation Management>Processes and tasks>Manage processes).
But looking in the general log, I found much more trace information!! At the very end I found the following:
Caused by: com.sap.glx.core.kernel.api.TransitionException: Cannot instantiate abstract SDO type commonj.sdo:DataObject.
at com.sap.glx.core.internaladapter.typeregistry.TypeRegistryImpl.instantiateSDO(TypeRegistryImpl.java:113)
at com.sap.glx.core.internaladapter.typeregistry.TypeRegistryImpl.access$000(TypeRegistryImpl.java:41)
at com.sap.glx.core.internaladapter.typeregistry.TypeRegistryImpl$3.invoke(TypeRegistryImpl.java:283)
at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:463)
at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:248)
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:791)
... 12 more
Hope this is helpful.
Livio.

Similar Messages

  • BPM 11g- Terminate process instance

    Hi,
    How can I terminate a process instance that could either be sitting in an Human Interactive or a Timer activity.
    TaskService is one solution but I don't want to take that route to achieve this simple requirement. Is there any recommended pattern to implement this.
    I also thought of an event boundary with interuupting event, but not sure what to write there..
    It was easy in Oracle BPm 10G where you could have a Notification Wait with interrupt and that is attached to an "Automatic" activity where we could say:
    this.action=ABORT;
    Thanks
    Raj

    Hi Raj
    1. Terminate means you want to End that Process no matter where it is at any instance of time. Say if I have BPM Process with 10 SwimLanes it can be at any of the Lanes with any User. I am taking simple Example with Human Tasks, but you can apply for other component like Timer servces etc.
    2. I hope you are aware of 2 things specially for Human Tasks: Action named "Withdraw" and a role named "Process Owner". For any human task, under Actions menu you should See a Withdraw option. You can code your application to capture this output using XOR gateway and if outcome is "WITHDRAW" directly end the process and go to End Node. If you have many places like this, there is easy way instead of running wires eveywhere. Create a simple throw even that goes to End Node. And after each human task check outcome if Withdraw, that that error, which will end the process. I hope you got the point.
    b) The reason I mentioned Process Owner is, generally I do NOT give Withdraw control to each User who can work on any Task. If accidentally that User do this action, thats it. The process ENDS and you can never retriive it back. So under .TASK file, I preven Withdraw action to Asssignee and Instead give this action only to OWNER (Process Owner). Process owner is like admin who can pretty much see any tasks and I would give him all the permissions like these Withdraw, Reassing, Suspend etc etc. This gives more controlled power to your application. Anyhow, in bpm workspace, login as process owner and search for any Task aged for long time and jus Withdraw it.
    You can do all the above using APIs also as far as you have Withdraw action going to the End Node.
    If your requirement is something else, ignore above notes. But still you can think along the above lines, if all you want is to Kill a Running Process anytime.
    Thanks
    Ravi Jegga

  • 'End Terminate' event does not completely terminate the process instance!

    Hi,
    my process make use of the 'End Terminate' event, this will be used pending on the outcome of a prior task, using the 'Exclusive' gateway. This works quite well but in case of process termination some strange behavior happens.
    The Enterprise Manager tell me that the process instance is in state 'Terminated' but the BPM Workspace in the 'Process Tracking' tab this instance is still in state 'Running' and if I check the WFTASK database table the process instance is still in state 'OPEN' and not 'CANCELED'.
    So my question is, do I use the 'End Terminate' event the wrong way or is this a bug/feature?
    Thanks in advance,
    Daniel
    PS: I use BPM Suite 11.1.1.5 with Feature Pack.

    If we see a human task active even after termination end event is not considered a bug... I'm sorry, but i think that if every task active in the process instance is not terminated or "killed", the terminate end event is not working well. So we are talking about a bug.
    If I'm wrong, what is the expected behavior of teminate end event?
    Thanks in advance.

  • Process.Start(url) sometimes one instance fails

    I need some help!!!
    ASPX.NET/C#- Call Process.Start(url) several times, sometimes one instance fails without error!!
    I have a program that calls a http aspx.net with arguments(URL) to execute some stuff. That program are invoking 10 times that aspx.net (all in the same time) with diferents urls.
    But sometimes, one of the calls (url) do not launch in browser.
    Code is very simple:
    public partial class _Default : System.Web.UI.Page
    private Object thisLock = new Object();
    protected void Page_Load(object sender, EventArgs e)
    try
    string URL = Request.Params["URL"];
    Logger.Log("CURRENT URL TO LAUNCH->", URL);
    lock (thisLock)
    ProcessStartInfo startInfo = new ProcessStartInfo("IExplore.exe");
    startInfo.WindowStyle = ProcessWindowStyle.Maximized;
    startInfo.Arguments = URL;
    Process.Start(startInfo);
    catch (Exception ex)
    Logger.Log("Exception", ex);
    }The URL launch are a client side technology!And that´s because i need to open the IE in WebServer!It´s silverlight web application to generate reports!The silverlight application closes the IE instances after finish. Everything goes right, except sometimes in 10 requests one fail 
    Thanks

    What's the url do?
    Is it possibly that the url isn't ready or there?
    I can't recall ever doing process start from a web page.
    Maybe there's an alternative way of approaching whatever you're trying to do.
    BTW
    I think you should probably ask this question in the asp.net forum since there's actually no Silverlight in the mix there
    Hope that helps.
    Recent Technet articles: Property List Editing;
    Dynamic XAML

  • Process instances terminate upon application redeployment

    Hello all,
    I have been trying to find an answer for this question in the forums, but to no result.
    I have created a proof-of-concept process and deployed it on the server. The process works just fine, containing Client Request controls, creating Tasks etc.
    The problem is when, during development, I make some change in some helper class or the procees itself and redeploy the application. Even when I just rebuild/redeploy w/o any changes.
    Then, any running process instances (e.g. blocked, waiting for a Client Response or a Task onComplete) are terminated w/o any message, at least not a message that I can see.
    Is this a "feature" or have I forgotten to setup something correctly?
    If this is a feature, why aren't the open Task Controls also terminated, like the process instances that created them are?
    How can I prevent the process instances from being auto-terminated upon application redeployment?
    My process' properties:
    - freeze on failure: true
    - persistent: always
    - on sync failure: rethrow
    - retry count: 1
    - retry delay: <empty>
    - stateless: false
    - binding: webservice
    - version strategy: loosely coupled
    My configuration:
    - Weblogic Integration 8.5 SP6
    - Weblogic Server 8.1 SP6
    - Back-end DB: the default DB server, that comes with the BEA installation
    I would greatly appreciate any help/suggestions/links, as I find this feature/error very frustrating.
    My apologies if this has already been answered before.
    Thank you for your time,
    S.

    OK, to answer my own question.
    It was not a "problem", but a "feature".
    I had the server starting in development mode, so by default process instances are terminated upon redeployment.
    Editing the setDomainEnv.cmd and setting
    set PRODUCTION_MODE=true
    solved my "problem".
    Hope this helps s/o in the future.

  • BPEL process instances remain in-flight

    Hi
    I've got a BPEL process (GetUpdates) that calls a couple of other asynchronous BPEL processes (CommitPerson, CommitAddress etc) all of which are deployed on the same SOA server.
    Although most of the processes complete, quite a few instances of the GetUpdates process just sit in an Active state. The BPEL console shows GetUpdates has made a call to another process (for example CommitAddress) and it is apparently waiting for a response. However when I examine the cube_instance table in the dehydration store I can only find 1 instance relating to the particular process. Is that correct?
    If I then try to re-run these particular failed updates (by modifying the sequencing table that GetUpdates polls) the processes complete without any issue (and records exist in the cube_instance table for each of the processes that have been called as well).
    There can be a large number of requests being processed so could this problem be due to the server being under too much load, with the invoke being lost in the ether somewhere?!?
    Is there any documentation that explains the workings of the dehydration store or the BPEL server itself? Also what log files I should be looking at? (I'd really like to understand what's happening under the covers!!!)
    We're currently only using 10.1.3.1 SOA Suite so we should probably upgrade to 10.1.3.3 to see if that fixes anything.
    Any help or advice in the meantime would be great.
    Thanks
    Robin

    Hi
    Just thought I'd update this posting with my findings ....
    I think that the reason the instances remained inflight was simply because they were making calls to synchronous processes that were timing out.
    The default timeout setting for synchronous processes is from what I've read 45 seconds. The process instances that remained inflight were calling other (asynchronous) BPEL processes, that in turn called synchronous E-Business suite APIs that were timing out.
    I managed to simulate the above some time ago with dummy BPEL processes, however I have only just now (after several months of dealing with Oracle Support!) managed to resolve the E-Business suite problem that was causing the synchronous process to timeout.
    Anyway now that is resolved, we no longer get the large number of process instances remaining inflight ... and the updates are now flying along on the server!!
    Therefore the issue was a very simple one - timeout of synchronous processes. Unfortunately it wasn't all that obvious that it was happening in the first place(!) ... and it took some time to trace the actual culprit ... and even longer to find a solution (which we had to come up with ourselves ... without much help from support!) ... hence the amount of time that has passed from me creating this message and replying to it!
    Anyway I hope this post may help others in case they stumble upon a similar issue.

  • How to solve the take was stuck in a process instance

    Hi ,guys
      Now i came cross a problem .a task was  stuck in a process instance.the task'state is inactive and the process is onging.When I searched  the task in NWA and resumed it .It casted exception  like below:
       It seems like cluster problem .When I change the URL by adding the parameter ?sap-nodeid=65045051 .It didn't work. There is always cache in IE.
    Finally  we tried to restart the server. the task become normal .But  you know it is not a  ultimate  solution in PRD,we can't restart the server  in anytime.
    Is  there anybody helping me solve the problem.Many thanks.
    The error is :
    'Resume' action on Task instance in 'Manage Tasks' monitor has failed as that Task does not exist :: Task [de1f6f79e70c11e4a9780000014e097a] is currently locked
    [EXCEPTION]
    com.sap.bpem.tm.exception.NoSuchTaskException: Task [de1f6f79e70c11e4a9780000014e097a] is currently locked
    at com.sap.bpem.tm.adapter.cachestore.CachingTaskStore.resolveTaskGalaxyObject(CachingTaskStore.java:151)
    at com.sap.bpem.tm.adapter.cachestore.CachingTaskStore.getTaskObjectContainer(CachingTaskStore.java:114)
    at com.sap.bpem.tm.adapter.coordination.BPEMTaskParentImpl.getTaskObjectContainer(BPEMTaskParentImpl.java:184)
    at com.sap.bpem.tm.adapter.coordination.BPEMTaskParentImpl.getTaskGalaxyObject(BPEMTaskParentImpl.java:189)
    at com.sap.bpem.tm.adapter.coordination.BPEMTaskParentImpl.readLock(BPEMTaskParentImpl.java:318)
    at com.sap.bpem.tm.impl.TaskManagerImpl$TaskLock.readLock(TaskManagerImpl.java:170)
    at com.sap.bpem.tm.impl.TaskManagerImpl$TaskLock.access$200(TaskManagerImpl.java:136)
    at com.sap.bpem.tm.impl.TaskManagerImpl.resumeTask(TaskManagerImpl.java:1334)
    at com.sap.bpem.tm.impl.AdminTaskManagerBean.resumeTask(AdminTaskManagerBean.java:42)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy2423.resumeTask(Unknown Source)
    at com.sap.bpem.nwa.tm.TaskManagementUtilities.resumeTask(TaskManagementUtilities.java:378)
    at com.sap.bpem.nwa.tm.SAP_ITSAMGLXTaskService_Impl.ResumeTask(SAP_ITSAMGLXTaskService_Impl.java:368)
    at com.sap.bpem.nwa.tm.SAP_ITSAMGLXTaskServiceWrapper.invoke(SAP_ITSAMGLXTaskServiceWrapper.java:516)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:468)
    at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
    at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:612)
    at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
    at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:365)
    at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
    at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:289)
    at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
    at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.invoke(ITSAMUIMBeanServerConnectionWrapper.java:379)
    at com.sap.tc.lm.itsam.ui.proxy.JMXGenericModelClassMBean.invokeOperation(JMXGenericModelClassMBean.java:610)
    at com.sap.tc.lm.itsam.ui.proxy.JMXAbstractModelClass.invokeOperation(JMXAbstractModelClass.java:159)
    at com.sap.bpem.nwa.tm.wd.model.tm.SAP_ITSAMGLXTaskService.ResumeTask(SAP_ITSAMGLXTaskService.java:283)
    at com.sap.bpem.nwa.tm.wd.model.tmmonitorapp.comp.TMMonitorComp.resumeTask(TMMonitorComp.java:1057)
    at com.sap.bpem.nwa.tm.wd.model.tmmonitorapp.comp.wdp.InternalTMMonitorComp.resumeTask(InternalTMMonitorComp.java:825)
    at com.sap.bpem.nwa.tm.wd.model.tmmonitorapp.comp.FilterView.onActionResumeTask(FilterView.java:679)
    at com.sap.bpem.nwa.tm.wd.model.tmmonitorapp.comp.wdp.InternalFilterView.wdInvokeEventHandler(InternalFilterView.java:1139)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.glx.core.dock.api.DockingPortException: com.sap.glx.core.dock.api.StorageException: com.sap.glx.core.api.ClusterEntryUnavailableException: Cluster entry couldn't be retrieved from cluster node 21891450 because of: Storage group de1f6f79-e70c-11e4-a978-0000014e097a could not be evicted (2500 ms timeout elapsed)
    at com.sap.glx.core.dock.impl.DockingPortalAccess.resolve(DockingPortalAccess.java:151)
    at com.sap.glx.core.dock.impl.DockingPortalAccess.resolve(DockingPortalAccess.java:135)
    at com.sap.bpem.tm.adapter.cachestore.CachingTaskStore.resolveTaskGalaxyObject(CachingTaskStore.java:147)
    ... 115 more
    Caused by: com.sap.glx.core.dock.api.StorageException: com.sap.glx.core.api.ClusterEntryUnavailableException: Cluster entry couldn't be retrieved from cluster node 21891450 because of: Storage group de1f6f79-e70c-11e4-a978-0000014e097a could not be evicted (2500 ms timeout elapsed)
    at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.locate(StorageManagerImpl.java:803)
    at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.locate(StorageManagerImpl.java:653)
    at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.locate(StorageManagerImpl.java:648)
    at com.sap.glx.core.dock.impl.DockingPortalAccess.resolve(DockingPortalAccess.java:149)
    ... 117 more
    Caused by: com.sap.glx.core.api.ClusterEntryUnavailableException: Cluster entry couldn't be retrieved from cluster node 21891450 because of: Storage group de1f6f79-e70c-11e4-a978-0000014e097a could not be evicted (2500 ms timeout elapsed)
    at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.redeem(StorageManagerImpl.java:899)
    at com.sap.glx.core.cluster.CollectiveIndexControl.fetch(CollectiveIndexControl.java:920)
    at com.sap.glx.core.cluster.CollectiveIndexControl.acquire(CollectiveIndexControl.java:1076)
    at sun.reflect.GeneratedMethodAccessor722.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:240)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:466)
    at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

    Hi
    Refer the SAP note for exception "com.sap.bpem.tm.exception.NoSuchTaskException: Task"
    2036326 - 'NoSuchTaskException' error while opening a task
    BR
    SS

  • BPM 11g - Abort process instance

    I have a BPMN process that does 3 things:
    1. Calls the third party interface
    2. Starts the Timer proces aynchronously. This timer process is to make sure that the task gets picked up up an admin user (Human Task);if we don't get the response within the agreed time limit.
    3. Awaits the response.
    So, when we get the response back from the backend system, it should do 2 things:
    1. Stop the timer process.This could either be in a waiting state (i.e if the timer hasn't expired) or might have moved to the Human task step.
    2. Notify the awaiting instance so that it is then moved onto the next step in the process.
    I have used correlationId to match the request and response.It is working (with Send/Receive task) and notifying the waiting instance, but I am not sure how to abort the running Timer process.
    Should I use an interrupting event subprocess in my Timer process, that if called should throw an exception. This will then move the Timer process instance to the Exception handling flow and that will lead to the termination of the process instance, or is there a better way to achieve this. TaskService is the other option I thought of, but to achieve this simple thing, I thought that would be an overkill. Is there a re-commended pattern to meet this requirement.
    Thanks
    Raj
    Edited by: user588394 on 21-Feb-2013 09:04

    Hi Raj
    1. Terminate means you want to End that Process no matter where it is at any instance of time. Say if I have BPM Process with 10 SwimLanes it can be at any of the Lanes with any User. I am taking simple Example with Human Tasks, but you can apply for other component like Timer servces etc.
    2. I hope you are aware of 2 things specially for Human Tasks: Action named "Withdraw" and a role named "Process Owner". For any human task, under Actions menu you should See a Withdraw option. You can code your application to capture this output using XOR gateway and if outcome is "WITHDRAW" directly end the process and go to End Node. If you have many places like this, there is easy way instead of running wires eveywhere. Create a simple throw even that goes to End Node. And after each human task check outcome if Withdraw, that that error, which will end the process. I hope you got the point.
    b) The reason I mentioned Process Owner is, generally I do NOT give Withdraw control to each User who can work on any Task. If accidentally that User do this action, thats it. The process ENDS and you can never retriive it back. So under .TASK file, I preven Withdraw action to Asssignee and Instead give this action only to OWNER (Process Owner). Process owner is like admin who can pretty much see any tasks and I would give him all the permissions like these Withdraw, Reassing, Suspend etc etc. This gives more controlled power to your application. Anyhow, in bpm workspace, login as process owner and search for any Task aged for long time and jus Withdraw it.
    You can do all the above using APIs also as far as you have Withdraw action going to the End Node.
    If your requirement is something else, ignore above notes. But still you can think along the above lines, if all you want is to Kill a Running Process anytime.
    Thanks
    Ravi Jegga

  • Cancel process instance CE 7.2

    Hi,
    it is not possible to cancel some of the process instances shown in NWA->manage processes.
    If I try there is an error and the default trace shows the following:
    Error while resuming process instance '2713e1d90ae511e0c1de0000001532c2'.
    [EXCEPTION]
    com.sap.glx.adapter.api.AdapterException: Failed to cancel instance(s).
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.cancelProcessInstances(BPMNAdapter.java:2543)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.cancelProcessInstance(BPMNAdapter.java:2511)
    at com.sap.glx.process.impl.ProcessManagerImpl.cancelProcessInstance(ProcessManagerImpl.java:1248)
    at com.sap.glx.process.impl.ProcessManagerImpl.cancelProcessInstances(ProcessManagerImpl.java:1266)
    at com.sap.glx.process.impl.ProcessManagerBean.cancelProcessInstances(ProcessManagerBean.java:279)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    Any idea how to cancel these process instances?
    Thanks,
    Kevin

    Status is in process
    Here the stack trace:
    Error while resuming process instance '8e4c498309bc11e0b5eb0000001532c2'.
    [EXCEPTION]
    com.sap.glx.adapter.api.AdapterException: Failed to cancel instance(s).
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.cancelProcessInstances(BPMNAdapter.java:2543)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.cancelProcessInstance(BPMNAdapter.java:2511)
    at com.sap.glx.process.impl.ProcessManagerImpl.cancelProcessInstance(ProcessManagerImpl.java:1248)
    at com.sap.glx.process.impl.ProcessManagerImpl.cancelProcessInstances(ProcessManagerImpl.java:1266)
    at com.sap.glx.process.impl.ProcessManagerBean.cancelProcessInstances(ProcessManagerBean.java:279)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:39)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:23)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy2199.cancelProcessInstances(Unknown Source)
    at com.sap.glx.nwa.pm.SAP_ITSAMGalaxyProcessManagerImpl.cancelProcessInstance(SAP_ITSAMGalaxyProcessManagerImpl.java:696)
    at com.sap.glx.nwa.pm.SAP_ITSAMGalaxyProcessManagerWrapper.invoke(SAP_ITSAMGalaxyProcessManagerWrapper.java:329)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:468)
    at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
    at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:547)
    at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
    at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:340)
    at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
    at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:289)
    at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
    at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.invoke(ITSAMUIMBeanServerConnectionWrapper.java:350)
    at com.sap.tc.lm.itsam.ui.proxy.JMXGenericModelClassMBean.invokeOperation(JMXGenericModelClassMBean.java:613)
    at com.sap.tc.lm.itsam.ui.proxy.JMXAbstractModelClass.invokeOperation(JMXAbstractModelClass.java:159)
    at com.sap.tc.bpem.nwa.processmgmt.procmgmt.model.SAP_ITSAMGalaxyProcessManager.cancelProcessInstance(SAP_ITSAMGalaxyProcessManager.java:155)
    at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmt.CancelProcesses(ProcMgmt.java:847)
    at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.wdp.InternalProcMgmt.CancelProcesses(InternalProcMgmt.java:395)
    at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmtView.onActionProcessCommand(ProcMgmtView.java:2030)
    at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.wdp.InternalProcMgmtView.wdInvokeEventHandler(InternalProcMgmtView.java:896)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:514)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:55)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1689)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1503)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:918)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:890)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:343)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:400)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:80)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:54)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:746)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:202)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:81)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.cancelProcessInstances(BPMNAdapter.java:2540)
    ... 105 more
    Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_PDF_Rolle:DISRUPTOR(
    object){
      delete object;
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:68)
    at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:138)
    at com.sap.glx.core.kernel.mmtx.PrimaryTransaction.inPrepare(PrimaryTransaction.java:119)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:200)
    ... 107 more
    Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "delete object"
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:803)
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:63)
    ... 110 more
    Caused by: com.sap.bpem.tm.exception.TechnicalTaskException: Unable to retrieve parent go for go: 952bd6d6-09bc-11e0-ca1e-0000001532c2
    at com.sap.bpem.tm.adapter.cachestore.CachingTaskStore.getTaskInstanceId(CachingTaskStore.java:346)
    at com.sap.bpem.tm.adapter.cachestore.CachingTaskStore.dump(CachingTaskStore.java:319)
    at com.sap.bpem.tm.adapter.cachestore.CachingTaskStore.remove(CachingTaskStore.java:334)
    at com.sap.bpem.tm.adapter.invocation.TaskInvocationHandler.onDestruction(TaskInvocationHandler.java:311)
    at com.sap.glx.core.dock.impl.DockObjectImpl.deletion(DockObjectImpl.java:226)
    at com.sap.glx.core.dock.impl.DockObjectImpl.delete(DockObjectImpl.java:565)
    at com.sap.glx.core.kernel.trigger.config.Script$DeleteInstance.execute(Script.java:298)
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:798)
    ... 111 more

  • Synchronizing on Process Instance Object

    Hi,
    We have a process web service, which is used to create, notify and update BPM process instances.
    This process web service is accessed from Java code.
    The java code uses a re-try mechanism to talk to the process web service.
    We want this to be changed using wait-notify. But we have only the string value for Process Instance ID.
    Can anybody help me on how could we get the BPM process instance object with the Process Instance ID?
    I hope for this case we should synchronize on the BPM process Instance Object.
    Please find below the current code snippet with re-try which needs to be changed as wait-notify.
    for(int i = retryCount; i >= 0; i--) {
    try {
    sResult = wsClient.notifyUpdate(oEvent, oTG, sInstId);
    break;
    catch(Exception e) {
    if(i == 0) {
    throw e;
    logger.error(getClass().getName() + " - Failed to call wsClient.notifyUpdate()");
    try {
    logger.info(getClass().getName() + " - Retrying bpmUpdateProcessInstance ... " + (retryCount - i + 1) + " times in "
    + (System.currentTimeMillis() - startTimeMillis) + " millis.");
    Thread.sleep(retryInterval);      
    catch(InterruptedException ignore) {
         //silent catch is fine here
    }// end for loop

    Hi,
    Please correct me if I miss-understood your question.
    You want to know the process instance Id of a particular BPM process ?
    You want to do it through java code or in BPM process layer ?
    Which version of OBPM/ALBPM you are using ?
    Bibhu

  • Deleting Process Instances in Guided Procedures of NW CE 7.1

    Hi,
    I would like to ask is there a way to delete initiated process instances in Guided Procedures? I am facing this problem that in my Runtime there are so many outdates process instances (for previous test purpose) remaining, for example:
    - Alerts & Warnings (24)
    - Processes which I own (20)
    - Processes which I oversee (20)
    - Tasks that require my action (17)
    I have found the following article regarding the problem ([Guided Procedures - New and Enhanced Features in SAP NW CE 7.1 EHP1|http://help.sap.com/saphelp_nwce711/helpdata/en/87/563934e3f34114901ff69cd041ba38/content.htm]). But it seems that it is only available in EhP1.
    When I navigate to Administration -> Manage Processes -> Find Processes.
    I only can see these 3 buttons: "Change Authorization", "Terminate Instances" & "Complete Step". But without the "Delete Instances".
    Using the "Terminate Instances" did not solve my problem too.
    So I resort to this:
    Guided Procedures Runtime -> Administration -> Maintain processes -> Archiving and Deleting -> Maintain Process Templates -> Global Settings -> Global Settings for Process Instances:
    Completed:
    - Delete (After 1 day)
    Erroneous:
    - Delete (After 1 day)
    Terminated:
    - Delete (After 1 day)
    Still, this did not help me deleting the process instances.
    Could anyone provide me a solution?
    Regards,
    Joon Meng

    solved.

  • Process instances do not show in BPEL Console

    Hi all,
    I have a BPEL, which reads a files from a particular folder if any, Process records in that file and then stores it in database.
    I am facing a problem, my records gets processed, this BPEL works fine, as i can see the output in database, however associated instances are not shown in the BPEL Console. But if i restart the process (i.e. Switch OFF the process and Again Switch ON) it shows me all the previous instances and also the current instances. But sometime again this problem occurs.
    Has anyone faced the same issue? Please let me know in case anyone has solution.
    Thanks in advance.

    [http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf|http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf] I found below in SOA best practices guide:
    Why Does the Instance of an Invoked Process Not Display in Oracle BPEL Control?
    If the process invoked is asynchronous, the message headers and payload are stored in
    the invoke_message table. The invocation message is then processed by a
    background thread to create an asynchronous BPEL process instance. If an error is
    encountered while processing the invocation message, the transaction is rolled back
    and the invoke message remains in its unhandled state in the invoke_message table.
    See "How Does an Invoke Message and Activity Display in the Manual Recovery
    Page?" on page 1-18 for more details on this scenario.
    If the process invoked is synchronous, the cause for the missing instance is likely a
    transaction rollback. The reasons for a transaction rollback are as follows:
    ■ Third party manipulation of the JTA transaction. As described in "How Do I Force
    a Rollback in a BPEL Flow?" on page 1-5, a failed database adapter invocation can
    cause the TopLink layer to mark the JTA transaction for rollback. Because Oracle
    BPEL Server relies on the JTA transaction for persistence (not just as a signaling
    mechanism between transaction-aware modules), any changes to the status of the
    transaction impact Oracle BPEL Server’s ability to dehydrate the instance.
    ■ Transaction timeout. The synchronous process may be invoking one or more
    backend synchronous services; the total time of all the backend calls may exceed
    the timeout value for the transaction. See "How Do I Modify Transaction Timeout
    Settings for Oracle BPEL Server?" on page 1-9 for details on how to increase the
    transaction timeout value.
    ■ Failure to dehydrate the synchronous instance to the database. If the
    completionPersistPolicy is set to on, the instance attempts to save itself
    before returning to the caller. Typically, errors are encountered during this step if
    the database connection has been severed or the tablespace is full. Some customers
    Transactions
    Oracle BPEL Process Manager 1-9
    have encountered problems with saving the audit trail of the instance. For
    example, there are problems with JDBC batching in 10.1.3.1.0 that the audit trail
    persistence code uses. When a synchronous invocation does not result in an
    instance visible from Oracle BPEL Control (assuming that
    completionPersistPolicy is set to a value of on, deferred, or faulted),
    use the following steps to find the underlying error:
    – Enable all loggers to debug mode.
    – Resubmit the invocation message.
    – Check the Oracle Process Manager and Notification Server (OPMN) or
    command-line log for the underlying exception stack trace.
    Please refer to link below:
    http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf

  • How to create BPM process instances?

    I need to use java to create new BPM 11.1.1.5 process instances.
    How to connect to bpm and use API?
    Can anyone paste detail code sources?

    Thanks Evolution...i actually missed out this lookup....
    Now provisioning is working fine for other resource object also...
    I have one more doubts regarding child table...i am using the same child table UD_ADUSRC for this resource object also and when i assigned any group membership thru this child table (in AD User1) it gives me DOBJ.insert failed error. I have checked the tasks (+Add user to group, Remove user from group, update user to group+) and all are referring the correct attrs (as in AD User). There is mapping defined in Resource Object and Process definition for Reconciliation also but recon any user with group membership is also giving me error...
    can't we use one child form in two process forms ? any other configuration which i should check?
    I am using the same look up for Reconciliation mapping attrs for both the resource objects (AD User and AD User1)....

  • Process instances stop at timer event

    Hi,
    I modelled a process with intermediate timer event. When this timer expires an automatic activity is invoked which checks certain conditions. If these conditions are not met the process token returns to the timer until the conditions are met and another process path is entered. I observed quite a lot of process instances which stoped at this timer event, meaning: the timer doesn't expire any more and the entire process instance stands still. The reason for this seems to be:
    - database filled up (ok, this shouldn't happen. I accept that this has severe consequences)
    - restart of application or netweaver
    - running process archiving run
    Is there a way to reactivate these process instances other than aborting the current instance and starting a new one?
    Timer events use GalaxyTimerJob. I assume an appropriate database entry failed. Can I add this missing table entry by executing SQL commands or isn't it as easy as that?
    Thanks
    Regards
    Anja

    Hi Nick,
    yes, suspending and resuming doesn't change anything. 'Instance restart': you mean restarting NetWeaver? In fact, it seems to me, that fixes the problem for some process instances, but too many stay in their "corrupt" status.
    Can I execute some SQL statements to add this GalaxyTimerJob database entry? Even if there are such statements, would it be too critical as the various process instances might be in different states and the execution of such statements might rather brake than fix things?
    Regards
    Anja

  • Executing multiple process instances in a batch

    In one of our processes we need to execute multiple process instances together in one go. In order to accomplish this, we have taken a new process which takes a list of instanceStampIds to be processed and then using PAPI processing them one after another in a loop. There is a grab actibity defined, named "GrabAndProcess" to Grab the process instance and then to execute it. We're getting the exception: "Cannot invoke on remote components" while getting process instance using getInstance() in the code below. Here is the code:
    logMessage("\[MultiReconcile\]\[reconcileTask\] Inside Reconcile Task... " + instanceStampId);
    // Pre-Process instanceStampId
    instanceStampIdList = instanceStampId.split(delim : "!");
    // Define the arguments of the activity.
    argumentSet\["reconcilerCommentsArg"\] = reconcilerComments;
    argumentSet\["newStatusArg"\] = newStatus;
    argumentSet\["reconcilerIdArg"\] = reconcilerId;
    logMessage("\[MultiReconcile\]\[reconcileTask\] instanceStampIdList.length: " + instanceStampIdList.length());
    logMessage("\[MultiReconcile\]\[reconcileTask\] Connecting to ReconcilationProcess... ");
    ClientBusinessProcess.connectTo(processId : "/ReconcilationProcess");
    logMessage("\[MultiReconcile\]\[reconcileTask\] Connected to ReconcilationProcess... ");
    foreach (instanceStampIdVal in instanceStampIdList) {
    logMessage("\[MultiReconcile\]\[reconcileTask\] Inside loop... instanceStampId: " + instanceStampIdVal);
    // Pre-process Instance Id
    instanceStampIdParts = instanceStampIdVal.split("/");
    String baseInstanceStampId = "";
    for (int part=0; part < instanceStampIdParts.length - 1; part++) {
    if (instanceStampIdParts[part].compareTo("") != 0)
    baseInstanceStampId = baseInstanceStampId + "/" + instanceStampIdParts[part];
    logMessage("\[MultiReconcile\]\[reconcileTask\] instanceStampId: " + instanceStampIdVal);
    logMessage("\[MultiReconcile\]\[reconcileTask\] baseInstanceStampId: " + baseInstanceStampId);
    // Grab Instance
    try {
    logMessage("\[MultiReconcile\]\[reconcileTask\] processInstanceId: " + baseInstanceStampId);
    logMessage("\[MultiReconcile\]\[reconcileTask\] Getting Process Instance..." + baseInstanceStampId);
    instance = ClientBusinessProcess.processService.getInstance(instance : baseInstanceStampId);
    logMessage("\[MultiReconcile\]\[reconcileTask\] Instance " + baseInstanceStampId + " Retrieved.");
    logMessage("\[MultiReconcile\]\[reconcileTask\] Grabbing Instance... " + instanceStampIdVal);
    instance.grab(grabActivity : "GrabAndProcess");
    if (instance.grabbed) {
    logMessage("\[MultiReconcile\]\[reconcileTask\] Instance " + instanceStampIdVal + " grabbed successfully!");
    // Process Instance
    instance.runTask(activity : "GrabAndProcess", args : argumentSet);
    reconcileResult = reconcileResult + "\nInstance " + instanceStampIdVal + " processed successfully!";
    logMessage("\[MultiReconcile\]\[reconcileTask\] Instance " + instanceStampIdVal + " processed successfully!");
    catch (Java.Lang.Exception e) {
    reconcileResult = reconcileResult + "\nInstance " + instanceStampIdVal + " could not be processed!";
    logMessage("\[MultiReconcile\]\[reconcileTask\] Exception occurred while processing instance " + instanceStampIdVal);
    logMessage("\[MultiReconcile\]\[reconcileTask\] Exception: " + e.message);
    logMessage("\[MultiReconcile\]\[reconcileTask\] Done with processing instanceStampId " + instanceStampIdVal);
    logMessage("\[MultiReconcile\]\[reconcileTask\] Leaving Reconcile Task... " + instanceStampId);
    display (reconcileResult);
    Why is it giving the execption "Cannot invoke on remote components"? What's wrong in the above approach?
    Any help in resolving the issue will be highly appreciated.
    Thanks,
    MK
    Edited by: goelmk on May 6, 2009 3:11 PM

    Hi,
    Could you go into your use case a little bit? I'm confused why you're using PAPI and the automatic grab functionality.
    Going under the assumption, you're trying to use it to do ad hoc routing of intstances. If this is the case, here's another approach to using an automatic grab to route instances. The "instF" search would need to be modified to suit your use case:
    BusinessProcess bp;
    try {
        logMessage("PapiHelper: actionGrabAndRoute: Entry: instance: " + instanceToActOn.instanceIn, severity : DEBUG);
        InstanceFilter instF = InstanceFilter();
        Fuego.Instance[] instances;
        String instanceDescription;
        bp.connectTo(url : Fuego.Server.directoryURL, user : "AUTOCLIENT", password : "P",
                     process : "/" + processName);
        instF.create(processService : bp.processService);
        instF.searchScope = SearchScope(participantScope : ParticipantScope.ALL, statusScope : StatusScope.ONLY_INPROCESS);
        instF.addAttributeTo(variable : VarDefinition.INSTANCE_NUMBER, comparator : Comparison.IS,
                             value : instanceToActOn.instanceIn);
        instances = bp.getInstancesByFilter(filter : instF);
        foreach (inst in instances) {
            logMessage("PapiHelper: actionGrabAndRoute: Found it: " + inst.id, severity : DEBUG);
            try {
                // change this to be the name of your Grab Activity
                inst.grab(grabActivity : "GrabAutomatic");
                logMessage("PapiHelper: actionGrabAndRoute: Grabbed Instance Status: " + inst.grabbed, severity : DEBUG);
                try {
                    inst.runTask(activity : "GrabAutomatic");
                    logMessage("PapiHelper: actionGrabAndRoute: Ran Grab " + inst.grabbed, severity : DEBUG);
                catch (Exception e) {
                    logMessage("PapiHelper: actionGrabAndRoute: tried to run grab and failed because no task to run in Grab", severity : DEBUG);
                inst.route(activity : groupGrabAndRouteToActivityName);
                logMessage("PapiHelper: actionGrabAndRoute: Routed back", severity : DEBUG);
            catch (Exception e1) {
                logMessage("PapiHelper: actionGrabAndRoute: Exception when running or routing: " + e1.cause, severity : DEBUG);
                errors = errors + "Instance could not be grabbed and reassigned\n\n";
                logMessage("PapiHelper: actionGrabAndRoute: Errors: " + errors, severity : DEBUG);
    finally {
        bp.disconnectFrom();
    }Dan

Maybe you are looking for

  • How to use no of iteration of for loop as the input for the for loop

    hi all, i wanna need some help here.. i'm using for loop to iterate to ceratin no of iteration.. then, i would like to use back the no of iteration as the input of 'N' for the next iteration.. in other word, eg: 1st run: i insert a control to 'N', le

  • How can identify the default currency for a customer?

    How can identify the default currency for a customer? I know that this is being determined when you create a sales order for a particular customer, for example, so I could break this process open and find out what it uses. But I thought it worth aski

  • Flex + cairngorm problem with 2 webservice

    hi i want to retrive data from 2 webservices using cairngorm.  flex can get data from the firsone and from the second is telling that doesn't see method, for me it is cos service it trying to find method from second webservice in this firstone. so wh

  • Dynamic Update Failed. Evend ID 8011

    Our environment uses Active Directory, DNS servers (not AD integrated) and static IP Addresses (not DHCP). All of them are Windows 2012 R2. The DNS zone accepts dynamic update and the client is configured to register on the correct DNS Zone name. We

  • Internet Explorer Options for IP Layouts

    Hi, We are executing IP layouts on Internet explorer, some of the users are having different challenges like the variable screen not poping up, download to excel giving a pop-up. Are they any NOTES or White Papers on IE browser settings for IP layout