tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11882] New: - Variable may not have been initialized
Date Wed, 21 Aug 2002 04:09:30 GMT
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=11882>.
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=11882

Variable may not have been initialized

           Summary: Variable may not have been initialized
           Product: Tomcat 4
           Version: 4.0 Final
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: josephkiok@ggold.net


I am using the following setup:

- Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
- jakarta-tomcat-4.0.4
- Solaris 8
- Apache 1.3.20 via mod_jk

>From time to time, when I modify my JSP file, I get an error

"Variable xxx may not have been initialized."

- Specifically, it happens on StringBuffer variables, and the "out" stream.
- It usually happens right after I modify the JSP code, (so could it be a
compiler issue)?
- Right after I get the error, I restart Tomcat, and everything works okay.

I tried it on both binaries, the LE and the FULL edition of Tomcat.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message