Lee Carroll | 9 Jul 01:51
Picon
Favicon

Re: jetty and fedora dist


Hello,

>Thank you.  I kept seeing 15 child processes of Java while I was
>writing the startup script.  Lenya is still slow after the move to
>Jetty.  Now I know what to research.

Well I can beat 15. 34 each with 56m of resident memory if you belive top. I 
no longer do.

Antonio saved the day. I was indeed compiling with the wrong java version.
(I was also using the wrong local.blocks.properties due to an inability to 
follow simple instructions)

jetty now starts in quick time with no errors. However still the wild number 
of java processes.

I'm begining to think I need to investigate the way fedora reports procs. I 
think I may be mis-interpreting the stats ?

Any hints would be great.

If I'm sounding flippent I apologise its just that its 10 to 1 in the 
morning and I'm lashed on german import.

Lee C
Antonio Gallardo | 9 Jul 02:30
Favicon

Re: jetty and fedora dist

solprovider <at> gmail.com wrote:

>Thank you.  I kept seeing 15 child processes of Java while I was
>writing the startup script.  Lenya is still slow after the move to
>Jetty.  Now I know what to research.
>
>Why the extra processes?
>
Dunno, simply weird. Check the java version as was told in my previous 
mail. Fedora has a GNU java + there other jars installed in the Fedora 
box. The other jars can create problems too, since often they are 
outdated in relation what Cocoon use.

BTW, Finally, I am planning to use lenya in production for first time. 
It will be in our internal intranet. I am going to play with lenya this 
weekend on our server that is still running Fedora Core 3.

>Rebuild Cocoon with less?
>
Yep. It helps a lot. i.e: Turn off the samples and docs generation.

>What exactly is needed, and why didn't local.build.properties work properly?
>  
>
This is not exactly that "local.build.properties" is bad. You can tweak 
it a little bit more. Tweaking local.blocks.properties helps too.

Lenya version takes the "local.b*.properties" file from a particular 
cocoon version. If you use a newer cocoon version, it may include new 
blocks that are not defined in the "local.blocks.properties" file. 
(Continue reading)

Lee Carroll | 9 Jul 11:50
Picon
Favicon

Re: jetty and fedora dist

Dump of the processes running jetty.

With 256 of memory 4 browser clients requsting every 30 seconds fully load.
8 clients requesting at 30 seconds degrade to the point of errors

With 512 of memory it's the same story. 10 clients cause the server to be 
two slow.

I'm temped to try tomcat but would like to persist with jetty. I installed 
the jdk with the self extrcting binary. Would the rpm package be better?
Any clues in best approach to get to the causes of all these processes would 
be really appreciated.

Lee C

[root <at> serv-2-5-81 ~]# ps -ef | grep java
root     26056     1  0 00:57 ?        00:00:07 
/etc/j2sdk1.4.2_08/bin/java -Xms32M -Xmx512M -cp 
./tools/loader -Djava.endorsed.dirs=./build/lenya/webapp/WEB-INF/lib/endorsed 
 -Dorg.xml.sax.parser=org.apache.xerces.parsers.SAXParser -Djetty.port=8888  
-Dloader.jar.repositories=./tools/jetty/lib:./build/lenya/webapp/WEB-INF/lib/endorsed 
 -Dwebapp=./build/lenya/webapp -Dhome=. -Dloader.main.class=org.mortbay.jetty.Server 
Loader ./tools/jetty/conf/main.xml
root     26057 26056  0 00:57 ?        00:00:00 
/etc/j2sdk1.4.2_08/bin/java -Xms32M -Xmx512M -cp 
./tools/loader -Djava.endorsed.dirs=./build/lenya/webapp/WEB-INF/lib/endorsed 
 -Dorg.xml.sax.parser=org.apache.xerces.parsers.SAXParser -Djetty.port=8888  
