This post was updated on .
*Extending the discussion from this thread: http://www.nabble.com/Data-lost-on-%22Save-Document%22-td18389797.html to this one.*
I am attempting to configure orbeon to use an eXist database running in a separate tomcat instance (eventually a separate server). orbeon: localhost:8083 eXist: localhost:8081 eXist cache connection is working with the following config: <property as="xs:anyURI" name="oxf.xforms.store.application.uri" value="xmldb:exist://localhost:8081/eXist-1.2.3-rev7866/xmlrpc"/> <property as="xs:string" name="oxf.xforms.store.application.collection" value="/db/orbeon/xforms/cache/"/> But the following does not work for the storage connection: <property as="xs:anyURI" name="oxf.fr.persistence.service.exist.uri" value="/eXist-1.2.3-rev7866/rest/db"/> <property as="xs:anyURI" name="oxf.fr.appserver.uri" value="<a href="http://localhost:8081"/>">http://localhost:8081"/> Error log (browser): Fatal error: Premature end of file. Error log (orbeon.log): : 134 - Cache hits for cache.main: 13, fault: 13, adds: 13, expirations: 0, success rate: 50% 2008-07-23 13:56:43,641 INFO ProcessorService - /xforms-server/dynamic/0B7B0ECF3ED3D69D0A96C173EB946FCD - Timing: 169 - Cache hits for cache.main: 7, fault: 5, adds: 5, expirations: 0, success rate: 58% 2008-07-23 13:56:44,997 INFO ProcessorService - /xforms-server - Received request 2008-07-23 13:56:45,150 INFO ProcessorService - /xforms-server - Timing: 153 - Cache hits for cache.main: 19, fault: 16, adds: 13, expirations: 0, success rate: 54% 2008-07-23 13:56:45,202 INFO ProcessorService - /fr/orbeon/builder/new/ - Received request 2008-07-23 13:56:45,496 INFO XSLTTransformer - Resource:: http://localhost:8081/fr/service/resource/crud/orbeon/builder/form/form.xhtml 2008-07-23 13:56:45,517 ERROR ProcessorService - Exception at org.orbeon.oxf.common.ValidationException: : Fatal error: Premature end of file. null, line -1, column -1: Fatal error: Premature end of file. at org.orbeon.oxf.xml.XMLUtils$ErrorHandler.fatalError(XMLUtils.java:306) at orbeon.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:178) at orbeon.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:351) at orbeon.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:281) at orbeon.apache.xerces.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:188) at orbeon.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:802) at orbeon.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:768) at orbeon.apache.xerces.parsers.XMLParser.parse(XMLParser.java:108) (lots more) This occurs when I click "New Form" in the Form Builder Note: orbeon verion = Orbeon Forms 3.7.0alpha.200807202311 Thanks |
Administrator
|
On Wed, Jul 23, 2008 at 10:59 AM, lazx <[hidden email]> wrote:
> But the following does not work for the storage connection: > > <property as="xs:anyURI" name="oxf.fr.persistence.service.exist.uri" > value="//eXist-1.2.3-rev7866/rest/db"/> Try to change this to (this should point to your eXist database): http://localhost:8081/orbeon/exist/rest/db > <property as="xs:anyURI" name="oxf.fr.appserver.uri" > value="http://localhost:8081"/> Leave this set to "" (empty). You only need to change this when you have a special situation with a proxy in front of Tomcat/Orbeon Forms which itself cannot be accessed by the machine on which Tomcat/Orbeon Forms runs. You'll let us know how this works for you. 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 [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Thanks Alessandro,
That did the trick! Will start testing out that deadlock problem :) (aka if separating exist and orbeon into separate tomcat instances works).
|
Re the deadlock problem
Have you tried to get a thread dump of the running tomcat process If you are running on unix: kill -SIGQUIT <pid of tomcat> (it doesnt actually quit just dumps the trace) The dump goes to the logfile catalina.out (in my case) I imagine that on windows you could execute "catalina.bat run" and type Ctrl-Break to get the dump The best would be to do several in succession to see what changes. That might help to track down what is going on. Let us know how you get on Andy Bailey http://www.hazlorealidad.com -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
On Tue, Aug 5, 2008 at 11:50 AM, Andrew Bailey <[hidden email]> wrote:
> I imagine that on windows you could execute "catalina.bat run" and > type Ctrl-Break to get the dump And on unixish systems, a ctrl-\ does the same as ctrl-break on Windows (assuming you have java running in a terminal). 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 [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |