Hi
is there a way to externally influence the switch between versions with
the new parallel deployment method. As I understand it tomcat
automatically switches to the new version for new requests as soon as
the context with the new version is started. Instead I would like to
manually control wich
Hi
I just setup a tomcat 7 on linux for test. I just used this connection
property in server.xml
here is out connector
Connector maxKeepAliveRequests=-1 port=7070 protocol=HTTP/1.1
allowTrace=false connectionTimeout=2 clientAuth=false /
, but when we try to connect from a client Firefox
Christopher Schultz ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luke,
On 4/11/12 5:17 PM, Luke Meyer wrote:
Just noticed what I was missing about connectionTimeout - it's the
default for keepAliveTimeout. So, that clears that up.
Still don't think
The only control you have is by ensuring that the version you want to be used
by default has the highest version number.
Mark
Christoph Maser christoph.ma...@1und1.de wrote:
Hi
is there a way to externally influence the switch between versions with
the new parallel deployment method. As I
Do you see any chance a request for feature in that direction would be
accpeted?
Chris
Am Donnerstag, den 12.04.2012, 09:40 +0100 schrieb Mark Thomas:
The only control you have is by ensuring that the version you want to be used
by default has the highest version number.
Mark
Christoph
Hi,
We are observing an increase in VIRT and RES memory of tomcat6.0 which
internally invokes our custom API is invoked (This API internally does an JNI
call).
The same API code when invoked through a standalone java process repeatedly
does not lead to an increase in the VIRT /RES memory.
Is
Hello,
Apologize for delay.
That should be fixed now (I have deployed 2.0-SNAPSHOT).
If you could try with your use case.
Thanks,
2012/4/8 Olivier Lamy ol...@apache.org:
Hello Leigh,
Thanks for creating issue.
Until now I tried to reproduce the issue but I failed.
I wonder if you could attach
Hi Olivier,
That's solved the problem, thanks. Unfortunately, declaring a custom class
loader in a context.xml causes Tomcat to use that one, instead of the one
set up with the correct class path by the plugin. I'll keep looking to see
if I can find a way around this.
Thanks for your prompt help
Hi,
This mechanism is meant to be a standard way for web frameworks to extend
the Servlet Container. IMHO this is compliant with the specification:
8.2.4 Shared libraries / runtimes pluggability
In addition to supporting fragments and use of annotations one of the
requirements
is that not
Hi folks,
I am sending a custom error message in my authenticator but it gets removed by
the StandardHostValve.
This is what I do in my authenticator:
catch (PrivilegedActionException e) {
logger.error(Unable to login as the service principal, e.getException());
Hi,
I've added mbeans-descriptors.xml to the package
org.apache.tomcat.util.net (the same package where JIOEndpoint is) in
the classpath with this (almost) empty content:
mbeans-descriptors
/mbeans-descriptors
org.apache.tomcat.util.modeler.Registry looks in the current package
down to the
Actually, a mbean entry with the correct type attribute was needed:
mbeans-descriptors
mbean name=ThreadPool
description=JIoEndpoint
domain=Catalina
group=Connector
type=org.apache.tomcat.util.net.JIoEndpoint
/mbean
The plugin has an option to setup context.xml to use see [1].
You can try to write an other context.xml only for using with the plugin ?
--
Olivier
[1]
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/run-mojo.html#contextFile
2012/4/12 Leigh Anderson
2012/4/11 Konstantin Kolinko knst.koli...@gmail.com:
2012/4/11 Lazar Kirchev lazar.kirc...@gmail.com:
I want the ServletContainerInitializer to be called for all applications I
deploy, not only with web.xml version 3.0, but also with lower version. Is
this possible?
2. You would even be able
2012/4/12 Mehdi Sarmadi msarm...@gmail.com:
I just setup a tomcat 7 on linux for test. I just used this connection
property in server.xml
here is out connector
Connector maxKeepAliveRequests=-1 port=7070 protocol=HTTP/1.1
allowTrace=false connectionTimeout=2 clientAuth=false /
, but
Violeta Georgieva violet...@apache.org wrote:
Hi,
This mechanism is meant to be a standard way for web frameworks to
extend
the Servlet Container. IMHO this is compliant with the specification:
Your not really humble at all opinion is wrong. This is a Servlet 3.0 feature
and therefore not
Christoph Maser christoph.ma...@1und1.de wrote:
Do you see any chance a request for feature in that direction would be
accpeted?
Right now, no. I don't see a requirement that isn't met by the existing
implementation. If there was a use case that wasn't completely off the wall
that couldn't be
2012/4/12 sandeep.shrid...@emc.com:
Hi,
We are observing an increase in VIRT and RES memory of tomcat6.0 which
internally invokes our custom API is invoked (This API internally does an JNI
call).
The same API code when invoked through a standalone java process repeatedly
does not lead
you'r right just fixed it.
Connector maxKeepAliveRequests=5 port=7070 protocol=HTTP/1.1
allowTrace=false connectionTimeout=2 clientAuth=false /
anyway, I can't still find the Connection: Keep-Alive HTTP Response(from
tomcat) header. I just don't know where to check, any clues? anything
I just misunderstood, so you'r saying it is HTTP 1.0 we will have the
keep-alive in HTTP?
I'll check that.
--
Mehdi Sarmadi
On Thu, Apr 12, 2012 at 5:36 PM, Mehdi Sarmadi msarm...@gmail.com wrote:
you'r right just fixed it.
Connector maxKeepAliveRequests=5 port=7070 protocol=HTTP/1.1
Assuming keep-alive being on by default in HTTP/1.1 how come, apache does
not work that way?
I mean even I force HTTP/1.1 in apache with Keep-Alive On, it sends back
Connection: KeepAlive in HTTP Response?
Moreover, turning keepalive feature on, makes Apache response about 8 to 10
times more than
2012/4/12 Osipov, Michael michael.osi...@siemens.com:
Hi folks,
I am sending a custom error message in my authenticator but it gets removed
by the StandardHostValve.
This is what I do in my authenticator:
catch (PrivilegedActionException e) {
logger.error(Unable to login as the service
2012/4/12 Mehdi Sarmadi msarm...@gmail.com:
you'r right just fixed it.
Connector maxKeepAliveRequests=5 port=7070 protocol=HTTP/1.1
allowTrace=false connectionTimeout=2 clientAuth=false /
anyway, I can't still find the Connection: Keep-Alive HTTP Response(from
tomcat) header. I just
2012/4/12 Ashima Sharma ashpr...@gmail.com:
Most of the jsps have this issue...but it happens randomly. For e.g., i wd
be able to access the registration page 5 times w/o any issue, and the 6th
time I'd get this error.
Its bizarre that tomcat tries to recompile the already compiled jsp at some
Christopher, response to your questions:
[Can you confirm that after you try to access the .jsp from the
browser, the timestamp on the .java file changes?] -* It does not change.
ALL the .java and .class files have the same timestamp as the .jsp files
which is the same as when the war was
Konstantin, responding to your questions:
[What is the type and value of _jspx_dependants field? ]
*private static java.util.Mapjava.lang.String,java.lang.Long
_jspx_dependants;
It does match the method return type!*
[Can you cite with what parameters JspServlet in your web.xml is
configured,
Konstantin Kolinko wrote:
2012/4/12 Osipov, Michael michael.osi...@siemens.com:
Hi folks,
I am sending a custom error message in my authenticator but it gets
removed by the StandardHostValve.
This is what I do in my authenticator:
catch (PrivilegedActionException e) {
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 4/12/12 4:37 AM, Mark Thomas wrote:
HTTP keep-alive is nearly always between a client and a server
across the internet. mod_jk keep-alive is nearly always between a
client and a server on the same LAN and often on the same machine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Randy,
On 4/12/12 8:13 AM, Randy Gray wrote:
Actually, a mbean entry with the correct type attribute was
needed:
Could you file an issue in Bugzilla and reference this email thread?
Thanks,
- -chris
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
On 4/11/12 10:40 PM, Tom H wrote:
An instance running tomcat 6.0.24 as root
Obviously, you won't make that mistake again.
Was the manager app available to non-localhost clients?
in our developer network was compromised today by a scanning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 16:20, Christopher Schultz wrote:
On 4/12/12 4:37 AM, Mark Thomas wrote:
In short, disabling mod_jk keep-alive frequently has no
noticeable performance impact (some customers of mine reported a
performance improvement!)
That
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/12/12 10:03 AM, Konstantin Kolinko wrote:
What is the type and value of _jspx_dependants field?
Ashima has sent the original JSP and the translated .java file to me.
The interesting parts are here:
// Starting at line 21
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/12/12 12:44 PM, Christopher Schultz wrote:
Ashima has sent the original JSP and the translated .java file to
me. The interesting parts are here:
Also, there isn't much in the way of directives in the original JSP.
First, some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph,
On 4/12/12 2:42 AM, Christoph Maser wrote:
is there a way to externally influence the switch between versions
with the new parallel deployment method. As I understand it tomcat
automatically switches to the new version for new requests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 4/12/12 8:58 AM, ma...@apache.org wrote:
If you want to use Servlet 3.0 features then you need to declare
3.0 in the web.xml.
+1
Since the spec is (almost entirely) backward-compatible, this shouldn't
represent an undue hardship. If you
Am Donnerstag, den 12.04.2012, 14:29 -0400 schrieb Christopher Schultz:
It's worth mentioning that requests bound to sessions that were
associated with the old version will continue to be serviced by the
old version of the webapp.
You said new requests but new sessions is more accurate.
FYI, effective immediately this (nicholas.willi...@ul.com) is my new email
address. I can no longer be reached at nicholas.willi...@puresafety.com.
Nick
-Original Message-
From: Nick Williams [mailto:nicholas.willi...@puresafety.com]
Sent: Tuesday, April 03, 2012 4:57 PM
To: Tomcat
2012/4/10 Konstantin Kolinko knst.koli...@gmail.com:
2012/4/10 Nick Porter nick.por...@tradar.com:
[NP] Yes. I can fathom no pattern to them. In fact, the only way I can
actually see them is to packet trace the HTTP exchange.
You do not have AccessLogValve configured?!
I did the following
Hello,
Currently, I cannot reproduce.
Do you have more logs/details from your tomcat instance ?
Especially: $CATALINA_HOME/logs/localhost_access_log.-MM-dd.txt
and entries corresponding to the deployment
Are you passing tru a http server which is proxying/redirecting to the
Tomcat instance ?
Olivier,
Thanks for getting to this.
Do you have more logs/details from your tomcat instance ?
Especially: $CATALINA_HOME/logs/localhost_access_log.-MM-dd.txt
and entries corresponding to the deployment
I will collect these and send them in a subsequent email.
Are you passing tru a
Thanks for the response Mark - it is consistent with both observations that i
noted in the original email (heap post startup was near 0, and disabling
scanning resolves). I looked in the changelog in 26/27 and did not see anything
in there that fits this? If your hypothesis is correct , I
Olivier,
When I try to deploy from Maven, the following message appears in the access
log. [1] There are no other messages in any of the other logs for this event.
[1] 127.0.0.1 - - [12/Apr/2012:21:15:59 -0700] PUT
/manager/html/deploy?path=%2F HTTP/1.1 401 2550
Matt
On Apr 12, 2012, at
42 matches
Mail list logo
