This content has been marked as final. Show 4 replies
I deleted the decision service and built the whole thing up from scratch again and got back to the point where I was when the error occurred, but this time with no exception. It doesn't make any sense. It smells like some sort of caching problem.
Well, this could well be my final posting on this forum. I've put forward four separate questions over the last couple of weeks and have had back not one reply. After battling with JDeveloper for two weeks now I go before the decision panel tomorrrow to recommend an interfaces approach for the software we are building. Given the battles I've had with SOA Suite/JDev, combined with lack of transparency of errors or meaningful logging, as well as the 0% return on the questions I've asked in this forum... what can I say?
I know this is an old thread, but I'm sure someone else will get this error like I and the original poster did.
I got the same error and couldn't figure out what it was. There were no gaps in the rules and after reading through the XML I couldn't find this "more than one instance" of a fact type.
So I ended up deleting the rule and it's references, recreating it with the same rules and values and it worked. I don't know why this works as the XML should be the same.
If anyone else comes up with a way around this error I'd be glad to hear it.
You are creating more than one instance of the same fact and Rules Engine cannot decide which instance to use. This happens when more than one rule creating the same type of instance is scheduled to fire. You may be expecting a modify statement to disable one of the rules but that particular rule which you expect to be disabled might be firing before the rule that disables it.