Opened 11 years ago
Closed 11 years ago
#518 closed defect (fixed)
Installation wizard must be run twice
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | minor | Milestone: | Reggie v2.13 |
Component: | net.sf.basedb.reggie | Keywords: | |
Cc: |
Description
Sometimes the installation wizard need to update/fix so many things that it causes a transaction failure on some items.
Trying to run the installation wizard a second time reports a lot less items in need of a fix (since the fix worked the first time) and then the wizard is able to fix them as well.
At the moment it is a bit hard to be more specific about details since this problem is impossible to replicate unless the initial database state is backed up and restored before trying again.
A fresh BASE installation with an Reggie 2.12 is probably a good starting point. Back it up and then try updating to Reggie 2.13. Restore from the backup and repeat until the problem can be identified.
Attachments (1)
Change History (6)
comment:1 by , 11 years ago
Status: | new → assigned |
---|
comment:2 by , 11 years ago
comment:3 by , 11 years ago
The annotation type with id=1164 is the PlateProcessResult
annotation. It already exists in Reggie 2.12 but need two modifications in Reggie 2.13
- It must be enabled for
PHYSICALBIOASSAY
items - It must be added to the
FlowCell
category
The installation wizard will detect 1 and make modifications as necessary on the annotation type.
Then, the installation wizard detects that FlowCell
doesn't yet exists and creates it IN A SEPARATE TRANSACTION. The problem is that the extra transaction that creates the category is also used to fix 2. This causes a problem since the main transaction has already modified the annotation type.
The solution to this problem is that the SEPARATE transactions that are used for creating items should NEVER modify any other items. They should only be modified by the main transaction.
After a quick scan of the installation wizard it seems like there are no other places were this is happening. So moving the fix for 2 out to the main transaction seems to solve the problem.
comment:4 by , 11 years ago
Milestone: | Reggie v2.x → Reggie v2.13 |
---|
comment:5 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I have made some tests and when updating between Reggie 2.12 and 2.13-beta-1 the error message is (see attached image):
Full stacktrace in the Tomcat error log: