| Author |
Message
|
| Sunray |
 Posted: Wed Sep 22, 2004 11:32 am Post subject: (SOLVED)Problem With NOOP |
 |
|
Newbie
Joined: 03 Feb 2004
Posts: 6
|
Hi all,
I am on Workflow 3.5, using NOOP activity in my flow. NOOP is working fine when I am starting the flow using Workflow client and as well as from Web Client and is flowing according to the conditions. But when we are using JSP page to create and start the instance, that process instance is struck at NOOP activity, and shows INERROR state, so I am realizing that the problem in Workflow as it said INERROR state. But I defined all the definitions for NOOP required.
If the NOOP is not defined properly why it is working in Thick client and also in Webclient. I am getting that problem only when JSP trying to start the workflow. JAVA code is successfully starting the request. But if the flow starts in such a way then I did see that problem of INERROR state.
When I click on Instance Monitor in Webclient, I did see the following error.
FMC00138E Process activity NoOpActivity has one of its own parent processes assigned. Following is the chain of processes: CC=0.
Please help me.
_________________
Sunray
Last edited by Sunray on Mon Sep 27, 2004 1:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Sep 22, 2004 11:54 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
IS Your NOOP activity the first activity in your process instance?
When you say it is working with STANDARD fat and web clients is it manually started? If yes, then what about the I/P DS for that process.
If you are using a JSP then how are you starting the process instance
Issuing a java api call are through XML? |
|
| Back to top |
|
|
| Sunray |
| Posted: Wed Sep 22, 2004 12:48 pm Post subject: |
|
|
Newbie
Joined: 03 Feb 2004
Posts: 6
|
Vennela,
Our NOOp activity is the first activity in the process
we are using java api call to create and start the process. ( not the XML)
We are using the same DS as I/P to start the process instance that is defined in the workflow.
_________________
Sunray |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Sep 23, 2004 9:05 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
The Noop must have a default connector coming out, or you might get this error.
Have a look at the EmptyActivity doc from IBM. Go to the IBM search site, and search on NOOP and you should find a link. There may also be a link to it in this forum.... Search here first.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Sunray |
| Posted: Mon Sep 27, 2004 1:32 pm Post subject: SOLUTION |
|
|
Newbie
Joined: 03 Feb 2004
Posts: 6
|
Thanks Jmac and Vennela for your help.
Here is the solution for my problem.
I defined the binary decision controle after noop activity as an emty string or non empty string, It is working fine if i start the process with web client or from thick client as we are filling that field, But if the JSP page starts the process Instance it is filling either spacess or Null at that field for which i haven't defined that condition. So it is remaining at the the NOOP activity itself and showing inerror state. We solved it by setting up an initial value and comparing that initial value we are controlling the flow, where you have only two options. Either 'yes' or 'no' choices.
We just messed up by thinking that the problem with NOOP, and now we realised that it not the proble with noop, but the problem is at the decision we are using after noop.
Thanks for your efforts.
_________________
Sunray |
|
| Back to top |
|
|
| amithshenoy |
| Posted: Fri Aug 11, 2006 12:13 pm Post subject: |
|
|
Newbie
Joined: 11 Aug 2006
Posts: 2
|
I had a similar problem. I had a noop activity just before the sink. It used to branch to several asynchronous activities with some transit condition for each control flow.
In one case, the container values were set such that all these transit conditions were false due to which it stayed where it was with this error.
The solution we put was we added another noop activity before the sink and connected this previous noop activity to this new noop activity through a default connector.
Now atleast, if all the transition conditions are false, it will still go to the default connector and terminate.
Hope it helps.
_________________
Thanks,
Amith |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Aug 11, 2006 12:31 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What makes you reply to a two year old post and that too which is marked solved.
Eitherway, welcome to the forum. |
|
| Back to top |
|
|
| amithshenoy |
| Posted: Fri Aug 11, 2006 12:35 pm Post subject: |
|
|
Newbie
Joined: 11 Aug 2006
Posts: 2
|
Just thought will help somebody in future...
Thanks for the welcome...sure you spend a lot of time on this forum...
_________________
Thanks,
Amith |
|
| Back to top |
|
|
|
|
