I have a problem saving documents with xpages. I had built a simple performance planning application for my company, and during the pilot, users noticed that sometimes they would fill out the web-based (xpages-based) form and save, and the document would disappear.
After some testing, I have narrowed down the problem to this:
If the XSP Command Manager refreshes after I have opened an xpages form, but before I attempt to save my document, the save fails.
Steps to reproduce:
Create a simple xpages application with an xpages form capable of saving a simple document to the database (I can send such a database to whoever might be able to help me fix this).
Open the xpages form in a browser.
Enter the “tell http xsp refresh” command into the server console, or wait for the XSP Command Manager to refresh automatically (happens every 10 minutes).
Go back to the xpages form that is open in your browser and attempt to save. The document will not save, and the xpage will simply reload.
Can anyone tell me if this is a known issue? Or if there is some server setting that needs to be changed?
I’m confused that no one else seems to have seen this issue.
Turns out this ‘xsp command manager’ refresh issue is worse than I thought.It seems like any xpage sessions that are currently active lose all their state whenever the command manager is refreshed.
So buttons that set a field and refresh the screen, or rely on session scope variables, etc., none of that works after a refresh.
And the refresh happens every 10 minutes.
How is it possible that no one else has experienced this? Unless no one actually uses xpages…
Or maybe there is some server setting that would help?
We are experiencing the same problem - XSP Command Manager does a refresh while users are logged in. All state (session as well as application) gets lost. Anything new on this topic? Is this a bug or do I have to configure the XSP Command Manager in some way?