Tomcatx.x and vista
I'm trying to get tomcat to run on vista w/iis. I have jdk/jre1.6.0_06 and tomcat 6.0 installed. I start tomcat as a service manually using Administrative Tools from the Control Panel. In Firefox I enter http://localhost:8080/examples/index.html and what I get back is: The system cannot find the file specified. I also have isapi_redirect-1.2.27.dll allowed in ISAPI and CGI Restrictions in the IIS manager. I have also installed tomcat on Ubuntu 8.10 with apache 2.2/jdk/jre1.6.0_06/tomcat 6.0 installed with the same results. I have googled the web, read through the tomcat site, and searched the maillist archives finding similar questions but no solutions. I'm certain this can't be that difficult and I must be missing something but I don't know what. A look at the logs tomcat comes up and runs. It just doesn't seem to get the redirection. Any thoughts, ideas? - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Http]ServletResponseWrapper.getOutputStream()
Christopher Schultz schrieb am 12.11.2008 um 14:46:08 (-0500): Michael Ludwig wrote: IllegalStateException: getOutputStream() has already been called for this response But I haven't called getOutputStream() - I've called getWriter(). Yes, but your included resource probably called getOutputStream. Yes, this is happening. You should really override getOutputStream as well as getWriter in your HttpServletResponseWrapper. That's true. You have to, I think, in order to have your filter work in all situations. So how can I implement getOutputStream() to substitute a buffer? Does anyone have an implementation? How are you doing this with getWriter? With a StringWriter? Maybe you want to look at java.io.ByteArrayOutputStream. For getWriter(), I was using PrintWriter with CharArrayOutputStream. ByteArrayOutputStream as the most general stream implementation seems to be the right thing to look at. What you need to do is provide a unified buffer that /both/ calls can write to. If you use a ByteArrayOutputStream at the lowest level and then wrap that in an OutputStreamWriter for calls to getWriter(), you should be able to handle arbitrary use of your wrapper. This sounds very reasonable. I followed this road. Unfortunately, the included resource still is written elsewhere. Or maybe not flushed? Hope that helps, Yes, this has helped. Thanks! Anyway, what I would like to have is a trace of the method calls that are done by Tomcats's DefaultServlet. Is there a way to get one? Michael Ludwig - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-users.xml file becomes unusable
jakarta-tomcat-5.5.4-6 I don't have a copy of the changed file. Here is the original, passwords removed. As soon as we see this again I'll post the changed one. permission on the original file are 0600. owner is apache, group is an internal name. Thanks, Joe On Fri, Nov 14, 2008 at 4:53 PM, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Joe Bolin [mailto:[EMAIL PROTECTED] Subject: tomcat-users.xml file becomes unusable We are seeing a sporadic issue where the tomcat-users.xml file changes in some way. The file command repots the type as 'data' rather than XML. What version of Tomcat are you using? What are the contents of the changed file? Can you post it here (obfuscate the passwords, of course)? Tomcat does rewrite the tomcat-users.xml file during startup, unless you specify the readonly=true attribute for the UserDatabase Resource. However, I've never known it to rewrite it with anything but correct XML. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ?xml version='1.0' encoding='utf-8'? tomcat-users role rolename=tomcat/ role rolename=standard/ role rolename=manager/ role rolename=admin/ user username=mon password= roles=manager/ user username=tomcat password= roles=tomcat/ /tomcat-users - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debian + Apache 2.2 + Tomcat 5.5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Alexander Diedler wrote: Where I have to place my webapp and where I have to change some files to make my Application available onto the server? I have a Debian 4.05 with Apache 2.2.5 and Tomcat 5.5.20 from Debian .deb packages Drop the WAR file in /var/lib/tomcat5.5/webapps. It should deploy automatically. See /usr/share/doc/tomcat5.5/README.Debian for additional information. Also you may want/need to update to the Tomcat from Debian lenny (5.5.26-5 currently) since the packaging has improved a lot. Cheers, Marcus -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkfI7gACgkQXjXn6TzcAQnBDgCfX6k/0y15IAX8BEGtjlC0NF3z sAgAoMpz6SaXCA1s6iFQKakYpe7wNBQZ =1vKg -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat-users.xml file becomes unusable
From: Joe Bolin [mailto:[EMAIL PROTECTED] Subject: Re: tomcat-users.xml file becomes unusable jakarta-tomcat-5.5.4-6 That's not a real Tomcat, but rather a 3rd-party repackaged - and frequently broken - version. Try installing a proper one from tomcat.apache.org and see if the problem goes away. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
