このコンテンツは選択した言語では利用できません。
5. Known Issues
- BZ#822250 - Tomcat6 mod_cluster config file (JON)
- In JBoss Web Server, a mod_cluster config file error is displayed on the
Inventory Connectionsscreen even after configuring the file.This is a known issue in JBoss Web Server 3 and there is currently no workaround for this problem. - BZ#1201269 - Tomcat 7 datasources are not discovered if defined in server.xml file
- This release of JBoss Web Server carries a bug that prevents Tomcat 7 datasources from being discovered if they are defined in the
server.xmlfile.A workaround to this issue is to define the datasources in thecontext.xmlfile. - BZ#1025057 - SSLProxyMachineCertificateFile doesn't support PKCS#8 key format
- In JBoss Web Server, when a PKCS#8 key generated by OpenSSL is used, JBoss Web Server displays the following error and then terminates:
incomplete client cert configured for SSL proxy (missing or encrypted private key?)
The PKCS#8 format is not supported by mod_ssl, as mod_ssl uses different functions when loading the proxy key pair.This is a known issue in JBoss Web Server 3.0. As a workaround, convert from PKCS#8 to the raw PEM encoding of the RSA key and use "openssl pkcs8". - BZ#1086412 - SSLFIPS option does not operate the same as RHEL httpd
- In JBoss Web Server, the SSLFIPS option does not operate as expected.This is a known issue in JBoss Web Server 3 and there is currently no workaround for this problem.
- BZ#1100599 - Tomcat7 - catalina.out contains warning and errors (after shutdown)
- When using JBoss Web Server 3 on Microsoft Windows, starting and then stopping Tomcat7 results in warnings and errors being unexpectedly displayed after Tomcat7 has shut down.The web application
[/docs]initiates a thread named[SeedGenerator Thread]but does not stop the thread when it shuts down. As a result, the errors and warnings continue to appear after Tomcat7 shuts down.This is a known issue in JBoss Web Server 3 and there is currently no workaround for this problem. - BZ#1116863 - [rpm] hibernate extra source jars
- In JBoss Web Server 3.0, some source files are included in the Hibernate RPM distribution that are not present in the Hibernate ZIP distribution.This is a known issue and there is currently no workaround for this problem.
- JWS-204 - Solaris tomcat bin contains wrong commons-daemon.jar symlink
- On Solaris, if you try to use
./daemon.sh --tomcat-user your_user start, it will hit an incorrectly expanded symlink:commons-daemon.jar.../../java/commons-daemon-*.jar This error originates from the postinstall script’screatesymlink()lnfunction, as it does not expand the*increatesymlink "../../java/commons-daemon-*.jar" commons-daemon.jar.To workaround this issue, inJWS_HOME/share/tomcat<VERSION>/binrun:ln -sf ../../java/commons-daemon.jar commons-daemon.jar
This issue will be fixed in a future release. - JWS-191 - Catalina log: Not excluded JARs without Tag Library Descriptors
- When starting Tomcat 8, entries may be logged to
catalina.outsimilar to the following:21-Jul-2015 09:04:58.259 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 21-Jul-2015 09:04:58.530 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /opt/ews/workspace/jws-3.0/tomcat8/webapps/ROOT has finished in 3,857 ms 21-Jul-2015 09:04:58.532 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /opt/ews/workspace/jws-3.0/tomcat8/webapps/examples
This is occurring because the following JARs should be added tocatalina.propertiesastomcat.util.scan.StandardJarScanFilter.jarsToSkip.jboss-logging.jar mod_cluster-container-tomcat8.jar mod_cluster-core.jar mod_cluster-container-catalina-standalone.jar mod_cluster-container-spi.jar mod_cluster-container-catalina.jar
This issue is expected to be fixed in a future update. - JWS-190 - service tomcat{7|8} status may end with no info printed
- When starting Tomcat 7 or 8, if a particular pid file (e.g.
/var/run/${NAME}.pid) exists but the process has already exited, then there is no message displayed to the user.In this situation, it is expected that the user will be notified. This issue is expected to be fixed in a future release. - JWS-189 - tomcat init scripts should use variable CATALINA_PID
- In JBoss Web Server 3, the Tomcat 7 and Tomcat 8 init scripts use
"/var/run/${NAME}.pid"as the value for the Tomcat pid file. However, in the Tomcat configuration, the pid file is specified as a complete path, usingCATALINA_PID. For example,CATALINA_PID="/var/run/tomcat8.pid".The value used in the Tomcat init scripts may create problems, as depending on the configuration, the actual pid file might not be placed where configuration itself says it should.This issue will be fixed in a future release. - JWS-186 - /host-manager application doesn't persist newly created virtual hosts
- In Tomcat 7 or Tocmat 8, if you create a new virtual host using
/host-manager/html, the newly created host does not persist between Tomcat restarts.The cause of this issue is currently under investigation. - JWS-185 - IPv6 :: address slowing down Tomcat6/7 on MS Windows
- When an IPv6 address is used to start Tomcat 7 on Microsoft Windows (for example,
<Connector port="8080" protocol="HTTP/1.1" address="::" />), this results in a significantly slowed down shutdown process when Tomcat is shut down. During the shutdown process, thecatalina.logfile contains a warning similar to the following:WARNING: Acceptor thread [http-0%3A0%3A0%3A0%3A0%3A0%3A0%3A0-8080-Acceptor-0] failed to unlock. Forcing hard socket shutdown
The cause of this issue is currently under investigation. - JWS-157 - JON Tomcat7: Web apps unreachable when Tomcat Connector configured
- When using JBoss ON to manage Tomcat 7 in JBoss Web Server, web applications may begin to throw exceptions and incorrect redirects after attempting to configure a Tomcat 7 HTTP connecter through JBoss ON.The cause of this issue is currently under investigation.
- JWS-156 - replace init scripts for tomcat7 and 8 on RHEL7 by systemd units
- On Red Hat Enterprise Linux 7, the JBoss Web Server Tomcat 7 and 8 init scripts still use SysV units, which run in systemd compatibility mode.In a future version of JBoss Web Server, these SysV init scripts will be replaced with systemd ones.
- JWS-154 - tomcat7 and tomcat8 init scripts are in wrong directory in rpms
- In an RPM install of JBoss Web Server, the init scripts for Tomcat 7 and 8 are installed in the wrong directory.The init scripts are installed to
/etc/init.d/tomcat<VERSION>, when it they should be installed to/etc/rc.d/init.d/tomcat<VERSION>.This issue is expected to be fixed in a future release. - JWS-132 - JON Tomcat: NullPointerException when Tomcat Web Application (WAR) config change
- When monitoring JBoss Web Server using JBoss ON, a
NullPointerExceptionsimilar to below may be thrown when a Tomcat web application has its configuration changed.java.lang.NullPointerException at org.rhq.plugins.jmx.MBeanResourceComponent.updateResourceConfiguration(MBeanResourceComponent.java:532) at org.jboss.on.plugins.tomcat.TomcatWarComponent.updateResourceConfiguration(TomcatWarComponent.java:950) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocation.call(ResourceContainer.java:759) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)
The cause of this issue is currently under investigation. - JWS-128 - Tomcat sessionsList.jsp does not work
- This release of JBoss Web Server contains an issue with
sessionsList.jspin Tomcat 7 and 8. An error similar to the following is thrown during compile:An error occurred at line: [18] in the generated java file: [/usr/share/tomcat7/work/Catalina/localhost/manager/org/apache/jsp/WEB_002dINF/jsp/sessionsList_jsp.java] Only a type can be imported. org.apache.catalina.ha.session.DeltaSession resolves to a package An error occurred at line: 109 in the jsp file: /WEB-INF/jsp/sessionsList.jsp DeltaSession cannot be resolved to a type
This error occurs becausesessionsList.jsphas a dependency on theDeltaSessionHA class.This issue is expected to be resolved in a future release of JBoss Web Server. - JWS-126 - JON Httpd: Windows: Httpd server can't be stopped
- Using JBoss ON to manage an Apache HTTP Server instance running on Microsoft Windows, it is not possible to stop the Apache HTTP Server using JBoss ON’s stop scheduling.The cause of this issue is currently under investigation.
- JWS-125 - JON Httpd: Update configuration of An IfModule updates conf files and apache can't be restarted
- When using JBoss ON to update the configuration of a JBoss Web Server Apache HTTP Server
IfModule, after the change is made the Apache HTTP Server cannot be stopped, restarted, or started.The cause of this issue is under investigation. - JWS-124 - JON Httpd: IfModule can't be created
- Using JBoss ON to create a JBoss Web Server Apache HTTP Server
IfModuledoes not work.The cause of this issue is under investigation. - JWS-123 - JON Httpd: Directory inventory empty
- When using JBoss ON to monitor JBoss Web Server’s Apache HTTP Server, the directories for an Apache Virtual Host do not contain any child resources their
Inventorytab.The cause of this issue is currently under investigation. - JWS-122 - JON Httpd: Creation of Directory does not create directory in FS + dir. duplicites shown in JON
- Using JBoss ON with JBoss Web Server and attempting to create a directory in the child resources of an Apache Virtual Host, the directory is not created in file system of the agent. Additionally, some directories are shown twice in JON web interface.The cause of this issue is under investigation.
- JWS-121 - JON Httpd: does not support httpd installed from RPM
- The JBoss ON Apache HTTP Server plugin currently does not support a JBoss Web Server 3 Apache HTTP Server that has been installed using RPMs.This issue is expected to be fixed in a future release.
- JWS-120 - JON Httpd: start failed after configuration new Listen port in JON
- Using JBoss ON with JBoss Web Server and adding a new
Listenport to an Apache HTTP Server may result in the Apache HTTP Server not being able to restart.This seems to happen because theListendirective is being added at the end ofhttpd.confeven though it may already be defined inconf.d/ssl.conf.This issue is expected to be fixed in a future release. - JWS-109 - hibernate c3p0 mchange-commons-java raises error on IBMJDK
- The Hibername c3p0
mchange-commons-javaJAR raises errors similar to the following when used with an IBM JDK.java.lang.ClassNotFoundException: org.slf4j.ILoggerFactory at org.apache.catalina.loader.WebappClassLoader.loadClass(Unknown Source) at org.apache.catalina.loader.WebappClassLoader.loadClass(Unknown Source) at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:199) at com.mchange.v2.log.MLog.findByClassnames(MLog.java:143) at com.mchange.v2.log.MLog.refreshConfig(MLog.java:73) at com.mchange.v2.log.MLog.<clinit>(MLog.java:51)
The cause of this issue is under investigation. - JWS-99 - httpd apxs utility needs EWS_HOME var. set
- To be able to properly run the Apache Extension Tool (apxs) with Apache HTTP Server in JBoss Web Server 3, the
EWS_HOMEenvironment variable needs to be set to the JBoss Web Server installation directory. - JWS-87 - JWS: VirtualHosts share pointer to mod_proxy configuration, results in: CreateBalancers behave the same with option 0 or 2
- The directive
CreateBalancerswith the option0or2creates the balancers on all Apache HTTP Server virtual hosts.When using option2, it is expected that the balancers should be created on the main server only, and not on the virtual hosts.The cause of this issue is under investigation, and is expected to be resolved in a future release. - JWS-86 - Upgrading Tomcat plugin, metric names not updated
- When upgrading a RHQ 4.5 installation to 4.6, the Tomcat plugin may not be properly updated.In this situation the following exception is thrown:
java.lang.IllegalArgumentException: The property [name] marked as required in the configuration definition of [Tomcat Connector] has no attribute 'default'
The cause of this issue is currently under investigation. - JWS-85 - Problem to start tomcat with a user whose group has a name different to the user
- The Tomcat init scripts are not designed to be run by a user with a name that does not correspond to an existing group.In this situation, the Tomcat processes are not able to be stopped with the provided scripts, as well as other operational issues regarding the
CATALINA_PIDfile.To workaround this issue, please follow the configuration instructions in the JBoss Web Server 3 Installation Guide, and create atomcatuser that belongs to atomcatgroup. - JWS-84 - Tomcat8: Backport Add option to disable log rotation in FileHandler.
- Tomcat 8 in JBoss Web Server 3 does not currently have the ability to disable log rotation in 'FileHandler`.This issue will be fixed in a future update.
- JWS-68 - Windows: Tomcat7/8 - catalina.out contains warning and errors (after shutdown)
- When shutting down Tomcat on Microsoft Windows, the
catalina.outlog may contain warning and errors similar to the following:SEVERE: The web application [/docs] appears to have started a thread named [SeedGenerator Thread] but has failed to stop it. This is very likely to create a memory leak.
Tomcat does not use aSeedGeneratorthread, so this log may be erroneous.The cause of this issue is under investigation. - JWS-67 - Windows: Tomcat8 WebDAV move operation fails
- Attempting to execute a
MOVEoperation in Tomcat 8 on Microsoft Windows returns a HTTP 500 error. An error similar to the following is added to theaccess_log:127.0.0.1 - tomcat [16/Apr/2015:02:58:43 -0700] "MOVE /webdavapp/webdav/hello.txt HTTP/1.1" 500 1040
This issue is currently under investigation. - JWS-63 - Tomcat mod_cluster integration does not allow one to choose a connector
- Configuring mod_cluster to use
ws://withEnableWsTunnel(mod_proxy_wstunnel) requires Tomcat to use ahttpconnector, and does not allow you to use anajpconnector.At the moment, Tomcat ignores this option.This issue is expected to be fixed in a future update. - JWS-61 - Tomcat7/8 breaks session stickyness with ;jsessionid= followed by /
- If a
/is included after ajsessionidin a URL, this may result in Tomcat 7 and Tomcat 8 failing to maintain the client session. In this situation, Tomcat fails to understand thejsessionidstring and creates a newjsessionid.This issue is currently under investigation.
