[Exist-development] Busy DB

[Hungerburg <pc...@my...>]

Logging onto my system, i noticed high uptime. Top told me, its java, 
one of the eXist processes. Looking at collectd graphs I see that its 
been so since friday noon, when I did some tricks on a controller.xql to 
have it return json for some xml, just editing xquery in eXide. I cannot 
tell exactly, what triggered eXist-db to hog the cpu. Both system and 
eXist were quite responsive nevertheless.

Below what top and ps told me. Attached a jstack, that may tell enough 
for eg. Dmitriy to know, what eXist did not like, maybe a busy loop 
somewhere, or a fight between two threads. If this helps find and fix a 
bug, I was delighted.

## top:
   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  2187 wirt      20   0 1935m 471m 2964 S  197 23.7   8315:12 java
## ps axuwww:
wirt      2187  123 23.6 1981532 482904 ?      Sl   Jan23 8311:36 
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java 
-Djava.endorsed.dirs=../../../lib/endorsed -Dfile.encoding=UTF-8 
-Dexist.home=../../.. -Djetty.home=../../../tools/jetty 
-Dlog4j.configuration=file:../conf/log4j.xml -Xms256m -Xmx512m 
-Djava.library.path=../lib -classpath 
../classes:../lib/wrapper.jar:../../../start.jar 
-Dwrapper.key=bU63D03NiPgda5k6 -Dwrapper.port=32000 
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
-Dwrapper.disable_console_input=TRUE -Dwrapper.pid=2185 
-Dwrapper.version=3.5.17 -Dwrapper.native_library=wrapper 
-Dwrapper.arch=x86 -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 
-Dwrapper.jvmid=1 org.exist.wrapper.Main jetty 
../../../tools/jetty/etc/jetty.xml

Kind Regards

Peter