Just a heads up to the Tomcat team - I switched all our comet handling to
Jetty, and these issues are resolved. Something is definitely amiss in the
NIO connector.
Regards,
Matt Tyson
On Sat, Dec 31, 2011 at 10:23 AM, Mark Thomas wrote:
> On 31/12/2011 16:35, Matthew Tyson wrote:
> &g
On Wed, Dec 28, 2011 at 1:04 AM, wrote:
> Matthew Tyson wrote:
>
> >That's right, there is an f5 load balancer. The valve is used to keep
> >track of whether the request was via HTTPS or not.
>
> What happens if you go direct to Tomcat and bypass the F5?
>
>
On Fri, Dec 30, 2011 at 11:57 AM, S Ahmed wrote:
> I know with other frameworks (like python/rails) people tend to run
> multiple instaces of the web server and round robin requests to each using
> something like haproxy.
>
> Is this known in the tomcat community at all?
>
> If I have a server wi
On Thu, Dec 29, 2011 at 12:02 PM, Tim Watts wrote:
> On Thu, 2011-12-29 at 11:22 -0800, Matthew Tyson wrote:
>
>
>
> > How an empty 200 response could be generated
> > without executing the logging statement here is a mystery.
> >
>
> Do you still have tha
On Thu, Dec 29, 2011 at 11:07 AM, Pid wrote:
> On 29/12/2011 17:27, Matthew Tyson wrote:
> > On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson
> > wrote:
> >
> >> On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr >wrote:
> >>
> >>> Am 28.12.2011
On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson
wrote:
> On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr wrote:
>
>> Am 28.12.2011 10:04, schrieb ma...@apache.org:
>>
>> Matthew Tyson>
>>> wrote:
>>>
>>> That's right, there is an f5 load
On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr wrote:
> Am 28.12.2011 10:04, schrieb ma...@apache.org:
>
> Matthew Tyson>
>> wrote:
>>
>> That's right, there is an f5 load balancer. The valve is used to keep
>>> track of whether the request was via
On Tue, Dec 27, 2011 at 1:31 PM, Stefan Mayr wrote:
> Am 24.12.2011 00:39, schrieb Matthew Tyson:
>
> Hello,
>>
>> We have been having quite a few problems with using long-polling
>> connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
>> d
On Tue, Dec 27, 2011 at 11:11 AM, Mark Thomas wrote:
> On 25/12/2011 02:17, Matthew Tyson wrote:
>
> >> INFO 2011-12-24 10:25:35,578 COMET REQUEST: 75.149.42.46 POST null |
> >> TRACE:
> >> java.lang.Throwable
> >> at
> org.cometd.server
On Sat, Dec 24, 2011 at 10:33 AM, Matthew Tyson
wrote:
> On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomas wrote:
>
>> On 23/12/2011 23:39, Matthew Tyson wrote:
>> > Hello,
>> >
>> > We have been having quite a few problems with using long-polling
>> &
On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomas wrote:
> On 23/12/2011 23:39, Matthew Tyson wrote:
> > Hello,
> >
> > We have been having quite a few problems with using long-polling
> > connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
> > d
Hello,
We have been having quite a few problems with using long-polling
connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
definitely improved things, but we are still seeing major issues.
The problems only crop up after a couple minutes under some load (modest
load, around
the OS and/or
> user that is running Tomcat.
>
> - Bob
>
>
>
> From: Matthew Tyson
> To: Tomcat Users List
> Sent: Tuesday, November 15, 2011 4:18 PM
> Subject: Re: Errors with NIO processor
>
> Is there more info I can provide to help diagnose this error?
Is there more info I can provide to help diagnose this error? It is
killing us.
Thanks,
Matt
On Tue, Nov 15, 2011 at 9:00 AM, Matthew Tyson
wrote:
> Hey Guys,
>
> We are seeing the following errors (in production of course, testing
> didn't reveal this) after switchin
Hey Guys,
We are seeing the following errors (in production of course, testing didn't
reveal this) after switching to NIO protocol.
This is Tomcat 7.0.22 on CentOS 6. There is a load balancer sending only
comet traffic to port 8080, where the NIO protocol is used.
Nov 15, 2011 8:39:29 AM org.ap
ble.
Would you give us a sense of how using a non-blocking connector would be
important when doing comet? Once startAsync is called, will the standard
(blocking) connector continue to hold resources (where the NIO connectors
won't)?
Thanks,
Matt
On Wed, Nov 9, 2011 at 1:24 AM, wrote:
&g
,
and have it be handled without blocking IO, I need to use the NIO connector?
Thanks,
Matt
On Tue, Nov 8, 2011 at 12:27 PM, Mark Thomas wrote:
> On 08/11/2011 20:15, Matthew Tyson wrote:
> > Hey Guys,
> >
> > It has been my assumption that Tomcat 7's comet impleme
Hey Guys,
It has been my assumption that Tomcat 7's comet implementation (ie,
asyncSupported=true), will automatically use NIO processing.
Is that not true? Do I need to set the connector to be
org.apache.coyote.http11.Http11NioProtocol explicitly?
Thanks,
Matt
sage is created by
> o.a.tomcat.util.bcel.classfile.Constant#readConstant(...). There is a
> switch() and default: label results in this exception being thrown.
> Expected values there are from 1 to 12. Your 60 is far outside the
> range.
>
>
> 2011/7/21 Matthew Tyson :
>
11 at 11:43 AM, Konstantin Kolinko wrote:
> 2011/7/20 Matthew Tyson :
> > Adding that to the skip list definitely prevented that error, but I'm
> > getting many jars with the same problem. I thought I could maybe get
> away
> > with just skipping them all, but I'm
,dnsns.jar,jcharset.jar,pager-taglib.jar
Any ideas?
Thanks,
Matt
On Wed, Jul 20, 2011 at 12:21 AM, Mark Thomas wrote:
> On 20/07/2011 03:55, Matthew Tyson wrote:
> > Hey guys,
> >
> > tomcat 7.0.19
> > Java 1.6.0_22
> > CentOS 5.6
> >
> > I just
Hey guys,
tomcat 7.0.19
Java 1.6.0_22
CentOS 5.6
I just switched the web.xml to servlet 3.0 (from a app running servlet 2.4
previously without issue) and now I'm seeing the following error (turned on
fine logging in the util class):
FINE: Scanning JAR [file:/usr/java/jdk1.6.0_22/jre/lib/ext/jchar
22 matches
Mail list logo
