9 Jul 23:18
Re: jetty and fedora dist
Antonio Gallardo <agallardo <at> agssa.net>
2005-07-09 21:18:56 GMT
2005-07-09 21:18:56 GMT
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" > <agallardo <at> agssa.net> > To: <user <at> 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 <at> lenya.apache.org >>> For additional commands, e-mail: user-help <at> lenya.apache.org >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe <at> lenya.apache.org >> For additional commands, e-mail: user-help <at> lenya.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe <at> lenya.apache.org > For additional commands, e-mail: user-help <at> lenya.apache.org
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"
> <agallardo <at> agssa.net>
> To: <user <at> 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.
RSS Feed