building Tomcat7 from src (apache-tomcat-7.0.29-src) with
java -version
java version 1.7.0_b147-icedtea
OpenJDK Runtime Environment (suse-27.1-x86_64)
OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
from Opensuse 12.1's repos
On Tue, Jul 24, 2012, at 06:11 PM, Caldarale, Charles R wrote:
Tomcat 7 must be built with JDK 6 due to incompatibilities introduced by
Sun/Oracle in JRE 7. Once built, you may run Tomcat 7 under JRE/JDK 7.
Tomcat 8 will be buildable with JDK 7.
As JDK7 is our stanrard fare, is there a
I've built/installed Tomcat 7.0.29 from source on linux/64.
I've setup an init.d using jsvc launch, loosely based on the src-bundled
daemon.sh script.
@ tomcat service launch, using out-of-the-box config for now, I see two
listeners on ONE pid,
netstat -pan --tcp | grep jsvc
Hi
On Mon, Jul 23, 2012, at 01:10 PM, Jeff Beard wrote:
ps is showing threads as processes, which occurs with some versions of
Linux kernel. The listeners are 2 different threads: an AJP on 8009 and
an
HTTP on 8080.
Ok, so that sounds like one PID per thread, at least according to ps on
this
I've Tomcat 7.0.29 installed on linux/64.
@ service shutdown,
sh /etc/init.d/tomcat7 stop
I see in my logs two WARNING: Acceptor thread [null] failed to unlock.
Forcing hard socket shutdown:
INFO: Deploying web application directory
On Mon, Jul 23, 2012, at 04:15 PM, Christopher Schultz wrote:
netstat -pan --tcp | grep jsvc tcp0 0 :::8080
:::* LISTEN 30891/jsvc.exec tcp0 0 :::8009
:::* LISTEN 30891/jsvc.exec
jsvc's job is to allow the controlled process to open ports, so all
No other instance of 'java', 'jsvc' or 'tomcat' in the output.
Hm. Re-reading the commons-daemon page, it looks like maybe the
launcher process exits shortly after launch, leaving only two
long-running processes: the controlling process (the one in the
fork()/wait() loop) and the
I've installed
rpm -qa | grep -i ^tomcat
tomcat-lib-7.0.27-7.1.noarch
tomcat-docs-webapp-7.0.27-7.1.noarch
tomcat-javadoc-7.0.27-7.1.noarch
tomcat-webapps-7.0.27-7.1.noarch
Hi,
On Sun, Jul 22, 2012, at 09:29 AM, Tony Anecito wrote:
I do it at the OS level via the adaptor properties for windows. If your
network does not support IPv6 I would disable it else you will get errors
in your logs about IPv6 for like say DHCP assignment.
My network supports IPv6 just
reading here on this issue:
Re: Tomcat is only listening with ip6 and not ip4
http://linux.derkeiler.com/Mailing-Lists/Debian/2009-12/msg01262.html
... Thus you should report a bug against Tomcat. Also
you can replace net.ipv6.bindv6only=1 with
Hi,
On Sun, Jul 22, 2012, at 01:24 PM, Tim Watts wrote:
On Sun, 2012-07-22 at 08:03 -0700, k9...@operamail.com wrote:
Linux svr 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27
05:21:40 UTC 2012 (d016078) x86_64 x86_64 x86_64
GNU/Linux
IPv4 is enabled
What happens if you install a real Tomcat from tomcat.apache.org
same issue
What do your Connector elements in your server.xml file look like?
It's out-of-the-box:
...
Service name=Catalina
Connector port=8080 protocol=HTTP/1.1
connectionTimeout=2
Hi,
On Sun, Jul 22, 2012, at 02:08 PM, Tim Watts wrote:
No. I want Tomcat7 to listen ONLY on one address: the IPv4 loopback @
127.0.0.1. No other IPv4 addresses, and no IPv6 addresses at all.
Oh, that's easy: specify address=127.0.0.1 on your Connector.
it certainly appears to be:
On Sun, Jul 22, 2012, at 08:42 PM, André Warnier wrote:
You still have a Connector listening on port 8009 (and IPv6). You may
want to disable that one too (the AJP connector), to match your above
desires.
Of course. Now at,
netstat -pan --tcp | grep java
tcp0 0
Hi,
On Sun, Jul 22, 2012, at 03:57 PM, Tim Watts wrote:
But doing so would close the door on ::1, turning prefer into
require. Whereas binding on ::* allows both IPv6 4 in. I guess
what's confusing in all this is that the preferences just deal with
outbound addresses and connections (e.g.
15 matches
Mail list logo
