N�o sei se voc� j� viu a lista de problemas com rela��o ao linux, se voc� j�
olhou
ignore...
Installation Notes
JavaTM 2 SDK, Standard Edition
Version 1.3.1
Linux
Japanese
System Requirements
This version of the Java 2 SDK is supported on Intel Pentium platforms running the
Linux kernel v 2.2.12 and glibc v2.1.2-11 or later. A minimum of 32 megabytes RAM are
required. Recommended 48 megabytes of RAM, 16-bit color mode, KDE and KWM window
managers used in conjunction with displays set to local hosts.
Check your version of glibc using the following command:
ls /lib/libc-*
You should have about 75 megabytes of free disk space before attempting to install
the Java 2 SDK software. If you also install the separate documentation download
bundle, you need an additional 125 megabytes of free disk space.
The officially supported Linux platform for J2SDK 1.3.1 is RedHat Linux 6.2, and most
testing of J2SDK 1.3.1 for Linux has been conducted on that operating system.
However, J2SDK 1.3.1 has undergone limited testing on other Linux operating systems.
The following table shows the Linux platforms, by locale, on which Sun has tested
this release to at least a limited extent. See below for information about Known
Problems on various Linux operating systems.
Locale Linux platform tested
English Red Hat Linux 6.1
Red Hat Linux 6.2
Red Hat Linux 7.1
Caldera OpenLinux 2.4
Mandrake Linux 7.1
Turbo Linux Workstation 6.0
SuSe Linux 6.4
German Red Hat Linux 6.2
Japanese Red Hat Linux 6.2J
Red Hat Linux 6.2J Second Edition
Simplified Chinese Turbo Linux Workstation 6.0
Known Problems
RedHat Linux 6.2 is the officially supported Linux platform for J2SDK 1.3.1. Limited
testing has been done on other Linux operating systems, and the following are known
problems on the non-supported platforms.
* Behavior in comformance with the API specification is not guaranteed while
running as superuser on any version of Linux whose kernel was compiled with the
CONFIG_IP_TRANSPARENT_PROXY option. The default kernel shipped with the RedHat 6.2
distribution is compiled with this option. To avoid incompatibilities associated with
this problem, either do not use the Java platform while superuser or else upgrade to
a Linux operating system whose kernel was not compiled with the
CONFIG_IP_TRANSPARENT_PROXY option. Red Hat 7.1 ships with the version 2.4 kernel
which does not have this problem.
* If you use Red Hat Linux 7, we recommend version 7.1 rather than 7.0. Limited
testing has revealed problems when using J2SDK with Red Hat Linux 7.0, some of which
are described below.
* The newer glibc-2.2.x libraries cannot correctly handle initial thread stack
sizes larger than 6 MB. This can cause a segmentation fault on come Linux platforms
that use the newer libraries. Such platforms include Red Hat 7.0, Mandrake 8.0, SuSe
7.2, and Debian 2.2. The problem will not occur on Linux platforms that are using
glibc-2.1.x such as Red Hat 6.1 and 6.2. It will also not affect Red Hat 7.1 because
it uses a different thread stack layout. This problem is being tracked as bug 4466587.
Workaround - Use "ulimit -s 2048" in bash shell or "limit stacksize 2048" in
tcsh to limit the initial thread stack to 2 MB.
* When System.exit(int) is invoked on Red Hat 7.0, the program never exits with
a non-zero value. This problem is apparently due to a bug in the exit function in
libc.so library. To avoid this problem, use the supported Red Hat release, version
6.2, or, if you want to use Red Hat 7, use version 7.1 rather than 7.0.
* On RedHat Linux 7.0, if you want to use the Classic VM rather than one of the
Java HotSpot VMs in J2SDK 1.3.1, you must download and install glibc-2.2-9.i386.rpm
file available at http://www.redhat.com/support/errata/RHBA-2000-079.html. Do not
install the i686 files available on that same web page, as those will prevent proper
functioning of the Java HotSpot VMs in J2SDK 1.3.1.
* If you use RedHat Linux 7 Server, you must manually install
compat-libstdc++-6.21-2.9.0.0.i386.rpm to prevent "error while loading shared
libraries" when using the Java HotSpot VMs. This file is located in the /RedHat/RPMS
directory on the RedHat Linux 7 CD-ROM. You may also obtain a copy of this file from
http://rpmfind.net. To install the file, use this command:
rpm --install compat-libstdc++-6.21-2.9.0.0.i386.rpm
It is not necessary to manually install compat-libstdc++-6.21-2.9.0.0.i386.rpm
if you are using RedHat Linux 7 Workstation.
* When using RedHat Linux versions other than 6.1, the font.properties file may
fail to display some Symbol/Dingbats characters properly on some AWT components. To
correct this, use this revised font.properties file to replace the one at
<JAVA_HOME>/jre/lib/.
* Caldera OpenLinux uses version 2.1.2-3 of glibc. Because that version is not
greater than or equal to 2.1.2-11, the Java 2 SDK's rpm installer will fail during
its dependency check. We recommend that you obtain an updated version of the glibc
library available from Caldera at the following locations:
ftp.caldera.com:/pub/updates/eDesktop/2.4/current/RPMS
or
ftp.caldera.com:/pub/updates/eServer/2.3/current/RPMS
* Some users have reported that to get J2SE SDK 1.3.1 to work on Debian 2.2, they had
to install libstdc++2.9-glibc2.1 from the oldlibs archive.
Leila wrote:
> Em um dos casos, trato um resultset grande e a partir deste gero um pdf,
> mesmo fazendo um close no resultset e no statement e liberando a classe
> que gera o pdf, mesmo assim a memoria nao eh liberada.
> Mas mesmo nos casos mais simples, onde um formulario eh aberto e sao
> carregados alguns javabeans, ha aumento sem liberacao posterior.
> Respondendo ao Claudio, a vers�o do linux � 2.2.16.
> Aquela opcao "-server" alguem sabe onde eu coloco?
> Obrigado pela atencao.
> Leila
>
> ----- Original Message -----
> *From:* HERLANI JUNIOR <mailto:[EMAIL PROTECTED]>
> *To:* [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> *Sent:* Monday, July 22, 2002 6:28 PM
> *Subject:* Re: [enterprise-list] JSP + tomcat - problemas de
> ocupa��o de mem�ria
>
> Leila,
>
> Vc tentou isolar as chamadas dos JSP/Servlet/Beans ?
> N�o existe nenhum erro de l�gica q possa estar utilizando
> Vectors/Arrays ou um resultset que retorna muitos registros ???
>
> Ql SO ?
>
> HJUNIO
>
> ----- Original Message -----
> *From:* Leila <mailto:[EMAIL PROTECTED]>
> *To:* [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> *Sent:* Monday, July 22, 2002 04:57 PM
> *Subject:* [enterprise-list] JSP + tomcat - problemas de
> ocupa��o de mem�ria
>
> Pessoal,
>
> Desenvolvi uma aplica��o que utiliza servlets e jsp.
>
> Vers�es:
> *Tomcat 4.0.3 *
> **JAVA SDK 1.3.1_03-b03**
>
>
> Depois de um determinado tempo de uso da aplica��o, o Tomcat
> morre. Monitorando o sistema, pude observar que ocorre uma
> ocupa��o crescente da mem�ria, que n�o � desalocada.
>
> Como est� estruturada a aplica��o: na subida do Tomcat,
> � inicializado um servlet que � respons�vel por tratar todas as
> solicita��es dos formul�rios da aplica��o. Estas solicita��es
> s�o associadas a uma classe respons�vel pela execu��o de uma
> determinada tarefa e apresenta��o do resultado em outras p�ginas
> jsp. Estas geralmente acessam javabeans criados na inicializa��o
> do servlet ou na execu��o da tarefa em quest�o.
>
> Executando o "top", no linux, observo que o size, relacionado a
> ocupa��o de mem�ria, aumenta a cada execu��o e n�o diminui mais.
> Algu�m j� passou por este problema?
>
> Agrade�o antecipadamente.
> Leila
>
---------------------------------------------------------------------
Para cancelar a subscri��o, envie mensagem para:
[EMAIL PROTECTED]
Para comandos adicionais, envie mensagem para: [EMAIL PROTECTED]
