RE: Barracuda lockups...(Update)

Hi Jake,
 
>>Which version of Tomcat is version 4.3?  The latest I know of is 4.1.24. 
Oops,
My bad...
Your're correct. The Tomcat version I'm using is actually 4.1.3.
 
>>Try running using Tomcat directly rather than the mod_jk connector...
Running Tomcat Standalone without Apache(Although I did have Apache setup to
work with Tomcat 3.3. Have disabled the Apache service until I'm sure Tomcat
4 is working 100%).
 
>>As far as log4j goes, the latest CVS (do you mean the Tomcat5 cvs?) does
have this log4j issue.  Just ignore it.
I updated barracuda from the cvs. Will try and sort out the log4j problem
later today.
 
Thanx Jake,
Regards
KD
 

-----Original Message-----
From: Jacob Kjome [mailto:[email protected]]
Sent: 23 June 2003 05:28
To: [email protected]
Subject: RE: [Barracuda] Barracuda lockups...(Update)



Which version of Tomcat is version 4.3?  The latest I know of is 4.1.24.
Additionally, I don't think this has anything to do with Barracuda, but with
the Apache/Tomcat mod_jk connector.  Try running using Tomcat directly
rather than the mod_jk connector or, at least upgrade the connector to the
latest version.  Also, you should use the Coyote Connector in Tomcat's
server.xml rather than the older connector if you aren't already.  If you
haven't changed the server.xml from the defaults, then need not worry about
this.

As far as log4j goes, the latest CVS (do you mean the Tomcat5 cvs?) does
have this log4j issue.  Just ignore it.  They are doing something wrong with
log4j and has nothing to do with logging in Barracuda or your own app.  To
log in your own app, make sure to look at Barracuda's web.xml to see how
logging is being set up there.  Also look at Barracuda's log4j.xml to see
how it is set up for logging.  Change the FileAppender <param name="File"
value="${Barracuda.log.home}/main.log" /> to match your own app such as ....

<param name="File" value="${MyContextName.log.home}/main.log" />

The configuration will automatically set up a system property that provides
the logging path for your context and the naming convention for the system
property that stores this information will be (at least under Tomcat)
[webapp context name].log.home.  That's why the above works.

let me know if any of this is not clear.

Jake

At 02:45 PM 6/23/2003 +0200, you wrote:


Hi Christian,

Upgraded to Tomcat 4.3 and the latest cvs version.
I can def confirm that the problem is still happening.

Will report any progress as I go along.

What I can say is that Tomcat has reported the following message in
the debug console after I get the lockup.

2003/06/23 02:24:08 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached

Then again.. that might be a normal error for Tomcat 4.
Still getting used to it.

Still need to get Log4J configured correctly.
Getting the following error.
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.

Gotten that before. Need to sort out the web.xml file I suppose.

Haven't used the WorkBench.bat to test the app yet.
Will do so withing the next 2 days.

Regards
KD

-----Original Message-----
From: Christian Cryder [ mailto:[email protected]
<mailto:[email protected]> ]
Sent: 19 June 2003 05:08
To: [email protected]
Subject: RE: [Barracuda] Barracuda lockups...


Hi Kirk,

> a while back.. in one of your posts...you posted something
> along the lines of fixing a few things to provide for thread
> safety....

Yeah, it was in DefaultDOMLoader. Now, I don't think there were major
problems there, but we did make some improvements, so its certainly
possible.

> Haven't had a chance to upgrade to version 2.0 yet....
> So I can't confirm that the changes you made fix's this.

I'm willing to do whatever necessary to help you get this fixed, but tht's
probably going to require you to upgrade to the latest version in cvs, first
to verify whether or not its still a problem, and then second to fix it if
it is. Can you do this?

One of the things that may be helpful in duplicating this is to use the
Barracuda Workbench (you can run this from
WEB-INF/bin/Barracuda_WorkBench.bat)...it has a simple URL stress tester
that will allow you to hit a webapp with multiple threads, usually exposing
any threadsaftey issues. The downside is that the stress tester does not
currently support authentication, cookies, or redirect requests, so it may
be a tad limited where you can use it.

I CAN confirm that I used this to test my changes to DefaultDOMLoader, and
it held up under load without problems. So one of the things you might want
to do before upgrading even is to try it out on your existing app to see if
you can duplicate the problem. If you CAN'T, then maybe its a different
issue altogether.

Hopefully this will give you some ideas on where to start...holler if you
have questions, and let us know what you find.

Christian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
<http://barracudamvc.org/> 
----------------------------------------------
"Coffee? I could quit anytime, just not today"


> -----Original Message-----
> From: [email protected]
> [ mailto:[email protected]
<mailto:[email protected]> ]On Behalf Of Kirk Daries
> Sent: Thursday, June 19, 2003 8:59 AM
> To: [email protected]
> Subject: [Barracuda] Barracuda lockups...
>
>
> Hi Christian...
>
> I'm experiencing periodic lockups when my pages are rendered.
> They eventually render after about 4 mins or so...
> I've got no idea why this is happening.... ;(
>
> Now..
> a while back.. in one of your posts...
> you posted something along the lines of fixing a few things to
> provide for thread safety....
>
> Could this be related??
> Haven't had a chance to upgrade to version 2.0 yet....
> So I can't confirm that the changes you made fix's this.
>
> Just thought I'd put my feelers out to see if anyone else ever experienced
> this.
>
> Regards
> KD
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda
<http://barracudamvc.org/lists/listinfo/barracuda> 

_______________________________________________
Barracuda mailing list
[email protected]
http://barracudamvc.org/lists/listinfo/barracuda
<http://barracudamvc.org/lists/listinfo/barracuda> 
_______________________________________________
Barracuda mailing list
[email protected]
http://barracudamvc.org/lists/listinfo/barracuda
<http://barracudamvc.org/lists/listinfo/barracuda>