Capturing Standard Out in Windows
I'm running Tomcat under Windows XP, and I want to redirect theTomcat standard out to a file. I tried editing catalina.bat using ' logfile.txt' to redirect it, but the java command doesn't seem to support this. Is there another way to do this? Thanks, Cory Cory Isaacson President CTO Compuflex International (818) 884-1168 [EMAIL PROTECTED] www.compuflex.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Resend: Page Load Problem in Stand-alone Mode
When running Tomcat in stand-alone mode, if I successively request pages in two different frames, the second page often does not display. I get a Server not found error in the browser. For example, to keep pages in multiple frames in synch I submit one frame based on the JavaScript ONLOAD event of the other, so the second pages is requested immediately after the first. Using the Coyote connector, this works fine so long as both pages are JSP. If one page is JSP and the other HTML, the HTML will display using Coyote, after about a 10 second delay (with both JSPs there is no delay). Using the regular default connector, I almost always get the server not found error. I tried this same code in WebSphere 4.x, and it works fine with JSP and an HTML page without delay or a problem. Because it works in WebSphere and to some degree with Coyote, I wonder if its just not a configuration problem. Here are the relevant sections from the server.xml file: Service name=Tomcat-Standalone !-- Define a non-SSL HTTP/1.1 Connector on port 8000 -- Connector className=org.apache.catalina.connector.http.HttpConnector port=8000 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8043 acceptCount=10 debug=0 connectionTimeout=6/ !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8081 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2/ Thanks in advance for any help on this. Cory Cory Isaacson President CTO Compuflex International (818) 884-1168 [EMAIL PROTECTED] www.compuflex.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Page Load Problem in Stand-alone Mode
When running Tomcat in stand-alone mode, if I successively request pages in two different frames, the second page often does not display. I get a Server not found error in the browser. For example, to keep pages in multiple frames in synch I submit one frame based on the JavaScript ONLOAD event of the other, so the second pages is requested immediately after the first. Using the Coyote connector, this works fine so long as both pages are JSP. If one page is JSP and the other HTML, the HTML will display using Coyote, after about a 10 second delay (with both JSPs there is no delay). Using the regular default connector, I almost always get the server not found error. I tried this same code in WebSphere 4.x, and it works fine with JSP and an HTML page without delay or a problem. Because it works in WebSphere and to some degree with Coyote, I wonder if its just not a configuration problem. Here are the relevant sections from the server.xml file: Service name=Tomcat-Standalone !-- Define a non-SSL HTTP/1.1 Connector on port 8000 -- Connector className=org.apache.catalina.connector.http.HttpConnector port=8000 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8043 acceptCount=10 debug=0 connectionTimeout=6/ !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8081 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2/ Thanks in advance for any help on this. Cory Cory Isaacson President CTO Compuflex International (818) 884-1168 [EMAIL PROTECTED] www.compuflex.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Page Load Problem in Stand-alone Mode
When running Tomcat in stand-alone mode, if I successively request pages in two different frames, the second page often does not display. I get a Server not found error in the browser. For example, to keep pages in multiple frames in synch I submit one frame based on the JavaScript ONLOAD event of the other, so the second pages is requested immediately after the first. Using the Coyote connector, this works fine so long as both pages are JSP. If one page is JSP and the other HTML, the HTML will display using Coyote, after about a 10 second delay (with both JSPs there is no delay). Using the regular default connector, I almost always get the server not found error. I tried this same code in WebSphere 4.x, and it works fine with JSP and an HTML page without delay or a problem. Because it works in WebSphere and to some degree with Coyote, I wonder if its just not a configuration problem. Here are the relevant sections from the server.xml file: Service name=Tomcat-Standalone !-- Define a non-SSL HTTP/1.1 Connector on port 8000 -- Connector className=org.apache.catalina.connector.http.HttpConnector port=8000 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8043 acceptCount=10 debug=0 connectionTimeout=6/ !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8081 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2/ Thanks in advance for any help on this. Cory Cory Isaacson President CTO Compuflex International (818) 884-1168 [EMAIL PROTECTED] www.compuflex.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
