Data lost on "Save Document"

lazx wrote

Just ran into a large problem.  Here is the situaton:

Version: Orbeon 3.7 Form Runner/Builder Nightly Build

First 4 completed forms were saved successfully. For the 5th+ form the following happens:

1) A new form is created.
2) Information is entered into the form
3) Save Document is pressed -> Form Runner reports that the document has been saved successfully
4) Document is NOT saved to the database (eXist).

Ouch!

Any suggestions on what is going on here??

Erik Bruchez wrote

I am not sure why this is happening, but it sounds lie there is an  
eXist error, and the error should be propagated to the client so you  
know the data wasn't saved. But it clearly isn't.

Do you see errors in the logs?

-Erik

On Jul 10, 2008, at 12:28 PM, lazx wrote:

>
> Let me describe the situation a little more.
>
> There were multiple users filling out forms simultaneously.  There  
> was also
> some (x)queries in eXist occurring when the users were completing  
> these
> forms.
>
> I looked into the eXist database, and it appears the the "resource"
> collection for each form data document (data.xml) was not created -  
> and nor
> was the data.xml document in the eXist db - so, the data is really  
> lost.
>
> As of 5 minutes ago, it seems that I am able to save form data  
> again.  At
> this point, I am the only one using Form Runner.
>
> Let me know if there is any other information needed.
>
> Thanks!
>
>
> lazx wrote:
>>
>> Just ran into a large problem.  Here is the situaton:
>>
>> Version: Orbeon 3.7 Form Runner/Builder Nightly Build
>>
>> First 4 completed forms were saved successfully. For the 5th+ form  
>> the
>> following happens:
>>
>> 1) A new form is created.
>> 2) Information is entered into the form
>> 3) Save Document is pressed -> Form Runner reports that the  
>> document has
>> been saved successfully
>> 4) Document is NOT saved to the database (eXist).
>>
>> Ouch!
>>
>> Any suggestions on what is going on here??
>>
>
> --
> View this message in context: http://www.nabble.com/Data-lost-on-%22Save-Document%22-tp18389797p18390030.html
> Sent from the ObjectWeb OPS - Users mailing list archive at  
> Nabble.com.
>
>
> --
> You receive this message as a subscriber of the ops-users@ow2.org  
> mailing list.
> To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
> For general help: mailto:sympa@ow2.org?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Alessandro Vernet wrote

On Thu, Jul 10, 2008 at 7:24 PM, lazx <lazx888@gmail.com> wrote:
> I have checked the log in the /var/tomcat/orbeon/exist directory - did not
> see anything out of the norm.

You should find errors with submissions in the orbeon.log. If you are
using Tomcat, it should be in Tomcat's log directory. You can change
the location of this file in config/log4j.xml.

> Also, while I have your attention - can you point me to some
> guidelines/instructions/config_files on how to get orbeon use a non-embedded
> exist/etc database?  For updating the nightly builds, the exist database not
> persisting is not going to work :)  And I'd also like to try the 1.3 dev
> release of exist.

You can change the location of eXist in properties.xml. You will see
two references there:

1) oxf.fr.persistence.service.exist.uri points to the eXist used by Form Runner.
2) oxf.xforms.store.application.uri points to the eXist used by the
XForms Store.

Most likely you just want to change #1 and not #2.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws


-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

Alessandro Vernet wrote

On Thu, Jul 10, 2008 at 7:24 PM, lazx <lazx888@gmail.com> wrote:
> I have checked the log in the /var/tomcat/orbeon/exist directory - did not
> see anything out of the norm.

You should find errors with submissions in the orbeon.log. If you are
using Tomcat, it should be in Tomcat's log directory. You can change
the location of this file in config/log4j.xml.

> Also, while I have your attention - can you point me to some
> guidelines/instructions/config_files on how to get orbeon use a non-embedded
> exist/etc database?  For updating the nightly builds, the exist database not
> persisting is not going to work :)  And I'd also like to try the 1.3 dev
> release of exist.

You can change the location of eXist in properties.xml. You will see
two references there:

1) oxf.fr.persistence.service.exist.uri points to the eXist used by Form Runner.
2) oxf.xforms.store.application.uri points to the eXist used by the
XForms Store.

Most likely you just want to change #1 and not #2.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws


-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

Erik Bruchez wrote

Many applications seem to hit this issue (with Tomcat, Eclipse, etc.).  
It is not entirely clear why this space runs out.

Do you hot-redeploy your app into Tomcat, or do you shutdown Tomcat  
instead?

This said the permgen space is a separate VM setting. It can be  
increased with a VM option, e.g.:

   -XX:MaxPermSize=128m

This may or may not solve your problem. Please let us now.

-Erik