Tag Info

Hot answers tagged

9

Well, after quick testing over some random servers holding Server: Apache-Coyotte header signature in their HTTP replies, it seems you are right as sending get / HTTP/1.1\r\nHost: <target_IP>\r\n\r\n with a simple netcat connection worked every time while a 400 HTTP code should have been received. For instance : $ { echo -en "get / HTTP/1.1\r\nHost: ...


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


6

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


6

Regardless of Tomcat's incorrect behaviour with regards to the HTTP standard, you should be using a whitelist to allow specific methods rather than a blacklist. For example, the following whitelist will block all methods except the case-sensitive GET and HEAD. <security-constraint> <web-resource-collection> ...


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

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

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


4

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


3

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


3

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


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

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

Here is the cause: Jul 23 01:19:31 myservername kernel: [<ffffffff81122df2>] ? oom_kill_process+0x82/0x2a0 There is not enough ram. oom_kill_process is the kernel function which kills some processes if there is no ram enough. Something seems leaking, or you have very few memory. Is your swap really enabled and working? (cat /proc/swaps). Extension: ...


3

It seems that there is no more memory available to use on your system. Please check if you have swap memory on your system with below command free -m output should be as below if you have swap enabled. total used free shared buffers cached Mem: 1876 1798 77 0 119 1440 -/+ ...


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

The server computer's OS firewall is probably sufficient to do what you're looking for. You don't mention the OS so I can't say anything specific. On a Linux machine you'd be throwing on some iptables rules on the INPUT chain. On a Windows machine you'd be creating rules in the "Windows Firewall with Advanced Security".


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

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

To view a domain locally (not over the internet) you would need to add an entry in your hosts file with the following format ipaddress hostname hostname2 hostname3 Example: 192.168.1.10 staging1.website.com staging2.website.com.au backend.website.com Your host file can be found at either: /etc/hosts C:\Windows\System32\Drivers\etc\hosts


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

You probably need to add a JkMount directive to the Apache mod_jk configuration. Edit the file /etc/tomcat6/mod_jk.conf and add a line like this: JkMount /sample* ajp13_worker The mod_jk.conf file most likely already contains JkMount directives for the manager webapp and a few others. Make sure the name of the AJP worker (ajp13_worker in the example ...


2

The exact reason of why Tomcat cannot read the directories as in approach 1 and 3 are still unknown to me. However, it seems impossible for Tomcat to use any directory located under /home/user/... as a webapp, even if this means using symlinks to link to this location and setting correct permissions on the directories! Although probably this is some kind of ...


2

You can use openssl's x509 subcommand: openssl x509 -subject -issuer -noout -in cert.pem and check the output. Should be self explanatory. An example: $ openssl x509 -noout -issuer -subject -in gd-class2-root.crt issuer= /C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority subject= /C=US/O=The Go Daddy Group, Inc./OU=Go Daddy ...



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