-Dloader.jar.repositories=./tools/jetty/lib:./build/lenya/webapp/WEB-INF/lib/endorsed 
 -Dwebapp=./build/lenya/webapp -Dhome=. -Dloader.main.class=org.mortbay.jetty.Server 
Loader ./tools/jetty/conf/main.xml
(Continue reading)

Lee Carroll | 9 Jul 14:40
Picon
Favicon

Re: jetty and fedora dist

Below thread is taken from the gmane archive of jetty support mail list 
(explains the proc issues)

Performance is still a concern.

I'm running appache providing ssl and php app support and proxying through 
to jetty for all lenya content.

Any performace tips greatly appreciated

Lee C

From: Heiner Westphal <susp48 <at> verit.de>
Subject: Re: Lots of processes running under Linux
Newsgroups: gmane.comp.java.jetty.support
Date: 2005-04-04 07:50:03 GMT (13 weeks, 5 days, 4 hours and 42 minutes ago)

Eric,

on 2.4.x linux kernels ps shows a line for each thread.
This changed on 2.6.x kernels.
And, as Chris stated, the memory infos are just duplicated
for each thread.

If you sum it up it makes you nervous.

But since jetty runs in one JVM and one JVM cannot run in
more than one process, what you see is the list of threads,
not processes.
AFAIK there is no mechanism in jetty to fork another JVM
(Continue reading)

Antonio Gallardo | 9 Jul 20:31
Favicon

Re: jetty and fedora dist

Hi Lee:

I read you 2 mails. Some hints:

1- Actually, Fedora Core 3 uses kernel 2.6. I don't remember is the CD 
version uses kernel 2.6. In my FC3 installation it is  2.6.11-1.35_FC3. 
You can check your version running:

 $ uname -r

If your this is not the case and you have root access, you can update 
your instalation running as root:

$yum update

and press "y" when asked to update. This way you will update all 
outdated server packages.

2- I am assuming it is a dedicated server (not shared with other users 
running some java apps), then try to kill all the java process. Use for 
that:

           $ killall java

3-Be sure, there are no more java process running, using

          $ ps ax | grep java

4-Restart jetty. Don't open any web page from the jetty server and check 
again how many process are running using the last step command.
(Continue reading)

Antonio Gallardo | 9 Jul 20:47
Favicon

Re: jetty and fedora dist

Lee Carroll wrote:

> Below thread is taken from the gmane archive of jetty support mail 
> list (explains the proc issues)

Sorry for take too long to not reply. I was out of my computer. ;-)

I read the your mails and I fully agree with Heiner Westphal reply. I 
have 6 years (since june-1999) running RedHat Linux servers and then I 
moved to Fedora, I think my first version was RH 6.0, but 100% sure 
right now.

Actually, I am sucessfully running servers with FC1, FC2, FC3  and FC4 
in production with java. This also means, I am using both kernels 2.4x. 
and 2.6.x.

If the advises of my previous mail does not work. Try to uninstall all 
the java stuff that comes in FC3 using rpm. The problem I see in using 
FC3 java stuff is that it is pretty outdated to our requirements. By 
uninstalling, you can be sure, that you will be using only the things 
you deployed in the server. Wich is good after all.

If you want help with FC3 package management (wich packages to 
uninstall), drop me a mail with the output of:

$ rpm -qa

Best Regards,

Antonio Gallardo.
(Continue reading)

Johannes Jander | 9 Jul 21:57
Picon
Picon
Favicon

Lenya 1.2, Kupu, BXE and image alignment

Hi,

I seem to be unable to insert images into the Default publication of 
a lenya 1.2.x SVN checkout from about 2 weeks ago.

In Kupu, I have the choice between left, right and inline, but 
neither as any effect - after saving, the image has no class- or 
align-attribute.

In BXE, the image object has a lot of attributes, but again neither 
class nor align. So again, no chance to align it somehow.

Am I doing something wrong? The wish to align an image seems rather 
basic to me, so I am puzzled...

Have a nice weekend

RE: Lenya 1.2, Kupu, BXE and image alignment

