On 19.06.2010 03:46, Neil Aggarwal wrote:
Rainer:
Hmmm, errno 11 is often EAGAIN. What platform are you using
(OS, version)?
I am using CentOS 5.5 freshly installed, not an upgrade.
I tried that as a fix to this problem. I wiped the server
clean and reinstalled everything from scratch. It
I moved hosting provider and have found eapps to be excellent. Despite the
same version of tomcat and same layout, I am unable to resolve this
exception. my databases are correct, the jdbc jar is in tomcat/lib. I don't
know what more to do :(
Rainer:
would you mind opening an issua in Bugzilla, attaching your
log snippet
and possibly your workers.properties
I created bug 49468 in bugzilla, included my log snippet and
attached the workers.properties file.
You can also open a second issue concering the obvisouly wrong
I have no choice left but to not let hibernate use my tomcat datasource. This
is not good. I have even moved host provider in hope that it was previous fult
tomcat install from dailyrazor (tomcat 6 does not hav common/lib) and is meant
to have tomcat/lib
I can say that my new container is
On 6/19/2010 1:31 PM, yucca...@live.co.za wrote:
I have no choice left but to not let hibernate use my tomcat datasource. This
is not good. I have even moved host provider in hope that it was previous
fult tomcat install from dailyrazor (tomcat 6 does not hav common/lib) and is
meant to
On 17/06/2010 08:59, Robinson, Eric wrote:
If your heap size is right on the edge of your minimum for a Tomcat
instance, you may be doing more GC work than is really needed.
However, if you're satisfied with the response time and CPU
utilization, you should be ok.
Time to hit the vendor
Robinson, Eric wrote:
On 17/06/2010 08:59, Robinson, Eric wrote:
If your heap size is right on the edge of your minimum for a Tomcat
instance, you may be doing more GC work than is really needed.
However, if you're satisfied with the response time and CPU
utilization, you should be ok.
Time
Just a note here : 160 X 512 MB = 81 GB. If each Tomcat's
JVM Is allowed to use up to 512 MB of Heap, there might be
moments where a lot of JVM's will be using close to that
amount. Unless your system can really support that amount
of real RAM, you may be in for massive swapping.
On Jun 19, 2010, at 18:31, André Warnier a...@ice-sa.com wrote:
As Mark writes above (and my interpretation of things) :
- a bigger Heap means that the JVM will be able to accumulate more
dead stuff in it,
- when it is needed however, it will take much longer, because there
is more
