-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Konstantin,
On 6/5/14, 4:27 PM, Konstantin Kolinko wrote:
> 2014-06-05 23:06 GMT+04:00 Christopher Schultz
> :
>> On 6/5/14, 11:58 AM, Konstantin Kolinko wrote:
>>> 2014-06-05 19:19 GMT+04:00 Christopher Schultz
>>> :
I tried invoking "backgro
2014-06-05 23:06 GMT+04:00 Christopher Schultz :
> On 6/5/14, 11:58 AM, Konstantin Kolinko wrote:
>> 2014-06-05 19:19 GMT+04:00 Christopher Schultz
>> :
>>> I tried invoking "backgroundProcess" on my Manager bean via JMX
>>> but it didn't seem to actually clean anything up. Is there any
>>> hope of
Arseny wrote:
...
Thanks again, Chris, for your very helpful message. I never heard
earlier about documentation and never visited
http://tomcat.apache.org/tomcat-7.0-doc/ before.
Even assuming that you don't mean "documentation" in general, that seems a bit hard to
swallow. But I gues
05.06.2014 22:09, Christopher Schultz пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arseny,
On 6/5/14, 12:21 PM, Arseny wrote:
The Tomcat documentation clearly states that you can (and should!) do
that, too. I guess having someone else do your homework for you is
easier than reading do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arseny,
On 6/5/14, 12:21 PM, Arseny wrote:
> 05.06.2014 18:20, Christopher Schultz пишет:
>
> The file should be called ROOT.xml and should not have a "path"
> attribute *at all*. Please read the configuration guide:
> http://tomcat.apache.org/to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Konstantin,
On 6/5/14, 11:58 AM, Konstantin Kolinko wrote:
> 2014-06-05 19:19 GMT+04:00 Christopher Schultz
> :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> All,
>>
>> One of dev instances this morning is screaming because I have
>> hu
Hello,
I am using this combo of components:
* Apache Tomcat 8.0.8
* Apache CXF 2.7.11
* Servlet 3.0
* JAX-RS 2.0
* JDK 1.7.0_45
* Windows 7
* Chrome browser with the Advanced REST Client plug-in
I developed some web services using REST that leverages CXF ability to
do asynchronous methods, and u
I'm attempting to reply to a post by Mark Thomas posted on Mon, 21 Jan 2013
20:15:58 GMT at (
http://mail-archives.apache.org/mod_mbox/tomcat-users/201301.mbox/%3c50fda1fe@apache.org%3E)
but I'm not sure if this is the way to do it. I'm not too keen on the
whole mailing list translations to th
05.06.2014 18:20, Christopher Schultz пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The file should be called ROOT.xml and should not have a "path"
attribute *at all*. Please read the configuration guide:
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html
- -chris
-BEGIN
2014-06-05 19:19 GMT+04:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> All,
>
> One of dev instances this morning is screaming because I have hundreds
> of active sessions. I checked, and it looks like the background
> processor thread for the context is not runnin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Didier,
On 6/5/14, 4:10 AM, DDU DUQUENNOY Didier wrote:
> Chris,
>
> Thank you for your answer. You are right about tomcat itself not
> being involved. I was fooled by the class ByteChunk belonging to
> tomcat, and didn't see that the MultipartStre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arseny,
On 6/5/14, 2:25 AM, Arseny wrote:
> 05.06.2014 3:28, Christopher Schultz пишет: Am I missed something?
> Tomcat keep it in some cache? This is why nobody should define
> elements in server.xml: they always mess them up.
>
> In addition to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
One of dev instances this morning is screaming because I have hundreds
of active sessions. I checked, and it looks like the background
processor thread for the context is not running, therefore no sessions
are expiring.
Tomcat 7.0.52, Debian L
2014-06-04 19:46 GMT+04:00 Don Asper :
> Hi: I want my web apps running on Tomcat 7.0.35 to use a custom classloader.
> The reason is that I want each web app classloader instance to do some
> processing to set up the classpath for the web app it belongs to. I have the
> following questions:
Sorry, I made a mistake in defining the variable.
Jeff
-Original Message-
From: Jeff Cai [mailto:jeff_...@symantec.com]
Sent: Thursday, June 05, 2014 5:51 PM
To: users@tomcat.apache.org
Subject: c:forEach doesn't support variable in Tomcat 7.0.54 while 7.0.37
supports
Hi,
In tomcat 7
2014-06-05 13:50 GMT+04:00 Jeff Cai :
> Hi,
>
> In tomcat 7.0.54, the variable is not supported.
> I changed the source
> apache-tomcat-7.0.54/webapps/examples/jsp/tagplugin/foreach.jsp
>
>
>
> ${item}
>
>
> Then it reports:
>
> org.apache.jasper.JasperException: Unable to c
Hi,
In tomcat 7.0.54, the variable is not supported.
I changed the source
apache-tomcat-7.0.54/webapps/examples/jsp/tagplugin/foreach.jsp
${item}
Then it reports:
org.apache.jasper.JasperException: Unable to compile class for JSP
org.apache.jasper.JspCompilatio
Chris,
Thank you for your answer.
You are right about tomcat itself not being involved. I was fooled by the class
ByteChunk belonging to tomcat, and didn't see that the MultipartStream belongs
in fact to commons-fileupload.jar.
The jbossweb-tomcat55.sar module in jboss 4.0.4.GA does come with
18 matches
Mail list logo
