18 Mar
2008
18 Mar
'08
5:09 p.m.
Hi Vincent,
Vincent Massol wrote:
Isn't this the same as http://jir a.xwiki.org/jira/browse/XWIKI-
1736? <http://jira.xwiki.org/jira/browse/XWIKI-1736>
Ludovic has had the same exception reported today and was asking me if
I knew how to fix it. I couldn't find a solution in this thread.
What was the outcome and how did you solve it Ricardo?
We have been chatting about this in the #IRC channel on March the 7th. I
remember we have considered this issue at some moment, but it seems it
is not the same problem.
Here the explanation and the solutions posted by Sergiu:
<envelope>
<sender
hostmask="n=sdumitri(a)guest-96.loria.fr">sdumitriu</sender>
<message id="NUUF7K1PPN1" received="2008-03-07 02:03:20
+0100">So
the problem is</message>
<message id="VUD4F22PPN1" received="2008-03-07 02:03:38
+0100">- You
used 1.2 M1</message>
<message id="F9R77M2PPN1" received="2008-03-07 02:03:58
+0100">- 1.2
M1 did not contain a minimum length for the XWR_PATCH column</message>
</envelope>
<envelope>
<sender self="yes"
hostmask="rrodriguez(a)231.Red-80-34-100.staticIP.rima-tde.net">rrodriguez</sender>
<message id="XHUGKS2PPN1" received="2008-03-07 02:04:04
+0100">that
is sure. In fact I received a warning from Vincent for doing that <span
class="emoticon
smile"><samp>:-)</samp></span></message>
</envelope>
<envelope>
<sender
hostmask="n=sdumitri(a)guest-96.loria.fr">sdumitriu</sender>
<message id="S8WKE63PPN1" received="2008-03-07 02:04:18
+0100">-
Thus, it was created as "text", which is small</message>
<message id="TTE5GX3PPN1" received="2008-03-07 02:04:45
+0100">-
Hibernate does not update column definitions</message>
<message id="U912KA5PPN1" received="2008-03-07 02:05:34
+0100">-
XWikiPreferences is poorly designed, so it is HUGE when exported as
XML</message>
<message id="IEVO8J6PPN1" received="2008-03-07 02:06:19
+0100">- On
top of that, there seems to be a bug either in hibernate on in XWiki, as
it allows partial commit of a transaction, or it doesn't use a
transaction at all</message>
<message id="FDMB3Z6PPN1" received="2008-03-07 02:06:35
+0100">What
we can do now</message>
<message id="M4PBI79PPN1" received="2008-03-07 02:07:55
+0100">- The
fast workaround is to write a migrator that checks if the column is of
type text instead of longtext, and if so, to manually update it, and
delete all the bad columns</message>
<message id="DS82GT9PPN1" received="2008-03-07 02:08:17
+0100">- The
longterm idea is to solve the transaction bug</message>
<message id="FMT1C3APPN1" received="2008-03-07 02:08:27
+0100">and
to recover from such errors</message>
<message id="TI7MJJAPPN1" received="2008-03-07 02:08:43
+0100">Now,
I hope there aren't many users that used 1.2M1</message>
</envelope>
<envelope>
<sender self="yes"
hostmask="rrodriguez(a)231.Red-80-34-100.staticIP.rima-tde.net">rrodriguez</sender>
<message id="FLYO8KCPPN1" received="2008-03-07 02:09:56
+0100">At
least another server: our production one</message>
</envelope>
<envelope>
<sender
hostmask="n=sdumitri(a)guest-96.loria.fr">sdumitriu</sender>
<message id="LYX9FGDPPN1" received="2008-03-07 02:10:28
+0100">Well,
you know what to do</message>
<message id="JN73EPPN1" received="2008-03-07 02:10:51
+0100">alter
table xwikircs modify column xwr_patch longtext;</message>
<message id="QQRZHCEPPN1" received="2008-03-07 02:11:00
+0100">delete from xwikircs where xwr_isdiff is null;</message>
<message id="Y98QKFEPPN1" received="2008-03-07 02:11:03
+0100">restart</message>
</envelope>
When Ludovic got the same exception reported, I tried to reconstruct the
flow and find that we have not documented the solution. I keep asking
how is the best way of doing it.
HTH,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team