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

Was not calculated MAGIC_HEADER length for check_sum? #256

Closed
CaoJunCJ opened this issue Jan 21, 2019 · 5 comments
Closed

Was not calculated MAGIC_HEADER length for check_sum? #256

CaoJunCJ opened this issue Jan 21, 2019 · 5 comments

Comments

@CaoJunCJ
Copy link

CaoJunCJ commented Jan 21, 2019

I need add "eventDeserializer.setChecksumType(ChecksumType.NONE);" for every time to readEvent, else it will throw java.io.EOFException.

try (BinaryLogFileReader reader = new BinaryLogFileReader(binlogFile, eventDeserializer)) {
            for (Event event; (event = reader.readEvent()) != null; ) {
                //eventDeserializer.setChecksumType(ChecksumType.NONE);
                System.out.println(event);
            }
        }
@CaoJunCJ CaoJunCJ changed the title Was not calculation MAGIC_HEADER length for check_sum? Was not calculated MAGIC_HEADER length for check_sum? Jan 21, 2019
@shyiko
Copy link
Owner

shyiko commented Jan 22, 2019

@CaoJunCJ any chance you can provide a binlogFile to reproduce the problem? Also, just to confirm - you are running the latest (0.17.0) release, right?

@CaoJunCJ
Copy link
Author

CaoJunCJ commented Jan 22, 2019

Hello @shyiko ,
This is maven dependency with running:

<dependency>
    <groupId>com.github.shyiko</groupId>
    <artifactId>mysql-binlog-connector-java</artifactId>
    <version>0.17.0</version>
</dependency>

The binlog file link:https://www.dropbox.com/s/t6sp33z3i1tqmt8/mysql-bin.000022?dl=0

shyiko pushed a commit that referenced this issue Jan 22, 2019
@shyiko
Copy link
Owner

shyiko commented Jan 22, 2019

Thank you, @CaoJunCJ. That was really helpful. Fixed in 0.18.0.

@shyiko shyiko closed this as completed Jan 22, 2019
@dentarg
Copy link

dentarg commented Jan 28, 2019

@shyiko is 68c0ec7 the same thing as these old commits in the develop branch? 1f4fe85, 671c7e8

@shyiko
Copy link
Owner

shyiko commented Jan 30, 2019

@dentarg same result, yes. I completely forgot about 68c0ec7, to be honest 🤦‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants