- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Exception when debugging rule service initializa tion - BA 6.10.1 .NET
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
02-14-2012 06:01 AM - edited 02-14-2012 06:01 AM
Hi
Environment: Win 7 64 bit, BA 6.10.1 .NET 64 bit, NET Framework 4.0, Visual Studio 2010. Direct repository access with dmanager, no precompiled adb. Executing code by running/debugging unit tests from Visual Studio.
We are having problems in all our projects when debugging code that invokes a rule service.
An exception occurs when calling NdStatelessServer.invokeService, but only when debugging tests. When running tests without debugging it works fine.
java.rmi.RemoteException: "Error getting project file contents"
inner exception:
java.lang.IllegalArgumentException: "Field 'G' defined on type 'com.blazesoft.engines.rules.NdRuleSet' is not a field on the target object which is of type 'com.blazesoft.engines.rules.NdRuleSet+RuleSetEval
inner exception:
System.SystemException [System.ArgumentException]
_exceptionMethod: Void CheckConsistency(System.Object)
_Message: Field 'G' defined on type 'com.blazesoft.engines.rules.NdRuleSet' is not a field on the target object which is of type 'com.blazesoft.engines.rules.NdRuleSet+RuleSetEval
_source: '"mscorlib"
Anyone got some pointers on what we are doing wrong here?
Solved! Go to Solution.
Re: Exception when debugging rule service initializa tion - BA 6.10.1 .NET
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Not the Solution
- Email to a Friend
- Report Inappropriate Content
02-15-2012 10:30 AM
No one got any similar experiences?
Re: Exception when debugging rule service initializa tion - BA 6.10.1 .NET
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Accept as Solution
- Email to a Friend
- Report Inappropriate Content
03-08-2012 01:01 PM
I've done a bit of investigating on this issue today using a clean project, and it seems what triggers is for us is the combination of
- 64 bit referred assemblies
- Deployment manager
- Debugging the invocation of a rule service through a Unit Test
I'm surprised no one else have had this issue if that's all it takes? Can anyone confirm having success with this setup?

