Hide Forgot
Description of problem: Tomcat 6 service doesn't work as expected Version-Release number of selected component (if applicable): --- [root@dhcp-10-30-23-232 ~]# rpm -q tomcat6 tomcat6-6.0.30-6.fc15.noarch [root@dhcp-10-30-23-232 ~]# java -version java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.1) (fedora-57.1.10.1.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) --- How reproducible: 100% Steps to Reproduce: After installation of tomcat, first of all i can't start it: --- [root@dhcp-10-30-23-232 ~]# service tomcat6 start Starting tomcat6: [ OK ] [root@dhcp-10-30-23-232 ~]# service tomcat6 status PID file exists, but process is not running [WARNING] tomcat6 lockfile exists but process is not running [FAILED] --- After i fix some permissions it starts OK: --- [root@dhcp-10-30-23-232 ~]# chmod go+x /etc/tomcat6 [root@dhcp-10-30-23-232 ~]# chmod go+x /var/log/tomcat6 [root@dhcp-10-30-23-232 ~]# service tomcat6 start Starting tomcat6: [ OK ] [root@dhcp-10-30-23-232 ~]# service tomcat6 status tomcat6 (pid 1263) is running... [ OK ] [root@dhcp-10-30-23-232 ~]# service tomcat6 status tomcat6 (pid 1263) is running... [ OK ] --- But i can't connect to it using browser and wget with Bad request error: --- [root@dhcp-10-30-23-232 ~]# LANG=C wget http://localhost:8080 --2011-06-02 15:27:30-- http://localhost:8080/ Resolving localhost... ::1, 127.0.0.1 Connecting to localhost|::1|:8080... connected. HTTP request sent, awaiting response... 400 Bad Request 2011-06-02 15:27:30 ERROR 400: Bad Request. --- Actual results: tomcat6 service is unusable Expected results: tomcat6 service should works as expected Please fix
my testing for -4.fc15 didn't show this problem. tomcat6-6.0.32-4.fc15 is in test on bodhi [root@nec-em11 ~]# rpm -q tomcat6 tomcat6-6.0.32-4.fc15.noarch [root@nec-em11 ~]# service tomcat6 start Starting tomcat6: [ OK ] [root@nec-em11 ~]# service tomcat6 status tomcat6 (pid 2813) is running...[ OK ] [root@nec-em11 ~]# java -version java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (fedora-58.1.10.2.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) [root@nec-em11 ~]# wget http://localhost:8080 --2011-07-05 13:38:01-- http://localhost:8080/ Resolving localhost... ::1, 127.0.0.1 Connecting to localhost|::1|:8080... connected. HTTP request sent, awaiting response... 200 OK Length: 7777 (7.6K) [text/html] Saving to: “index.html.1” 100%[======================================>] 7,777 --.-K/s in 0s 2011-07-05 13:38:01 (134 MB/s) - “index.html.1” saved [7777/7777]
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
this can't be reproduced in f18. changing state to closed:currentversion