DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27240>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27240 Slide startup failure leaves a dangling /tempaction that makes subsequent Slide startup always fail. Summary: Slide startup failure leaves a dangling /tempaction that makes subsequent Slide startup always fail. Product: Slide Version: 2.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The problem is in Namespace.loadBaseData(). It creates and removes /tempaction in 2 separate transactions. If the create tx succeeded and the remove tx failed, /tempaction would be left in the database. Next time when Slide starts again, /tempaction can't be created and causes loadBaseData() to fail. Resolution: a) check if /tempaction exists before create it; or b) combine the 2 separate transactions into one. I'm not sure if the 2 separate transactions are there for a reason though. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
