Neoclipse on Juno

[Radhakrishna Kalyan]

Hi,

I tried to analyzed the cause of Null pointer while running neoclipse on Juno, as I read that there has been some major archetectural changes done from eclipse 4.2, few applications may find few issues, even though it is mentioned that one can still run older versions of eclipse application on Juno without any problems, but I think its not possible in case of neoclipse.

Actually I am able to run neoclipse and view the graph and run cypher query, but I am seeing lots of other null pointer exceptions on the console.

Which I am currently working on to fix. I am in the process of modifying neoclipse so that one can compile and run on Juno. Will update the progress by weekend.

As of now neoclipse can be successfully compiled and run on Eclipse 3.7/8 .

Any suggestions/advice will be appreciated.

--

Thanks and Regards
N Radhakrishna Kalyan

G/S/T/F:  nrkkalyan
P:  +46 768 800 824
L:   http://www.linkedin.com/in/nrkkalyan

[Peter Neubauer]

Yes,
I am seeing the same thing. Seems kinda strange for Juno to start breaking things without any code changes. Quite annoying. Thanks for looking into it!

/peter

Send from mobile.

[Radhakrishna Kalyan]

Hi,

I have analyzed the current code and read about the changes related to Juno.

Finally I understood that we need to rewrite few parts of the current code which is not compatible with Juno. 

So I am working on the same..

Kalyan

[Peter Neubauer]

Oh,
cool, just looked into this, and can't find what is going on. Great
that you found the changes needed. hack this Friday on it?

Cheers,

/peter neubauer

G: neubauer.peter
S: peter.neubauer
P: +46 704 106975
L: http://www.linkedin.com/in/neubauer
T: @peterneubauer

Wanna learn something new? Come to @graphconnect.

[Radhakrishna Kalyan]

Yes, its going on, Will have a skype call on friday at 17.00. Is it ok?

--

[Kivs]

I get the following error as I'm actively writing to the database in a java program when I sync the database with neoclipse. I have connected to the database in read-only mode. Is this caused by Juno (which I'm using with neoclipse 1.7) or is this some bug? If I downgrade my eclipse will this fix the issue?

Exception in thread "Thread-3" java.lang.IllegalStateException: Unable to lock store [C:\Documents and Settings\Desktop\Neo4j\neo4j-community-1.8.M06\data\graph.db\neostore], this is usually a result of some other Neo4j kernel running using the same store.

at org.neo4j.kernel.impl.nioneo.store.CommonAbstractStore.checkStorage(CommonAbstractStore.java:173)

at org.neo4j.kernel.impl.nioneo.store.CommonAbstractStore.<init>(CommonAbstractStore.java:114)

at org.neo4j.kernel.impl.nioneo.store.AbstractStore.<init>(AbstractStore.java:77)

at org.neo4j.kernel.impl.nioneo.store.NeoStore.<init>(NeoStore.java:82)

at org.neo4j.kernel.impl.nioneo.store.StoreFactory.attemptNewNeoStore(StoreFactory.java:88)

at org.neo4j.kernel.impl.nioneo.store.StoreFactory.newNeoStore(StoreFactory.java:77)

at org.neo4j.kernel.impl.nioneo.xa.NeoStoreXaDataSource.<init>(NeoStoreXaDataSource.java:213)

at org.neo4j.kernel.InternalAbstractGraphDatabase.create(InternalAbstractGraphDatabase.java:416)

at org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:223)

at org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:79)

at org.neo4j.graphdb.factory.GraphDatabaseFactory$1.newDatabase(GraphDatabaseFactory.java:70)

at org.neo4j.graphdb.factory.GraphDatabaseBuilder.newGraphDatabase(GraphDatabaseBuilder.java:195)

at org.neo4j.graphdb.factory.GraphDatabaseFactory.newEmbeddedDatabase(GraphDatabaseFactory.java:56)

at Grapher.setUp(Grapher.java:130)

at Console2$MessageLoop.run(Console2.java:103)

at java.lang.Thread.run(Unknown Source)

[Radhakrishna Kalyan]

I don't think so. I believe its something to do with the locking of the database.

Kalyan

--
 
 

[Kivs]

So neoclipse is essentially creating a lock on the database when it reads the information because the program works fine as long as I don't use neoclipse. So does neoclipse read-only mode have to create a lock on the database or can I have it not create a lock? Is there any way around this?

[Peter Neubauer]

Mmh,
Have to check this. What happens if you open the db first from your java program and then with neoclipse readonly?

I dimly remember that Lucene index searches have some problems in readonly mode also...

/peter

Send from mobile.

--
 
 

[Kivs]

I do open the database first in java and create several transactions then shutdown (so I can view it in neoclipse) and restart to continue modifying the database but when I am restarting the database sometimes I get the lock. So I am going to guess neoclipse creates a lock to quickly read the data then unlocks it after its done . It just so happens that my java program is trying to open the database when its reading the data with the lock on it. Is this correct? And is there anyway around this?