Hi Konstantin,
On 08/07/14 09:45, Konstantin Kolinko wrote:
There is no "application/x-pointplus" string in the default
conf/web.xml of Tomcat. So first you have to find where the string
comes from.
Yeap, that's the problem, we cannot reproduce the issue: it works fine
in Linux and Windows, a
Well, thanks for the helpful advice thus far..
So, now that I've added a listener properly, I get this:
java.lang.UnsupportedOperationException: Section 4.4 of the Servlet
3.0 specification does not permit this method to be called from a
ServletContextListener that was not defined in web.xml, a
w
Hi,
I did some more experimenting with both error handling approaches.
Tomcat 7.0.54 and 8.0.9 seemed to work a bit differently: on 8.0.9 some
requests timed out with "Exception while processing an asynchronous
request" error message. I was unable to reproduce this on TC 7.0.54 or
Resin 4.0.40.
W
On 7/8/2014 2:52 AM, Konstantin Kolinko wrote:
2014-07-07 21:07 GMT+04:00 Terence M. Bandoian :
On 7/5/2014 6:36 PM, André Warnier wrote:
I agree with André about the difficulties of debugging character encodings.
A couple of things you might check are the character encodings of the page
and th
On 09/07/2014 16:53, Marko Asplund wrote:
> On 09/07/2014 09:16, Mark Thomas wrote:
>
>>> There's a couple of parts in particular that I'm wondering about:
>>> - what's the correct way to deliver error response to client? Can I just
>>> cast the response acquired from AsyncContext to HttpServletRe
On Wed, 09 Jul 2014 09:59 Martin Grigorov wrote:
> Casting ServletResponse to HttpServletResponse is OK most of the time. You
> can check with "instanceof" before doing the cast.
> But casting AsyncContext to HttpServletResponse is way too brave.
Quite true, I'm not usually that courageous on pur
On 09/07/2014 09:16, Mark Thomas wrote:
> > There's a couple of parts in particular that I'm wondering about:
> > - what's the correct way to deliver error response to client? Can I just
> > cast the response acquired from AsyncContext to HttpServletResponse and
use
> > the normal Servlet API mech
Thank you for the answer. I will begging experimenting on 1 box with this
configuration:
I a couple of questions raises from your reply:
1) a couple of years ago we did a BENCHMARK mod_proxy vs mod_jk and the
difference was noticeable in favor of mod_jk. There was any improvement on
mod_pr
if Tomcat is fronted by a web server then I would also check the connector.
I've seen similar issues in the past with IIS and a faulty AJP connector.
switching to nginx with an APR connector resolved it in my case.
Igal
On 7/9/2014 2:49 AM, Mark Thomas wrote:
On 09/07/2014 08:43, yanchun.y..
como corrigir isso?
jul 09, 2014 9:22:01 AM org.apache.catalina.loader.
WebappClassLoader clearReferencesThreads
GRAVE: The web application [/jsf] appears to have started a thread named
[Mojarra-WebResourceMonitor-1-thread-1] but has failed to stop it.
This is very likely to create a memory
Hi,
We are running Tomcat 6.0.37 and Java JDK 1.6.0_60
We recently upgraded to JDK 1.6.0_75 and recieved below error at several
places
javax.net.ssl.SSLException: Fatal Alert received: Handshake Failure
We debugged and after analysis found that if we remove below 3 ciphers
suits from server.xml
On Wed, Jul 9, 2014 at 12:48 PM, Marko Asplund
wrote:
> On Wed, 09 Jul 2014 07:23 Martin Grigorov wrote:
>
> > > ...
> > > try {
> > > response = (HttpServletResponse)asyncContext;
> > >
> >
> > Maybe it is implementation detail that this cast works but usually you
> have
> > to
On Wed, 09 Jul 2014 07:23 Martin Grigorov wrote:
> > ...
> > try {
> > response = (HttpServletResponse)asyncContext;
> >
>
> Maybe it is implementation detail that this cast works but usually you
have
> to use
>
http://docs.oracle.com/javaee/6/api/javax/servlet/AsyncContext.html#
On 09/07/2014 08:43, yanchun.y...@finnova.ch wrote:
> Hello,
>
> We got a serious problem on our online banking applications: a user U1 of
> bank A got to see the data of another user U2 of another bank B.
> It happened only once, before and after that went everything well.
>
> The two same onli
On 08/07/2014 23:18, Marko Asplund wrote:
> Hi,
>
> I'm just starting out with using the Servlet 3.1 asynchronous processing
> API.
> I use the API for generating response content, that can potentially be a
> slow process, in another thread.
> The code appears to be working, but since the specific
Hi.
This kind of question is very difficult to answer reasonably, for anyone that is not you
and does not have direct access to your system, to see what happens, when it happens.
The general and reasonable answer would be that you need to use some monitoring tools, to
find out where exactly the
Hi,
I had a look at the documentation and the tomcat source to get a better
understanding
of what the '|org.apache.catalina.connector.RECYCLE_FACADE' parameter
actually does.|
I have seen that Tomcat objects like Cookies, Request etc. are designed
to be reusable.
What I currently do not unde
Hello,
We got a serious problem on our online banking applications: a user U1 of bank
A got to see the data of another user U2 of another bank B.
It happened only once, bevor and after that went everything well.
The two same online banking applications are running on one instance of tomcat
(V.6
Hi,
On Wed, Jul 9, 2014 at 1:18 AM, Marko Asplund
wrote:
> Hi,
>
> I'm just starting out with using the Servlet 3.1 asynchronous processing
> API.
> I use the API for generating response content, that can potentially be a
> slow process, in another thread.
> The code appears to be working, but s
On Wed, Jul 9, 2014 at 4:47 AM, Hernán Marsili wrote:
> Hi,
>
Hello Hernán,
>
> For the past 4 years we has been working with a 'stable' configuration in
> which we put APACHE in front of TOMCAT7 (previously Tomcat6) with mod_jk
> connector. We usually serve high traffic sites with about 7000
20 matches
Mail list logo
