Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Something wrong with binary protocol on 1.0rc7 [moved] #605

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Something wrong with binary protocol on 1.0rc7 [moved] #605

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 605 moved from a Google Code project.
Added by 2011-11-15T10:15:56.000Z by Anton.A....@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Done).

Original labels: Type-Defect, Priority-Medium, v1.0rc7

Original description

<b>What steps will reproduce the problem?</b>
1. Connect via console and dump data with Wireshark:
> connect remote:localhost/demo writer writer
Connecting to database [remote:localhost/demo] with user 'writer'...OK

Wireshark:
XX XX XX XX XX XX XX X 03 ff ff ff ff 00 00 00  ..x...x.........
05 74 61 73 6b 73 00 00 00 05 61 64 6d 69 6e 00  .tasks....admin.
00 00 05 61 64 6d 69 6e                          ...admin


Response:
XX XX XX XX XX XX XX XX 00 ff ff ff ff 00 00 01  ..y...x.........
ae 00 00 00 19 00 00 00 05 64 75 6d 6d 79 00 00  .........dummy..
--CUT--

Console is connected ok.
<b>2.</b>
Connect with binary via OrientDB-PHP

     0 : 03 ff ff ff ff 00 00 00 04 64 65 6d 6f 00 00 00 [.........demo...]
    10 : 06 77 72 69 74 65 72 00 00 00 06 77 72 69 74 65 [.writer....write]
    20 : 72                                              [r]
>protocol_version
     0 : 00 05                                           [..]
>request_status
     0 : 01                                              [.]
>TransactionID
     0 : ff ff ff ff                                     [....]
     0 : 01                                              [.]
>exception_javaclass
     0 : 00 00 00 2a                                     [...*]
     0 : 6a 61 76 61 2e 75 74 69 6c 2e 55 6e 6b 6e 6f 77 [java.util.Unknow]
    10 : 6e 46 6f 72 6d 61 74 43 6f 6e 76 65 72 73 69 6f [nFormatConversio]
    20 : 6e 45 78 63 65 70 74 69 6f 6e                   [nException]
>exception_message
     0 : 00 00 00 10                                     [....]
     0 : 43 6f 6e 76 65 72 73 69 6f 6e 20 3d 20 27 30 27 [Conversion = '0']
     0 : 00                                              [.]
<b>3.</b>

<b>What is the expected output? What do you see instead?</b>
Connect via binary failed, but bytes are identical. Could this the same problem, that affects building on MacOS?

<b>Please use labels and text to provide additional information.</b>
1.0rc7-snapshot
@lvca lvca closed this as completed Dec 10, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant