Eclipse Community Forums: Memory Analyzer (MAT) » IllegalArgumentException In OQL Statement

Help

Home

Home » Archived » Memory Analyzer (MAT) » IllegalArgumentException In OQL Statement

Show: Today's Messages :: Show Polls :: Message Navigator

IllegalArgumentException In OQL Statement [message #3589]

Wed, 27 August 2008 16:38

Erik Onnen

Messages: 1
Registered: July 2009

Junior Member

I'm attempting an OQL statement where I use <String>.value.toString(). For
example:

SELECT s.value.toString() FROM java.lang.String s

The query completes but renders char[] with address, length and size, but
not the actual string. The same query works fine in the jhat OQL console.

When executing the query, I receive an IllegalArgumentException dialog
with Details:

"An error has occurred. See error log for more details."
"Argument not valid"

I'm not sure what error log the dialog is referring to, and the console
has no further information.

I'm running Memory Analyzer as a plugin in Eclipse 3.4, JDK 1.6.0_10-beta
x86_64 on a 2.6.22-15 linux kernel.

Report message to a moderator

Re: IllegalArgumentException In OQL Statement [message #3655 is a reply to message #3589]

Thu, 28 August 2008 07:31

Andreas Buchen

Messages: 123
Registered: July 2009

Senior Member

Erik Onnen wrote:
> SELECT s.value.toString() FROM java.lang.String s

Try: SELECT toString(s.value) FROM java.lang.String s
Or: SELECT toString(s) FROM java.lang.String s

Currently, if one calls #toString(), the actual method of the object at
hand is executed - which is of course not a String, but an object
representing the String object found in the heap. But I guess I should
change this to make it more intuitive.

> When executing the query, I receive an IllegalArgumentException dialog
> with Details:

> "An error has occurred. See error log for more details."
> "Argument not valid"

If you select "Window" -> "Error Log" inside the Memory Analyzer, you see
the Eclipse error log. Double-click on the log entry to see the stack
trace. The full log is also kept at ~/mat/workspace/.metadata/.log.

If the problem persists, it would be great if you could open a bugzilla
bug so that I can check into that:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=MAT

Andreas.

Report message to a moderator

Previous Topic:	Any known issues with analyzing huge heap dumps?
Next Topic:	Finding top n largest strings

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Dec 12 18:39:32 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter