Hot answers tagged

28

Inside the Service tag change: <Connector port="8080" protocol="HTTP/1.1" ... to: <Connector address="127.0.0.1" port="8080" protocol="HTTP/1.1" ... For more information: http://tomcat.apache.org/tomcat-6.0-doc/config/http.html


19

Ok I finally solved it. I was directed to try this and Henk's solution. Neither of which seemed to work with the remote virtual server. I'm guessing the fact that because I'm on a shared kernel space so the provider prevents this. In any case I added: JAVA_OPTS= $JAVA_OPTS -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses to the catalina.sh ...


18

A neat trick is to run the command "lsof -p PID" where PID is the process id of your tomcat server. This command will give you a list of all files opened by the process, including the log file. See Wikipedia page.


13

We've been dealing with this issue too. It looks like Amazon found the root cause and corrected it. Here is the info they gave me. Hi, I am pasting below an explanation of what was causing this issue. Good news is that this has been fixed very recently by our engineering team. To get fix, all you'll have to do is STOP/START the Windows Server ...


12

Many suggested updating catalina.sh startup script. Yes, that solution would work, but catalina.sh script is not meant to be customized/updated. All changes should go into the customization script instead, i.e. setenv.sh. NOTE: TOMCAT_HOME/bin/setenv.sh doesn't exist by default, you need to create it. Check the catalina.sh script and you will see the ...


11

ProxyPass / http://www.abc.com:8080/myApp/ ProxyPassReverse / http://www.abc.com:8080/myApp/ Read more about mod_proxy


11

Don't touch the init script. Instead, edit the /etc/default/tomcat6 file and comment out the line enabling remote debugging there: # To enable remote debugging uncomment the following line. # You will then be able to use a java debugger on port 8000. JAVA_OPTS="${JAVA_OPTS} -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n"


11

Taken from this page add "digest" attribute on your element in server.xml with a hash algorithm as value (possible values are for example md5, sha-1 or sha-256, where the latter is strongly recommended). Run $CATALINE_HOME/bin/digest.sh -a <YOUR_HASH_ALGORITHM> <YOUR_PASSWORD> You will get an output in the following form ...


8

By default check /var/log/tomcat6/catalina.out or something like that and check logging properties in /usr/share/tomcat6/conf/logging.properties usually /usr/share/tomcat6/conf/ is symbolic link to /etc/tomcat6/


7

share my experiences,hope it helps step1: enable tomcat plugins sudo ln -s /usr/share/munin/plugins/tomcat_access /etc/munin/plugins/tomcat_access sudo ln -s /usr/share/munin/plugins/tomcat_jvm /etc/munin/plugins/tomcat_jvm sudo ln -s /usr/share/munin/plugins/tomcat_threads /etc/munin/plugins/tomcat_threads sudo ln -s /usr/share/munin/plugins/tomcat_volume ...


5

By the look of the error the Tomcat native launcher does not find the rt.jar file in your JRE install. Make sure that: the JVM is correctly installed; the JRE_HOME variable points to it.


5

It looks way too "procedural," IMO. You have to think in a "declarative" way. I would personally just create .rpm's or .deb's from those tarballs, and specify another repo to use so all you would have to do is something like this: class tomcat { Package { "tomcat": ensure => installed, } File { "/etc/init.d/tomcat": source => ...


5

I don't have enough reputation to add a comment to @Michael's answer above, so I'm adding as an answer - First, it's a great answer! However, when you mention manually running and checking using "/etc/munin/plugins/tomcat_jvm," this doesn't pick up the environment variables from /etc/munin/plugin-conf.d/munin-node (i.e. user/password), so it fails. The ...


4

Very late to this discussion, but it appears that the 03catalina.policy file in both tomcat5.5 & tomcat6 doesn't actually permit writing to logfiles. The simplest solution is to change the JULI permissions to: // These permissions apply to JULI grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" { permission java.security.AllPermission; }; ...


4

Ok first thing: Do you really need to use a Java Security Policy? The simplest solution by far is to disable this in tomcat's startup script: in /etc/init.d/tomcat6 replace TOMCAT6_SECURITY=yes with TOMCAT6_SECURITY=no Assuming you must use the security manager, and you must match an existing installation, I would suggest un-installing ...


4

I've seen this problem a few times with Tomcat. A couple of things that might help: Give it some time to make sure the process really isn't shutting down; the Tomcat shutdown script tries to do a clean shutdown, and that can take a while if the Tomcat server had a large number of threads open when you called the shutdown script. If it takes more than 5 ...


4

The first location you should take a look at is catalina.out, it will tell you what might be wrong. If you can't make it works with multicast, just try static membership (I think it will simpler). Below is my config: Put the <Cluster node inside the <Host element: <Engine name="Catalina" defaultHost="localhost" jvmRoute="tomcat1"> ...


4

How do I update for 3 web servers? Do the same as when doing with 2 nodes. On the deployment node, add one more member in StaticMembershipInterceptor: <Member className="org.apache.catalina.tribes.membership.StaticMember" port="4002" securePort="-1" host="192.168.5.208" ...


4

I would use at least an m1.small or better an m1.large Instance. The micro-instance really is for development only, because the 613MB may soon not be enough even with zero users. Besides that, you will most likely see a lot of CPU steal time and your Server will not react some time after you had a small cpu peak. That is very annoying. I would try to get ...


4

I've recently seen this problem as well and it appears to be isolated to a change made in the 32-bit Oracle JVM between Java 6 and 7. On Linux, running the 32-bit Java 7 VM with strace shows the following system call when ServerSocket.accept() is invoked without having set SO_TIMEOUT: 32369 poll([{fd=5, events=POLLIN|POLLERR}], 1, 4294967295 <unfinished ...


4

Problem The problem with the standard Tomcat shutdown script is that it is simply not tough enough. When you are using your distro's service scripts to stop Tomcat you'll eventually simply be calling Tomcat's own shutdown script. CentOS is no different in this respect. For this reason you need to be familiar with what Tomcat's shutdown script can do for you ...


4

Tomcat always returns status code 400 Because the webapps directory is empty: # ls -l /usr/share/tomcat6/webapps/ total 0 https://issues.apache.org/bugzilla/show_bug.cgi?id=50734 Either create a dummy ROOT context to get a 404 status: # mkdir /usr/share/tomcat6/webapps/ROOT # ls -l /usr/share/tomcat6/webapps/ total 4 drwxr-xr-x 2 root root 4096 ...


3

You have to tell the Connector in the server.xml file, that you want to use it on every port, not only on 127.0.0.1 by changing the address attribute's value to 0.0.0.0 <Connector port="8080" protocol="HTTP/1.1" maxHttpHeaderSize="65536" connectionTimeout="20000" redirectPort="8443" address="0.0.0.0" /> ...


3

For future visitors: I had a similar problem on a Linux server and none of the "solutions" I've found helped. Finally, I found that I just had firewall settings that blocked that port.


3

Have you actually enabled Tomcat to listen on the eth0 port, rather than just the localhost port. If you can just access it via the localhost (even when you type in the IP addresses it still goes to the local host) but not externally, this is normally the case. <Host name="www.example.com" appBase="webapps" unpackWARs="true" autoDeploy="true" ...


3

You are trying to install a compat library for a different version of the JDK than you have install from Sun. You are trying to install compat-1.6.0.03 which would match up to JDK 1.6.0_03. Your java version is 1.6.0_18. You can get 1.6.0_03 here It looks like they haven't updated the compat libraries since U3 (1.6.0_03) This gem is a little hidden in ...


3

I went around in circles on this for a while then had a DOH! moment when I realized the defaut tomcat-users.xml file has the sample list of users commented out with XML comments!


3

If you're using the standard packages, I believe they send it to syslog. You can check the /etc/init.d/tomcat6 file and look to see where -outfile and -errfile are set to. If it's SYSLOG then it's going to syslog, otherwise it's a filename. The reason for this is because if it's set to a filename, it's impossible to rotate the logs as they're always kept ...



Only top voted, non community-wiki answers of a minimum length are eligible