Am 15.02.2011 06:42, schrieb Brett Porter: > > On 14/02/2011, at 10:09 PM, Benjamin Knoth wrote: > >> If i use archiva dump on 100 cpu usage it creates a dump of the java >> process with a high pid. This process runs normally with 0 % cpu and 4.9 >> % Mem. But if i restart archiva and make a dump with archiva dump i >> didn't found a second java process on top. > > This sounds a little weird. You have two java processes running? Or only when > the dump is done? (haven't noticed that before - but the dump runs too fast > to check).
Sorry only one java process is running. But two processes from archiva. If i start archiva dump i get this two messages. Dumping Apache Archiva... Dumped Apache Archiva. But i can see any changes on archiva.pid or new processes of archiva or dump. This Processes did i found with ps aux | grep archiva root 21392 0.0 0.0 10000 620 ? Sl 12:36 0:00 /data/archiva/apache-archiva-1.3.3/bin/./wrapper-linux-x86-32 /data/archiva/apache-archiva-1.3.3/bin/../conf/wrapper.conf wrapper.syslog.ident=archiva wrapper.pidfile=/data/archiva/apache-archiva-1.3.3/bin/../logs/archiva.pid wrapper.daemonize=TRUE wrapper.lockfile=/var/lock/subsys/archiva root 21394 99.9 9.4 876032 397936 ? Sl 12:36 169:52 java -Dappserver.home=. -Dappserver.base=. -Djetty.logs=./logs -Xms512m -Xmx512m -Djava.library.path=lib -classpath lib/wrapper.jar:lib/archiva-jetty-1.3.3.pom:lib/jetty-6.1.19.jar:lib/jetty-util-6.1.19.jar:lib/servlet-api-2.5-20081211.jar:lib/start-6.1.19.jar:lib/jetty-naming-6.1.19.jar:lib/mail-1.4.jar:lib/jsp-2.1-jetty-6.1.19.jar:lib/core-3.1.1.jar:lib/jsp-api-2.1-glassfish-9.1.1.B60.25.p0.jar:lib/jsp-2.1-glassfish-9.1.1.B60.25.p0.jar:lib/ant-1.6.5.jar:lib/jetty-plus-6.1.19.jar:lib/geronimo-spec-jta-1.0.1B-rc4.jar:lib/derby-10.1.3.1.jar:lib/activation-1.1.jar:lib/commons-dbcp-1.2.1.jar:lib/commons-collections-3.2.jar:lib/commons-pool-1.2.jar:lib/xml-apis-1.0.b2.jar:lib/postgresql-9.0-801.jdbc3.jar -Dwrapper.key=zXRSxqH5Ghp21yZj -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=21392 -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.mortbay.start.Main ./conf/jetty.xml > > You can confirm what is expected by checking the PID in ./logs/archiva.pid. > Is that the one on 100% CPU? No in archiva.pid is saved this pid 21392. > >> What should i do with the dump of archiva? > > Does the list of threads give any hint about what is going on in the server > at that time? Perhaps you could attach that text to a jira issue for further > investigation. We'd mainly be interested in anything that contains a trace > from "org.apache.*" > >> >> At the same time in meantime there are using max. 5 people archiva at >> the same time. > > Given what you've shown in the logs, status page, and number of users so far, > there should be no reason for the CPU to go to 100% at all, other than at > pre-defined scanning intervals. > > I think we'll need to gather more logs or data via JIRA to figure out what's > happening... Ok > > - Brett > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > > > >
