Support for Neo4j 1.9.M01 #223

Closed
cnstaging opened this Issue Nov 27, 2012 · 2 comments

2 participants

@cnstaging

We were running tests of the the latest milestone release for "High Availablity" (Enterprise) of Neo4j and ran into the following error message.

Some helpful requests
1. Identify and document the supported Neo4j versions on the main readme here on github.
2. Do you have any steps or suggestions for those of us wanting to test the latest Neo4j versions? (is it as simple as updating Jar files, etc)

New Setup Docs
http://docs.neo4j.org/chunked/milestone/ha-setup-tutorial.html

Blog Information
http://blog.neo4j.org/2012/10/neo4j-19m01-self-managed-ha.html

2012-11-27 07:12:20.487+0000 ERROR [neo4j.cluster]: Receive exception:
java.io.StreamCorruptedException: Unsupported version: 0
    at org.jboss.netty.handler.codec.serialization.CompactObjectInputStream.readStreamHeader(CompactObjectInputStream.java:41) ~[netty-3.5.7.Final.jar:na]
    at java.io.ObjectInputStream.<init>(Unknown Source) ~[na:1.6.0_31]
    at org.jboss.netty.handler.codec.serialization.CompactObjectInputStream.<init>(CompactObjectInputStream.java:30) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.handler.codec.serialization.ObjectDecoder.decode(ObjectDecoder.java:127) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:422) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.handler.logging.LoggingHandler.handleUpstream(LoggingHandler.java:333) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:84) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:465) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:332) ~[netty-3.5.7.Final.jar:na]
    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35) ~[netty-3.5.7.Final.jar:na]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [na:1.6.0_31]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.6.0_31]
    at java.lang.Thread.run(Unknown Source) [na:1.6.0_31]
@andreasronge
Neo4jRB member

Hi

I have not tested with Neo4j 1.9.M01 yet.
It's rather easy to build the neo4j-community, neo4j-advanced and neo4j-enterprise gems.
Check the readme https://github.com/dnagir/neo4j-community

It would great if you could test with 1.9.M01 and see if the RSpecs for neo4j-core, neo4j-wrapper and neo4j still works.
There are some info how to upgrade here - https://github.com/andreasronge/neo4j/wiki/Upgrading

Another reason using 1.9.M01 is that the HA setup is simpler. This means that using the rails console (with write support) should be easier to setup, see https://github.com/andreasronge/neo4j/wiki/Neo4j%3A%3ARails-Config

Regarding which version of neo4j is used it is declared here: https://github.com/andreasronge/neo4j-core/blob/master/neo4j-core.gemspec
I agree, it should be visible on the readme too.

Cheers

@andreasronge andreasronge added a commit that referenced this issue Dec 28, 2012
@andreasronge andreasronge Support for HA cluster with neo4j, 1.9.X, #228, #99, #223
* Fixed for IRB/Pry console using HA to concurrently access the database
* Updated the HA examples
* Removed ZooKeeper and its configuration
5895b86
@andreasronge
Neo4jRB member

To test with other neo4j versions you have to build the neo4j-community (and maybe neo4j-advanced and neo4j-enterprise) gems your self, https://github.com/dnagir/neo4j-community

Also see https://github.com/andreasronge/neo4j/wiki/Neo4j%3A%3Aha-cluster how to use the HA cluster in 1.9.M03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment