This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 207599 - IllegalArgumentException: Invalid argument count: expected 2, received 3
Summary: IllegalArgumentException: Invalid argument count: expected 2, received 3
Status: RESOLVED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-21 16:15 UTC by stefanocrosta
Modified: 2012-04-23 13:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 184636

Attachments
stacktrace (4.04 KB, text/plain)
2012-01-21 16:15 UTC, stefanocrosta 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description stefanocrosta 2012-01-21 16:15:38 UTC 
Build: NetBeans IDE 7.1 RC2 (Build 201111302200)
VM: Java HotSpot(TM) 64-Bit Server VM, 22.0-b10, Java(TM) SE Runtime Environment, 1.7.0_02-b13
OS: Windows 7

Stacktrace: 
java.lang.IllegalArgumentException: Invalid argument count: expected 2, received 3
   at com.sun.tools.jdi.MethodImpl.validateAndPrepareArgumentsForInvoke(MethodImpl.java:368)
   at com.sun.tools.jdi.ClassTypeImpl.invokeMethod(ClassTypeImpl.java:221)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.invokeMethod(EvaluatorVisitor.java:3301)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.visitMethodInvocation(EvaluatorVisitor.java:431)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.visitMethodInvocation(EvaluatorVisitor.java:194)
   at com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1338)
Comment 1 stefanocrosta 2012-01-21 16:15:45 UTC 
Created attachment 115143 [details]
stacktrace
Comment 2 Martin Entlicher 2012-04-23 13:37:50 UTC 
The exception seems to be a result of this call: DbFilterUtil.andFilter(...)
This is probably in Watches, this is why you get it many times.

Please provide some details about DbFilterUtil.andFilter(...) and how can we reproduce this.