I had the ClassNotFoundException with my failure.
- Brian
On Mar 12, 2006, at 9:20 AM, David Czarnecki wrote:
> Hmmmm, can you look in another other of the log files
to see if
> Blojsom is
> throwing a ClassNotFoundException? That's what line 93
is in
> BlojsomBaseServlet. And that seems odd given that
you've got the
> class name
> correct. There aren't any spaces after the class name
in
> blojsom-fetcher=org.blojsom.fetcher.CachingFetcher are
there? Just
> thought
> that maybe if there was that'd screw things up.
>
>
> On 3/11/06 2:26 AM, "ogjunk-blojsom yahoo.com" <ogjunk-
> blojsomyahoo.com>
> wrote:
>
>> Hello,
>>
>> Just tried adding OSCache to Blojsom as described
at
>> <http://wiki.blojsom.com/wiki/display/blojsom/En
abling+Caching>,
>> and got the
>> exception below.
>>
>> javax.servlet.ServletException:
org.blojsom.fetcher.CachingFetcher
>> at
>>
org.blojsom.servlet.BlojsomBaseServlet.configureFetcher
>> (BlojsomBaseServlet.jav
>> a:93)
>> at
>>
org.blojsom.servlet.BlojsomBaseServlet.configureBlojsom
>> (BlojsomBaseServlet.jav
>> a:120)
>> at org.blojsom.servlet.BlojsomServlet.init
>> (BlojsomServlet.java:292)
>> at
>> org.mortbay.jetty.servlet.ServletHolder.initServlet
>> (ServletHolder.java:383)
>> at
>>
org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.
java:243)
>> at
>>
org.mortbay.jetty.servlet.ServletHandler.initializeServlets
>> (ServletHandler.jav
>> a:446)
>> at
>>
org.mortbay.jetty.servlet.WebApplicationHandler.initializeSe
rvlets
>> (WebApplicat
>> ionHandler.java:321)
>> at
>>
org.mortbay.jetty.servlet.WebApplicationContext.doStart
>> (WebApplicationContext.
>> java:509)
>> at
org.mortbay.util.Container.start(Container.java:72)
>> at
org.mortbay.http.HttpServer.doStart(HttpServer.java:753)
>> at
org.mortbay.util.Container.start(Container.java:72)
>> at
org.mortbay.jetty.Server.main(Server.java:460)
>> javax.servlet.ServletException:
org.blojsom.fetcher.CachingFetcher
>> at
>>
org.blojsom.servlet.BlojsomBaseServlet.configureFetcher
>> (BlojsomBaseServlet.jav
>> a:93)
>> at
>>
org.blojsom.servlet.BlojsomBaseServlet.configureBlojsom
>> (BlojsomBaseServlet.jav
>> a:120)
>> at
>>
org.blojsom.extension.xmlrpc.BlojsomXMLRPCServlet.init
>> (BlojsomXMLRPCServlet.ja
>> va:284)
>> at
>> org.mortbay.jetty.servlet.ServletHolder.initServlet
>> (ServletHolder.java:383)
>> at
>>
org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.
java:243)
>> at
>>
org.mortbay.jetty.servlet.ServletHandler.initializeServlets
>> (ServletHandler.jav
>> a:446)
>> at
>>
org.mortbay.jetty.servlet.WebApplicationHandler.initializeSe
rvlets
>> (WebApplicat
>> ionHandler.java:321)
>> at
>>
org.mortbay.jetty.servlet.WebApplicationContext.doStart
>> (WebApplicationContext.
>> java:509)
>> at
org.mortbay.util.Container.start(Container.java:72)
>> at
org.mortbay.http.HttpServer.doStart(HttpServer.java:753)
>> at
org.mortbay.util.Container.start(Container.java:72)
>> at
org.mortbay.jetty.Server.main(Server.java:460)
>> javax.servlet.ServletException:
org.blojsom.fetcher.CachingFetcher
>> at
>>
org.blojsom.servlet.BlojsomBaseServlet.configureFetcher
>> (BlojsomBaseServlet.jav
>> a:93)
>> at
>>
org.blojsom.servlet.BlojsomBaseServlet.configureBlojsom
>> (BlojsomBaseServlet.jav
>> a:120)
>> at
>>
org.blojsom.extension.comment.CommentAPIServlet.init
>> (CommentAPIServlet.java:15
>> 4)
>> at
>> org.mortbay.jetty.servlet.ServletHolder.initServlet
>> (ServletHolder.java:383)
>> at
>>
org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.
java:243)
>> at
>>
org.mortbay.jetty.servlet.ServletHandler.initializeServlets
>> (ServletHandler.jav
>> a:446)
>> at
>>
org.mortbay.jetty.servlet.WebApplicationHandler.initializeSe
rvlets
>> (WebApplicat
>> ionHandler.java:321)
>> at
>>
org.mortbay.jetty.servlet.WebApplicationContext.doStart
>> (WebApplicationContext.
>> java:509)
>> at
org.mortbay.util.Container.start(Container.java:72)
>> at
org.mortbay.http.HttpServer.doStart(HttpServer.java:753)
>> at
org.mortbay.util.Container.start(Container.java:72)
>>
>> Does anyone know if some additional
steps/configurations are
>> needed other
>> than the ones described?
>>
>> Thanks,
>> Otis
>>
>>
>>
>> ----- Original Message ----
>> From: David Czarnecki <davidblojsom.com>
>> To: blojsom-users mailing list
<blojsom-userslists.sourceforge.net>
>> Sent: Thursday, March 9, 2006 3:06:13 PM
>> Subject: Re: [Blojsom-users] Blojsom chewing my CPU
>>
>> Well, although the caching fetcher doesn't use
memcached, it
>> shouldn't be
>> too much too just throw it in the mix, eh?
>>
>> <http://wiki.blojsom.com/wiki/display/blojsom/En
abling+Caching>
>>
>>
>>
>> On 3/9/06 2:57 PM, "ogjunk-blojsomyahoo.com" <ogjunk-
>> blojsomyahoo.com>
>> wrote:
>>
>>> Hi David,
>>>
>>> I used DB queries example for simplicity - the
server also does a
>>> lot of
>>> Lucene work, which is all FS (but cached) 
>>>
>>> Hm, reading all entries.... that is what I
suspected and was
>>> afraid off.
>>> Luckily, I post only about once a week, but
that still won't
>>> scale much
>>> longer
>>> for me. :(. Are there any plans for changing
this in one of the
>>> near-future
>>> versions?
>>>
>>> Also, are there any memcached hooks? I use
memcached and would
>>> love to use
>>> it
>>> to cache Blojsom stuff, so I don't have yet
another caching
>>> mechanism in my
>>> system.
>>>
>>> Thanks for your fast answers, David!
>>> Otis
>>>
>>>
>>> ----- Original Message ----
>>> From: David Czarnecki <davidblojsom.com>
>>> To: blojsom-users mailing list
<blojsom-userslists.sourceforge.net>
>>> Sent: Thursday, March 9, 2006 2:39:37 PM
>>> Subject: Re: [Blojsom-users] Blojsom chewing my
CPU
>>>
>>> DB queries != File System queries
>>>
>>> I guess there are some shortcomings with the
way things are
>>> implemented as
>>> far as the standard "fetching"
mechanism is done in blojsom right
>>> now. It
>>> loads all the entries and then the plugins cut
'em down, so to
>>> speak,
>>> depending on things like date parameters, limit
for entries to
>>> display,
>>> etc...
>>>
>>> So, not the best way of doing things. I won't
argue 'bout that.
>>>
>>> On 3/9/06 2:32 PM, "ogjunk-blojsomyahoo.com" <ogjunk-
>>> blojsomyahoo.com>
>>> wrote:
>>>
>>>> Yeah, that would be a bandaid. But before
I resort to bandaids,
>>>> I'd love to
>>>> figure out what the app is doing that is SO
CPU intensive. The
>>>> same server
>>>> runs http://www.simpy.com/ , and
the front page (not cached)
>>>> with several DB
>>>> queries and joins renders faster than
Blojsom, which should
>>>> really be doing
>>>> simple and non-CPU intensive stuff, like
reading files off of
>>>> disk (and the
>>>> FS
>>>> has them cached).
>>>>
>>>> Any ideas? Does Blojsom do something else
there?
>>>>
>>>> Thanks,
>>>> Otis
>>>>
>>>> ----- Original Message ----
>>>> From: David Czarnecki <davidblojsom.com>
>>>> To: blojsom-users mailing list <blojsom-
>>>> userslists.sourceforge.net>
>>>> Sent: Thursday, March 9, 2006 2:23:59 PM
>>>> Subject: Re: [Blojsom-users] Blojsom
chewing my CPU
>>>>
>>>> I'd throw the caching in front of it and
that should greatly
>>>> improve things.
>>>>
>>>>
>>>> On 3/9/06 2:12 PM,
"ogjunk-blojsomyahoo.com" <ogjunk-
>>>> blojsomyahoo.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Can somebody familiar with the code
explain in a few words what
>>>>> Blojsom
>>>>> webapp
>>>>> does when its main page is loaded?
>>>>> More precisely, what are some of the
more expensive operations?
>>>>>
>>>>> I'm asking because my Blojsom-powered
blog seems to take up to
>>>>> 10 seconds
>>>>> to
>>>>> load on an otherwise not overloaded
server. Here is the output
>>>>> of 'vmstat
>>>>> 1'
>>>>> that shows the CPU getting chewed up
100% while the blog loads:
>>>>>
>>>>> procs -----------memory----------
---swap-- -----io---- --system--
>>>>> ----cpu----
>>>>> 0 0 128 124876 102476 2461200 0
0 0 0
>>>>> 273 94 1 0
>>>>> 99
>>>>> 0
>>>>> 0 0 128 124876 102476 2461204 0
0 0 72 323
>>>>> 170 2 2
>>>>> 96
>>>>> 0
>>>>> 0 0 128 124876 102476 2461204 0
0 0 0 306
>>>>> 153 1 0
>>>>> 99
>>>>> 0
>>>>> 0 0 128 124876 102476 2461204 0
0 0 0 295
>>>>> 142 3 1
>>>>> 96
>>>>> 0
>>>>> 1 0 128 124768 102476 2461208 0
0 0 0 284
>>>>> 120 50 50
>>>>> 0
>>>>> 0 <==
>>>>> 1 0 128 124768 102476 2461208 0
0 0 948 283
>>>>> 124 51 49
>>>>> 0
>>>>> 0 ..
>>>>> 1 0 128 124768 102476 2461208 0
0 0 0 259
>>>>> 104 52 48
>>>>> 0
>>>>> 0 ..
>>>>> 1 0 128 124768 102476 2461208 0
0 0 0 260
>>>>> 109 56 44
>>>>> 0
>>>>> 0 ..
>>>>> 1 0 128 124768 102476 2461208 0
0 0 0 266
>>>>> 118 56 44
>>>>> 0
>>>>> 0 ..
>>>>> 1 0 128 124892 102476 2461208 0
0 0 0 272
>>>>> 129 97 3
>>>>> 0
>>>>> 0 ..
>>>>> 0 0 128 124892 102476 2461212 0
0 0 2080 318
>>>>> 162 19 4
>>>>> 75
>>>>> 2 <==
>>>>> 0 0 128 124908 102476 2461216 0
0 0 0 303
>>>>> 190 8 0
>>>>> 92
>>>>> 0
>>>>>
>>>>>
>>>>> The important columns are the last 2
columns. My arrows mark
>>>>> begin/end of
>>>>> the
>>>>> CPU-munch.
>>>>> Note that the last column is 0,
indicating there is no waiting
>>>>> for IO.
>>>>>
>>>>> Any ideas what's going on?
>>>>> The blog in question is: http://blog.simpy.com/
>>>>>
>>>>> The blog has only 122 entries:
>>>>> $ find . -name \*.html | wc -l
>>>>> 122
>>>>>
>>>>> I can throw caching in front of it, but
I think there is a
>>>>> problem to be
>>>>> solved here.
>>>>> I'm using version 2.29.
>>>>>
>>>>> Thanks,
>>>>> Otis
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
-------------------------------------------------------
>>>>> This SF.Net email is sponsored by xPML,
a groundbreaking
>>>>> scripting language
>>>>> that extends applications into web and
mobile media. Attend the
>>>>> live
>>>>> webcast
>>>>> and join the prime developer group
breaking into this new
>>>>> coding territory!
>>>>> http://sel.as-us.fal
kag.net/sel?
>>>>>
cmd=lnk&kid=110944&bid=241720&dat=121642
>>>>>
_______________________________________________
>>>>> Blojsom-users mailing list
>>>>> Blojsom-userslists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/blojsom-u
sers
>
> --
> David Czarnecki
>
> http://www.blojsom.com/b
log/ | http://blojsom.sf.net
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a
groundbreaking scripting
> language
> that extends applications into web and mobile media.
Attend the
> live webcast
> and join the prime developer group breaking into this
new coding
> territory!
> http://sel.as-us.fal
kag.net/sel?
> cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Blojsom-users mailing list
> Blojsom-userslists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/blojsom-u
sers
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Blojsom-users mailing list
Blojsom-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/blojsom-u
sers
|