Yea, when versioning warfiles themselves you can count on the version being a
part of the deploy root.
I'm using a versioned context.xml files in confBase/[engine]/[host]
Html manger reports them correctly. The version number simply isn't there in
the text list.
> On Oct 23, 2015,
On 10/23/15 6:32 AM, Konstantin Kolinko wrote:
> 2015-10-22 20:55 GMT+03:00 Christopher Schultz :
>> On 10/14/15 11:03 PM, Christopher Schultz wrote:
>>> On 7/3/15 1:40 PM, Christopher Schultz wrote:
Running Tomcat 8.0.x trunk
2015-10-22 20:55 GMT+03:00 Christopher Schultz :
> On 10/14/15 11:03 PM, Christopher Schultz wrote:
>> On 7/3/15 1:40 PM, Christopher Schultz wrote:
>>> Running Tomcat 8.0.x trunk as of 167 (slightly old) on
>>> jdk1.8.0_45 on Mac OS X, I'm
I’m trying make Websockets work with embedded Tomcat (8.0.28) started by Main
class (shown below). When I try to open websocket connection from browser using
the URLs below, I always get “Error during WebSocket handshake: Unexpected
response code: 404”.
Is there anything wrong with the
Thank you Mark for replying.
> The URL
pattern therefore needs to be "/*"
Could not do anything with the above statement. May be an example could suffice.
Somehow could see an example for PreResources in the internet and this is
how I did it without an TestApp#web.xml file in
On 23.10.2015 16:53, Beyer, Gregory L wrote:
# Inbound SSL Settings
Thank you Konstantin and Chris Schultz. Been trying all you suggested
Konstantin, and a heck of a lot more without much success. But I finally did
get /something/ in a log that might be helpful if anyone can interpret it.
Chris, on your observation:
I'm not sure how Apache Felix fits
From: Chris Gamache [mailto:cgama...@gmail.com]
Sent: 22 October 2015 19:58
To: Tomcat Users List
Using Tomcat 8 ...
Has anyone noticed that /manager/text/list doesn't show version numbers when
On 23/10/2015 03:39, Pradyut Bhattacharya wrote:
> I had configured virtual directories in glassfish3.x over which I could
> write filters.
> For an example I could access files at c:/web from
> http://localhost/TestApp/web over which I could also place a filter at my web
> app's web/xml
> I know mod_jk will complain if it can't
> make a connection or if there is a timeout... I suspect mod_proxy_http
> will do the same.
They both are supposed to log 502, while Tomcat will raise a "connection
reset by peer" when answering to an already closed connection.
Timeouts for both are
For those interested, the Wireshark 2.0 which is now running the RC
process, has a built-in dissector for Tomcat clusters (named ATH for Apache
"Live monitoring is the only way to go, unless you want your customers
to surprise you with performance problems on your own site. :)"
Monitoring, ok, but alerting is critical for large scale production
environments. You mention JMX callbacks for alerting, but it would be worth
Mail list logo