eXist DB Size Issue

Hi - We are using Tomcat+Liferay to host our Xforms portlets. The application is running fine but we noticed recently that the size of dom.dbx and words.dbx files is increasing very fast. Our application becomes slow to almost unusable state and works fine only when the files are deleted and the app server restarted. We are not sure on why this problem is occurring. But for example, the file size increased from 700MB to 1.4 GB in less than an hour.

Any suggestion on identifying the problem or handling the eXist log files would be extremely helpful.

Lakshman

Hello , We are using Orbeon and exist integrated. On production we are have very strange behavior , exist-data size is being increased continuously, specially log file..i do't understand why it is happening..Could you please suggest something.. Do we need to use separate deployment of exist with Orbeon... /Chandra

Hello Everybody,

Could you suggest something about the issue..It is very critical..

Thanks,
Chandra

Hi Chandra,

I'm not certain what your problem is. However I had a problem where my Exist database was continuously
growing, I believe this was to do with Exist not removing user sessions when they expired. This may be the problem you describe.

There is a section in web.xml which by default (in dev-3.7 anyway) is commented out. Uncommenting this section apparently enables Exist to remove expired sessions and prevents Exist growing too much.

In
${TOMCAT_HOME}/webapps/myescholar/WEB-INF/web.xml
Uncomment lines 147 to 150 enabling

<listener>
    <listener-class>org.orbeon.oxf.webapp.OPSSessionListenerDelegate</listener-class>
</listener>

See also this thread:
http://n4.nabble.com/SessionListener-disabled-by-default-td43851.html#a43852

I performed this configuration a while ago so have doubts as to how much of what I said above is true and valid.

Good luck and HTH,

Tom

chandra wrote

Hello Everybody,

Could you suggest something about the issue..It is very critical..

Thanks,
Chandra

It is already uncommented.. I am using version 3.6.0 .

Thanks for your reply..
/Chandra

Exist integrated into Orbeon XForm is not at all working after 30 minutes ...XQuery is not able to read the data from Exist DB after that.

XQuey has been deployed as standard files in web container.. that could be a cause for the problem?
all XQuery need to be deployed  in ExistDB..? Please suggest me..

your help would be much appreciated..
/Chandra

Chandra,

As mentioned above, at some point (maybe 3.7.1?) we had an issue
whereby the session listener was not properly cleaning-up expired
session data in eXist. This has since been fixed in nightly builds and
will be in 3.7.2.

But you are saying you are using 3.6, and I am not sure 3.6 had that
particular issue or not. And anyway it seems your listener is in
place, so that might not be the issue.

Last year we had this bug, which might be what you are hitting:

http://forge.ow2.org/tracker/index.php?func=detail&aid=311644&group_id=168&atid=350207

But since 3.6 we upgraded eXist to a more recent version, and we
haven't seen that particular issue since then.

If the issue is in fact related to a particular version of eXist, you
might be able to plug in a newer version of eXist.

Also note that there are two different uses of eXist in Orbeon Forms:

1. on one hand, it is used by the XForms engine itself to store some
state information
2. on the other hand, it can be used by applications to store form data

Here the issue is likely related to #1.

-Erik

On Tue, Nov 24, 2009 at 6:50 AM, chandra <[hidden email]> wrote:

--
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

Hi ,

It seems Exist 1.4 upgrade will help me..
Has anybody has integrated exist 1.4 into orbeon any version..
I am doing the exist upgrade and facing some issue...

Thanks,
Chandra

Hi Chandra:

Yes, we have eXist1.4 running alongside our Orbeon installations.  
However, we run eXist separately from Orbeon.  What is the nature of
your issue?

Nigel

chandra wrote:

--
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

Hi Nigel,

Great to hear so..

In Orbeon 3.6 (Production release) Exist has been integrated version 1.2.4 series..
We are facing problem..please see the above dialogues.

After doing the evaluation, i decided to upgrade  Orbeon XQuery engine with latest 1.4 version because that seems to solve the problems.

Please advice me if i am wrong on that..

I have updated all relevant jar from exist 1.4 to Orbeon's web-inf/lib..
and i changed the lucene configuration block in exist-conf.xml in orbeon.

I also copied the backup.properties and client.properties (using the # access a local instance of the database uri=xmldb:exist://)

When i restart the Jboss it gives me error Exist DB instance not available.

I have also  build  Exist src 1.4  and deployed the war  war file that is working fine as separate instance on same Jboss.. but not working in orbeon context. as local instance.

/Chandra

Hi Chandra:

Our situation is a little different:

o We're using a fairly recent nightly build of 3.7.1dev
o We are using eXist running separately, in its own Jetty container
  - To do this, we set the appropriate property in the
properties-xforms.xml file:

  <property as="xs:anyURI"  name="oxf.xforms.store.application.uri"  
value="xmldb:exist://url-of-exist-container:8080/exist/xmlrpc/"/>

 (and there are some other relevant properties there, too)

o We have removed the exist servlet lines in the Orbeon web.xml file

and all seems to work as expected.

So, I wonder if 3.6.0 had that property at all.  I also suspect that the
splitting of the properties into different files happened somewhere in
the 3.7 development process.  I also recollect that the embedded version
of eXist had one or more jars 'orbeonized' (presumably because of
package name clashes), which might make just updating the embedded
version more difficult.

Nigel

chandra wrote:

--
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