Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 4. Known Issues

This chapter contains a description of known issues in JBoss Enterprise Web Server 2.0. Where available, these issues include workarounds.

4.1. General Known Issues
Copiar enlace

The following is a list of known issues in JBoss Enterprise Web Server 2:
JBPAPP-10084 - IPv6 :: address slowing down Tomcat6/7 on MS Windows
When an IPv6 address is used to start Tomcat 6 or 7 on Windows (for example <Connector port="8080" protocol="HTTP/1.1" address="::" />) and results in a significantly slower shutdown process when the user shuts down Tomcat. During the shutdown process, the catalina.log file logs a warning for this shutdown: 
WARNING: Acceptor thread [http-0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-Acceptor-0] failed to unlock. Forcing hard socket shutdown
Copy to Clipboard Toggle word wrap
JBPAPP-3628 - /host-manager application doesn't persist newly created virtual hosts
When a virtual host is created using the /host-manager/html application, all actions work as expected, but the newly created host is not persistently added to the Tomcat configuration. Only the localhost is listed after server restart.
As a workaround for persistence issues, virtual hosting can be managed manually.
JBPAPP-10131 - mod_jk doesn't support IPv6
The version of mod_jk included with JBoss Enterprise Web Server 2 does not support IPv6. This is an upstream bug.
JBPAPP-10112 - mod_cluster: advertising doesn't work in mixed IPv4/IPv6 setting
When using JBoss Enterprise Web Server with Red Hat Enterprise Linux 5 and 6, advertising using mod_cluster fails when IPv6 is used by itself and when a mixed protocol setting (IPv4 and IPv6) is used. The following error message displays in the error_log: 
[error] (22)Invalid argument: mod_advertise: ma_group_join apr_mcast_hops failed
[error] (22)Invalid argument: mod_advertise: multicast join failed for ff01::1:25533.
Copy to Clipboard Toggle word wrap
This occurs due to an old version of the apr library available in Red Hat Enterprise Linux 6. As a workaround, use RHN to get the package apr-devel-1.3.9-5.el6_2 or newer, which fixes this problem. Users without access to RHN cannot access the apr package version that fixes this problem
JBPAPP-10235 - Tomcat[6,7]: Start with security manager fails on RHEL with jdk-ibm16,ibm17
When using JBoss Enterprise Web Server with Red Hat Enterprise Linux with either the IBM JDK 1.6 or 1.7, the startup.sh -security command does not start tomcat (6 or 7) as expected and produces exceptions in the logs.
JBPAPP-10280 - Jsvc doesn't work with ibm jdk
Attempting to start jsvc on JBoss Enterprise Web Server using Red Hat Enterprise Linux 5 or 6 with the IBM JDK 1.6 or 1.7 fails. Specifically the failure occurs when jsvc is started using a command similar to the following: 
/opt/ews/workspace/jboss-ews-2.0/extras/jsvc   -showversion -cp /opt/ews/workspace/jboss-ews-2.0/tomcat6/bin/bootstrap.jar  -outfile /opt/ews/workspace/jboss-ews-2.0/tomcat6/logs/catalina.out -errfile /opt/ews/workspace/jboss-ews-2.0/tomcat6/logs/catalina.err -pidfile /opt/ews/workspace/jboss-ews-2.0/tomcat6/tomcat6.pid   -user hudson  -Dcatalina.home=/opt/ews/workspace/jboss-ews-2.0/tomcat6 -Djava.io.tmpdir=/opt/ews/workspace/jboss-ews-2.0/tomcat6/temp -jvm server org.apache.catalina.startup.Bootstrap
Copy to Clipboard Toggle word wrap
In the error file (specified by the -errfile option in the command), the following error appears: 
Invalid JVM name specified server
Cannot locate JVM library file
Service exit with a return value of 1
Copy to Clipboard Toggle word wrap
JBPAPP-9704 - Mod_jk: recover_time is not properly used
The recover_time value is only applied correctly once (the first time). The problem manifests when recover_time is set to a value greater than 60 seconds and is greater than the value of worker.maintain. After the first recover attempt passes and the worker errors back out to its global error state, the worker will be placed in recovery mode again on the next invocation of the worker.maintain method.
JBPAPP-9814 - Tomcat7: daemon.sh startup error
When using JBoss Enterprise Web Server with Red Hat Enterprise Linux, starting tomcat7 as a jsvc service using the daemon.sh script fails and displays the following error: 
/opt/jboss-ews-2.0/share/tomcat7/bin/daemon.sh[186]: /opt/jboss-ews-2.0/share/tomcat7/bin/jsvc: not found [No such file or directory]
Copy to Clipboard Toggle word wrap
As a workaround for this issue, copy jsvc from jboss-ews-2.0/sbin/jsvc to jboss-ews-2.0/share/tomcat7/bin.
JBPAPP-9703 - JK status manager - mass nodes handling works strange
Attempts to manage multiple nodes using the status manager URL such as the following does not work correctly: 
cmd=update&mime=prop&w=router&att=vwa&val0=1&val1=1
Copy to Clipboard Toggle word wrap
As a workaround for this problem, use the status manager's web interface instead.
JBPAPP-10316 - hibernate-dist.zip contains different hibernate-release-4.1.3.Final-redhat-1/lib/required/ant-antlr.jar
The ant-antlr.jar file, while packaged and shipped in the ZIP installation files, is not supported in JBoss Enterprise Web Server 2.0.
JBPAPP-10311 - jaspter-jdt.jar
The file jaspter-jdt.jar is packaged in JBoss Enterprise Web Server's Tomcat 7 library for Windows and Solaris and Red Hat Enterprise Linux 6 ZIP installation files. Additionally, in the Red Hat Enterprise Linux 5 ZIP files, the file is included in both the Tomcat 6 and 7 libraries. jaspter-jdt.jar should be called jasper-jdt.jar but the spelling error does not affect its function in JBoss Enterprise Web Server.
JBPAPP-10315 - Tomcat6 el-api.jar is linked to Tomcat7 version
In JBoss Enterprise Web Server, both alternatives/el_api and tomcat%{name}-el-api-%{version}.jar point to a common target within the tomcat libraries in /usr/share/java. As a result, the alternatives package points to the EL API library in /usr/share/java as does the link from /usr/share/tomcat${version}/lib.
Tomcat%{version} installs el_api in alternatives using the same name: el_api. Therefore, either can overwrite the other without the user knowing it. As a result, alternatives/el_api users may receive a version of the el_api that is different from the one they expect.
This does not affect the el-api library used by tomcat%{version}, but does affect users of alternatives/el_api.
JBPAPP-10334 - Problem with manager, host-manager in Tomcat6 installed from EWS2.0 RPMs
When JBoss Enterprise Web Server 2.0 is installed using RPMs in Red Hat Enterprise Linux 5 or 6 and Tomcat 6 is started, deployment of the manager and host-manager fail with a Permission denied error for the manager.xml and host-manager.xml files. This occurs because the parent directory of these files (/etc/tomcat6/Catalina/localhost) is owned by the user root instead of the expected user tomcat.
A workaround for this issue is to modify permissions for the Catalina directory as follows: 
# cd /etc/tomcat6; chmod -R tomcat Catalina
Copy to Clipboard Toggle word wrap
After successfully changing the permissions for the directory, run the command service tomcat6 start to run Tomcat 6.
JBPAPP-9958 - Tomcat6/7 doesn't allow character ':' in several properties (server.xml)
JBoss Enterprise Web Server's version of Tomcat6/7 does not allow the character : in server.xml for hostname specifications. Normally, the character is used as a delimiter for IPv6 addresses.
JBPAPP-10321 - mod_cluster returns "Bad Gateway" HTTP ErrorCode 502 with https
mod_cluster returns a HTTP error 502 (Bad Gateway) after a period of inactivity if only HTTPS connector is enabled for balancer-worker communication. Httpd tries to re-use a connection that has already been closed already. SSL handshake fails and HTTP error is triggered.
As a workaround, either allow AJP connector on all workers or set maxKeepAliveRequests="1" in server.xml, set smax to 0 in mod_cluster worker configuration, set SetEnv proxy-nokeepalive 1 and SetEnv proxy-initial-not-pooled 1 in your httpd configuration.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat