Re: [Neo4j] Issue with lucene index
They guys could create at least one in Malmö? Isn't Andreas there as well, and certainly some more fine folks? We can do one locally here in Gemany, perhaps Berlin (perhaps we can combine that with our monthly flight to CPH). Cheers Michael Am 14.03.2011 um 11:50 schrieb Jim Webber: Hey Rick, It was a pleasure to meet you too. And this got me thinking - it would be great to meet more folks from this list, or to form user groups, or generally just get a beer and talk Neo4j graphs. Is there, for example, a strong London contingent on this list? I only know me and Nat Pryce so far. Anyone else care to get together in London? Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
Berlin sounds great. Last year a couple of guys met up at StudiVZ, and suddenly we were 30 people. Go for it, there is a LOT of good vibe in Beerlin! Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Mon, Mar 14, 2011 at 12:37 PM, Michael Hunger michael.hun...@neotechnology.com wrote: They guys could create at least one in Malmö? Isn't Andreas there as well, and certainly some more fine folks? We can do one locally here in Gemany, perhaps Berlin (perhaps we can combine that with our monthly flight to CPH). Cheers Michael Am 14.03.2011 um 11:50 schrieb Jim Webber: Hey Rick, It was a pleasure to meet you too. And this got me thinking - it would be great to meet more folks from this list, or to form user groups, or generally just get a beer and talk Neo4j graphs. Is there, for example, a strong London contingent on this list? I only know me and Nat Pryce so far. Anyone else care to get together in London? Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
That would be great! Or Frankfurt? It's a little more central (but Berlin is ok for me, too) BTW: We should change the subject (it sounds so negative) ;-) Since I created the original post, I'll start a new thread. On 14.03.2011 13:02, Peter Neubauer wrote: Berlin sounds great. Last year a couple of guys met up at StudiVZ, and suddenly we were 30 people. Go for it, there is a LOT of good vibe in Beerlin! Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/- Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Mon, Mar 14, 2011 at 12:37 PM, Michael Hunger michael.hun...@neotechnology.com wrote: They guys could create at least one in Malmö? Isn't Andreas there as well, and certainly some more fine folks? We can do one locally here in Gemany, perhaps Berlin (perhaps we can combine that with our monthly flight to CPH). Cheers Michael Am 14.03.2011 um 11:50 schrieb Jim Webber: Hey Rick, It was a pleasure to meet you too. And this got me thinking - it would be great to meet more folks from this list, or to form user groups, or generally just get a beer and talk Neo4j graphs. Is there, for example, a strong London contingent on this list? I only know me and Nat Pryce so far. Anyone else care to get together in London? Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
Thanks, Mattias. That prompts two more questions: Any chance of backporting this to Neo4J 1.2? If not, any rough estimate of the 1.3 release timetable? Rick -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Mattias Persson Sent: Thursday, March 10, 2011 2:21 AM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index 2011/3/9 Rick Bullotta rick.bullo...@burningskysoftware.com Hi, Mattias. Is the ability to delete a node from a Lucene fulltext index the old way (just provide node + key name) in M03 and M04? Yes, they arrived in M03 Thanks, Rick -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Mattias Persson Sent: Wednesday, March 09, 2011 2:24 PM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index Den onsdagen den 9:e mars 2011 skrev David Montagdavid.mon...@neotechnology.com: Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner a...@morgner.de wrote: Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app) concurrently writes updates to the index, too. After such an exception, the system is unable to recover unless I manually remove the lucene, lucene-fulltext and index folders from the neo4j directory and start over. Then the system comes up again, and I can sucessfully rebuild the index. Do I have to take care of locking by myself? Greetings Axel [1] java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexTyp e.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneComman d.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.jav a:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransac tion.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaRes ourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaRe sourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.j ava:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.jav a:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) javax.transaction.xa.XAException: Unknown xid[GlobalId[NEOKERNL|-7500914275797900644|1974], BranchId[ 52 49 52 49 52 49 ]] at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.rollback(XaR esourceManager.java:471) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.rollback(Xa ResourceHelpImpl.java:112) at org.neo4j.kernel.impl.transaction.TransactionImpl.doRollback(TransactionImpl .java:534) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:650) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.jav a:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) 09.03.2011 18:27:07 org.neo4j.kernel.impl.transaction.TxManager commit SCHWERWIEGEND: Unable to rollback transaction. Some resources may be commited others not. Neo4j kernel should be SHUTDOWN for resource maintance and transaction recovery java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromD-- David Montag Neo Technology, www.neotechnology.com Cell: 650.556.4411 david.mon
Re: [Neo4j] Issue with lucene index
Hi Rick, That prompts two more questions: Any chance of backporting this to Neo4J 1.2? If not, any rough estimate of the 1.3 release timetable? Full releases are every quarter, M05 is due next week, and the following release will be 1.3 GA. So you're looking at about 3 weeks. Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
Perfect. Thanks, Jim. Nice to meet you in person last week. Look forward to chatting w/you and Michael on some ideas for the REST API. -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Jim Webber Sent: Sunday, March 13, 2011 6:26 PM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index Hi Rick, That prompts two more questions: Any chance of backporting this to Neo4J 1.2? If not, any rough estimate of the 1.3 release timetable? Full releases are every quarter, M05 is due next week, and the following release will be 1.3 GA. So you're looking at about 3 weeks. Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
On Wed, Mar 9, 2011 at 8:24 PM, Mattias Persson matt...@neotechnology.com wrote: Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. Not so gentle from yours to force an upgrade from M03 to M04 sir... ;-) did it will take a long on a 20G db? Cheers -- Massimo http://meridio.blogspot.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
2011/3/10 Massimo Lusetti mluse...@gmail.com On Wed, Mar 9, 2011 at 8:24 PM, Mattias Persson matt...@neotechnology.com wrote: Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. Not so gentle from yours to force an upgrade from M03 to M04 sir... ;-) did it will take a long on a 20G db? It will leave the store virtually untouched, mostly do sanity checks. So it will not take more than a few seconds at the most, irregardless of store size. What you benefit from it is that you can put several times more data in it. I think it's a fair trade :) Cheers -- Massimo http://meridio.blogspot.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner a...@morgner.de wrote: Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app) concurrently writes updates to the index, too. After such an exception, the system is unable to recover unless I manually remove the lucene, lucene-fulltext and index folders from the neo4j directory and start over. Then the system comes up again, and I can sucessfully rebuild the index. Do I have to take care of locking by myself? Greetings Axel [1] java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexType.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneCommand.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.java:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaResourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaResourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.java:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) javax.transaction.xa.XAException: Unknown xid[GlobalId[NEOKERNL|-7500914275797900644|1974], BranchId[ 52 49 52 49 52 49 ]] at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.rollback(XaResourceManager.java:471) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.rollback(XaResourceHelpImpl.java:112) at org.neo4j.kernel.impl.transaction.TransactionImpl.doRollback(TransactionImpl.java:534) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:650) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) 09.03.2011 18:27:07 org.neo4j.kernel.impl.transaction.TxManager commit SCHWERWIEGEND: Unable to rollback transaction. Some resources may be commited others not. Neo4j kernel should be SHUTDOWN for resource maintance and transaction recovery java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexType.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneCommand.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.java:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaResourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaResourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.java:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) org.neo4j.graphdb.TransactionFailureException: Unable to commit transaction at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:105)
Re: [Neo4j] Issue with lucene index
Den onsdagen den 9:e mars 2011 skrev David Montagdavid.mon...@neotechnology.com: Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner a...@morgner.de wrote: Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app) concurrently writes updates to the index, too. After such an exception, the system is unable to recover unless I manually remove the lucene, lucene-fulltext and index folders from the neo4j directory and start over. Then the system comes up again, and I can sucessfully rebuild the index. Do I have to take care of locking by myself? Greetings Axel [1] java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexType.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneCommand.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.java:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaResourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaResourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.java:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) javax.transaction.xa.XAException: Unknown xid[GlobalId[NEOKERNL|-7500914275797900644|1974], BranchId[ 52 49 52 49 52 49 ]] at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.rollback(XaResourceManager.java:471) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.rollback(XaResourceHelpImpl.java:112) at org.neo4j.kernel.impl.transaction.TransactionImpl.doRollback(TransactionImpl.java:534) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:650) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) 09.03.2011 18:27:07 org.neo4j.kernel.impl.transaction.TxManager commit SCHWERWIEGEND: Unable to rollback transaction. Some resources may be commited others not. Neo4j kernel should be SHUTDOWN for resource maintance and transaction recovery java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromD-- David Montag Neo Technology, www.neotechnology.com Cell: 650.556.4411 david.mon...@neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
Upgraded to 1.3.M03, issue is gone. Thanks a lot! Axel Am 09.03.2011 20:24, schrieb Mattias Persson: Den onsdagen den 9:e mars 2011 skrev David Montagdavid.mon...@neotechnology.com: Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgnera...@morgner.de wrote: Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app) concurrently writes updates to the index, too. After such an exception, the system is unable to recover unless I manually remove the lucene, lucene-fulltext and index folders from the neo4j directory and start over. Then the system comes up again, and I can sucessfully rebuild the index. Do I have to take care of locking by myself? Greetings Axel [1] java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexType.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneCommand.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.java:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaResourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaResourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.java:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) javax.transaction.xa.XAException: Unknown xid[GlobalId[NEOKERNL|-7500914275797900644|1974], BranchId[ 52 49 52 49 52 49 ]] at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.rollback(XaResourceManager.java:471) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.rollback(XaResourceHelpImpl.java:112) at org.neo4j.kernel.impl.transaction.TransactionImpl.doRollback(TransactionImpl.java:534) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:650) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) 09.03.2011 18:27:07 org.neo4j.kernel.impl.transaction.TxManager commit SCHWERWIEGEND: Unable to rollback transaction. Some resources may be commited others not. Neo4j kernel should be SHUTDOWN for resource maintance and transaction recovery java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromD-- David Montag Neo Technology, www.neotechnology.com Cell: 650.556.4411 david.mon...@neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
Hi, Mattias. Is the ability to delete a node from a Lucene fulltext index the old way (just provide node + key name) in M03 and M04? Thanks, Rick -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Mattias Persson Sent: Wednesday, March 09, 2011 2:24 PM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index Den onsdagen den 9:e mars 2011 skrev David Montagdavid.mon...@neotechnology.com: Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner a...@morgner.de wrote: Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app) concurrently writes updates to the index, too. After such an exception, the system is unable to recover unless I manually remove the lucene, lucene-fulltext and index folders from the neo4j directory and start over. Then the system comes up again, and I can sucessfully rebuild the index. Do I have to take care of locking by myself? Greetings Axel [1] java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexType.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneCommand.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.java:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaResourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaResourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.java:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) javax.transaction.xa.XAException: Unknown xid[GlobalId[NEOKERNL|-7500914275797900644|1974], BranchId[ 52 49 52 49 52 49 ]] at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.rollback(XaResourceManager.java:471) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.rollback(XaResourceHelpImpl.java:112) at org.neo4j.kernel.impl.transaction.TransactionImpl.doRollback(TransactionImpl.java:534) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:650) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) 09.03.2011 18:27:07 org.neo4j.kernel.impl.transaction.TxManager commit SCHWERWIEGEND: Unable to rollback transaction. Some resources may be commited others not. Neo4j kernel should be SHUTDOWN for resource maintance and transaction recovery java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromD-- David Montag Neo Technology, www.neotechnology.com Cell: 650.556.4411 david.mon...@neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Issue with lucene index
2011/3/9 Rick Bullotta rick.bullo...@burningskysoftware.com Hi, Mattias. Is the ability to delete a node from a Lucene fulltext index the old way (just provide node + key name) in M03 and M04? Yes, they arrived in M03 Thanks, Rick -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Mattias Persson Sent: Wednesday, March 09, 2011 2:24 PM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index Den onsdagen den 9:e mars 2011 skrev David Montagdavid.mon...@neotechnology.com: Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. Correct, and go with the M03 milestone first because M04 will introduce changes which requires an upgrade from a cleanly shut down database. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner a...@morgner.de wrote: Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app) concurrently writes updates to the index, too. After such an exception, the system is unable to recover unless I manually remove the lucene, lucene-fulltext and index folders from the neo4j directory and start over. Then the system comes up again, and I can sucessfully rebuild the index. Do I have to take care of locking by myself? Greetings Axel [1] java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromDocument(IndexType.java:165) at org.neo4j.index.impl.lucene.LuceneCommand$RemoveCommand.perform(LuceneCommand.java:228) at org.neo4j.index.impl.lucene.LuceneTransaction.doCommit(LuceneTransaction.java:231) at org.neo4j.kernel.impl.transaction.xaframework.XaTransaction.commit(XaTransaction.java:319) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.commit(XaResourceManager.java:447) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.commit(XaResourceHelpImpl.java:65) at org.neo4j.kernel.impl.transaction.TransactionImpl.doCommit(TransactionImpl.java:517) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:623) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) javax.transaction.xa.XAException: Unknown xid[GlobalId[NEOKERNL|-7500914275797900644|1974], BranchId[ 52 49 52 49 52 49 ]] at org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.rollback(XaResourceManager.java:471) at org.neo4j.kernel.impl.transaction.xaframework.XaResourceHelpImpl.rollback(XaResourceHelpImpl.java:112) at org.neo4j.kernel.impl.transaction.TransactionImpl.doRollback(TransactionImpl.java:534) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:650) at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:586) at org.neo4j.kernel.impl.transaction.TransactionImpl.commit(TransactionImpl.java:105) at org.neo4j.kernel.TopLevelTransaction.finish(TopLevelTransaction.java:86) at org.structr.core.node.TransactionCommand.execute(TransactionCommand.java:37) at org.structr.core.entity.AbstractNode.commit(AbstractNode.java:968) at org.structr.core.log.LogService.run(LogService.java:85) 09.03.2011 18:27:07 org.neo4j.kernel.impl.transaction.TxManager commit SCHWERWIEGEND: Unable to rollback transaction. Some resources may be commited others not. Neo4j kernel should be SHUTDOWN for resource maintance and transaction recovery java.lang.NullPointerException at org.neo4j.index.impl.lucene.IndexType$CustomType.removeFromD-- David Montag Neo Technology, www.neotechnology.com Cell: 650.556.4411 david.mon...@neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
