On Sat, Apr 5, 2014 at 8:35 AM, Vicky B wrote:
> The problem is solved now .
Erm, well. Perhaps for some definition of "solved"...
> I had no clue that firewall would drop the connection if it does not
> recieve response within stiplulated time.
> Can i increase this timeout period ?
May I su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 4/5/14, 8:35 AM, Martin Gainty wrote:
>
>
>
>> Date: Sat, 5 Apr 2014 06:57:23 -0400 From: dcker...@verizon.net
>> To: users@tomcat.apache.org Subject: Re: AW: AW:
>> tomcat-connectors-1.2.39-windows-x86_64-iis does not work
>>
>> ...
HI All,
The problem is solved now . we are have implemented a callback
functionality where after every 45 seconds we call back the same method
again .Hence making sure that there is no timeout.
But as per identifying the actual reason behind the problem i tried to
reproduce the issue,after
2014-04-03 23:34 GMT+04:00 André Warnier :
> Alten, Jessica-Aileen wrote:
>>>
>>> -Ursprüngliche Nachricht-
>>> Von: André Warnier [mailto:a...@ice-sa.com]
>>> Gesendet: Donnerstag, 3. April 2014 15:36
>>> An: Tomcat Users List
>>> Betreff: Re: AW: tomcat-connectors-1.2.39-windows-x86_64-ii
Jeffrey Janner wrote:
-Original Message-
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
Sent: Friday, April 04, 2014 12:04 PM
To: 'Tomcat Users List'
Subject: RE: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does
not work
-Original Message-
From: Christopher Sc
> Date: Sat, 5 Apr 2014 06:57:23 -0400
> From: dcker...@verizon.net
> To: users@tomcat.apache.org
> Subject: Re: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does not work
>
> ...
>
> > but
> >> if the server is a *nix implementation, the better diag tool
> >> might be dig
...
but
if the server is a *nix implementation, the better diag tool
might be dig. And yes, I would not expect the address 0.0.0.0
on a client to connect to the localhost. That is a special
case address
meaning
"local network". If anything, it would be sending packets out
the NIC card, not v