> Hi,
> 
> I seem to be unable to insert images into the Default publication
> of a lenya 1.2.x SVN checkout from about 2 weeks ago.
> 
> In Kupu, I have the choice between left, right and inline, but 
> neither as any effect - after saving, the image has no class- or 
> align-attribute.
> 
> In BXE, the image object has a lot of attributes, but again
> neither class nor align. So again, no chance to align it somehow.
> 
> Am I doing something wrong? The wish to align an image seems
> rather basic to me, so I am puzzled...
> 
> Have a nice weekend

Yeah, I found this out the hard way myself.  Here's what I did to
fix it:

1.  Go to lenya/resources/kupu/apache-lenya/lenya/ and edit the
file kupusave.xsl.  You should see a chunk like the following:

<!-- this template converts the img tag to object
  for more, see http://www.xml.com/pub/a/2003/07/02/dive.html -->
<xsl:template match="xhtml:img">
   <object>
     <xsl:attribute name="data">

Towards the bottom, you'll see a couple of <xsl:if> statements
(Continue reading)

Lee Carroll | 9 Jul 22:53
Picon
Favicon

Re: jetty and fedora dist

HelloAntonio,

when i do a apt-get upgrade the below list  get flagged for upgrading

I'm not to sure but glibc and glibc-common look worrying, do these under pin 
the jvm ?? Anyway, the upgrade fails due to a signiture problem

Thanks for all this help

Lee C

The following packages will be upgraded
   at (3.1.8-60 => 3.1.8-70_FC3)
   bzip2 (1.0.2-13 => 1.0.2-13.FC3.1)
   bzip2-libs (1.0.2-13 => 1.0.2-13.FC3.1)
   e2fsprogs (1.35-11.2 => 1.36-1.FC3.1)
   glibc (2.3.4-2.fc3 => 2.3.5-0.fc3.1)
   glibc-common (2.3.4-2.fc3 => 2.3.5-0.fc3.1)
   gzip (1.3.3-13 => 1.3.3-15.fc3)
   info (4.7-5 => 4.8-2.1)
   initscripts (7.93.5-1 => 7.93.7-1)
   krb5-libs (1.3.6-2 => 1.3.6-5)
   libgcc (3.4.2-6.fc3 => 3.4.3-22.fc3)
   libstdc++ (3.4.2-6.fc3 => 3.4.3-22.fc3)
   lycos-vds-dummy (0.1-1 => 2.0-0.1.fc3)
   openssh (3.9p1-7 => 3.9p1-8.0.2)
   openssh-clients (3.9p1-7 => 3.9p1-8.0.2)
   openssh-server (3.9p1-7 => 3.9p1-8.0.2)
   openssl (0.9.7a-40 => 0.9.7a-42.1)
   perl (5.8.5-9 => 5.8.5-12.FC3)
(Continue reading)

Antonio Gallardo | 9 Jul 23:18
Favicon

Re: jetty and fedora dist

Hi:

This is OK. I have all of this packages already installed and everything 
works. Try yum instead of apt. yum is the prefered package for Fedora 
update. If you plan to use apt, then you will need to configure it 
first. Don't worry about apt, yum is already configured and ready to do 
the job! ;-)

Best Regards,

Antonio Gallardo

Lee Carroll wrote:

> HelloAntonio,
>
> when i do a apt-get upgrade the below list  get flagged for upgrading
>
> I'm not to sure but glibc and glibc-common look worrying, do these 
> under pin the jvm ?? Anyway, the upgrade fails due to a signiture problem
>
> Thanks for all this help
>
> Lee C
>
> The following packages will be upgraded
>   at (3.1.8-60 => 3.1.8-70_FC3)
>   bzip2 (1.0.2-13 => 1.0.2-13.FC3.1)
>   bzip2-libs (1.0.2-13 => 1.0.2-13.FC3.1)
>   e2fsprogs (1.35-11.2 => 1.36-1.FC3.1)
(Continue reading)


Gmane