dear Dan
Thanks a ton for the detailed info I will try it out in a couple of days. This
email had got into my spam folder and I had missed it till today
rgds,
nandy
On Wed, 2/25/15, Daniel Mikusa dmik...@pivotal.io wrote:
Subject: Re: Help setting
Brian,
This list is a Tomcat help list. We specialise in helping people resolve problems related
to using Tomcat, and Tomcat is a Java Servlet Engine : a specialised kind of webserver,
whose main purpose is running Java servlets (a kind of Java program written specially to
be run in such an
My host is http://zedlabs.in .
Please suggest me the appender file configaration so that it generates the
log in my j2ee application folders.
*Thanks and Regards,*
Muralidhar Yaragalla.
*http://yaragalla.blogspot.in/ http://yaragalla.blogspot.in/*
On Sat, Feb 28, 2015 at 11:32 PM,
Hello
I'm trying to set-up an EventSource servlet, yet Tomcat seems to be adding
Transfer-Encoding: chunked header to my responses, so they trigger the
onerror handler on my EventSource object.
According to some, setting org.apache.coyote.http11.Http11NioProtocol as
the protocol on my http
Hello again :)
Apparently adding Connection: close header to my response prevents the
evil heaqder to be added.
And it turns out the header isn't the reason why EventSource receives the
message-less error.
Cheers
Jarda
On Sat, Feb 28, 2015 at 9:54 PM, Jaroslav Záruba jaroslav.zar...@gmail.com
Hi i have given the following configaration in log4j.properties file
log4j.appender.file.File=${rootPath}WEB-INF/logs/Zedlabsloging.log
The above configuration is generating log file in my d: drive. but i want
to generate log file in my applications WEB-INF folder. What configaration
should i
Root cause?
On Feb 28, 2015, at 15:20, Jaroslav Záruba jaroslav.zar...@gmail.com wrote:
Hello again :)
Apparently adding Connection: close header to my response prevents the
evil heaqder to be added.
And it turns out the header isn't the reason why EventSource receives the
message-less
Hello
I still have no clue. I tend to think EventSource simply works like that,
that is triggering the onerror handler (if you have set-up one) after a
response gets delivered. (Even a 200-status response.) And one simply has
to decide how to deal with such pseudo-error. If the readyState of your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Muralidhar,
On 2/28/15 1:02 PM, Yaragalla Muralidhar wrote:
Hi i have given the following configaration in log4j.properties
file
log4j.appender.file.File=${rootPath}WEB-INF/logs/Zedlabsloging.log
The above configuration is generating log
