Colin,

Thanks for the reply. The class just has a Name and an Id field, both 
strings. The Id field is indexed, UNIQUE (UUID, used as a PK).

The first query worked as expected:

select out() from #128:245823

----+------+----
#   |@CLASS|out
----+------+----
0   |null  |[5]
----+------+----

1 item(s) found. Query executed in 1.562 sec(s).


The second query never returned, but produced the following Console output:

 select expand(out()) from #128:245823

Error: com.orientechnologies.orient.core.exception.OStorageException: Error 
on executing command: sql.select expand(out()) from #128:245823

Error: java.lang.IllegalArgumentException: Unsupported record type: 0

Error: java.lang.IllegalArgumentException: Record type '0' is not supported

And the exception from the server console was this:

2015-03-16 17:49:48:617 INFO  OrientDB Server v2.0.3 is active. 
[OServer]java.lang.OutOfMemoryError: GC overhead limit exceeded
Dumping heap to java_pid4188.hprof ...
Heap dump file created [1407643643 bytes in 16.454 secs]
Sent run-time exception to the client /127.0.0.1:64960: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
        at java.util.Arrays.copyOf(Unknown Source)
        at java.lang.AbstractStringBuilder.expandCapacity(Unknown Source)
        at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown 
Source)
        at java.lang.AbstractStringBuilder.append(Unknown Source)
        at java.lang.StringBuffer.append(Unknown Source)
        at java.io.StringWriter.write(Unknown Source)
        at java.io.PrintWriter.write(Unknown Source)
        at java.io.PrintWriter.write(Unknown Source)
        at java.io.PrintWriter.print(Unknown Source)
        at java.io.PrintWriter.println(Unknown Source)
        at java.lang.Throwable$WrappedPrintWriter.println(Unknown Source)
        at java.lang.Throwable.printStackTrace(Unknown Source)
        at java.lang.Throwable.printStackTrace(Unknown Source)
        at 
com.orientechnologies.common.log.OLogFormatter.format(OLogFormatter.java:58)
        at java.util.logging.StreamHandler.publish(Unknown Source)
        at java.util.logging.ConsoleHandler.publish(Unknown Source)
        at java.util.logging.Logger.log(Unknown Source)
        at java.util.logging.Logger.doLog(Unknown Source)
        at java.util.logging.Logger.log(Unknown Source)
        at 
com.orientechnologies.common.log.OLogManager.log(OLogManager.java:116)
        at 
com.orientechnologies.common.log.OLogManager.error(OLogManager.java:182)
        at 
com.orientechnologies.orient.core.fetch.OFetchHelper.processRecord(OFetchHelper.java:316)
        at 
com.orientechnologies.orient.core.fetch.OFetchHelper.fetch(OFetchHelper.java:72)
        at 
com.orientechnologies.orient.server.network.protocol.binary.OAbstractCommandResultListener.fetchRecord(OAbstractCommandResultListener.java:54)
        at 
com.orientechnologies.orient.server.network.protocol.binary.OSyncCommandResultListener.result(OSyncCommandResultListener.java:40)
        at 
com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.command(ONetworkProtocolBinary.java:1215)
        at 
com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:385)
        at 
com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:220)
        at 
com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:69)


Processor utilization started out around 20%, then just before it quit, 
jumped to > 80%, probably while it was writing the dump file.

Any suggestions are welcome. I've already increased the heap size, by the 
way.

Thanks,

Patrick

On Monday, March 16, 2015 at 2:40:59 PM UTC-6, Colin wrote:
>
> Hi Patrick,
>
> It's very difficult to say for sure without knowing the schema and the 
> number of edges going out from the record #128:245823.
>
> I would try this exact same scenario from the console and see if you get 
> an error or if it returns a proper result.  It might just be a bug in 
> Studio.
>
> -Colin
>
> Orient Technologies
>
> The Company behind OrientDB
>
> On Monday, March 16, 2015 at 2:53:47 PM UTC-5, Patrick Hoeffel wrote:
>>
>> Using OrientDB 2.0.3 Community Edition with a populated graph having 2M 
>> vertices and 11M edges:
>>
>> This query:
>>
>>      `select out() from #128:245823`
>>
>> returns 1 row with 5 links in 0.026 second.
>>
>> This query:
>>
>>      `select *expand*(out()) from #128:245823`
>>
>> does not return at all and crashes Chrome. 
>>
>> Does anyone see what I may be doing wrong, what I do not understand about 
>> the `expand()` function?
>>
>> Thanks!
>>
>> Patrick
>>
>>
<https://lh6.googleusercontent.com/-OEon6ltOFkI/VQdUj4JjmvI/AAAAAAAAQZM/i8VTagoQk8E/s1600/Console%2B1.PNG>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to