2012/11/13 Fred Toth :
> On 11/12/2012 4:24 PM, Konstantin Kolinko wrote:
>>
>> 2012/11/13 Fred Toth :
>>>
>>> Hello again,
>>>
>>> I've found my problem, sort of.
>>>
>>> In this particular application, ever since tomcat 5, we've been remapping
>>> the DefaultServlet url-pattern. Works fine in 5 a
Many Thanks
There was really a dead lock in our system.
Regards
CA
-Ursprüngliche Nachricht-
Von: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Gesendet: Dienstag, 6. November 2012 07:53
An: Tomcat Users List
Betreff: RE: AW: AW: AW: AW: AW: tomcat 6.0.32 stops expiring sessions
On 11/12/2012 4:24 PM, Konstantin Kolinko wrote:
2012/11/13 Fred Toth :
Hello again,
I've found my problem, sort of.
In this particular application, ever since tomcat 5, we've been remapping
the DefaultServlet url-pattern. Works fine in 5 and 6, but not in 7. Which
means I've got another probl
This same setup works fine locally on my laptop..so it does work :)
On Mon, Nov 12, 2012 at 10:55 PM, S Ahmed wrote:
> I can't seem to connect to my mysql database from my java code, but I can
> do it via terminal using the user and password that is in my spring context
> file.
>
> I also tried
> From: selvakumar netaji [mailto:vvekselva...@gmail.com]
> Subject: Re: Handling requests when under load - ACCEPT and RST vs non-ACCEPT
> I'm new to this mailing list. I read the above mail list and not able to
> grasp the concepts like load balancing, keep alive. Can you please give me
> links
Hi All,
I'm new to this mailing list. I read the above mail list and not able to
grasp the concepts like load balancing, keep alive. Can you please give me
links where I can find links about it.
On Tue, Nov 13, 2012 at 6:32 AM, Mark Thomas wrote:
> "Asankha C. Perera" wrote:
>
> >I do not und
"Asankha C. Perera" wrote:
>I do not understand the negativity here..
You are trying to solve a problem no-one here recognises.
You are ignoring and/or dismissing people that ask difficult questions or point
out flaws in your proposal.
Your posts - this one in particular - come across as very
Esmond Pitt wrote:
>Asankha
>
>To reiterate what Christopher said, if you close the listening socket
>because you think you can't service one extra client, you will lose all
>the
>connections on the backlog queue, which could be hundreds of clients,
>that
>you *can* service.
Indeed. I'd like to
On 11/12/2012 10:47 PM, Terence M. Bandoian wrote:
On 11/9/2012 1:41 PM, Christopher Schultz wrote:
Closing the listening socket, as you seem to be now suggesting, is
>a very poor idea indeed: what happens if some other process grabs
>the port in the meantime: what is Tomcat supposed to do then?
Hi Esmond
To reiterate what Christopher said, if you close the listening socket
because you think you can't service one extra client, you will lose all the
connections on the backlog queue, which could be hundreds of clients, that
you *can* service.
I do not see a problem here. We develop softwar
sorry to take so long to respond, but i was finally able to capture a
thread dump during one of these events...
the thread dump (taken via jstack) is view-able here:
https://gist.github.com/aa772c922feee65177c1
any help deciphering it would be appreciated. no deadlocks, but it does
appear there
2012/11/13 Fred Toth :
> Hello again,
>
> I've found my problem, sort of.
>
> In this particular application, ever since tomcat 5, we've been remapping
> the DefaultServlet url-pattern. Works fine in 5 and 6, but not in 7. Which
> means I've got another problem, but at least I know why the app fail
Hello again,
I've found my problem, sort of.
In this particular application, ever since tomcat 5, we've been
remapping the DefaultServlet url-pattern. Works fine in 5 and 6, but not
in 7. Which means I've got another problem, but at least I know why the
app fails to run.
Here's the problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Esmond,
On 11/11/12 10:18 PM, Esmond Pitt wrote:
> Asankha
>
> To reiterate what Christopher said, if you close the listening
> socket because you think you can't service one extra client, you
> will lose all the connections on the backlog queue, whi
Hi,
Sorry, just getting back to this after a delay.
I've added an AccessValve to my context and it, too, reports 404. So
this is more confirmation that my context has actually deployed (as the
logs report), and, at least at some level, the requests are being mapped
by tomcat to the correct co
On 11/9/2012 1:41 PM, Christopher Schultz wrote:
Closing the listening socket, as you seem to be now suggesting, is
>a very poor idea indeed: what happens if some other process grabs
>the port in the meantime: what is Tomcat supposed to do then?
I haven't been following this thread closely eno
16 matches
Mail list logo
