On 20/08/2015 16:58, Steffen Heil (Mailinglisten) wrote:
> Hi
>
>
> I have several servlets with mappings such as
> /a/*
> /b/*
> /c/*
> And so on.
>
> One of these mappings was for the old Tomcat 7.0.27 websocket implementation:
> /ws/*
>
> That worked.
>
> Now, with the new JSR versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gerald,
On 8/20/15 3:28 PM, Miller, Gerald wrote:
> Follow-up:
(Weird... I never got the first message. Thanks for including it. I'm
going to re-arrange the message so it's not in top-posting form.)
> I had previously set up Tomcat 8 on an Ubuntu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 8/20/15 11:58 AM, Steffen Heil (Mailinglisten) wrote:
> I have several servlets with mappings such as /a/* /b/* /c/* And so
> on.
>
> One of these mappings was for the old Tomcat 7.0.27 websocket
> implementation: /ws/*
>
> That worked
Note also: RemoteAddrValve is still commented out.
From: Miller, Gerald
Sent: Thursday, August 20, 2015 3:28 PM
To: 'users@tomcat.apache.org'
Subject: RE: HTTP Authenticate ignored by Tomcat 7 (Windows)
Follow-up: I reviewed the logs and saw a number of requests coming from
localhost, where I h
Follow-up: I reviewed the logs and saw a number of requests coming from
localhost, where I had run experimental queries to the exact same service. I
also confirmed through Rawcap that they were using the same Authorization
header field. The only one receiving the 401 status was the one coming
I added logging to this module and found that there is a problem with
System.getProperty("sflow.dsindex”) call.
It was resolved by adding to startup.sh :
export CATALINA_OPTS="$CATALINA_OPTS -Dsflow.dsindex=1234
-Dsflow.hostname=app_1"
Now SflowValve,jar is working.
Thanks!
Sergey
> On Aug 1
Hi
I have several servlets with mappings such as
/a/*
/b/*
/c/*
And so on.
One of these mappings was for the old Tomcat 7.0.27 websocket implementation:
/ws/*
That worked.
Now, with the new JSR version in Tomcat 8, I cannot get this to work.
The problem is, that all of the following pa
Thanks. I will investigate the logging and cookie processor configuration.
The SEVERE cookie error does come with a stack trace:
17-Aug-2015 01:13:23.051 SEVERE [catalina-exec-942]
org.apache.coyote.http11.AbstractHttp11Processor.process Error processing
request
java.lang.IllegalArgumentExcep
From: Christopher Schultz
To: Tomcat Users List
Date: 17-08-2015 18:32
Subject:Re: Tomcat hanged on window server 2012
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Chris,
Thanks for the reply, our response to ur questions are highlighted in
blue.
Any help is greatl
2015-08-19 18:21 GMT+03:00 Robert Tupelo-Schneck :
> I'm running Tomcat 8.0.24. I see lots of errors in catalina.out with lines
> like
>
> Note: further occurrences of Cookie errors will be logged at DEBUG level.
> Note: further occurrences of Parameter errors will be logged at DEBUG level.
>
Unsubscibe
On 19 August 2015 at 13:30, jean-frederic clere wrote:
> On 08/17/2015 01:10 PM, Mark Thomas wrote:
>
>> The Apache Tomcat Project is proud to announce the release of version
>> 1.2.41 of the Apache Tomcat Connectors.
>> This version fixes one security issue (CVE-2014-8111) and a nu
Yes since Apache TomEE is Java EE 6 certified it can runs with any JPA
provider. As suggested you can use previous links for this. It is really
simple. Also briefly Apache TomEE 7 M1 (Java EE 7 compatible) will be
released.
As mentioned subscribe to TomEE mailing list or you can contact myself
wit
12 matches
Mail list logo
