Re: Tomcat loops indefinitely

2008-09-08 Thread Kjetil Kjernsmo
On Monday 08 September 2008 04:20:31 Konstantin Kolinko wrote:
 What is that address? Judging from the behavior, it occurs that it makes
 request back to itself.

That's actually a possibility. I checked the variable's value, and that had 
the correct value, so it shouldn't happen. What might happen is of course 
that some other part of the application may have overwritten something that 
caused it to go into that loop.

This morning, I just deleted absolutely everything, checked it out from SVN 
again, built it, and it runs. I guess I will never figure out what actually 
went wrong, but the important thing is that it runs, I guess...

Kind regards 

Kjetil Kjernsmo
-- 
Senior Knowledge Engineer
Direct: +47 6783 1136 | Mobile: +47 986 48 234
Email: [EMAIL PROTECTED]   
Web: http://www.computas.com/

|  SHARE YOUR KNOWLEDGE  |

Computas AS  Vollsveien 9, PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | 
Fax:+47 6783 1001


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat loops indefinitely

2008-09-07 Thread Konstantin Kolinko
Well, I do not know what DefaultSparqlDispatcher actually is, but googling found
the following source code of it:

https://submarine.computas.com/sublima/tags/0.9.5/blocks/sublima-query/src/main/java/com/computas/sublima/query/impl/DefaultSparqlDispatcher.java

Thus, the following line:
SettingsService.getProperty(sublima.joseki.endpoint);
is the address to where it opens an HttpURLConnection.

What is that address? Judging from the behavior, it occurs that it makes
request back to itself.

Best regards,
Konstantin Kolinko

2008/9/5 Kjetil Kjernsmo [EMAIL PROTECTED]:
 Hi all!

 I'm struggling with a really weird problem. I have a Cocoon 2.2 application
 that runs on Tomcat 5.5.25-5ubuntu1 and Java 1.5.0. My (semi-)production
 system, my test system and my development system are Ubuntu 8.04 boxes, and
 they differ very little, with the exception that the production environment
 is a Vmware slice, the others are not. The application runs fine on the
 development and test systems, but it is not at all working on the production
 box.

 What's happening is that I deploy the war, restart the server. I then GET a
 URL on the system, apparently, any URL will do. The application starts doing
 its thing. In my log, I see messages like
 http-8180-Processor230 DEBUG impl.DefaultSparqlDispatcher - SPARQLdispatcher
 connected to Joseki.
 http-8180-Processor229 DEBUG impl.DefaultSparqlDispatcher - SPARQLdispatcher
 connected to Joseki.
 http-8180-Processor228 DEBUG impl.DefaultSparqlDispatcher - SPARQLdispatcher
 connected to Joseki.

 which my application emits. The problem is that the application has apparently
 gone into a loop, as this appears to be different threads. Eventually, it
 runs out of threads, and comes to a halt:

 (...)

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat loops indefinitely

2008-09-05 Thread Caldarale, Charles R
 From: Kjetil Kjernsmo [mailto:[EMAIL PROTECTED]
 Subject: Tomcat loops indefinitely

 The problem is that the application has apparently
 gone into a loop, as this appears to be different threads.
 Eventually, it runs out of threads, and comes to a halt:

What does a thread dump show?  (Before taking one, you might want to reduce the 
number of threads to avoid a lot of clutter in the dump.)  You can use the 
jstack utility from the JDK (among other mechanisms) to get a thread dump of an 
active JVM.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]