- Noticed only when running in debugger with breakpoint set for StackOverflowError. - The error is translated by Java's reflection mechanism to an InvocationTargetException, which is caught and silently ignored by IntrospectionUtils. - Connector.initialize() sets jkHome property on Http11NioProtocol. - Http11NioProtocol sets jkHome property on NioEndpoint. - NioEndpoint recursively invokes its own setProperty method via IntrospectionUtils.setProperty, causing the stack overflow. - Using embedded Tomcat. - Using Nio connector. Does not happen for standard connector. - Happens in 6.0.18 and 6.0.20; haven't tested with earlier versions.
Created attachment 24573 [details] Tomcat 6.0 patch
Works for me, thanks!
The patch has been applied to 6.0.x and will be included in 6.0.21 onwards.
Created attachment 25134 [details] Patch in other way We have this problem either. And unfortunately we use a JVM which generate a coredump while stack overflow. -- Java VM: Java HotSpot(TM) Server VM (11.0-b16 mixed mode solaris-sparc) I patch the tomcat source in other way
(In reply to comment #4) > Created an attachment (id=25134) [details] > Patch in other way > > We have this problem either. > > And unfortunately we use a JVM which generate a coredump while stack overflow. > -- Java VM: Java HotSpot(TM) Server VM (11.0-b16 mixed mode solaris-sparc) > > I patch the tomcat source in other way BTW, We found this issue in tomcat 6.0.16 SunOS xxxx 5.10 Generic_139555-08 sun4v sparc SUNW,SPARC-Enterprise-T5120