We are developing JSP-based application and use JRun Pro as the JSP/Servlet
engine on top of IIS 4.0.
We are experiencing a number of significant problems with it.
- Although we have identically configured several development machines, JRun
behaves differently on some. It does not recompile JSP files when they
change. The funny thing is it sometimes does not recompile them even after
3 JRun shutdown/restarts!!! It works as expected on some other machines.
Any help on this? Has anyone experienced this problem?
- Browsing through our JSP pages often results in a JVM crash (a bad one!).
We get "javaw.exe - Application Error. ...Instruction referenced memory
...." This happens randomly, could happen on any page, but it does crash
almost every time. We try/catch all code that might throw exceptions. It
seems that JRun is at fault. Any suggestions? Anyone had similar behavior?
- We use HttpSession for session management. Although JRun's documentation
states it supports URL rewriting, using following code and disabling cookies
resulted in creation of new session every time and HTML source reveals that
Session ID was not appended to URL.
<%= response.encodeUrl("menu.jsp") %>
Any help on this?
I would appreciate your comments and suggestions if you experienced any of
these problems.
Thanks.
____________________________________
Ken Borinsky
Developer, Internet Division
CompInfo, Inc.
Voice: (212)353-7518
Fax: (212)353-7600
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
