You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to run WAS (Web Application Server) on IKVM and set Tomcat to run on IKVM, it crashed with a StackOverflowException. So I tested it by removing the option parts created in the batch file used when running Tomcat one by one, and confirmed that it crashed with the exception when the '-Djava.protocol.handler.pkgs=org.apache.catalina.webresources' option was entered.
The comment for the option part is as follows.
rem Register custom URL handlers
rem Do this here so custom URL handles (specifically 'war:...') can be used in the security policy
It seems that a class inside the 'org.apache.catalina.webresources' package inside Tomcat is doing some work and causing a StackOverflowException. In the net472 version, it only displays the message 'Process is terminated due to StackOverflowException.' and dies, but in the net8.0 version, it shows a detailed call stack, so you can check where the exception occurs. The original Java made in C or C++ does not cause this exception. Is there a possibility that this issue will be resolved in a future version?
Also, when the WAS (Tomcat) starts and the first connection is made, it takes a long time to compile the JSP. Is there a possibility that this issue will be resolved?
The text was updated successfully, but these errors were encountered:
The net472 version only shows the message 'Process is terminated due to StackOverflowException.', so I attached the Stacktrace from running it on the net8.0 version.
After some checking, I confirmed that the Stack Overflow exception occurs unconditionally when trying to use the java.protocol.handler.pkgs property in IKVM, not when running Tomcat.
In a standard JVM, a StackOverflowError exception is raised only when you try to use a URL object with an illegal value in java.protocol.handler.pkgs, as shown below.
However, in IKVM, even if you put any value in the java.protocol.handler.pkgs property, it will throw a stack overflow exception before even executing the user code, as shown below.
Test in the screenshot below is a fictional class name that does not actually exist.
I think we need to check the part that uses the java.protocol.handler.pkgs property within the IKVM JVM.
I've run some tests and it appears that this isn't a problem with Tomcat, but rather a problem with itself. Should I close this issue and register a new one?
Thank you for creating a JVM that runs on .NET.
When I tried to run WAS (Web Application Server) on IKVM and set Tomcat to run on IKVM, it crashed with a StackOverflowException. So I tested it by removing the option parts created in the batch file used when running Tomcat one by one, and confirmed that it crashed with the exception when the '-Djava.protocol.handler.pkgs=org.apache.catalina.webresources' option was entered.
The comment for the option part is as follows.
rem Register custom URL handlers
rem Do this here so custom URL handles (specifically 'war:...') can be used in the security policy
It seems that a class inside the 'org.apache.catalina.webresources' package inside Tomcat is doing some work and causing a StackOverflowException. In the net472 version, it only displays the message 'Process is terminated due to StackOverflowException.' and dies, but in the net8.0 version, it shows a detailed call stack, so you can check where the exception occurs. The original Java made in C or C++ does not cause this exception. Is there a possibility that this issue will be resolved in a future version?
Also, when the WAS (Tomcat) starts and the first connection is made, it takes a long time to compile the JSP. Is there a possibility that this issue will be resolved?
The text was updated successfully, but these errors were encountered: