Tag Info

Hot answers tagged

7

This is the logrotate software (that, as the name says, "rotate" logs) complaining about a non-existent user configured to rotate your tomcat logs. Try searching the /etc/logrotate.d/ directory for something like "tomcat" or "tomcat6" and remove the file if you find it, it's useless now that tomcat is not installed anymore.


6

It depends on what kill signal you are using: If you use TERM (the numeric equivalent is kill -15), theoretically you are letting the java process signal its children and exit in a correct way. If you use KILL (kill -9), you don't, and you left all sorts of temporary files, sockets, etc... behind. That said, tomcat has its own mechanism to shutdown ...


5

No difference This is what I have in my tomcat init : restart) $0 stop sleep 1 $0 start ;; It calls stop first then wait for a second and calls start . You may increase sleep value if it takes time for you.


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

You need to call cfn-init (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-init.html) inside the UserData property of the instance: "Resources": { "Tomcat": { "Type": "AWS::EC2::Instance", "Metadata": { "AWS::CloudFormation::Init": { "config": { "packages": { ...


4

This isn't too tricky, assuming both apps can access similar session data. But only if you can mess around with the code a bit. Since you're talking about different companies providing the software that second part might not be possible. Basically when a session is started with AppA the username/password is checked against some source (be it a database, ...


3

I don't think your 60k clients are the actual problem. You will more likely have problem with not enough file descriptors, but that should be easy to fix as part of OS configuration. Here's why connections will not be your problem. Each connection is characterised by its source ip address, source port, destination ip address and destination port. Inside the ...


3

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 ...


3

I was experiencing the same problem using Tomcat 7.0.35 with Java 1.7.0_10 (32bit) on a 64-bit Debian Linux. In my case updating and using the 64bit JDK solved this problem


3

Why don't you just let your netbeans build to your desired directory?


3

gd_bundle-g2-g1.crt: Go Daddy Certificate Bundles - G2 With Cross to G1, includes Root gdig2.crt: Go Daddy Secure Server Certificate (Intermediate Certificate) - G2 2b9918dccf2f1d.crt: Your certificate Source: https://certs.godaddy.com/anonymous/repository.pki


3

EPEL testing does include Tomcat 7 : http://pkgs.org/centos-6/epel-testing-i386/tomcat-7.0.33-3.el6.noarch.rpm.html


3

You can launch: ps -o nlwp PID (PID will be the pid of your process) nlwp = number of lightweight process


3

I found a working solution: sudo touch /etc/authbind/byport/80 sudo chmod 500 /etc/authbind/byport/80 sudo chown tomcat7 /etc/authbind/byport/80 http://stackoverflow.com/questions/23272666/tomcat7-bind-to-port-80-fails-in-ubuntu-14-04lts


3

You can do this with <Location /dev> RewriteEngine on RewriteRule ^/dev/(.*) /$1 ProxyPass / http://localhost:8080/ nocanon ProxyPassReverse / http://localhost:8080/ </Location> and so on. That will give you different proxies for the different URLs, and remove the leading /dev, /staging, or /prod from the URLs. But ...


3

PSK ciphers are not supported in the JSSE provider provided by Oracle (or any of the other JVM vendors as far as I am aware). You'll have to find a JSSE provider that supports PSK ciphers. That provider should include documentation on how to configure it. Note that while Oracle does list PSK ciphers in the Java standard names, that does not mean that they ...


3

Depending on the version of Tomcat 5 and Version 6 the SSLEnabled="true" might not work as it was added mid-release. To get past this you just need to edit the following: sslProtocols = TLS To: sslProtocols = "TLSv1,TLSv1.1,TLSv1.2" Seems strange but even though it says TLS, it contains the SSL 3. This fixed it on our Tomcat 5.5.20 and our Tomcat 6 ...


2

Yes, you can do this. If you are using Windows you can use the official documentation: http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html I would recommend downloading the service.bat file associated with your windows distribution. This answer covers how to do that: ...


2

In practice, simply apache2ctl graceful will gracefully restart apache process allowing it to load a new configuration Here for example, lets say you have in production www.v1 and dev in www.v2 <VirtualHost *:80> ServerName www.example.com DocumentRoot /var/www/vhosts/example.com/www.v1 [...] </VirtualHost> <VirtualHost ...


2

If you don't want autoDeploy feature, in production environments for instance, you may consider the following attributes in the conf/Catalina/localhost context file : autoDeploy="false" and deployXML="false" autoDeploy="false" may not work alone because application context.xml (in META-INF) can override server.xml settings of autoDeploy. The ...


2

If you're seeing this error, but you're in an environment where other webapps already exist, you can simply create a ROOT directory, then create a zero byte index.html inside of it. A 200 will be readily returned upon successful curl.


2

Above answer is correct. But you also should make sure that you have sucessfully installed CloudFormation helper scripts. Please follow to http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-helper-scripts-reference.html for installation details.


2

Add connectionTimeout and keepAliveTimeout to your AJP connector found in /etc/tomcat7/server.xml. <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" connectionTimeout="10000" keepAliveTimeout="10000" /> Info about the AJP connector at https://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html connectionTimeout = The number ...


2

Websockets requires tomcat 7.0.47 or 8, also be sure you have JRE 7 one more thing check that your ELB configured at TCP/SSL level instead of HTTP/HTTPS


2

The answer depends on where you have located the class file(s) used by your webapp. If you put a given class in the Tomcat Common class loader path of $CATALINA_HOME/lib it will be made available to all webapps. The same goes for its cached form. If you use the Tomcat web application class loader path of webapps/webapp/WEB-INF/classes and ...


2

RAM/CPU? Clustering? Load balancing? Only you can know. I've seen RAM occupation vary from a few megabytes to several hundreds, even for what seemed to be simple applications. A lot depends on what libraries you'll be loading. Same for CPU. There is no substiture for profiling a web application's performances. Start from a sample configuration, get some ...


2

I ran into this today. In my case the cause was a stale pid file. Tomcat started fine after doing a rm /var/run/tomcat6.pid.


2

Configuration management tools like puppet. chef, ansible etc are the tools of choice for the modern sysadmin.


2

Most Mongo drivers these days can handle multiple Mongos's in a connection string, the Java driver implemented this as of 2.9.0: https://jira.mongodb.org/browse/JAVA-381 It's only for failover, however, not load balancing. You normally do not need to load balance between Mongos's, the bottlenecks are typically on the backend shards in a well optimized ...


2

As a practical matter you won't need more MongoDB router instances until you have a LOT of servers (each doing a LOT of traffic). Assuming you get to that point though the problem is really a lot easier to solve than you think it is. Expanding on what MrKurt said, what you would typically do is split your Tomcat servers into groups, and then configure ...



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