[jboss-jira] [JBoss JIRA] Commented: (JBAS-6682) StringIndexOutOfBoundsException in JvmRouteValve

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459931#action_12459931 ] 

Brian Stansberry commented on JBAS-6682:
----------------------------------------

This happened when there was an existing session whose id included a jvmRoute that matches the host handling the request, but the request itself didn't specify any jvmRoute.

> StringIndexOutOfBoundsException in JvmRouteValve
> ------------------------------------------------
>
>                 Key: JBAS-6682
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6682
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-5.1.0.Beta1
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.1.0.CR1
>
>
> Saw this while testing mod_cluster:
> 2009-03-26 03:39:08,718 ERROR [org.apache.catalina.connector.CoyoteAdapter] (ajp-192.168.2.2-8009-5) An exception or error occurred in the container during the request processing
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> 	at java.lang.String.substring(String.java:1938)
> 	at org.jboss.web.tomcat.service.session.JvmRouteValve.handleJvmRoute(JvmRouteValve.java:192)
> 	at org.jboss.web.tomcat.service.session.JvmRouteValve.checkJvmRoute(JvmRouteValve.java:117)
> 	at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:84)
> 	at org.jboss.web.tomcat.service.session.LockingValve.invoke(LockingValve.java:62)
> 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
> 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> 	at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436)
> 	at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384)
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> 	at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira