Thanks a bunch Daniel for your help. Also for the patience in answering my
question.
The solution to this issue to make Tomcat handle the connection pooling instead
of the application code OR to restart the application servers along with the DB.
--- On Fri, 20/7/12, Daniel Mikusa wrote:
> Fro
Thanks Felix for your great explaination.
--- On Sat, 21/7/12, Felix Schumacher wrote:
> From: Felix Schumacher
> Subject: Re: java.sql.SQLException: No more data to read from socket
> To: users@tomcat.apache.org
> Date: Saturday, 21 July, 2012, 6:41 PM
> Am Samstag, den 21.07.2012, 08:44
> +08
On Fri, Jul 20, 2012 at 7:20 PM, Mark Thomas wrote:
> Brett Mason wrote:
> >Could someone please clarify if Tomcat supports forms authentication
> >without cookies?
>
> It should.
>
> > If it is intended to be a supported configuration I'm
> >happy to submit a bug report and can provided a simpl
On Fri, Jul 20, 2012 at 7:06 PM, Pid * wrote:
> On 20 Jul 2012, at 03:38, Brett Mason wrote:
> > Could someone please clarify if Tomcat supports forms authentication
> > without cookies? If it is intended to be a supported configuration I'm
> > happy to submit a bug report and can provided a sim
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 connec
On Sun, 2012-07-22 at 11:21 -0700, k9...@operamail.com wrote:
> On Sun, Jul 22, 2012, at 02:08 PM, Tim Watts wrote:
> > By default, Tomcat will listen on port 8080 on all available addresses
> > (IPv6 and 4, barring configuration settings at the OS level). The key
> > "word" in those java.net prop
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 127.0.0.1:8
By the way,
k9...@operamail.com wrote:
>
(previously) :
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.
---
and
netstat -pan --tcp | grep java
tcp0 0 127.0.0.1:8080 0.0.0.0:*
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 .
it certainly appears to be:
vi
On Sun, 2012-07-22 at 10:32 -0700, k9...@operamail.com wrote:
> 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 (d
> From: k9...@operamail.com [mailto:k9...@operamail.com]
> Subject: Re: Tomcat 7.0.27 listens only @IPv6 localhost, ignores
> 'use IPv4' JAVA_OPTS in tomcat.conf. How to correctly force IPv4?
>
> connectionTimeout="2"
>redirectPort="8443" />
>
> >
> What happens if you install a real Tomcat from tomcat.apache.org
same issue
> What do your elements in your server.xml file look like?
It's out-of-the-box:
...
...
> Have you installed APR?
yes.
apr-2-config --version
2.0.0
svn info `a
> From: Tim Watts [mailto:t...@cliftonfarm.org]
> Subject: Re: Tomcat 7.0.27 listens only @IPv6 localhost, ignores
> 'use IPv4' JAVA_OPTS in tomcat.conf. How to correctly force IPv4?
> Since you've told the OS to not allow IPv4 connections on IPv6 sockets,
> I believe you would need to configure
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 i
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 on the server. The IPv6 stack is also enabled, and
>
> From: k9...@operamail.com [mailto:k9...@operamail.com]
> Subject: Tomcat 7.0.27 listens only @IPv6 localhost, ignores
> 'use IPv4' JAVA_OPTS in tomcat.conf. How to correctly force IPv4?
> I've installed
> rpm -qa | grep -i ^tomcat
> tomcat-lib-7.0.27-7.1.noarch
>
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" wit
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 fi
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.
Regards,
-Tony
--- On Sun, 7/22/12, k9...@operamail.com wrote:
From: k9...@operamail.com
S
Good question. What I read it has to do with scalability. The smaller the
thread stack size the more threads you can scale to and the smaller the overall
memory footprint that has to be managed. That is what I thought I read
someplace.You could say performance and scalability go hand in hand and
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
tomcat-admin-webapps-7.0.27-7.1.noar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony,
On 7/21/12 3:11 PM, Tony Anecito wrote:
> Lots of time I apply best practices that I learn over time or are
> recommended by experts (Like Mark Thomas). You do that first as
> early in the development life cycle as possible. Funny I guess how
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix,
On 7/21/12 9:11 AM, Felix Schumacher wrote:
> To mitigate the problem of handing out broken connections the pool
> often has functionality to check a connection, before it hands it
> to the client. When using the tomcat database connection pool
U
- Original Message -
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Friday, July 20, 2012 10:53 PM
To: Tomcat Users List
Subject: Re: Location of Tomcat 7 jvm defualt settings...
On 20/07/2012 21:42, Tony Anecito wrote:
> Thanks Charles I have found documention for all the below fro
Alexander Shutyaev wrote:
>Hi Mark,
>
>The problem is that I have a dynamic app where webapps come and go, so
>I
>can't call addWebapp() before calling start(). The best I can do is a
>delayed start() - in my method that calls addWebapp() I can make a
>check -
>and if this is the first time - c
25 matches
Mail list logo
