DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5887>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5887 Forte hangs, reports: The Tomcat Server is not running correctly with Struts-using apps Summary: Forte hangs, reports: The Tomcat Server is not running correctly with Struts-using apps Product: Struts Version: 1.0.1 Final Platform: PC URL: http://www.go-canes.com/fortestruts OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Whenever a web application that uses struts.jar is launched from within the Forte 3.1 IDE (includes 12/2001 jumbo fix), the internal Tomcat server hangs for almost exactly 40 seconds at the same point, reports that "The Tomcat Server is not running correctly", then seems to run fine from that point onward. My specific setup consisted of a virgin installation of the J2SE 1.4b3 SDK + Forte 3.0 (w/3.1 jumbo fix), running under Win2k(sp2) w/512mb. This behavior has been widely observed by others on the Forte newsgroups as also occuring with both J2SE 1.3 and J2EE 1.3, and with both Forte Community Edition and Forte Enterprise Edition. On the Forte newsgroup, one poster (Damian Frach) stated: Problem is caused by very long Tomcat output.If you are able to configure Struts framework, it will not produce so long output (part of this output is in the end of this mail), everythink should be ok. Unfortunately, he didn't clarify what he actually meant by that (recompile it with different settings? Alter one of the config files?) Although, strictly speaking, it's possible that the bug might lie with Forte itself, it's important to note that nearly EVERY message in the Forte newsgroup matching a query for the string "The Tomcat Server is not running correctly" has to do with Struts. In any case, it's hurting the adoption of Struts because Forte is quite good, quite popular, free for almost everyone, and something a developer isn't likely to give up for the sake of using Struts. I listed it as "Major" because, while it's possible to semi-live with a 40 second delay every time Tomcat gets restarted for a few compile-launch cycles, there's a limit to how many times one can put up with it before it simply becomes intolerable. If a bugfix is inappropriate, but Forte-using webapps can somehow be configured to avoid this problem (or Struts itself can be specially recompiled to avoid the issue), Forte should be classified as a servlet container in the Struts reference pages and the details should be listed there (in the case of recompiling, the instructions should be aimed at someone who's not afraid to do the usual "tar zxvf; perl Makefile.PL; make; make test; make install" type activities and capable of doing the equivalent with ant. Incidentally, when I ran the struts-example webapp, all of the tests seemed to pass EXCEPT Logic: Match tags. The relevant logfiles (Forte's own ide.log, Tomcat's jasper, servlet, and tc logs, and the stderr output from Tomcat) are available for perusal at http://www.go-canes.com/fortestruts. What I did: Installed the Forte 3/1.4b3 cobundle on a virgin computer and applied the December 3.1 jumbo fix. Unzipped struts-exercise.war into c:\java\struts_exercise Loaded Forte, and created a new project named "Struts Exercise" mounted c:\java\struts_exercise as a filesystem. Forte recognized it as a web module. right-clicked "index.jsp" and chose "execute". Tomcat launched, hung for 40 seconds, reported "The Tomcat Server is not running correctly", then proceeded to launch index.jsp in the web browser and (with the exception of the Match tags, which might be another bug entirely) seemed to work fine. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
