PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=764
*** shadow/764 Thu Sep 6 17:53:50 2001
--- shadow/764.tmp.3151 Sat Sep 8 15:38:36 2001
***************
*** 2,9 ****
| java.lang.StackOverflowError |
+----------------------------------------------------------------------------+
| Bug #: 764 Product: Regexp |
! | Status: NEW Version: unspecified |
! | Resolution: Platform: PC |
| Severity: Critical OS/Version: Windows NT/2K |
| Priority: High Component: Other |
+----------------------------------------------------------------------------+
--- 2,9 ----
| java.lang.StackOverflowError |
+----------------------------------------------------------------------------+
| Bug #: 764 Product: Regexp |
! | Status: RESOLVED Version: unspecified |
! | Resolution: WONTFIX Platform: PC |
| Severity: Critical OS/Version: Windows NT/2K |
| Priority: High Component: Other |
+----------------------------------------------------------------------------+
***************
*** 436,438 ****
--- 436,452 ----
when running the same code against the same data in Sybase Jaguar on Solaris
2.7. Some tests scenarios work on both 2000 and Solaris while others never
work on Solaris but always work on 2000.
+
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-09-08 15:38 -------
+ The regular expression matcher is recursive so the more work it has to do the
+ larger the stack required.
+
+ Possible solutions to this problem (for the user):
+ 1) Tune the regular expression esp removing alternations where possible.
+ 2) Give the JVM more stack space.
+ 3) Use smaller data sets.
+
+ There may be ways of optimising the matcher to no use so much stack space but
+ that requires major refactoring.
+
