On 12/12/2013 06:35, Igor Urisman wrote:
> As seen in 8.0.0 RC5:
>
> java.lang.IllegalStateException: javax.websocket.DeploymentException:
> Multiple Endpoints may not be deployed to using the same path
> [/conntestCloseEndpoint]
>
> IMHO, the message can't make up its mind between "to the same p
On Dec 12, 2013, at 1:42 PM, Vic Katte wrote:
> Hello Dan,
First, please don't top post. Reply inline, like me, or at the bottom. That
is the convention followed on this list.
> Thanks for responding. Without going too much into the code, I am trying to
> understand whether Tomcat does suppo
Hello Dan,
Thanks for responding. Without going too much into the code, I am trying to
understand whether Tomcat does support the concept of a Naming Server. With
JMS, it is possible to create and store administration objects such as
ConnectionFactory, Destinations in a Naming Service (such as LDA
Hi Christopher,
Changing the existing AccessLogValve to use a logger would have an impact
on performances with the creation of intermediate String objects and
keeping backward compatibility on the access logs files management (naming,
rotation, ...) with a new "LogFactory.getLogger()" approach wou
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 12/12/13, 2:42 AM, André Warnier wrote:
The original issue of the OP was to be notified ASAP when an OOM
occurs. And he indicated that an OOM resulted in a message in the
logs. So, "something" is already catch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Cyrille,
On 12/12/13, 3:56 AM, Cyrille Le Clerc wrote:
> Hello Christopher,
>
> Delegating to log4j/logback/java.util.logging could be an option
> but it would still greatly benefit of a refactoring to split the
> existing AccessLogValve into an Ab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 12/12/13, 2:42 AM, André Warnier wrote:
> The original issue of the OP was to be notified ASAP when an OOM
> occurs. And he indicated that an OOM resulted in a message in the
> logs. So, "something" is already catching the OOM exception, t
Caldarale, Charles R wrote:
From: Junek Leoš [mailto:ju...@oksystem.cz]
Subject: Unreachable URL at Tomcat doc webpage
At http://tomcat.apache.org/connectors-doc-archive/jk2/proxy.html I found 2
invalid URLs - the last two links at "Source and Configuration" section:
I´m getting 404 error.
> From: Junek Leoš [mailto:ju...@oksystem.cz]
> Subject: Unreachable URL at Tomcat doc webpage
> At http://tomcat.apache.org/connectors-doc-archive/jk2/proxy.html I found 2
> invalid URLs - the last two links at "Source and Configuration" section:
> I´m getting 404 error.
> Could you fix it, p
On Dec 12, 2013, at 4:25 AM, Vic Katte wrote:
> Hello,
What version of Tomcat are you using?
>
> How does one configure tomcat so that a hosted application could connect to
> a JMS Message server such as WebSphereMQ?
>
> I have managed to write a small test application in JMS and deployed i
Thanks for your support Brian :-)
Regarding the performances, I'm sure that a native
SyslogAccessLogValve will have much better performances than relying
on a logging framework:
* there will be less layers to go through
* we can eliminate any String or byte[] creation which to lower the
pressure o
On 12/12/13 08:56, Cyrille Le Clerc wrote:
Hello Christopher,
Delegating to log4j/logback/java.util.logging could be an option but it
would still greatly benefit of a refactoring to split the existing
AccessLogValve into an AbstractAccessLogValve with the formatting logic and
an AccessLogValve t
Hello!
At http://tomcat.apache.org/connectors-doc-archive/jk2/proxy.html I found 2
invalid URLs - the last two links at "Source and Configuration" section:
http://httpd.apache.org/docs-2.1/mod/mod_proxy_ajp.html
http://httpd.apache.org/docs-2.1/mod/mod_proxy_balancer.html
I´m getting 404 error.
Hello,
How does one configure tomcat so that a hosted application could connect to
a JMS Message server such as WebSphereMQ?
I have managed to write a small test application in JMS and deployed it to
tomcat and configured it to connect to MQ. This application defines the
default initial context u
Hello Christopher,
Delegating to log4j/logback/java.util.logging could be an option but it
would still greatly benefit of a refactoring to split the existing
AccessLogValve into an AbstractAccessLogValve with the formatting logic and
an AccessLogValve that would keep the logic to write in the file
15 matches
Mail list logo
