On 02/09/2015 21:53, Cohen, Laurence wrote:
> Thank you Chris,
>
> We only have one webserver and two tomcat applications on the back end.
> Where do I set the connections allowed if we are using mod_proxy_httpd?
If this is the issue (and it is a good bet it is) the quick (and not
that dirty) sol
1. apache httpd 2.2.x
2. mod_proxy_httpd
3. I'll have to clean up this information.
4. 7.0.59, jdk 1.8u51
5. I'll have to clean up this information.
6. Yes, we have iptables running on both the app server and web server but
even when we shut them down we still have the problem.
I'll send 3 and 5 a
Thank you Chris,
We only have one webserver and two tomcat applications on the back end.
Where do I set the connections allowed if we are using mod_proxy_httpd?
Thanks,
Larry Cohen
On Wed, Sep 2, 2015 at 4:47 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Larry,
On 9/2/15 3:54 PM, Cohen, Laurence wrote:
> We have a webserver and an appserver, and the webserver talks to
> the appserver on port 8007. Every once the communication will
> stop, and we will notice an error on the webserver saying that it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry,
On 9/2/2015 12:54 PM, Cohen, Laurence wrote:
> Hi,
>
> We have a webserver and an appserver, and the webserver talks to
> the appserver on port 8007. Every once the communication will
> stop, and we will notice an error on the webserver sayin
Larry,
Make sure that you’re closing any resource that you’ve opened.
Jeff
Sent from Windows Mail
From: Cohen, Laurence
Sent: Wednesday, September 2, 2015 2:54 PM
To: Tomcat Users List
Hi,
We have a webserver and an appserver, and the webserver talks to the
appserve
Hi,
We have a webserver and an appserver, and the webserver talks to the
appserver on port 8007. Every once the communication will stop, and we
will notice an error on the webserver saying that it can't talk to the
appserver. When this happens, I will run a netstat -an |grep 8007 on the
appserve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Diarmuid,
(Marking as OT because this is not a Tomcat issue.)
On 9/1/15 5:34 PM, dmccrthy wrote:
> Sorry for the ambiguity, we're using scenario (b), outgoing client
> connections. The server cert is signed by GeoTrust but we don't
> have the full
