Re: [Exist-open] JMXClient help

[Casey J. <cas...@jo...>]

On Tue, Feb 22, 2011 at 2:43 PM, Wolfgang Meier <wol...@ex...>wrote:

> > So the next thing I did was up my memory on the server to 4GB and set the
> > Xmx setting in bin/functions.d/eXist-settings.sh to 2500M.
>
> There has to be something wrong with the settings. Did you increase
> both -Xmx parameters in eXist-settings.sh?
>
>
Here is an excerpt from the eXist-settings.sh file:

-----------------
set_client_java_options() {
    if [ -z "${CLIENT_JAVA_OPTIONS}" ]; then
        CLIENT_JAVA_OPTIONS="-Xms128m -Xmx512m -Dfile.encoding=UTF-8";
    fi
    JAVA_OPTIONS="${CLIENT_JAVA_OPTIONS}
-Djava.endorsed.dirs=${JAVA_ENDORSED_DIRS}";
}

set_java_options() {
    if [ -z "${JAVA_OPTIONS}" ]; then
        JAVA_OPTIONS="*-Xms128m -Xmx2512m* -Dfile.encoding=UTF-8";
    fi
    JAVA_OPTIONS="${JAVA_OPTIONS}
-Djava.endorsed.dirs=${JAVA_ENDORSED_DIRS}";
}
set_exist_options() {
    OPTIONS="-Dexist.home=$EXIST_HOME"
}

-----------------

However I am using a custom startup script that looks like this:

-----------------
export EXIST_HOME=/usr/local/exist-stable-1.4.1
export JAVA_OPTIONS="$JAVA_OPTIONS -Djava.awt.headless=true"

$EXIST_HOME/bin/startup.sh -j 1099
----------------

Could this be messing things up?


> Does "corruption" mean that eXist was attempting a recovery run at
> restart (and failed?) or did it just start up and some docs were
> missing? Also, were any updates done to the database in the one or two
> minutes before it crashed? If so, we could decrease the checkpoint
> period. If not, I'm not sure why it should corrupt any data and I'll
> need to run some tests myself.
>

I got the "database instance "exist" is not available" type error. So I
removed the necessary *.dbx and *.lck files and restarted. After a re-index
everything seemed ok, but obviously I can't afford to do this in a
production environment.


>
> Certainly, on a machine with just 512 mb memory, the caches will be
> much smaller and pages will be written faster. It thus becomes more
> unlikely that pages get lost during an out of memory. Well, I'll run
> some tests here...
>

That makes sense, and I don't intend to run eXist in that type of low memory
environment, I was just seeing what would happen if I did. That being said,
during normal operations for one user in our system eXist performed pretty
well on 512MB of ram.


Thanks,

Casey

-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
Cell (585) 348 7399
Office (585) 239 6060
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.