EmmanuelOga / hypergraphdb

Automatically exported from code.google.com/p/hypergraphdb
1 stars 0 forks source link

"Transaction configured as read-only was used to modify data!" #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Exception seems related to hg.findAll or hg.getAll. Described in this thread: 
https://groups.google.com/group/hypergraphdb/browse_thread/thread/909005237f19ac
a3?hl=de&noredirect=true
Seems Alain had a possible fix, but it is unclear if he actually committed. it

What is the expected output? What do you see instead?

Caused by: org.hypergraphdb.HGException: Transaction configured as read-only 
was used to modify data!
at org.hypergraphdb.transaction.HGTransaction.commit(HGTransaction.java:206)
at 
org.hypergraphdb.transaction.DefaultTransactionContext.endTransaction(DefaultTra
nsactionContext.java:62)
at 
org.hypergraphdb.transaction.HGTransactionManager.endTransaction(HGTransactionMa
nager.java:247)
at 
org.hypergraphdb.transaction.HGTransactionManager.transact(HGTransactionManager.
java:415)
at 
org.hypergraphdb.transaction.HGTransactionManager.ensureTransaction(HGTransactio
nManager.java:322)
at org.hypergraphdb.HGQuery$hg.findAll(HGQuery.java:1661)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by Ingvar.Bogdahn on 4 Jul 2012 at 9:02

GoogleCodeExporter commented 9 years ago
The problem as originally reported by Alain does not happen. It would help if 
you could provide a test program that creates that problem now.

Original comment by borislav...@gmail.com on 5 Jul 2012 at 1:37

GoogleCodeExporter commented 9 years ago

Original comment by borislav...@gmail.com on 16 Jul 2012 at 4:36