Hi,
as a reminder: I will summarize test feedback for mod_jk 1.2.16 late
friday, and provided positive test results the Apache Tomcat project
will proceed to vote on the final release. Until now only about 10
downloads happened, so we need more users to participate!
To ensure a quality release
Hello,
I think you found a real bug. Could you please try the following patch:
Index: jk_status.c
===
--- jk_status.c (revision 418136)
+++ jk_status.c (working copy)
@@ -755,13 +755,9 @@
i = status_bool(wd,
Several people now tried it and the code is much cleaner, so chances are
very good, that the busy part is correct now. Of course, the version is
not finally released now, so the user base of it is still pretty small.
If this is so important for you, you should neverthelese use some script
to
Hi,
Lopez Jarillo, Cesar schrieb:
Hello all,
I'm installing mod_jk.so version 1.2.14 on Apache 2.0.55 (Solaris 8 OS). I've
compiled the source code
You should definitely not use 1.2.14. For example have a look at
http://issues.apache.org/bugzilla/show_bug.cgi?id=36525
If you need the
Hello,
if you would give detailed information about your problems, we could
advise you, whether it is known, and whether it has been fixed in some
version.
The latest release is 1.2.15, we tried to produce a 1.2.16 release, that
but it has now been withdrawn because of a regression bug. Another
It might not be the reason for your problems, but you should not start
this with an apache version that old. If you want to use mod_jk,
consider first updating to apache 2.0.58 or something close to it.
Is your JkWorkersFile readable for the apache user?
I never noticed such behaviour, so no
to release
1.2.17.
Regards,
Edmon
On 7/11/06, Brian Munroe [EMAIL PROTECTED] wrote:
On 7/3/06, Rainer Jung [EMAIL PROTECTED] wrote:
version 1.2.16 of the Apache Tomcat mod_jk web server connector has
been
tagged. This version contains numerous bug fixes and some new
improvements
Hi,
thanks to everyone who tested 1.2.16. Unfortunately we had one
regression bug in the status worker (hanging update request because of
double locking). For full results please see:
http://marc.theaimsgroup.com/?l=tomcat-devm=115234851210076w=2
Today version 1.2.17 of the Apache Tomcat mod_jk
Which platform are you using?
You can increase JkLogLevel to trace and then check the log during
startup of apache. Maybe something is wrong with the permissions on the
shared memory file which is being used by the status worker.
Could you post the log of startup+request for jkstatus?
About
You already posted the same question 4 days ago. I replied and got no
answer from you. Here is my original reply.
Which platform are you using?
You can increase JkLogLevel to trace and then check the log during
startup of apache. Maybe something is wrong with the permissions on the
shared
Hi,
thanks to everyone who tested 1.2.17. We had one bug related to special
types used in the networking code. Furthermore there was one request for
enhancement we included in the next version 1.2.18.
Today this version 1.2.18 of the Apache Tomcat mod_jk web server
connector has been
Whops: we had some hassle with the files and it looks like the docs has
been unintentionally erased by myself. It's there on the source web
server now, thanks for the information.
It might take an hour or two to replicate to the public web server. If
you need it earlier: the docs are included
When you are starting or restarting Apache it should log a line similar
to the following:
[Sat Jul 22 07:59:41 2006] [notice] Apache/2.0.58 (Unix) DAV/2
mod_jk/1.2.15 configured -- resuming normal operations
It includes the mod_jk version (mod_jk/1.2.15).
The same should be found via
combined
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Friday, July 21, 2006 11:15 PM
To: Tomcat Users List
Subject: Re: Load Balance not working for mod_jk???
When you are starting or restarting Apache it should log a line similar
to the following
is 1.2.15 to be found at
http://tomcat.apache.org/download-connectors.cgi
Rainer
Patrick Wang schrieb:
You are Right, the Strings things work great, which shows the version of the
mod_jk 1.2.6.
Pat
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Monday, July 24
Hi,
I'm right now building from subversion head of 5.5 and I don't get the
error, although the URLs look exactly the same::
Rao Jianguo schrieb:
downloadgz:
[get] Getting:
http://switch.dl.sourceforge.net/sourceforge/mx4j/mx4j-3.0.1.tar.gz
[get] To:
mod_jk 1.2.17 had a subtle build problem e.g. on AS400 platform. There
is no known problem on Linux. Glad to hear it also worked for you, but
you should nevertheless take the next opportunity and move to the
official release. 1.2.17 will never be officially released. Furthermore
1.2.18 added a new
Hi Michael,
Michael Huettermann schrieb:
The whole system is on my desktop:
Apache/2.0.55 (Win32) mod_jk/1.2.17
when using Apache 2 depending on the used MPM the worker cachesize
should not be 1:
worker.node1.cachesize=1
#worker.node2.cachesize=1
If your MPM is prefork, then 1 is actually
The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.18 of the Apache Tomcat mod_jk web server connector.
mod_jk is a connector which allows a web server such as Apache HTTPD
to act as a front end to the Tomcat web application server.
This version contains
Tomcat will not load any webapp jar containing javax.servlet.Servlet or
javax.servlet.jsp.JspPage. I would suggest to remove package
javax.servlet from your j2ee.jar. Furthermore trouble is to be expected,
if you try to load classes java.* from webapp jars.
I guess you don't use the security
I know this sounds very general, but 1.2.10 is quite antique. First
update to 1.2.18, try again and if your problem is still reproducible,
post your config (workers.properties and Jk* from httpd.conf) and
relevant parts of the mod_jk-Logfile with LogLevel trace.
Also try to relate tcp connection
You should download the most recent release jk-1.2.18 under
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/
Concerning 1.2 vs. 1.3:
There are AJP protocol version 1.2 and 1.3. Tomcat and mod_jk support
both, but 1.2 has been deprecated a long time ago. This is independant
of
example:
localhost/abc.html;jsessionid=afsdfasdf?test=abc
or
localhost/abc.html?;jsessionid=adsfasdftest=abc
which of the above is correct?
The first one.
Rainer
-
To start a new topic, e-mail: users@tomcat.apache.org
Could you please try the following patch to native/apache-1.3/mod_jk.c,
that should also work with older apache versions:
===
--- mod_jk.c(revision 423615)
+++ mod_jk.c(working copy)
@@ -2039,8 +2039,13 @@
}
else
Since you are using Apache 1.3: By theory setting the value to 1
should not be necessary. To understand what's going on: could you
increase JkLogLevel to trace and send us parts of the output around a
request producing a 503 error?
Java Rab wrote:
I have setup load balancing between Apache
mod_jk neither supports round-robin, nor random load-balancing.
Currently you can choose between three algorithms:
method=B (busyness): choose the worker with the lowwest number of
requests currently in processing.
method=R (requests): choose the worker that did the lowest number of
Hi,
first of all I assume you are using version 1.2.18 of mod_jk? Otherwise
please update.
Sharma, Siddharth schrieb:
We have a 12 (tomcat 5.5.16) instance cluster on 4 physical machines running
redhat linux. There is an Apache installed on each machine (4 mod_jks). Each
mod_jk's
Hi,
Mohan Wickramasinghe schrieb:
Hello
We are using the new Busyness method with 1.2.18
We have also using 'sticky sessions'.
Clarification on
As soon as there will be real load, behaviour will differ.
We have 9 nodes on 3 identitical servers with identical settings, lb
factor
Hi,
Mohan2005 schrieb:
Hello
Thaks. We will enable loggin to find this, but since its a production setup
will it affect performance ?
The numbers suggest, that you've got
210.000 * 12(instances) / 21 (days) = 120.000 requests/day
So depending on the time distribution, this should boild
jk2 has been deprecated quite some time ago. You might find some help
for it on this list, but you should seriously consider migrating to
mod_jk. The module mod_jk (*not* mod_jk2) is still being actively
developed and most features of mod_jk2 have been backported to mod_jk in
the meantime.
Mohan2005 wrote:
On the 'P' option which was recommended by Mladen Turk some time ago when we
had issues (share memory locking) with a older version of mod_jk ( 1.2.15),
we have left it as it is.
There definitely were issues concerning optimistic locking around
1.2.15, but we expect them to
jeusdi wrote:
If there is no choice can I use mod_jk in Apache2? I say it because I
perform aptitude install mod_jk in my ubuntu Brezzy and it downloads
apache1.3, but I want use Apache2 with mod_jk. Can I use mod_jk with
Apache2?
Uaaah. mod_jk 1.2 works with Apache 1.3, 2.0 and 2.2. The
Artur wrote:
Hello,
We have environment with Apache (2.2.0) + Tomcat (5.5.17) connected via
mod_jk (1.2.18). Further tomcat makes some queries to databese through
Tuxedo services (BEA).
Everything works fine until heavy load when something stops responding
(Service not available).
We think it
Hi,
thanks for the feedback. Good info!
fredk2 schrieb:
issue 1:
With mod_jk 1.2.15 i set my jk log level:
JkLogFile logs/mod_jk.log
#JkLogLevel info
JkRequestLogFormat %w %V %U %s %T %B %H %m
While switching to 1.2.18 I read in the fine manual that the default
Hi,
Artur schrieb:
- does it happen in times, when you get errors in the mod_jk-log? Does
it happen at all times, or do you have peaks at special times?
I can't figure it out, when this happens, but there isn't any special
moment I can observe.
It happens randomly. There isn't any error
I can load your workers.properties configuration using 1.2.18 (but I
Used Apache 2 and Solaris). The validate method code says, that either
there should be a message of level error before the first one you
copied to your mail (and that one will give us a better indication about
what's wrong), or
You should try 1.2.18 and depending on your time frame update to 1.2.19
once it's being released this month.
We improved load balancing code and with 1.2.19 also the observability
of what's happening.
Try the alternative method B (Busyness) for the load balancer in 1.2.18.
The default method
What about changing
worker.worker1.mount=/foo/* foo
to
worker.worker1.mount=/foo/* /foo
Regards,
Rainer
james edwards schrieb:
I am moving to jk (1.2.18) from jk2 am having problems with the
workers.properties file. I have separate apache and tomcat servers. Here is
my working jk2
Marc Richards wrote:
Also you can configure Apache to log the value of the
session cookie (if you're using session cookies --
LogFormat %{JSESSIONID}C...), which includes the lb
route so that you even know which instance of Tomcat
took the request.
... and finally once we release the next
Hi,
version 1.2.19 of the Apache Tomcat mod_jk web server connector has been
tagged. This version contains numerous bug fixes and some new
improvements over our last release 1.2.18. Please test and share your
experience. Your feedback helped us a lot during the previous release,
so we hope there
Hi,
I'm looking for a community member, who is willing to write a little
documentation about the status worker of mod_jk. We added a lot of new
information to it in the most recent release (candidate) 1.2.19 and I
think it would be worth writing a couple of lines about it. I can help
in answering
Hi,
in the last weeks, there were some discussions, about how to make mod_jk
automatically map requests which are url encoded (;jsessionid=).
Although in most cases it would be better to have a clear url structure
which you can use with JkMount, I understand that sometimes it will be
with no problems. I believe this means that there probably isn't
incorrectly encoded data.
I'll keep looking and will respond again if I an find the problem.
Thanks for the help.
James
On Sat, 16 Sep 2006 17:44:23 +0200
Rainer Jung [EMAIL PROTECTED] wrote:
I tried with mod_jk 1.2.18 and Apache
If you are willing to use the latest 1.2.19:
http://tomcat.apache.org/dev/dist/tomcat-connectors/jk/binaries/
This one is not yet officially released. The release vote will start
tomorrow, but until now no problems have beend found. So I'm confident,
that it will get official in very few
The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.19 of the Apache Tomcat mod_jk web server connector.
mod_jk is a connector which allows a web server such as Apache HTTPD
to act as a front end to the Tomcat web application server.
This version contains
The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.19 of the Apache Tomcat mod_jk web server connector.
mod_jk is a connector which allows a web server such as Apache HTTPD
to act as a front end to the Tomcat web application server.
This version contains
This is not an expected behaviour.
Any errors on the mod_jk or the tomcat side?
What are your mod_jk settings (Jk* ind httpd.conf and
workers.properties), what are your AJP13 connector settings on the
tomcat side?
Regards,
Rainer
Jean-Bernard BRIAND wrote:
Hello,
Thanks for your respawn
Yes :)
You can use it to inherit properties via multiple steps. But be careful,
it doesn't check for loops!
To make sure before I answered, I did a little check with a slightly
enhanced configuration:
# Make config observable
worker.list=status
worker.status.type=status
I'm not sure about the iis redirect, but in general mod_jk only permitts
patterns with a leading slash /. So please try /*.jsp.
Regards,
Rainer
Fisher, Mitchell L schrieb:
There is no problem with the missing arrow.
http://support.microsoft.com/kb/317204/en-us says:
In Internet Information
Hi,
if apache has the right idea, which hostname has been adressed and you
use mod_jk, usually you get the right redirects. If apache doesn't know,
because of ssl offloading or load balancers hiding the correct
information, you can set attributes on the tomcat side in server.xml to
the connector
Maybe I missed something, but I didn't see a worker.list in the
configuration.
Mladen Turk wrote:
VikasSharma-ATG, Noida wrote:
That's it, there's nothing after these lines when I access my
application. No errors, just the debug lines. I've checked
isapi_redirect.dll has execute and write
Thanks for the info. The docs are not in good shape, eventually there
will be more broken links.
I fixed the links in the Installation section be referring to the new
docs in HowTos.
Should be synced to the main web site in an hour or so and will be
included in the next release.
Rainer
JWM
The broken pipe error generally means, that the client (browser/ab)
closed the connection before tomcat finished sending it's response.
Most often this happens, when an answer takes longer, than users
expect/tolerate and the users pressed refresh, stop etc. Possibly also,
if you use a short
Hi Martin,
Martin Kautz schrieb:
Rainer,
Thank you, but I'd like to know a bit more. Is there a way to avoid
pipes get
broken? Even if this issue does not affect the user's expirience I'd
like to get rid of that log file pollution.
I forgot to mention that the issue only applies to
Hi Torsten,
you could try the FlushPakets JkOption from
http://tomcat.apache.org/connectors-doc/config/apache.html
Please let us know, if this helps. If not, please open a bugzilla ticket
and include your config and a simple test case.
Regards,
Rainer
Torsten R. schrieb:
hi,
i used
hi Jeff,
any tomcat log messges during startup?
Regards,
Rainer
Jeff Weinberger wrote:
Rainer:
Thank you very much for your help!
Sorry about the IP address confusion - I chose badly in including log
entries. I tried this with localhost (127.0.0.1) and I also tried it to
be accessed from
.-IdNr. DE 196 457 417
Geschäftsführer: Dr. Thomas Höfer, Rainer Jung, Sven Maurmann
===
kippdata
informationstechnologie GmbH Tel: +49 228 98549 -0
Bornheimer Str. 33aFax: +49 228 98549 -50
D-53111 Bonn www.kippdata.de
HRB 8018 Amtsgericht
Peter Kennard wrote:
Doesn't AJP multiplex traffic, that is queued up requests are
serialized through one connection that remains connected and it
switches between servlets on the receiving end? and recycles the
execution thread?
No multiplexing on connections.
Regards,
Rainer
At 19:19
Peter Kennard wrote:
Hmm I woudl have thought otherwise, since after reading the protocol it
seems specificly designed to support keeping connection alive.
That a sender would keep a pool of available connections and when a
hit comes in get one which is already connected, and push the request
JkMount works with respect to URLs, not file system pathes:
Use
JkMount /jsp-examples/* damnjk
instead of
JkMount /usr/local/tomcat5.5/webapps/jsp-examples/* damnjk
There might be further config bugs after fixing this one :)
Regards,
Rainer
Mario Pavlov wrote:
Hello guys
Hello,
module binaries for Apache httpd 2.0 and 2.2 are definitely
incompatible. Combining httpd 2.0 and mod_jk compiled for 2.2 will
result in completely undefined behaviour!
Although most modules compile unchanged from source for 2.0 and 2.2 (so
does mod_jk), the resulting binary only
N/A as a state means, that no requests have been sent to this worker for
some time. So mod_jk is not really able to tell you about the state of
the worker. It can only detect OK, ERROR etc. when it is sending
requests to the workers. No requests, no state.
A worker will be in state N/A
Usually there are SSL problems with (reverse) proxying concerning URLs
for redirects, since the Tomcat side doesn't know any longer that SSL
has been spoken originally. So self-referencing URLs use http as the
protocol. AJP fixes this, which is the correct interpretation of AJP
supporting SSL
As a first approximation this is true. But ProxyPassReverse does not
rewrite the body of responses. So if there is a wrong URL in the body,
then this will not be fixed by ProxyPassReverse. It is mostly (or only?)
for fixing the Location header in http redirects.
Regards,
Rainer
Erik
Melkersson
Rainer Jung wrote:
N/A as a state means, that no requests have been sent to this worker
for some time. So mod_jk is not really able to tell you about the
state of the worker. It can only detect OK, ERROR etc. when it is
sending requests to the workers. No requests, no state.
A worker
Just a guess: looks like SSL is waiting for /dev/random (blocking
random) to answer, and /dev/random can take a long time to answer if
there's not enough entropy in the system.
Usually you can choose betwenn /dev/random and /dev/urandom (non
blocking but cryptographic quality depending on
Possible entry point:
On tomcat.apache.org there is a menue point Migration Guide at the end
of the Documentation menue, often overlooked, because it's relatively
new and not inside the tomcat 6 docs. The Guide is very short, but might
give you some ideas.
http://tomcat.apache.org/migration.html
Hi Henk,
your analysis is right, it's a known deficiency and not easy to fix (not
in 1.2.x).
A couple of releases ago we added a note in the status worker docs page
http://tomcat.apache.org/connectors-doc/reference/status.html
Special Considerations concerning URL Maps and Virtual Hosts
Hi Peter,
have a look at the online docs, especially the apache page inside the
refrence guide. There are a couple of JkOptions of type ForwardURIxxx,
with which you can configure URI encoding behaviour.
Regards,
Rainer
Peter Coppens schrieb:
Gentlepeople,
I have a weird problem where I
Hi Rajiv,
I could provide Solaris SPARC builds for:
- Sun Web Server 7.0 either 32 Bit or 64 Bit
- Sun Web Server 6.1 SP7 32 Bit
Unfortunately you seem to need 6.0 64Bit. This release does only exist
for Solaris 10. I'll try, if I can install it on Solaris 8, but I
assume, this will not work.
Please try again by adding
shm_file=/usr/jakarta-tomcat-5.5.0/conf/jk-runtime-status
to the block
Init fn=jk_init
worker_file=/usr/jakarta-tomcat-5.5.0/conf/workers.properties
log_level=debug log_file=/usr/jakarta-tomcat-5.5.0/conf/nsapi.log
in magnus.conf.
If this doesn't work, I'll
OK, I'll check, but give me one or two days ...
Maybe someone else has an idea in the meantime.
Rajiv M wrote:
Did the changes.
Server still shows error on startup:
[https-sun210dev2.in.ibm.com]: failure: CORE3170: Configuration
initialization failed: Error running init function jk_init:
Hi Rajiv,
the other downloads you found are for the apache web server. They will
not work with the sun web server.
I was able to use Sun Web Server 6.1 SP7 64 Bit Sparc on Solaris 10,
with the binary library nsapi_redirector.so_sjsws61_sp7_64 I provided.
There is (at least) one bug in the
The plugin exits, because it can't stat the worker file.
In the zip you attached, the worker file is called worker.properties, in
magnus.conf it's called workers.properties. Note the difference! I hope
that's the solution to your problem (point 4) in my previous email).
If that fixes your
Are you able to produce a stack dump (from a core) of the httpd process,
which is responsible?
Artur Różycki wrote:
Hello,
We are running Red Hat Enterprise Linux ES (v. 4 for AMD64/Intel EM64T)
as an Web server with Apache (2.2.4 compiled from sources) connected
through mod_jk (1.2.21
Rajiv M wrote:
BTW, Can the .so you supplied be used in production
Difficult to answer:
1) The non-debug .so is trunk code version. But trunk is *very* near to
be released as 1.2.22. So I think there is no special risk, apart from
the usual it's a brand new patch release. I'm confident,
You will definitely have to read a bit about standard configuration of
Sun Web Server.
The web server docs will tell you, that the order of NameTrans
directives is relevant. I expect the file system rule comes first in
your config, before the jk NameTrans.
If you want to debug such issues:
Artur wrote:
Hello after the weekend,
Does it mean that mod_jk 1.2.18 is not using flock() function at all ?
With 1.2.18 there is no kernel panic problem.
I have written to RedHat support to tell them that this flock() function
could be buggy.
It does use flock(), but maybe with another use
no-jk is a last minute exit from forwarding and comes after the usual
forwarding/strip session handling.
Try to use JkUnMount instead of no-jk. That should make your config
work, including stripping sessions.
Let us know, if that works.
Regards,
Rainer
Alexey Kakunin wrote:
Hello!
-0
Bornheimer Str. 33aFax: 0228 98549 -50
53111 Bonn www.kippdata.de
HRB 8018 Amtsgericht Bonn / USt.-IdNr. DE 196 457 417
Geschäftsführer: Dr. Thomas Höfer, Rainer Jung, Sven Maurmann
===
kippdata
informationstechnologie GmbH Tel: +49
A pool size of 1 for a thread count of 20 per process is somewhat
strange. But OK, you could insist on this wish. Yes, it should be
configurable like that.
Start apache with JkLogLevel debug and check the log file about messages
concerning the pool size. You don't need to produce any traffic
In this case, why not simply use (mini test jsp):
User: %=request.getRemoteUser()%
:)
Honestly: mod_jk forwards quote some information apache has to tomcat,
because mod_jk knows it's a reverse proxy situation. Besides the SSL
info mentioned on the apache page of mod_jk reference guide, there
Please post the log parts (debug log level) which appear when starting
apache. Those are the lines that show, how mod_jk parses your
workers.properties, and which internal objects it generates out of it.
-
To start a new
: Re: HowTo forward user name from apache via mod_jk to tomcat
Rainer,
Rainer Jung wrote:
In this case, why not simply use (mini test jsp):
User: %=request.getRemoteUser()%
Oh, hey, that's a lot better. No config or anything ;) I didn't realize
that REMOTE_USER was already being forwarded without
Thanks Mladen, and sorry for jumping in that late: yes JkWorkersFile is
global. Most others can be used in VHosts, but for Apache 2.0 most of
this was completed only recently in version 1.2.20. Before 1.2.20 (you
are using 1.2.18) some things worked in vhosts (like JkMount) even
before, but
If you can reproduce your problem without high load, you can use
JkLogLevel debug to understand, which of the steps take the most time.
This might give an idea about the root cause.
The log contains time stamps and you can post log parts around the
moments, where you seem to loose most of the
, Rainer Jung, Sven Maurmann
===
kippdata
informationstechnologie GmbH Tel: +49 228 98549 -0
Bornheimer Str. 33aFax: +49 228 98549 -50
D-53111 Bonn www.kippdata.de
HRB 8018 Amtsgericht Bonn / USt.-IdNr. DE 196 457 417
Geschäftsführer: Dr. Thomas
Please give details:
- software (apache, tomcat, mod_jk) and platform versions
- relevant parts of configuration (Apache Jk*, workers.properties,
Connectors and jvmRoute from server.xml)
- maybe parts of the log files showing your activity
Please note:
Sticky sessions use routing identifiers
The following characters are safe:
[a-z][A-Z][0-9][_\-]
A dot should be OK, but I would not bet on it, neither would we care, if
it won't. The above character set is given in the workers.properties
page of the reference guide.
Regards,
Rainer
Tim Lucia schrieb:
Is there still a
' source
'JkMount'
I don't know how to interpret this. Can anyone help?
Thanks!
Avi
On 4/20/07, Rainer Jung [EMAIL PROTECTED] wrote:
If you can reproduce your problem without high load, you can use
JkLogLevel debug to understand, which of the steps take the most time.
This might give
This is an unexpected protocol error between mod_jk and Tomcat. As far
as I know, there is no open bug concerning the protocol.
Can you reproduce it? Does it only occur during high load? If you can
easily reproduce it without high load, set your JkLogLevel to trace and
post the full log file for
common: shared between all webapps and tomcat itself
shared: only shared between all webapps
Luis Rivera schrieb:
Hi,
Just as a comment. I use the shared classloader by using the shared folder
to avoid loading multiple times my shared libraries (for jni use). I am not
sure what is the
... and finally don't forget, that the pathes used by these class
loaders are configured in conf/catalina.properties.
Luis Rivera schrieb:
Well, that makes sense and I have had no problems using the shared class
loader. I guess I did something wrong when I tried to use the common class
loader
It was implemented starting with versions 1.4.2_12, 1.5.0_07 and 1.6.0 FCS.
[EMAIL PROTECTED] wrote:
Hello,
i'm experiencing memory issues on the heap space.
The guy that handle the server can't set the -XX:+HeapDumpOnOutOfMemoryError
option in JAVA_OPTS of the catalina.sh file, since he get
In the working directory of the process. Of course you need enough free
disk space.
There is also
-XX:HeapDumpPath=DIRECTORY_OR_FILE
(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).
You should check in the process table (if
You neded to change your start/stop scripts, so that they use the
management parameters only in the starting case and not in the stopping
case (define a new variable and add it in bin/catalina.sh to the start
case.
[EMAIL PROTECTED] schrieb:
Now jconsole works but when i shut it down with
Thank's for reminding me, I forgot. But I think he uses 5.5.9 (very
outdated). CATALINA_OPTS was used for start and stop until 5.5.20, and
with 5.5.21 we switched to only using it for startup.
Peter Rossbach schrieb:
Please use CATALINA_OPTS to set jmx options. The catalina.sh stop
command use
Please update mod_jk. 1.2.6 is *very* outdated. We are now at 1.2.22 and
a lot of things have improved.
After upgrading, check your configuration against the reference guide in
the docs, especially the pages for the worker properties and Apache
directives. You might want to add some more
Brantley Hobbs wrote:
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the add some more timeouts comment? Do
you mean a higher number on connection_pool_timeout?
Have a look at connect_timeout and prepost_timeout. Usually I also use
Hi Christopher,
this usually happens, if the value of the CC environment variable during
the creation of libtool differs from the one used when you are using
libtool.
For example: one might use CC=gcc -specs=/my/own/specs/file when
libtool gets created and later use CC=gcc during mod_jk
1301 - 1400 of 2031 matches
Mail list logo
