You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Ron Wheeler <rw...@artifact-software.com> on 2005/07/08 18:02:44 UTC
Re: Building Lenya 1.4 under Eclipse with Java 1.5
After all my fumbling around, you probably will find it hard to believe
that I am staring at a Jetty delivered "Welcome to Lenya" screen on
127.0.0.1:8888.
To get Lenya to build and run to this point under Java 1.5 using
Eclipse, I had to do the following things that are not in the Howto
1) Install the cocoon sources in a directory and set
local.build.properties to point to it
I did this in a directory outside Eclipse but I suppose you could
put them inside.
Set the cocoon.src.dir in your local.build.properties to point to
the top of the cocoon source tree.
There are ant taskdefs and probably other things that the build
needs in the cocoon source tree.
2) Set up xalan to override whatever Java 1.5 did to the xalan
functionality.
Download the latest xalan distribution
In your Java 1.5 jdk to which your JAVA_HOME points, create a
subdirectory under lib (I did it both under the jre and the main lib
just to be safe). Copy all the xalan jars into the endorsed subdirectory.
In Eclipse add xalan to the Lenya project classpath for java
compiles/builds.
It took me a bit of thinking to understand that the errors during the
build where really caused by Eclipse's lack of access to the xalan
functionailty required to run the ant tasks.
Since Eclipse does not use the build.bat file, the Ant used to process
the build.xml is Eclipse's ant which in my case is the latest virgin.
There were warnings about depricated functions during the build.
When I start Jetty, there are a lot of warnings saying
- Ignored element 'init-param' as child of 'servlet'.
I am not sure how jetty works and perhaps the xalan issue might come up
again.
I am now going to move on to the Tomcat install. I suspect that I will
have to do the same thing with xalan to make sure that Tomcat has access
to the xalan functionailty.
Thanks for all of the advice over this little trip.
I hope that these ideas can be incorporated into the Wiki for both the
Eclipse install and the command/shell line install under Java 1.5
I hope that someone will look into the deprecated function(it seems to
be just one) and the jetty configuration file errors.
It is hard to have confidence in your own installation if software
issues warnings.
Ron
Gregor J. Rothfuss wrote:
> Ron Wheeler wrote:
>
>> With Java 1.5 for everything I get this error which looks a bit
>> easier to fix. What am I missing?
>
>
>> BUILD FAILED
>> java.lang.NoClassDefFoundError: org/apache/xpath/XPathAPI
>
>
> this is due to http://issues.apache.org/bugzilla/show_bug.cgi?id=34191
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
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)
> 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)
> procps (3.2.3-5.1 => 3.2.3-5.2)
> telnet (0.17-30 => 0.17-32.FC3.2)
> tzdata (2005c-1.fc3 => 2005f-1.fc3)
> udev (039-10.FC3.6 => 039-10.FC3.7)
> util-linux (2.12a-16 => 2.12a-24.3)
> vixie-cron (4.1-20_FC3 => 4.1-33_FC3)
> words (3.0-2 => 3.0-2.3)
>
> ----- Original Message ----- From: "Antonio Gallardo"
> <ag...@agssa.net>
> To: <us...@lenya.apache.org>
> Sent: Saturday, July 09, 2005 7:47 PM
> Subject: 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.
>>
>>>
>>> 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
>>> (other than doing it yourself using Run or System or something).
>>>
>>> HTH,
>>>
>>> Heiner
>>>
>>> Eric Rizzo wrote:
>>>
>>>> On Apr 3, 2005 4:56 AM, Chris Haynes <chris <at> harvington.org.uk>
>>>> wrote:
>>>>
>>>>> Greg or Jan can give you the definitive answer on the number of
>>>>> threads needed,
>>>>> but I don't think it should be as high as you are seeing.
>>>>>
>>>>> I did some tests a few months ago and thought I was using 1 for
>>>>> the stop
>>>>> listener and exactly the right number accounted for by my declared
>>>>> listeners.
>>>>>
>>>>> Are you starting Jetty with just one service; just one .xml file
>>>>> in the start
>>>>> line?
>>>>>
>>>>> On the memory issue - Don't Panic!
>>>>>
>>>>> I run on SuSe Linux, but I expect Debian is the same in this
>>>>> respect...
>>>>>
>>>>> You have only one JVM, and so one set of memory. The threads all
>>>>> take their
>>>>> memory from within this one JVM allocation. The 'ps' listing
>>>>> can't see inside
>>>>> the JVM to see how much memory each thread is using, so it just
>>>>> lists the size
>>>>> of the (one) JVM against all of its threads!
>>>>
>>>>
>>>>
>>>>
>>>> Thanks for taking the time to reply. However, I am not talking about
>>>> threads - multiple thread don't bother me - what I'm seeing (or think
>>>> I'm seeing, at least) is a lot of individal processes. I first saw it
>>>> by doing the simple "java -jar start.jar" from the Jetty install
>>>> directory. I only tried tweking down the listener thread pool as a
>>>> "grasping at straws" attempt to find the cause of so many individual
>>>> processes.
>>>> I'm no Linux guru, but neither am I a *nix newbie, and I don't think
>>>> ps and top should be listing a separate processes for every thread
>>>> (even if the Jetty config I was using was creating 20 threads, which
>>>> I'm pretty sure it is not configured to do).
>>>>
>>>> Eric
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
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)
procps (3.2.3-5.1 => 3.2.3-5.2)
telnet (0.17-30 => 0.17-32.FC3.2)
tzdata (2005c-1.fc3 => 2005f-1.fc3)
udev (039-10.FC3.6 => 039-10.FC3.7)
util-linux (2.12a-16 => 2.12a-24.3)
vixie-cron (4.1-20_FC3 => 4.1-33_FC3)
words (3.0-2 => 3.0-2.3)
----- Original Message -----
From: "Antonio Gallardo" <ag...@agssa.net>
To: <us...@lenya.apache.org>
Sent: Saturday, July 09, 2005 7:47 PM
Subject: 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.
>
>>
>> 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
>> (other than doing it yourself using Run or System or something).
>>
>> HTH,
>>
>> Heiner
>>
>> Eric Rizzo wrote:
>>
>>> On Apr 3, 2005 4:56 AM, Chris Haynes <chris <at> harvington.org.uk>
>>> wrote:
>>>
>>>> Greg or Jan can give you the definitive answer on the number of threads
>>>> needed,
>>>> but I don't think it should be as high as you are seeing.
>>>>
>>>> I did some tests a few months ago and thought I was using 1 for the
>>>> stop
>>>> listener and exactly the right number accounted for by my declared
>>>> listeners.
>>>>
>>>> Are you starting Jetty with just one service; just one .xml file in the
>>>> start
>>>> line?
>>>>
>>>> On the memory issue - Don't Panic!
>>>>
>>>> I run on SuSe Linux, but I expect Debian is the same in this respect...
>>>>
>>>> You have only one JVM, and so one set of memory. The threads all take
>>>> their
>>>> memory from within this one JVM allocation. The 'ps' listing can't see
>>>> inside
>>>> the JVM to see how much memory each thread is using, so it just lists
>>>> the size
>>>> of the (one) JVM against all of its threads!
>>>
>>>
>>>
>>> Thanks for taking the time to reply. However, I am not talking about
>>> threads - multiple thread don't bother me - what I'm seeing (or think
>>> I'm seeing, at least) is a lot of individal processes. I first saw it
>>> by doing the simple "java -jar start.jar" from the Jetty install
>>> directory. I only tried tweking down the listener thread pool as a
>>> "grasping at straws" attempt to find the cause of so many individual
>>> processes.
>>> I'm no Linux guru, but neither am I a *nix newbie, and I don't think
>>> ps and top should be listing a separate processes for every thread
>>> (even if the Jetty config I was using was creating 20 threads, which
>>> I'm pretty sure it is not configured to do).
>>>
>>> Eric
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
Lee Carroll wrote:
>> If vds = virtual dedicated(?) server or something like that, then no
>> wonder why there are other jetty threads running + slowness. There is
>> not much we can do to improve performance since there are other
>> applications running from other users. Maybe the problem is not that
>> jetty stop responding. I will be glad to see the real load of the
>> server before blaming to jetty. ;-)
>>
>> Is this the case?
>
>
> I don't think so,but i'd be interested in opinions
> This thread started as our existing hosting provider went bust and
> disappeared without a trace. We are trying out a very large hosting
> company (This is the second hosting company who has went under on us
> so we are banking on a possibly rubbish but large company). They are
> offering a "VDS" based on linux v server. (http://linux-vserver.org/)
IMHO, actually VDS is a "hot" word in IT world. I had no time to fully
read about the technology internals of all this VDS products, but AFAIK,
most of them consumes considerable CPU power (relatively speaking). What
I know is one of the most important new features in Fedora Core 4 is XEN
(another VM product) -
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html
> Physical Resources (memory , cpu , priotiy, disk and network) are ring
> fenced and apparently completely isolated from other users on the
> hardware. the java procs running jetty are all mine.
I don't buy this. It is not consistent with the "virtual dedicated
server" concept. ;-)
We are running a similar technology in apache. ie: all this sites runs
into his own VDS. IIRC, it is a Solaris:
http://lenya.zones.apache.org:8888/
http://forrest.zones.apache.org/
http://cocoon.zones.apache.org/
ping struts.zones.apache.org
ping maven.zones.apache.org
and others.
One of the requirements we got is that each server cannot run
intensively task since all the resources (RAM, CPU, etc) are shared
between them. VDS means we create an illusion of differente separated
servers in one machines.
>
> As for blaming jetty I'm sure its not jetty which is the problem.
> Dodgy install of os , dodgy jdk etc ??
Try to stop all your jetty instance and see if you don't see other java
procceses running.
>
> we have 3 servers (vds) with high cpu priority, 512mb of memory, 1024
> kbps network connection. surely thats enough to support a modest lenya
> install ?
In one dedicated machine (non-virtual), it is enough. We have similar
configs in production. But in a VDS, I don't have idea. Since I don't
know how many virtual machines are there competing for the same hardware
resources, I don't know the real CPU power, real RAM size and so on. If
the sum of all the RAM used by running processes in all the virtual
machines is greater than the real amount of installed RAM, hence the
machine is swapping and this is painful slow.
Given this fact, try to lower the resources used by your jetty servers.
Start the default (64 MB) and check if this works for your needs. To be
honest, I will recommend you a real dedicated machines (non-VDS). I know
it mainly depends on the resources you have for the task.
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
> If vds = virtual dedicated(?) server or something like that, then no
> wonder why there are other jetty threads running + slowness. There is not
> much we can do to improve performance since there are other applications
> running from other users. Maybe the problem is not that jetty stop
> responding. I will be glad to see the real load of the server before
> blaming to jetty. ;-)
>
> Is this the case?
I don't think so,but i'd be interested in opinions
This thread started as our existing hosting provider went bust and
disappeared without a trace. We are trying out a very large hosting company
(This is the second hosting company who has went under on us so we are
banking on a possibly rubbish but large company). They are offering a "VDS"
based on linux v server. (http://linux-vserver.org/) Physical Resources
(memory , cpu , priotiy, disk and network) are ring fenced and apparently
completely isolated from other users on the hardware. the java procs running
jetty are all mine.
As for blaming jetty I'm sure its not jetty which is the problem. Dodgy
install of os , dodgy jdk etc ??
we have 3 servers (vds) with high cpu priority, 512mb of memory, 1024 kbps
network connection. surely thats enough to support a modest lenya install ?
Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
Lee Carroll wrote:
> The list was produced as root
>
> The server is a vds which might explain the partial list ?
If vds = virtual dedicated(?) server or something like that, then no
wonder why there are other jetty threads running + slowness. There is
not much we can do to improve performance since there are other
applications running from other users. Maybe the problem is not that
jetty stop responding. I will be glad to see the real load of the server
before blaming to jetty. ;-)
Is this the case?
Best Regards,
Antonio Gallardo.
>
> If I do remove packages should I re build cocoon an lenya ?
> Lee C
>
> ----- Original Message ----- From: "Antonio Gallardo"
> <ag...@agssa.net>
> To: <us...@lenya.apache.org>
> Sent: Sunday, July 10, 2005 12:37 AM
> Subject: Re: jetty and fedora dist
>
>
>> Lee Carroll wrote:
>>
>>>
>>>> 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
>>>>
>>>
>>> I upgraded packages (yum is missing from the install so had to use
>>> apt-get upgrade)
>>
>>
>> weird. On the rpm list below, I was unable to find up2date and
>> kernel. I wonder why the list is not complete? Try to run the $rpm
>> -qa as root and check for diff in package list.
>>
>> Anyway, I will review the partial package list and tell yo what you
>> can remove.
>>
>>> stopped all java procs and restarted lenya still 34 java procs
>>> running jetty, httpd also is spawning multiple procs.
>>
>>
>> Wich kernel do you have? (run: $uname -r)
>>
>> Best Regards,
>>
>> Antonio Gallardo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
The list was produced as root
The server is a vds which might explain the partial list ?
If I do remove packages should I re build cocoon an lenya ?
Lee C
----- Original Message -----
From: "Antonio Gallardo" <ag...@agssa.net>
To: <us...@lenya.apache.org>
Sent: Sunday, July 10, 2005 12:37 AM
Subject: Re: jetty and fedora dist
> Lee Carroll wrote:
>
>>
>>> 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
>>>
>>
>> I upgraded packages (yum is missing from the install so had to use
>> apt-get upgrade)
>
> weird. On the rpm list below, I was unable to find up2date and kernel. I
> wonder why the list is not complete? Try to run the $rpm -qa as root and
> check for diff in package list.
>
> Anyway, I will review the partial package list and tell yo what you can
> remove.
>
>> stopped all java procs and restarted lenya still 34 java procs running
>> jetty, httpd also is spawning multiple procs.
>
> Wich kernel do you have? (run: $uname -r)
>
> Best Regards,
>
> Antonio Gallardo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
Lee Carroll wrote:
>
>> 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
>>
>
> I upgraded packages (yum is missing from the install so had to use
> apt-get upgrade)
weird. On the rpm list below, I was unable to find up2date and kernel. I
wonder why the list is not complete? Try to run the $rpm -qa as root and
check for diff in package list.
Anyway, I will review the partial package list and tell yo what you can
remove.
> stopped all java procs and restarted lenya still 34 java procs running
> jetty, httpd also is spawning multiple procs.
Wich kernel do you have? (run: $uname -r)
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
> 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
>
I upgraded packages (yum is missing from the install so had to use apt-get
upgrade) stopped all java procs and restarted lenya
still 34 java procs running jetty, httpd also is spawning multiple procs.
rpm -qa produces the following
(Any help on what to remove would be great) lee c
hwdata-0.145-1
mktemp-1.5-10
rpm-libs-4.3.2-21
cracklib-2.7-28
cracklib-dicts-2.7-28
psmisc-21.4-4
iproute-2.6.9-3
grep-2.5.1-31.4
iputils-20020927-16
lvm2-2.00.25-1.01
coreutils-5.2.1-31
shadow-utils-4.0.3-56
MAKEDEV-3.13-1
SysVinit-2.85-34
rpm-4.3.2-21
openldap-2.2.13-2
setup-2.5.36-1
libselinux-1.19.1-8
chkconfig-1.3.11.1-1
elfutils-libelf-0.96-1
ncurses-5.4-13
readline-4.3-13
gdbm-1.8.0-24
tar-1.14-4
fedora-release-3-8
pcre-4.5-3
glib2-2.4.8-1.fc3
device-mapper-1.00.19-2
mingetty-1.07-3
wget-1.9.1-17
perl-Filter-1.30-6
cyrus-sasl-md5-2.1.19-3
gpg-pubkey-6b8d79e6-3f49313d
gpg-pubkey-4f2a6fd2-3f9d9d3b
gpg-pubkey-db42a60e-37ea5438
libuser-0.52.5-1
groff-1.18.1.1-3
man-1.5o1-7
sendmail-8.13.1-2
xinetd-2.3.13-4
ftp-0.17-22
mailx-8.1.1-33
rootfiles-8-1
vim-minimal-6.3.054-0.fc3.1
apr-0.9.4-24.2
apr-util-0.9.4-17
httpd-2.0.52-3.1
distcache-1.4.5-6
mod_ssl-2.0.52-3.1
gpg-pubkey-c5263616-425fcd5f
glibc-common-2.3.5-0.fc3.1
libgcc-3.4.3-22.fc3
bzip2-libs-1.0.2-13.FC3.1
gzip-1.3.3-15.fc3
procps-3.2.3-5.2
lycos-vds-dummy-2.0-0.1.fc3
initscripts-7.93.7-1
libstdc++-3.4.3-22.fc3
openssh-clients-3.9p1-8.0.2
openssh-server-3.9p1-8.0.2
bzip2-1.0.2-13.FC3.1
telnet-0.17-32.FC3.2
termcap-5.4-3
beecrypt-3.1.0-6
bash-3.0-18
sed-4.1.2-4
db4-4.2.52-6
cpio-2.5-7
libacl-2.2.23-5
hotplug-2004_04_01-8.1
ethtool-1.8-4
module-init-tools-3.1-0.pre5.3
mkinitrd-4.1.18-2
cyrus-sasl-2.1.19-3
apt-0.5.15cnc6-0.fdr.11.3
filesystem-2.3.0-1
basesystem-8.0-4
zlib-1.2.1.2-1
popt-1.9.1-21
libtermcap-2.0.8-39
findutils-4.1.20-7
gawk-3.1.3-9
less-382-4
net-tools-1.60-37.FC3.1
libattr-2.4.16-3
usbutils-0.11-6.1
libsepol-1.1.1-2
pam-0.77-66.2
sysklogd-1.4.1-26_FC3
gnupg-1.2.6-1
gpg-pubkey-f3b91a7b-420c8c9c
gpg-pubkey-8df56d05-3e828977
tcp_wrappers-7.6-37.2
procmail-3.22-14
hesiod-3.0.2-30
diffutils-2.8.1-12
file-4.12-1.FC3.1
crontabs-1.10-7
logrotate-3.7.1-2
man-pages-1.67-3
passwd-0.68-10
perl-Net-SSLeay-1.25-1.1.fc3.rf
expat-1.95.7-4
mailcap-2.1.17-1
httpd-suexec-2.0.52-3.1
make-3.80-5
j2sdk-1.4.2_08-fcs
tzdata-2005f-1.fc3
glibc-2.3.5-0.fc3.1
at-3.1.8-70_FC3
e2fsprogs-1.36-1.FC3.1
info-4.8-2.1
udev-039-10.FC3.7
util-linux-2.12a-24.3
krb5-libs-1.3.6-5
openssl-0.9.7a-42.1
openssh-3.9p1-8.0.2
vixie-cron-4.1-33_FC3
perl-5.8.5-12.FC3
words-3.0-2.3
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
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.
>
> 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
> (other than doing it yourself using Run or System or something).
>
> HTH,
>
> Heiner
>
> Eric Rizzo wrote:
>
>> On Apr 3, 2005 4:56 AM, Chris Haynes <chris <at> harvington.org.uk>
>> wrote:
>>
>>> Greg or Jan can give you the definitive answer on the number of
>>> threads needed,
>>> but I don't think it should be as high as you are seeing.
>>>
>>> I did some tests a few months ago and thought I was using 1 for the
>>> stop
>>> listener and exactly the right number accounted for by my declared
>>> listeners.
>>>
>>> Are you starting Jetty with just one service; just one .xml file in
>>> the start
>>> line?
>>>
>>> On the memory issue - Don't Panic!
>>>
>>> I run on SuSe Linux, but I expect Debian is the same in this respect...
>>>
>>> You have only one JVM, and so one set of memory. The threads all
>>> take their
>>> memory from within this one JVM allocation. The 'ps' listing can't
>>> see inside
>>> the JVM to see how much memory each thread is using, so it just
>>> lists the size
>>> of the (one) JVM against all of its threads!
>>
>>
>>
>> Thanks for taking the time to reply. However, I am not talking about
>> threads - multiple thread don't bother me - what I'm seeing (or think
>> I'm seeing, at least) is a lot of individal processes. I first saw it
>> by doing the simple "java -jar start.jar" from the Jetty install
>> directory. I only tried tweking down the listener thread pool as a
>> "grasping at straws" attempt to find the cause of so many individual
>> processes.
>> I'm no Linux guru, but neither am I a *nix newbie, and I don't think
>> ps and top should be listing a separate processes for every thread
>> (even if the Jetty config I was using was creating 20 threads, which
>> I'm pretty sure it is not configured to do).
>>
>> Eric
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
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
(other than doing it yourself using Run or System or something).
HTH,
Heiner
Eric Rizzo wrote:
> On Apr 3, 2005 4:56 AM, Chris Haynes <chris <at> harvington.org.uk> wrote:
>
>>Greg or Jan can give you the definitive answer on the number of threads
>>needed,
>>but I don't think it should be as high as you are seeing.
>>
>>I did some tests a few months ago and thought I was using 1 for the stop
>>listener and exactly the right number accounted for by my declared
>>listeners.
>>
>>Are you starting Jetty with just one service; just one .xml file in the
>>start
>>line?
>>
>>On the memory issue - Don't Panic!
>>
>>I run on SuSe Linux, but I expect Debian is the same in this respect...
>>
>>You have only one JVM, and so one set of memory. The threads all take
>>their
>>memory from within this one JVM allocation. The 'ps' listing can't see
>>inside
>>the JVM to see how much memory each thread is using, so it just lists the
>>size
>>of the (one) JVM against all of its threads!
>
>
> Thanks for taking the time to reply. However, I am not talking about
> threads - multiple thread don't bother me - what I'm seeing (or think
> I'm seeing, at least) is a lot of individal processes. I first saw it
> by doing the simple "java -jar start.jar" from the Jetty install
> directory. I only tried tweking down the listener thread pool as a
> "grasping at straws" attempt to find the cause of so many individual
> processes.
> I'm no Linux guru, but neither am I a *nix newbie, and I don't think
> ps and top should be listing a separate processes for every thread
> (even if the Jetty config I was using was creating 20 threads, which
> I'm pretty sure it is not configured to do).
>
> Eric
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
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.
This must fix the problem of multiple started jetty instances.
- 0 -
Jetty is used in big websites. I hear it is good and pretty fast and
stable. I believe we cannot complain about jetty.
The problem may arise if you are not stoping old jetty servlets while
you are starting a new one. That means the old one stays in memory,
hence why we see a lot using the ps command. This is the only problem I
can see in this case. Maybe I am wrong. Remember that, I am just trying
to be a "doctor" by phone. ;-)
The same problem might arise if you are only launching new tomcat
servelets without stopping the previous one. To summarize, when things
goes weird, kill all the servlet conainter process and launch a new one.
Best Regards,
Antonio Gallardo.
Lee Carroll wrote:
> 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@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
> root 26058 26057 0 00:57 ? 00:00:11
> /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 26059 26057 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
> root 26060 26057 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
> root 26061 26057 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
> root 26062 26057 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
> root 26063 26057 0 00:57 ? 00:00:05
> /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 26067 26057 0 00:57 ? 00:00:02
> /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 26080 26057 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
> root 26121 26057 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
> root 26125 26057 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
> root 26132 26057 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
> root 26138 26057 0 00:57 ? 00:00:05
> /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 26413 26057 0 00:58 ? 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
> root 26471 26057 0 00:58 ? 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
> root 26472 26057 0 00:58 ? 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
> root 26473 26057 0 00:58 ? 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
> root 26474 26057 0 00:58 ? 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
> root 26475 26057 0 00:58 ? 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
> root 26476 26057 0 00:58 ? 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
> root 26477 26057 0 00:58 ? 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
> root 26478 26057 0 00:58 ? 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
> root 26479 26057 0 00:58 ? 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
> root 26480 26057 0 00:58 ? 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
> root 26481 26057 0 00:58 ? 00:00:05
> /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 26484 26057 0 00:58 ? 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
> root 26486 26057 0 00:58 ? 00:00:01
> /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 26488 26057 0 00:58 ? 00:00:06
> /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 26489 26057 0 00:58 ? 00:00:18
> /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 26524 26057 0 00:58 ? 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
> root 26619 26057 0 00:58 ? 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
> root 19266 26057 0 09:46 ? 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
> root 19267 26057 0 09:46 ? 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
> root 14435 8536 0 10:41 pts/30 00:00:00 grep java
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
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@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
root 26058 26057 0 00:57 ? 00:00:11
/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 26059 26057 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
root 26060 26057 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
root 26061 26057 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
root 26062 26057 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
root 26063 26057 0 00:57 ? 00:00:05
/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 26067 26057 0 00:57 ? 00:00:02
/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 26080 26057 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
root 26121 26057 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
root 26125 26057 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
root 26132 26057 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
root 26138 26057 0 00:57 ? 00:00:05
/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 26413 26057 0 00:58 ? 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
root 26471 26057 0 00:58 ? 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
root 26472 26057 0 00:58 ? 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
root 26473 26057 0 00:58 ? 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
root 26474 26057 0 00:58 ? 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
root 26475 26057 0 00:58 ? 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
root 26476 26057 0 00:58 ? 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
root 26477 26057 0 00:58 ? 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
root 26478 26057 0 00:58 ? 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
root 26479 26057 0 00:58 ? 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
root 26480 26057 0 00:58 ? 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
root 26481 26057 0 00:58 ? 00:00:05
/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 26484 26057 0 00:58 ? 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
root 26486 26057 0 00:58 ? 00:00:01
/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 26488 26057 0 00:58 ? 00:00:06
/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 26489 26057 0 00:58 ? 00:00:18
/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 26524 26057 0 00:58 ? 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
root 26619 26057 0 00:58 ? 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
root 19266 26057 0 09:46 ? 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
root 19267 26057 0 09:46 ? 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
root 14435 8536 0 10:41 pts/30 00:00:00 grep java
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
solprovider@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.
Remember that by default cocoon builds all blocks. You can turn off
other blocks that you are not using. Some blocks can create more java
threads.
>(Please do not say to reinstall Lenya. I've customized everything.)
>
>
***************************************************************************************
Please remember to do a full backup of your installation before starting
to replace or remove no necesary jars.
***************************************************************************************
Well, another option is build your customized cocoon and just replace
the jars as needed. Also change as needed the WEB-INF dir your cofing
files as cocoon.xconf and web.xml between others. This is enough. ;-)
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by so...@gmail.com.
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? Rebuild Cocoon with less? What exactly is
needed, and why didn't local.build.properties work properly?
(Please do not say to reinstall Lenya. I've customized everything.)
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Antonio Gallardo <ag...@agssa.net>.
Hi:
I had used lenya in all the Fedora distros (included the current version
4). It works good. Some hints:
1. Check your cocoon build. While building Don't include blocks you are
not using:
**************** FROM THE STARTUP CONSOLE ***********************
ERROR [main] (ClassUtils.java:193) - Class
org.apache.cocoon.faces.samples.components.components.MapComponent not
found
java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.MapComponent
***********************************************************************
Are you using cocoon block faces? If not, feel free to don't include it
in the cocoon build
2. Fedora Core 3 (and above) include GNU java. To be sure wich version
are u using run: java -version.
Check the second point under "Additional installation information":
http://wiki.apache.org/cocoon/Installing
3. Run ps ax | grep java to see how many times you are running jetty.
Hope this helps.
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
> something is broken with your build
>
>> environment is lenya 1.2.3 , cocoon 2.1.7 and jdk 1_4_2_08
>>
>> Has anyone else got experience of fedora and jetty
>>
>> Is this normal ????
>
> no
>
> this is the output from solaris 10 (lenya.zones.apache.org) from just now,
> running a jetty each for 1.2.4 and 1.4alpha1 :
>
> UID PID VSZ TIME COMMAND
> 100 18446 214476 01:07:59 /usr/j2se/bin/java -Xms32M -Xmx512M -cp
> ./tools/loader -Djava.endorsed.dirs=./
> 100 18435 175872 26:41 /usr/j2se/bin/java -Xms32M -Xmx512M -cp
> ./tools/loader -Djava.endorsed.dirs=./
>
Thanks for the reply,
I've attached the start up log from jetty any helpwopuldbe appreciated (I'm
picking through the coocoon dist but having little luck
-------------------- Loading --------------------
Processing repository: ./tools/jetty/lib
Adding jar: ./tools/jetty/lib/jetty-4.2.23.jar
Adding jar: ./tools/jetty/lib/servlet-2.3.jar
Processing repository: ./build/lenya/webapp/WEB-INF/lib/endorsed
-------------------- Executing -----------------
Main Class: org.mortbay.jetty.Server
20:05:15.841 EVENT Checking Resource aliases
20:05:16.796 EVENT Starting Jetty/4.2.23
20:05:18.315 EVENT Started WebApplicationContext[/,./build/lenya/webapp]
INFO [main] (FacesConfigurator.java:195) - Reading standard config
net/sourceforge/myfaces/resource/standard-faces-config.xml
INFO [main] (FacesConfigurator.java:362) - Reading config
jar:file:/tmp/myfaces40226.jar!/META-INF/faces-config.xml
INFO [main] (FacesConfigurator.java:362) - Reading config
jar:file:/tmp/myfaces40227.jar!/META-INF/faces-config.xml
INFO [main] (FacesConfigurator.java:411) - Reading config
/WEB-INF/faces-config.xml
ERROR [main] (ClassUtils.java:193) - Class
org.apache.cocoon.faces.samples.components.components.MapComponent not found
java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.MapComponent
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
at
net.sourceforge.myfaces.application.ApplicationImpl.addComponent(ApplicationImpl.java:280)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:479)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
ERROR [main] (ApplicationImpl.java:286) - Component class
org.apache.cocoon.faces.samples.components.components.MapComponent not found
javax.faces.FacesException: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.MapComponent
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:194)
at
net.sourceforge.myfaces.application.ApplicationImpl.addComponent(ApplicationImpl.java:280)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:479)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.MapComponent
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
... 15 more
ERROR [main] (ClassUtils.java:193) - Class
org.apache.cocoon.faces.samples.components.components.AreaComponent not
found
java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.AreaComponent
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
at
net.sourceforge.myfaces.application.ApplicationImpl.addComponent(ApplicationImpl.java:280)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:479)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
ERROR [main] (ApplicationImpl.java:286) - Component class
org.apache.cocoon.faces.samples.components.components.AreaComponent not
found
javax.faces.FacesException: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.AreaComponent
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:194)
at
net.sourceforge.myfaces.application.ApplicationImpl.addComponent(ApplicationImpl.java:280)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:479)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.components.AreaComponent
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
... 15 more
ERROR [main] (ClassUtils.java:193) - Class
org.apache.cocoon.faces.samples.carstore.CreditCardConverter not found
java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.carstore.CreditCardConverter
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
at
net.sourceforge.myfaces.application.ApplicationImpl.addConverter(ApplicationImpl.java:306)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:486)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
ERROR [main] (ApplicationImpl.java:312) - Converter class
org.apache.cocoon.faces.samples.carstore.CreditCardConverter not found
javax.faces.FacesException: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.carstore.CreditCardConverter
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:194)
at
net.sourceforge.myfaces.application.ApplicationImpl.addConverter(ApplicationImpl.java:306)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:486)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.carstore.CreditCardConverter
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
... 15 more
ERROR [main] (ClassUtils.java:193) - Class
org.apache.cocoon.faces.samples.carstore.FormatValidator not found
java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.carstore.FormatValidator
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
at
net.sourceforge.myfaces.application.ApplicationImpl.addValidator(ApplicationImpl.java:356)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:507)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
ERROR [main] (ApplicationImpl.java:362) - Validator class
org.apache.cocoon.faces.samples.carstore.FormatValidator not found
javax.faces.FacesException: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.carstore.FormatValidator
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:194)
at
net.sourceforge.myfaces.application.ApplicationImpl.addValidator(ApplicationImpl.java:356)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:507)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:184)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.carstore.FormatValidator
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
... 15 more
ERROR [main] (ClassUtils.java:193) - Class
org.apache.cocoon.faces.samples.components.renderkit.AreaRenderer not found
java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.renderkit.AreaRenderer
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
at net.sourceforge.myfaces.util.ClassUtils.newInstance(ClassUtils.java:316)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:607)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:185)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
ERROR [main] (StartupServletContextListener.java:116) - Error initializing
ServletContext
javax.faces.FacesException: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.renderkit.AreaRenderer
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:194)
at net.sourceforge.myfaces.util.ClassUtils.newInstance(ClassUtils.java:316)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:607)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:185)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.renderkit.AreaRenderer
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
... 15 more
javax.faces.FacesException: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.renderkit.AreaRenderer
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:194)
at net.sourceforge.myfaces.util.ClassUtils.newInstance(ClassUtils.java:316)
at
net.sourceforge.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:607)
at
net.sourceforge.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:185)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:102)
at
net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:85)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:448)
at org.mortbay.http.HttpServer.start(HttpServer.java:663)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException:
org.apache.cocoon.faces.samples.components.renderkit.AreaRenderer
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at net.sourceforge.myfaces.util.ClassUtils.classForName(ClassUtils.java:171)
at
net.sourceforge.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:189)
... 15 more
INFO [main] (StartupServletContextListener.java:119) - ServletContext
'/src/apache-lenya-1.2.3-src/build/lenya/webapp' initialized.
20:05:49.800 WARN!! Delete existing temp dir /tmp/Jetty__8888__ for
WebApplicationContext[/,./build/lenya/webapp]
trying to register database
trying to register database
20:06:43.402 EVENT Started SocketListener on 0.0.0.0:8888
20:06:43.403 EVENT Started org.mortbay.jetty.Server@ab95e6
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: jetty and fedora dist
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Lee Carroll wrote:
> Hello all,
>
> Due to our isp going bust and effectively "disappearing" from the planet
> this week we've migrated out tomcat redhat 9 lenya instalation
> to a new host provider. We are now running with jetty on fedora (core 3).
>
> While we've now got the default pub up and running I'm concerned all is
> not well. The performance is average to say the least, and running
> jetty spawns a host of java process. See below (All the stopped procs
> where spawned by nohup ./lenya.sh &)
>
> The jetty start up sequence reports errors with what look like sample
> cocoon classes and take an age to register databases (2 minutes >)
something is broken with your build
> environment is lenya 1.2.3 , cocoon 2.1.7 and jdk 1_4_2_08
>
> Has anyone else got experience of fedora and jetty
>
> Is this normal ????
no
this is the output from solaris 10 (lenya.zones.apache.org) from just
now, running a jetty each for 1.2.4 and 1.4alpha1 :
UID PID VSZ TIME COMMAND
100 18446 214476 01:07:59 /usr/j2se/bin/java -Xms32M -Xmx512M -cp
./tools/loader -Djava.endorsed.dirs=./
100 18435 175872 26:41 /usr/j2se/bin/java -Xms32M -Xmx512M -cp
./tools/loader -Djava.endorsed.dirs=./
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
jetty and fedora dist
Posted by Lee Carroll <le...@aol.com>.
Hello all,
Due to our isp going bust and effectively "disappearing" from the planet
this week we've migrated out tomcat redhat 9 lenya instalation
to a new host provider. We are now running with jetty on fedora (core 3).
While we've now got the default pub up and running I'm concerned all is not
well. The performance is average to say the least, and running
jetty spawns a host of java process. See below (All the stopped procs where
spawned by nohup ./lenya.sh &)
The jetty start up sequence reports errors with what look like sample cocoon
classes and take an age to register databases (2 minutes >)
environment is lenya 1.2.3 , cocoon 2.1.7 and jdk 1_4_2_08
Has anyone else got experience of fedora and jetty
Is this normal ????
2386 root 11 0 2156 992 856 T 0.0 0.4 0:00.00 lenya.sh
2389 root 11 0 714m 91m 21m T 0.0 35.6 0:23.59 java
2395 root 11 0 714m 91m 21m S 0.0 35.6 0:00.00 java
2396 root 11 0 714m 91m 21m T 0.0 35.6 0:03.20 java
2398 root 11 0 714m 91m 21m T 0.0 35.6 0:00.01 java
2399 root 11 0 714m 91m 21m T 0.0 35.6 0:00.04 java
2400 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
2401 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
2402 root 11 0 714m 91m 21m T 0.0 35.6 0:04.05 java
2410 root 10 0 714m 91m 21m T 0.0 35.6 0:00.06 java
2498 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
2942 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
3006 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
3168 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
3244 root 12 0 6968 2332 1768 S 0.0 0.9 0:00.16 sshd
3255 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
3261 root 11 0 714m 91m 21m T 0.0 35.6 0:00.03 java
3361 root 11 0 714m 91m 21m T 0.0 35.6 0:00.00 java
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: Building Lenya 1.4 under Eclipse with Java 1.5
Posted by Ron Wheeler <rw...@artifact-software.com>.
I have updated the wiki with what I know.
Ron
Gregor J. Rothfuss wrote:
> Ron Wheeler wrote:
>
>> After all my fumbling around, you probably will find it hard to
>> believe that I am staring at a Jetty delivered "Welcome to Lenya"
>> screen on 127.0.0.1:8888.
>
>
> cool!
>
>> To get Lenya to build and run to this point under Java 1.5 using
>> Eclipse, I had to do the following things that are not in the Howto
>
>
> can you add these to the wiki? you need to create an account to have
> edit privileges, which you get by filling out
>
> http://wiki.apache.org/lenya/UserPreferences
>
>> There were warnings about depricated functions during the build.
>
>
> these are there to remind the developers that they have to clean up.
> in this case, it is the creator api which will go away.
>
>> I hope that someone will look into the deprecated function(it seems
>> to be just one) and the jetty configuration file errors.
>> It is hard to have confidence in your own installation if software
>> issues warnings.
>
>
> the 1.4 branch is under development, and has the warnings cranked up
> for a reason. if you were to turn on deprecation warnings in 1.2,
> you'd see tons :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: Building Lenya 1.4 under Eclipse with Java 1.5
Posted by Ron Wheeler <rw...@artifact-software.com>.
Trying to build for Tomcat.
I get an error about not being able to delete
... /WEB-INF/cocoon.xconf.ant_patch
in webapp-build.xml.
I got around this by commenting out the delete
<antcall target="copy-cocoon.xconf"/>
<!-- <delete file="${build.webapp}/WEB-INF/cocoon.xconf.ant_patch"/> -->
Any one have any idea why this file can not be deleted. I can only guess
that it is still in use by some ant task that has not quite finished
releasing all its files.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: Building Lenya 1.4 under Eclipse with Java 1.5
Posted by Ron Wheeler <rw...@artifact-software.com>.
I will make the changes to the wiki for the Eclipse.
The shell install under 1.5 probably should be checked by someone who
actually uses the shell install procedure.
Still working on Tomcat. There are a ton of files to move :-) . I have
set up the endorsed libraries for xlan but just get a blank page. I
probably did not move all ofthe lenya files properly.
Ron
Gregor J. Rothfuss wrote:
> Ron Wheeler wrote:
>
>> After all my fumbling around, you probably will find it hard to
>> believe that I am staring at a Jetty delivered "Welcome to Lenya"
>> screen on 127.0.0.1:8888.
>
>
> cool!
>
>> To get Lenya to build and run to this point under Java 1.5 using
>> Eclipse, I had to do the following things that are not in the Howto
>
>
> can you add these to the wiki? you need to create an account to have
> edit privileges, which you get by filling out
>
> http://wiki.apache.org/lenya/UserPreferences
>
>> There were warnings about depricated functions during the build.
>
>
> these are there to remind the developers that they have to clean up.
> in this case, it is the creator api which will go away.
>
>> I hope that someone will look into the deprecated function(it seems
>> to be just one) and the jetty configuration file errors.
>> It is hard to have confidence in your own installation if software
>> issues warnings.
>
>
> the 1.4 branch is under development, and has the warnings cranked up
> for a reason. if you were to turn on deprecation warnings in 1.2,
> you'd see tons :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: Building Lenya 1.4 under Eclipse with Java 1.5
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Ron Wheeler wrote:
> After all my fumbling around, you probably will find it hard to believe
> that I am staring at a Jetty delivered "Welcome to Lenya" screen on
> 127.0.0.1:8888.
cool!
> To get Lenya to build and run to this point under Java 1.5 using
> Eclipse, I had to do the following things that are not in the Howto
can you add these to the wiki? you need to create an account to have
edit privileges, which you get by filling out
http://wiki.apache.org/lenya/UserPreferences
> There were warnings about depricated functions during the build.
these are there to remind the developers that they have to clean up. in
this case, it is the creator api which will go away.
> I hope that someone will look into the deprecated function(it seems to
> be just one) and the jetty configuration file errors.
> It is hard to have confidence in your own installation if software
> issues warnings.
the 1.4 branch is under development, and has the warnings cranked up for
a reason. if you were to turn on deprecation warnings in 1.2, you'd see
tons :)
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org