Buffer inconsistency with REQUEST_DB_LIST

43 views
Skip to first unread message

Giraldo Rosales

unread,
Mar 26, 2014, 5:43:28 PM3/26/14
to orient-...@googlegroups.com
When running REQUEST_DB_LIST by itself after REQUEST_CONNECT, runs fine, returns the single database, 

GratefulDeadConcerts. When running the following sequence,

REQUEST_CONNECT
REQUEST_DB_EXIST
REQUEST_DB_LIST

Where the params for db exists is either a non-existent db or the GratefulDeadConcerts db. The buffer for the REQUEST_DB_LIST comes back invalid. It seems to have a larger buffer length than when leaving out REQUEST_DB_EXIST. Why is the buffer length coming in at different sizes?

Using the latest binary, 1.7

Giraldo Rosales

unread,
Mar 26, 2014, 10:23:03 PM3/26/14
to orient-...@googlegroups.com
When converting the buffer to a string, it returns:

|java.lang.NullPointerExceptionάsrjava.lang.NullPointerExceptionG1xrjava.lang.RuntimeException_G

detailMessagetLjava/lang/String;[va.lang.Throwable5'9wLcausetLjava/lang/Throwable;L

stackTracet[Ljava/lang/StackTraceElement;LsuppressedExceptionstLjava/util/List;xpqpur[Ljava.lang.StackTraceElement;F*<<"9xp

                                                                                                                            srava.lang.StackTraceElementa Ś&6݅I

lineNumberLdeclaringClassq~fileNameq~L

methodNameq~xpRtCcom.orientechnologies.orient.core.record.ORecordSchemaAwareAbstracttORecordSchemaAwareAbstract.javatgetSchemaClasssq~

                                                                                                                                      Uticom.orientechnologies.orient.core.serialization.serializer.record.string.ORecordSerializerSchemaAware2CSVt%ORecordSerializerSchemaAware2CSV.javatoStringsq~

                                                                                                                              \thcom.orientechnologies.orient.core.serialization.serializer.record.string.ORecordSerializerStringAbstractt$ORecordSerializerStringAbstract.javatoStreamsq~

                                                                                                                     q~q~q~sq~

q~q~sq~                                                                                                                       q~

q~q~sq~q~

       t7com.orientechnologies.orient.core.record.impl.ODocumenttODocument.javaq~sq~

                                                                                     tRcom.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBilistDatabasessq~ocolBinary.javat

                q~q~ texecuteRequestsq~

                                        ~tZcom.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstractt#OBinaryNetworkProtocolAbstract.javatexecutesq~

               -t/com.orientechnologies.common.thread.OSoftThreadtOSoftThread.javatrunsr&java.util.Collections$UnmodifiableList%1Llistq~xr,java.util.Collections$UnmodifiableCollectionB^LctLjava/util/Collection;xpsrjava.util.ArrayListxaIsizexpwxq~1x

Giraldo Rosales

unread,
Mar 27, 2014, 9:03:34 PM3/27/14
to orient-...@googlegroups.com
Seems to be similar to this problem:

It was giving me a warning when using a memory database, same as the link above. But I replaced the database directory with a fresh copy that just had GratefulDeadConcerts. With a fresh build, it still gave me the "java.lang.NullPointerException" error when running the binary commands in the order I have posted below.

Any thoughts or solutions? Is this a known bug or should it be added to the queue?

Thanks,
Giraldo

Luca Garulli

unread,
Mar 28, 2014, 6:25:44 AM3/28/14
to orient-database
Hi Giraldo,
this is a 100% bug. Let me check in...

Lvc@


--

---
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 orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Giraldo Rosales

unread,
Mar 28, 2014, 9:20:55 AM3/28/14
to orient-...@googlegroups.com

Thanks Luca! Thought I could be doing something wrong.

When you say "check in", do you mean it's already fixed and you have to do a push, or creating a bug issue on github?

You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/aHKiC4JRKcQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.

Luca Garulli

unread,
Mar 29, 2014, 1:58:05 PM3/29/14
to orient-database
Hi Giraldo,
it was a bug.. fixed under 1.7-SNAPSHOT just published.

Lvc@

Giraldo Rosales

unread,
Mar 29, 2014, 1:59:48 PM3/29/14
to orient-...@googlegroups.com

Perfect. Thanks!

Reply all
Reply to author
Forward
0 new messages