Menu

#20 some logs not going in

ROD3
open
nobody
5
2010-09-07
2010-09-07
Anonymous
No

Most of the inoc and spot logs have gone in, however one of each type (from different experiments) are not going in and they are producing this error message

The following error occurred: Exception thrown finding table type using DatabaseMetaData.getTables()
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:319)
org.datanucleus.jdo.JDOTransaction.commit(JDOTransaction.java:139)
uk.ac.cisban.rod.dao.specifics.ManageLogs.addInoculation(ManageLogs.java:308)
uk.ac.cisban.rod.dao.DAO.addInoculation(DAO.java:519)
uk.ac.cisban.rod.data.handlers.ParseInoculationTask.doInBackground(ParseInoculationTask.java:130)
uk.ac.cisban.rod.data.handlers.ParseInoculationTask.doInBackground(ParseInoculationTask.java:41)
javax.swing.SwingWorker$1.call(Unknown Source)
java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
java.util.concurrent.FutureTask.run(Unknown Source)
javax.swing.SwingWorker.run(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)

As a further note to this, it appears that this happens when I am loading another large file into ROD3 (like an image log for instance). When the image log stopped loading the logs went in fine. This may be unavoidable.

Discussion


Log in to post a comment.

MongoDB Logo MongoDB