Paul,<br><br>Thanks for the reply. It was in fact a 'dirty' shutdown. I'm guessing i didn't ensure all jvm processes were destroyed before my attempt to re-start mulgara.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The error you are seeing is happening while an uncommitted transaction<br>
is being committed. (Did the system shut down cleanly?) Once you get<br>
it up and running it might be fine to continue as normal. If that's<br>
the case, then forcing the system to NOT use file mappings should get<br>
you going again. Do this by updating the command line to include the<br>
following:<br>
java -Dmulgara.xa.forceIOType=explicit -jar mulgara-1.x.x.jar<br>
<br></blockquote></div>