Every XPage rename deletes that XPage

HCL Domino Domino Forum
1

  • I just lost two days work over this and it’s hard to feel positive about it. Sorry if that’s coloring this post.

  • Starting about an hour and a half ago, every single rename on a XPage effectively deletes that XPage. It still appears in the “Applications” Panel without any red “X” and appears perfectly normal, with no sign that anything is amiss. In all cases, double-clicking on the XPage to edit it shows an “IndexOutOfBoundsException” instead of the expected XML in the editor, with a “Details” button that shows a stack trace.

  • The inconsistent part is that sometimes when the renamed XPage is edited right after renaming, it does in fact appear in the editor. If a “Clean & Build” is then done, however, the renamed XPage gets a red “X”, even if it’s loaded in the editor. At that point it’s simply been deleted. Gone.

  • Other times it won’t open in the editor immediately after renaming. But the “deletion” result is the same: IndexOutOfBoundsException on edit, nothing “wrong” after renaming.

  • Ah. It occurs to me it may sometimes be doing a background build, as I have “Build Automatically” turned on. That would explain the “inconsistency” concerning renaming vs building, but I failed to notice this little detail.

  • Relaunching DDE has no effect. Restarting the machine running DDE appears to have fixed it.

  • If DDE becomes so broken that it throws out work, that seems like a serious problem. I know of no other IDE that destroys work so casually for any reason. It’s a critical failure for work to be lost, ever. That it happens when there are no errors at the time of failure, no dialogs or messages, no DDE freeze-up, no system crash, no hidden dialogs uncovered at DDE close, nothing what-so-ever to indicate other than completely normal operation - well that feels uncomfortably similar to salt in the wound.

  • Naturally this won’t be reproducible, but that’s not the issue. The issue is DDE tossed out two days work, and one would surmise the fact it happens at all should be cause for alarm.

If there are logs or suchlike I can pass along I’d be happy to do so. Thanks for your time…

2

Subject: Fixed in 852

What was the pattern of your rename operations?, were there multiple renames in quick succession?

There is a bug in 851 that can lead to corrupting xpage while renaming it in rare cases (timing issue), this is fixed in 852. Not doing quick renames (say a → a1 → a) and keeping the auto-build ON should avoid this issue from surfacing in 851.

3

Subject: I don’t recall it being “quick”…

  • My changes were not working, so I deleted the page, copied it, and renamed it. This was messed up so I deleted the one I just copied (and renamed), copied & renamed it again. This was messed up so I deleted that second copy and renamed the original. This was also deleted. This entire process took perhaps an hour, since I looked at “Details”, hopped on here and searched, etc, between attempts.

  • This also happened continually for some time after it originally occurred as I tried copying and renaming from various places. This doesn’t strike me as “rare”, when it’s continuous and repeatable over significant time spans until the machine is rebooted. That’s not a timing issue any longer. That’s unacceptable instability.

  • Automagic build is always on unless DDE decides to turn it off, which happens once in a while. It’s rare enough I’m always confused when my changes don’t appear after a design refresh. (grin)

  • Given how badly R8.5 → R8.5.1 utterly hosed every single XPage I’m not feeling excited about putting in R8.5.2 when I’m already under the gun for completion. I can’t afford to lose the three days I did then.

Thanks for your time…