For a few days, I have been breaking my head over this issue:
My goal is to create a filter which detects Ajax calls (using jQuery for
Ajax, which adds X-Requested-With: XMLHttpRequest to the request headers).
If some jsp is requested by an Ajax call, I want to process the jsp's output
with this
JVM's are part of the same group of services, I
have included this thread dump.
Any idea, anyone?
http://www.nabble.com/file/p20930602/20081210_isapi_redirect.zip
20081210_isapi_redirect.zip
http://www.nabble.com/file/p20930602/20081210_threaddump.txt
20081210_threaddump.txt
Jesse Klaasse
Hi Rainer,
Thanks for jumping in again..
Rainer Jung-3 wrote:
When using big heaps, you need to take extra effort to get your GC
settings right. Do you have GC-Logs? What are the JVM options you use to
start Tomcat?
The JVM options:
-Dcatalina.base=D:\tomcat -Dcatalina.home=D:\tomcat
this problem for the
most part, but a mapper which is actually a complete file system tree seems
rather disk/cpu intensive to me.
Can anyone think of another solution for the jsp:forward problem in this
case?
Leon Rosenberg-3 wrote:
On Mon, May 26, 2008 at 3:59 PM, Jesse Klaasse [EMAIL PROTECTED
, the
uri_select key hasn't been set for the Isapi Redirector, so I guess
default mode (proxy) is used.
Anyone? Thanks in advance! Kind regards, Jesse Klaasse.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e
André Warnier wrote:
It would appear (from the logs), that there is some double-encoding of the URI
going on.
[snip]
But, if somewhere along the line, a piece of code was receiving the encoded
URI http://.../test%5Bbrackets%5D.jsp;, and decided to re-encode it again
using the % hex hex method,
André Warnier wrote:
[...]
Now, I should add that using [ and ] in URL's is not really something I would
recommend, if only for legibility reasons. It will always make people wonder
if what they're seeing in the logfile is normal, or if it's some programming
syntax which escaped there.
And I
I have migrated a customer's server system to the following
configuration:
MS IIS 6.0 (port 80)
Unlimited connections
Connection timeout: 120s keep-alive
JK 1.2.25 AJP/1.3 Connector
isapi_redirect.properties:
uri_select=parsed
workers.properties:
connect_timeout=1
prepost_timeout=1
tomcat instances are busy or in error state
[Wed Jul 02 15:39:34.690 2008] [11800:10604] [error]
HttpExtensionProc::jk_isapi_plugin.c (1527): service() failed with http
error 503
Jesse Klaasse wrote:
I have also tried the 1.2.26 connector. It seemed like it needed a
restart even sooner
Hello Rainer,
First of all, thank you for your extensive answer and the time you have
taken to write the answer, this really gives me hope.
Rainer Jung-3 wrote:
Double check: The worker is a member of a load balancer. the member is
*not* in state STOP (because that is a configuration
Hi Rainer. Thank you very much for this preliminary information. I had
already noticed the AbandonedObjectPool messages myself.
My resource configuration:
name=bam/jdbc/vip8db
auth=Container
type=javax.sql.DataSource
username=***REMOVED***
password=***REMOVED***
Hello Rainer,
Thanks again for your prompt and clear reply. You're helping me a lot!
I have implemented the settings as you suggested (for the datasources of all
8 webapps on my Tomcat server). I need to wait for a restart of the
application before the settings become active, however.
For your
have any clues left?
Regards, Jesse.
Rainer Jung-3 wrote:
Hi Jesse,
Jesse Klaasse wrote:
Hello Rainer,
Thanks again for your prompt and clear reply. You're helping me a lot!
I have implemented the settings as you suggested (for the datasources of
all
8 webapps on my Tomcat server
these values to a higher value? What I
especially don't understand, is the reappearance of wait... after 10
seconds.
Again, thanks for your help so far! Regards, Jesse.
Rainer Jung-3 wrote:
Jesse Klaasse schrieb:
Hi Rainer,
We are a week later now, with the changed settings, and while
I will try to remove/increase socket_timeout to see what happens..
Unfortunately, Tomcat hung again today. It managed to work again without
manually restarting, but again, the 503 message for a while..
I attached two thread dumps and an excerpt of today's isapi_redirect.log.
BTW, this is APR
Pid Ster wrote:
Have you tested those memory and garbage collection settings with this
version of Java?
Well, actually I haven't touched the settings which I used using Java 5.
But, I have tested the settings to some extent. My development environment
worked perfectly fine using the same
Leon Rosenberg-3 wrote:
they are all seem to be either in an infinite loop:
at java.util.AbstractList$Itr.hasNext(AbstractList.java:339)
at
nl.indicia.vip.framework.util.Workflow.performWorkflowAction(Workflow.java:166)
at
Jesse Klaasse wrote:
Those Workflow and DQWorkflow classes are from our company, written by the
programmer who worked on this project before me. I have attached the two
files for further examination.
I have noticed the performWorkflowAction method in DQWorkflow is not
synchronized
Hi Leon,
I don't know what you mean exactly by re-intrant, but your comment points
out I have created an endless while-loop! Apart from moving to Java 6, I had
commented out some lines to reduce logging, not noticing I had created an
endless loop by doing so. I only did this in a jar compiled
I have now fixed the infinite loop, and again did the update from Java 5 to
Java 6. This time all seems to be working like a charm!
Along with fixing the infinite loop, I have dug a little deeper into the JVM
arguments. I found the following article particularly useful:
I also added the -XX:+UseCompressedOops JVM option (as suggested in the
Confluence article I mentioned earlier). BTW, for those who want to know:
this option is available since update 14 of JDK 6 (see also
http://java.sun.com/javase/6/webnotes/6u14.html), you don't need the
Performance branch as
Hi Chuck, thanks for your extensive comments about the JVM options..
n828cl wrote:
-Xms10240m -Xmx10240m
That's a very large heap; shouldn't hurt as long as you have enough RAM to
support it all without paging. (But see below for use with compressed
OOPs.)
This shouldn't be a
In the meantime, the environment has been much more stable than it was before
the move to Java 6 and the new JVM options. However, a few minutes ago,
Tomcat became completely unresponsive, while the CPU usage was very low
(~3%). This was on our external server, with these options:
Christopher Schultz-2 wrote:
Can you give us a timestamp for when the trouble started? Reading GC
output is pretty tedious.
I believe the trouble started around 15 - 20 minutes before the end of the
gc log, so that would be from ~61h36m.
Christopher Schultz-2 wrote:
Also, what
24 matches
Mail list logo
