Pid said on 7.7.2010 12:26: > On 07/07/2010 11:07, Tomislav Petrović wrote: >> Tomislav Petrović said on 30.6.2010 16:27: >>>>> Forgot to say: >>>>> Tomcat service is started with following parameters: >>>>> >>>>> JVM: have to check whether server or client, not sure at the moment. >>>> >>>> Server, one would hope. Did you find out the exact version? >>>> >>> >>> Yup JVM path for tomcat is ......\jdk1.6.0_18\jre\bin\server\jvm.dll, so >>> Java 6 update 18 server. >> >> Although initial excpetion and stacktrace (related to webapp reloading, >> actually checking that it should or should not be reloaded) went away with >> reloadable="false" workaround I now have similar problem. >> >> Please help since now machine is in (or near) production :(. >> >> New stacktrace in catalina logs looks like (and produces 404 errors): >> >> Jul 5, 2010 7:13:47 AM org.apache.catalina.connector.CoyoteAdapter service >> SEVERE: An exception or error occurred in the container during the request >> processing >> java.lang.StringIndexOutOfBoundsException: String index out of range: 115 >> at java.lang.String.substring(String.java:1934) >> at org.apache.catalina.util.RequestUtil.normalize(RequestUtil.java:131) >> at >> org.apache.naming.resources.FileDirContext.normalize(FileDirContext.java:771) >> at >> org.apache.naming.resources.FileDirContext.file(FileDirContext.java:811) >> at >> org.apache.naming.resources.FileDirContext.getAttributes(FileDirContext.java:429) >> at >> org.apache.naming.resources.BaseDirContext.getAttributes(BaseDirContext.java:747) >> at >> org.apache.naming.resources.ProxyDirContext.revalidate(ProxyDirContext.java:1501) >> at >> org.apache.naming.resources.ProxyDirContext.cacheLookup(ProxyDirContext.java:1457) >> at >> org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java:288) >> at >> org.apache.tomcat.util.http.mapper.Mapper.internalMapWrapper(Mapper.java:823) >> at >> org.apache.tomcat.util.http.mapper.Mapper.internalMap(Mapper.java:667) >> at org.apache.tomcat.util.http.mapper.Mapper.map(Mapper.java:557) >> at >> org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:462) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:296) >> at >> org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859) >> at >> org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579) >> at >> org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1555) >> at java.lang.Thread.run(Thread.java:619) >> >> Everything else is same as I posted before (config file, JVM versions, >> etc....) >> Any advice is appreciated.... > > I think the general feeling is that it's a JVM bug - but no-one can work > out what it is. I can't even work out how to get 115 characters out of > a normal file path. > > Can you move the installation from: > D:\Program Files\Apache Software Foundation\Tomcat 6.0 > > To: > D:\Tomcat60 > >
Don't know have to check with customer, but actual index varies in each occurrence of stack trace, sometimes it is even -1. In two days we had: 2x java.lang.StringIndexOutOfBoundsException: String index out of range: 131 1x java.lang.StringIndexOutOfBoundsException: String index out of range: 118 1x java.lang.StringIndexOutOfBoundsException: String index out of range: 106 4x java.lang.StringIndexOutOfBoundsException: String index out of range: -1 3x java.lang.StringIndexOutOfBoundsException: String index out of range: 127 2x java.lang.StringIndexOutOfBoundsException: String index out of range: 126 1x java.lang.StringIndexOutOfBoundsException: String index out of range: 123 Rest of stacktrace is identical in all occurences. In addition -- Tomy <t.petro...@inet.hr> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
