Hi all,
I am getting a weird error on tomcat 7. at first i deploy my war file and
everything is smooth.. but after some time - randomly - i cant access
anything on tomcat and in the log file I see these lines:
Jan 17, 2012 11:37:37 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE:
### Summary
TC fails to compile JSP when 1) the compiler is AntCompiler and 2) there
is a whitespace somewhere in the pathname to TC home dir.
Configuring logging.properties to have AntCompiler set to level FINEST,
logs show that:
- whitespace is translated to "%20";
- javac task fails with many
Hi.
I'll follow-up with an "out of band" message just for now.
It was not very clear from your initial explanations whether you were sending all of the
1000, 2000, .. 8000 "person's data records" at once, in one HTTP POST, or sending the data
in a person-by-person way.
So my wild guess was base
On 16-01-12 22:26, Pid wrote:
The JConsole and VisualVM applications provided with the JDK will tell
you how much memory is being consumed by the application in various
areas of the Java program's process heap.
You may use them to observe behaviour during the operation you are
experimenting with
On 16/01/2012 20:12, Bert Verhees wrote:
> Thanks, André, for your reply
>
>>
>> Is that per "person", or per POST ?
>
> It is per Person AND per post. The post creates a person-object which is
> stored in a database, and the person-object is formed out of an array of
> strings.
>>
>> to an webse
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 5.5.35 stable.
Apache Tomcat 5.5.35 is primarily a security and bug fix release. All users
of older versions of the Tomcat 5.5 family should upgrade to 5.5.35.
Please refer to the change log for the list of changes:
http
Thanks, André, for your reply
Is that per "person", or per POST ?
It is per Person AND per post. The post creates a person-object which is
stored in a database, and the person-object is formed out of an array of
strings.
to an webservice-call.
After some validation, the webservice
of w
Bert Verhees wrote:
Hi, I hope you can help me analyzing this problem:
I am using Tomcat6 6.0.32-5ubuntu1.1 together with Axis2 1.6.1
I am not sure if it is an Axis2 problem or a Tomcat-problem.
I have an client-application for test-purposes which runs inside the
Eclipse-IDE.
The problem only
On 1/16/2012 11:50 AM, S Ahmed wrote:
Meaning I have to run tomcat 2 times?
I thought it would be possible to have a single instace of tomcat running,
and 2 different applications running on seperate jvms.
Thanks for clarifying.
So there memory cost is even higher since you need 2 tomcats runn
Meaning I have to run tomcat 2 times?
I thought it would be possible to have a single instace of tomcat running,
and 2 different applications running on seperate jvms.
Thanks for clarifying.
So there memory cost is even higher since you need 2 tomcats running.
On Mon, Jan 16, 2012 at 11:17 AM,
Tomcat itself runs inside JVM, so you need 2 JVMs each with tomcat and your
app.
Separating apps is a good practice because of classpath issues
Ilya Kazakevich,
Developer
JetBrains Inc
http://www.jetbrains.com
"Develop with pleasure!"
>-Original Message-
>From: S Ahmed [mailto:sahmed1.
Hi, I hope you can help me analyzing this problem:
I am using Tomcat6 6.0.32-5ubuntu1.1 together with Axis2 1.6.1
I am not sure if it is an Axis2 problem or a Tomcat-problem.
I have an client-application for test-purposes which runs inside the
Eclipse-IDE.
The problem only occurs when running
If my tomcat has 2 web applications running on it, how do I create
different jvm pools to keep the apps isolated?
On 16/01/2012 14:06, Daniel Pyykkö wrote:
> Hi Mark,
>
> So this means that the JSESSIONID is no longer removed from the
> requestURL by tomcat (and is thereby now propagated all the way) and
> we as developers of our product must now take that in consideration
> that JSESSIONID is returned as par
Hi Mark,
So this means that the JSESSIONID is no longer removed from the requestURL by
tomcat (and is thereby now propagated all the way) and we as developers of our
product must now take that in consideration that JSESSIONID is returned as part
of the URI when calling for example httpServletRe
Hi Andre,
We have read about the Eod of life for Apache Tomcat but as per
company standard we need to follow the same.
If you can provide me information realted to the upgradation as
requested will be of great help.
Regards,
Deepak
On 1/16/12, André Warnier wrote:
> Deepak Mishra wrote:
>> Dea
Deepak Mishra wrote:
Dear Sir/Ma'am,
We are planning to upgrade tomcat from 5.5.20 to 5.5.34.
Have you read this ?
http://tomcat.apache.org/tomcat-55-eol.html
As I have
never done this up-gradation was wondering if we can directly upgrade
from 5.5.20 to 5.5.34 or we need to go step by step.
Dear Sir/Ma'am,
We are planning to upgrade tomcat from 5.5.20 to 5.5.34. As I have
never done this up-gradation was wondering if we can directly upgrade
from 5.5.20 to 5.5.34 or we need to go step by step. Also can you
please provide me the link to download the patch, mentioning the
specific s/w t
On 16/01/2012 12:45, Daniel Pyykkö wrote:
> Hi,
>
> I seem to have found a problem in tomcat 6.0.35 that did not exist in
> 6.0.32 or prior to that version that I would like to know if I should
> file as a bug or if it exists a solution to it (it seems to be a
> coding bug but just in case, I run
Hi,
I seem to have found a problem in tomcat 6.0.35 that did not exist in 6.0.32 or
prior to that version that I would like to know if I should file as a bug or if
it exists a solution to it (it seems to be a coding bug but just in case, I run
tomcat on a MAC).
The problem occurs when sending
20 matches
Mail list logo