Summary: | >=www-server/tomcat-6.0.30: IllegalStateException: No Java compiler available | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Max Nokhrin <mno2go> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://tomcat.apache.org/tomcat-6.0-doc/changelog.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 329937 | ||
Attachments: | ebuild with added ecj.jar |
Description
Max Nokhrin
2011-02-11 09:01:05 UTC
Created attachment 262115 [details]
ebuild with added ecj.jar
can you please try this ebuild? i tried to test it but i get weird behavior of tomcat here which does not make sense to me at all.
Thanks, I will test a little later tonight and report back. While doing some searching, it seems we don't need to use the ECJ approach. From http://apache.mirrors.tds.net/tomcat/tomcat-6/v6.0.30/RELEASE-NOTES Dependency Changes: =================== Tomcat 6.0 is designed to run on JSE 5.0 and later. In addition, Tomcat 6.0 uses the Eclipse JDT Java compiler for compiling JSP pages. This means you no longer need to have the complete Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment (JRE) is sufficient. The Eclipse JDT Java compiler is bundled with the binary Tomcat distributions. Tomcat can also be configured to use the compiler from the JDK to compile JSPs, or any other Java compiler supported by Apache Ant. As Gentoo requires JDK regardless, it may make sense to just set the JDK to be used for compiling JSPs. That patch works to the point where I can start tomcat and the JSPs build properly, no longer getting the IllegalStateException. However, when trying to start up tomcat through init.d: lastochka tomcat # /etc/init.d/tomcat-6 start * Caching service dependencies ... [ ok ] * Starting Tomcat ... [ !! ] lastochka maxitravel # /etc/init.d/tomcat-6 status * status: stopped While Tomcat is actually running properly. So, I cannot kill it through init.d, have to go through kill. How/where can I see the error that caused the init.d not to catch the start up properly? well, i have no idea where the output is written, but probably if ever logged, should go to system logger or /var/log/tomcat-6/catalina.out. you can also try to remove --background (and maybe even --stdout and --stderr) from ssd function in /etc/init.d/tomcat-6 to get the output directly on console. Neither system logger nor the catalina.out have anything. Probably because Tomcat actually starts correctly, and can compile JSPs just fine with this ebuild. Just the init.d system doesn't catch that it started yet... I'll dig around with the modifications, try to get some reason for that. i just committed tomcat-6.0.32-r1 which is the same as the ebuild attached. i tried starting tomcat as service and here it works fine. anyway, waiting for your results in case they are tomcat related and not some local issue. thanks, did you overwrite the 6.0.32, or did you commit 6.0.32-r1? after a sync just now, still only see .32 from before. nevermind, packages.gentoo.org not updated yet it seems and neither is my mirror. i've seen the -r1 in the changelog. i'll wait for it to propagate and then report back here. thanks again! y, takes some time till the commit goes through, anyway the ebuild is the same as the one attached here. i also removed the "old" tomcat-6.0.32 ebuild Removing --background and the --stdout and --stderr don't change anything. The script just hangs on "Starting tomcat" line, and Ctrl+C out of that kills tomcat. Here's a bit of the catalina.out that's relevant (I tried starting without the MaxiTravelWeb.war in the webapps dir, same results): Feb 13, 2011 6:44:11 PM org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.20. Feb 13, 2011 6:44:11 PM org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. Feb 13, 2011 6:44:11 PM org.apache.coyote.http11.Http11AprProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Feb 13, 2011 6:44:11 PM org.apache.coyote.ajp.AjpAprProtocol init INFO: Initializing Coyote AJP/1.3 on ajp-8009 Feb 13, 2011 6:44:11 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1203 ms Feb 13, 2011 6:44:11 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Feb 13, 2011 6:44:11 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.32 Feb 13, 2011 6:44:11 PM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor host-manager.xml Feb 13, 2011 6:44:12 PM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor manager.xml Feb 13, 2011 6:44:12 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive MaxiTravelWeb.war Requesting list of hotels. Hotels returned: 13683 Finished Loading! Feb 13, 2011 6:44:29 PM org.apache.coyote.http11.Http11AprProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Feb 13, 2011 6:44:29 PM org.apache.coyote.ajp.AjpAprProtocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 Feb 13, 2011 6:44:29 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 17643 ms The long start up is of course due to the MaxiTravelWeb.war app. It contacts a remote server on start up. The output from the init.d script is still: lastochka init.d # /etc/init.d/tomcat-6 start * Caching service dependencies ... [ ok ] * Starting Tomcat ... [ !! ] I'll post in forums, maybe someone else can find this behaviour. Posted on forum: http://forums.gentoo.org/viewtopic-t-864473-start-0-postdays-0-postorder-asc-highlight-.html the start bug is now handled in bug #326979 so closing this bug. thank you for help with fixing the original issue. Thanks Miroslav! |