RE: Potential JRun 4 getPathInfo Migration Issue
Hi Ben, I have been trying to reproduce this behavior and have come to the following assumption - your TestServlet servlet mapping uses the url pattern /TestServlet. Am I correct? I set up a mapping for my SnoopServlet using url pattern /snoop and requested http://localhost:8100/snoop/more/path/info and see the same results that you do - 404. However, when I use the url pattern /snoop/* I get the servlet path= /snoop and path info=/more/path/info as expected. While this may differ from JRun 3.x it is in compliance with the Servlet 2.3 spec (and matches the RI's behavior) and is touched upon in the example below from the spec. Hope this helps, Tom Ruggles JRun QA Table SRV.1: Example Context Set Up ContextPath /catalog Servlet Mapping Pattern: /lawn/* Servlet: LawnServlet Servlet Mapping Pattern: /garden/* Servlet: GardenServlet Servlet Mapping Pattern: *.jsp Servlet: JSPServlet Table SRV.2: Observed Path Element Behavior Request Path Path Elements /catalog/lawn/index.html ContextPath: /catalog ServletPath: /lawn PathInfo: /index.html -Original Message- From: Ben Groeneveld [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 05, 2002 3:08 PM To: JRun-Talk Subject: Potential JRun 4 getPathInfo Migration Issue I am having trouble migrating a servlet that uses request.getPathInfo(). We use a URL like: http://127.0.0.1:8100/tJRun4/TestServlet/extraParams?misc=stuffmore=NotEnough I developed a little testcase which presents the above as follows on JRun 3.0: doGet logRequestParameters request.getPathInfo(): /extraParams logRequestParameters request.getQueryString(): misc=stuffmore=NotEnough logRequestParameters request.getPathTranslated(): C:\usr\local\jrun-3.0\servers\default\tJRun4\extraParams logRequestParameters request.getRequestURL(): /tJRun4/TestServlet/extraParams logRequestParameters request.getParameterValues(): misc:[stuff] logRequestParameters request.getParameterValues(): more:[NotEnough] On JRun 4 I just get in the log: error Requested resource /tJRun4/TestServlet/extraParams not found Anyone have a clue as to what's up or what we're doing wrong? Thanks, BenG. -- Ben Groeneveld Information Concepts, Inc., 115 N.W. Oregon, Suite 30, Bend, OR 97701 Mailto:[EMAIL PROTECTED], phone:541.388.3611, cell:208.520.6488 __ Get the JRun Web Application Construction Kit - the only book written specifically for JRun developers. http://www.amazon.com/exec/obidos/ASIN/0789726009/houseoffusion Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Re: Potential JRun 4 getPathInfo Migration Issue
Yes, our pattern was /TestServlet and changing it to /TestServlet/* resolves the issue. Thanks! BenG. Thomas Ruggles wrote: Hi Ben, I have been trying to reproduce this behavior and have come to the following assumption - your TestServlet servlet mapping uses the url pattern /TestServlet. Am I correct? I set up a mapping for my SnoopServlet using url pattern /snoop and requested http://localhost:8100/snoop/more/path/info and see the same results that you do - 404. However, when I use the url pattern /snoop/* I get the servlet path= /snoop and path info=/more/path/info as expected. While this may differ from JRun 3.x it is in compliance with the Servlet 2.3 spec (and matches the RI's behavior) and is touched upon in the example below from the spec. Hope this helps, Tom Ruggles JRun QA Table SRV.1: Example Context Set Up ContextPath /catalog Servlet Mapping Pattern: /lawn/* Servlet: LawnServlet Servlet Mapping Pattern: /garden/* Servlet: GardenServlet Servlet Mapping Pattern: *.jsp Servlet: JSPServlet Table SRV.2: Observed Path Element Behavior Request Path Path Elements /catalog/lawn/index.html ContextPath: /catalog ServletPath: /lawn PathInfo: /index.html -Original Message- From: Ben Groeneveld [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 05, 2002 3:08 PM To: JRun-Talk Subject: Potential JRun 4 getPathInfo Migration Issue I am having trouble migrating a servlet that uses request.getPathInfo(). We use a URL like: http://127.0.0.1:8100/tJRun4/TestServlet/extraParams?misc=stuffmore=NotEnough I developed a little testcase which presents the above as follows on JRun 3.0: doGet logRequestParameters request.getPathInfo(): /extraParams logRequestParameters request.getQueryString(): misc=stuffmore=NotEnough logRequestParameters request.getPathTranslated(): C:\usr\local\jrun-3.0\servers\default\tJRun4\extraParams logRequestParameters request.getRequestURL(): /tJRun4/TestServlet/extraParams logRequestParameters request.getParameterValues(): misc:[stuff] logRequestParameters request.getParameterValues(): more:[NotEnough] On JRun 4 I just get in the log: error Requested resource /tJRun4/TestServlet/extraParams not found Anyone have a clue as to what's up or what we're doing wrong? Thanks, BenG. -- Ben Groeneveld Information Concepts, Inc., 115 N.W. Oregon, Suite 30, Bend, OR 97701 Mailto:[EMAIL PROTECTED], phone:541.388.3611, cell:208.520.6488 __ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Logging in JRun4
Hi,
Another trouble while doing server migration from JRun3.1 to JRun4.0:
In 3.1, I used System.out.println() to dump debug information to myserver-out.log.
However after we migrated to JRun4.0, it did not automatically setup logs for
System.out message. According to TechNote 23128 - JRun 4.0 : Configuring the Error and
Out Log Files, I started myserver as:
Jrun -start myserver 1{Jrun.rootdir}/logs/myserver-out.log
2{Jrun.rootdir}/logs/myserver-error.log
I did see myserver-out.log and myserver-error.log created under the logs directory.
However when I used System.out.println()/System.err.println() in my jsp files, nothing
was printed out.
Do I need any other settings to direct System.out or System.err information to the
related log files?
Your help is greatly appreciated!
Yuying Zhang
__
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
JDBC Issue
I am trying to make sure that our application that is running on JRUN 3.1 can recover from any brief database connection losses, due to some network break down between the web server and the database server or the database server it self going down. As of now while the web application is running and I stop and restart the database server I get the following exception. [JRun][SQLServer JDBC Driver]System Exception: Connection reset by peer: socket write error. It is understandable if I get this error when the database server is down, but if the database server is up after a brief interruption I would like to recover from the error by reconnecting and executing the sql. I see the same exception in when the db server is down or after the db server comes back up after a brief stoppage. Any ideas or suggestions are welcomed. Thanks a lot in advance. __ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
