You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-users@xml.apache.org by Mark Miller <mm...@moondance.com> on 2002/09/03 15:12:58 UTC
Xindice problem
From: Mark Miller <mm...@moondance.com>
Date: Tue Sep 3, 2002 13:51:27 Europe/Dublin
Subject: Xindice Problem
Hey all,
I am developing an application using Xindice (1.0 (Birthday)), and
Cocoon (2.0.2), and I'm having a problem (well three problems).
1. It all works fine most of the time, but then for no apparent reason,
a given request to Xindice will take ages to return (4-5 minutes), and
then everything will continue to work at normal (< 1sec) speeds.
This is a snippet from the cocoon log showing it just siting there.
Eventually the request was satisfied:
DEBUG (2002-09-03) 11:53.26:373
[cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-
form) Thread-19/XMLDBSource: Querying collection xmldb:xindi\
ce://localhost:4080/db/scannell/regulations/; query=
/scannell:regulation[scannell:checklists//scannell:relevantchecklist='/
texas/heuston/weirdfailedarchitects']/sca\
nnell:regulationreference
DEBUG (2002-09-03) 12:03.21:956
[cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-
form) Thread-19/CachingEventPipeline: Recycling of CachingEv\
entPipeline
The exact same request minutes later (nothing restarted):
DEBUG (2002-09-03) 12:07.29:879
[cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-
form) Thread-19/XMLDBSource: Querying collection xmldb:xindi\
ce://localhost:4080/db/scannell/regulations/; query=
/scannell:regulation[scannell:checklists//scannell:relevantchecklist='/
texas/heuston/weirdfailedarchitects']/sca\
nnell:regulationreference
DEBUG (2002-09-03) 12:07.30:053
[cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-
form) Thread-19/CachingEventPipeline: Recycling of CachingEv\
entPipeline
2. As well sometimes I get the following exception:
org.apache.cocoon.ProcessingException: Could not read resource
xmldb:xindice://localhost:4080/db/scannell/profileforms/Ireland/waste/:
org.xmldb.api.base.XMLDBException:
org.apache.cocoon.ProcessingException: Could not read resource
xmldb:xindice://localhost:4080/db/scannell/profileforms/Ireland/waste/:
org.xmldb.api.base.XMLDBException:
Original exception : org.xmldb.api.base.XMLDBException:
at
org.apache.xindice.core.FaultCodes.createXMLDBException(FaultCodes.java:
247)
at
org.apache.xindice.client.xmldb.DatabaseImpl.getCollection(DatabaseImpl.
java:226)
at
org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:194)
at
org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:157)
at
org.apache.cocoon.components.source.XMLDBSource.collectionToSAX(XMLDBSou
rce.java:274)
at
org.apache.cocoon.components.source.XMLDBSource.toSAX(XMLDBSource.java:2
22)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:1
42)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.process(Cachi
ngEventPipeline.java(Compiled Code))
at
org.apache.cocoon.components.source.SitemapSource.toSAX(SitemapSource.ja
va(Compiled Code))
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:1
42)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.process(Cachi
ngEventPipeline.java(Compiled Code))
at
org.apache.cocoon.components.source.SitemapSource.toSAX(SitemapSource.ja
va:351)
at
org.apache.cocoon.sitemap.ContentAggregator.generate(ContentAggregator.j
ava:148)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.process(Cachi
ngEventPipeline.java(Compiled Code))
at
org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(Cach
ingStreamPipeline.java:399)
...
at java.lang.Thread.run(Thread.java:498)
which only goes away if I restart Tomcat, but NOT the Xindice Server,
which leads me to believe it is a resource problem with Client side. I
am reasonably confident that it is not caused by me doing something
different, Because once it is unable to find the XMLDB Resource, all
subsequent requests give the same exception.
3. I created an indexer object that had some problem (not sure what it
was), now when I startup Xindice I get this exception:
org.apache.xindice.core.indexer.CannotCreateException: Cannot create
Index 'regref'
at
org.apache.xindice.core.indexer.IndexManager.register(IndexManager.java:
262)
at
org.apache.xindice.core.indexer.IndexManager$1.process(IndexManager.java
:133)
at
org.apache.xindice.util.Configuration.processChildren(Configuration.java
:684)
at
org.apache.xindice.core.indexer.IndexManager.setConfig(IndexManager.java
:128)
at
org.apache.xindice.core.Collection.setConfig(Collection.java:199)
at
org.apache.xindice.core.CollectionManager$1.process(CollectionManager.ja
va:96)
at
org.apache.xindice.util.Configuration.processChildren(Configuration.java
:684)
at
org.apache.xindice.core.CollectionManager.setConfig(CollectionManager.ja
va:92)
at
org.apache.xindice.core.Collection.setConfig(Collection.java:216)
at
org.apache.xindice.core.CollectionManager$1.process(CollectionManager.ja
va:96)
at
org.apache.xindice.util.Configuration.processChildren(Configuration.java
:684)
at
org.apache.xindice.core.CollectionManager.setConfig(CollectionManager.ja
va:92)
at
org.apache.xindice.core.Collection.setConfig(Collection.java:216)
at org.apache.xindice.core.Database.setConfig(Database.java:195)
at
org.apache.xindice.server.services.XindiceService.initialize(XindiceServ
ice.java:106)
at
org.apache.xindice.server.standard.StdServiceManager.addService(StdServi
ceManager.java:166)
at
org.apache.xindice.server.standard.StdServiceManager$1.process(StdServic
eManager.java:104)
at
org.apache.xindice.util.Configuration.processChildren(Configuration.java
:684)
at
org.apache.xindice.server.standard.StdServiceManager.setConfig(StdServic
eManager.java:90)
at org.apache.xindice.server.Kernel.loadAPI(Kernel.java:336)
at org.apache.xindice.server.Kernel.<init>(Kernel.java:150)
at org.apache.xindice.server.Kernel.<init>(Kernel.java:117)
at org.apache.xindice.server.Xindice.main(Xindice.java:99)
How do I delete the bad indexer?
Please help. I would love to use Xindice, but if its not stable I'll
have to find another solution.
Thanks,
Mark Miller
Moondance LTD
Re: Xindice problem
Posted by Mark Miller <mm...@moondance.com>.
Yes, that is the porblem. I think there is a leak in the client side
routines. Two threads are created for each request, and never go away.
I downloaded CocoBlog, and found the same thing.
On Wednesday, Sep 4, 2002, at 11:31 Europe/Dublin, John Moylan wrote:
> I'm guessing that if you count the number of java processes while the
> system is slow - the figure will be quite high.
Re: Xindice problem
Posted by John Moylan <jo...@rte.ie>.
I'm guessing that if you count the number of java processes while the
system is slow - the figure will be quite high. I had the same problems
with an app I'm developing using cocoon/xindice with lots of xincludes
using xpointers to xml in xindice. My solution was to generate static
pages of results from xindice queries once every 15 minutes using a
simple bash script and a cmd line xml parser. I only use cocoon for the
xslt transformations.
Also, I reduced the size of the XML documents I was feeding Xindice to
as small a size as possible using more bash/xslt before adding them.
John
Mark Miller wrote:
> *From: *Mark Miller <mm...@moondance.com>
> *Date: *Tue Sep 3, 2002 13:51:27 Europe/Dublin
> *Subject: *Xindice Problem
>
>
> Hey all,
>
> I am developing an application using Xindice (1.0 (Birthday)), and
> Cocoon (2.0.2), and I'm having a problem (well three problems).
>
> *1. It all works fine most of the time, but then for no apparent
> reason, a given request to Xindice will take ages to return (4-5
> minutes), and then everything will continue to work at normal (< 1sec)
> speeds.
> *
> *This is a snippet from the cocoon log showing it just siting there.
> Eventually the request was satisfied:
> *
> DEBUG (2002-09-03) *11:53.26:373*
> [cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-form)
> Thread-19/XMLDBSource: Querying collection xmldb:xindi\
> ce://localhost:4080/db/scannell/regulations/; query=
> /scannell:regulation[scannell:checklists//scannell:relevantchecklist='/texas/heuston/weirdfailedarchitects']/sca\
>
> nnell:regulationreference
> DEBUG (2002-09-03) *12:03.21:956 *
> [cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-form)
> Thread-19/CachingEventPipeline: Recycling of CachingEv\
> entPipeline
>
> *The exact same request minutes later (nothing restarted):
> *
> DEBUG (2002-09-03) *12:07.29:879*
> [cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-form)
> Thread-19/XMLDBSource: Querying collection xmldb:xindi\
> ce://localhost:4080/db/scannell/regulations/; query=
> /scannell:regulation[scannell:checklists//scannell:relevantchecklist='/texas/heuston/weirdfailedarchitects']/sca\
>
> nnell:regulationreference
> DEBUG (2002-09-03) *12:07.30:053*
> [cocoon.m](/webprofiler/admin/profile-editor/edit-form/show-editable-form)
> Thread-19/CachingEventPipeline: Recycling of CachingEv\
> entPipeline
>
> *2. As well sometimes I get the following exception:*
>
> org.apache.cocoon.ProcessingException: Could not read resource
> xmldb:xindice://localhost:4080/db/scannell/profileforms/Ireland/waste/:
> org.xmldb.api.base.XMLDBException:
> org.apache.cocoon.ProcessingException: Could not read resource
> xmldb:xindice://localhost:4080/db/scannell/profileforms/Ireland/waste/:
> org.xmldb.api.base.XMLDBException:
> Original exception : org.xmldb.api.base.XMLDBException:
> at
> org.apache.xindice.core.FaultCodes.createXMLDBException(FaultCodes.java:247)
>
> at
> org.apache.xindice.client.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:226)
>
> at org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:194)
> at org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:157)
> at
> org.apache.cocoon.components.source.XMLDBSource.collectionToSAX(XMLDBSource.java:274)
>
> at
> org.apache.cocoon.components.source.XMLDBSource.toSAX(XMLDBSource.java:222)
>
> at
> org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:142)
>
> at
> org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java(Compiled
> Code))
> at
> org.apache.cocoon.components.source.SitemapSource.toSAX(SitemapSource.java(Compiled
> Code))
> at
> org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:142)
>
> at
> org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java(Compiled
> Code))
> at
> org.apache.cocoon.components.source.SitemapSource.toSAX(SitemapSource.java:351)
>
> at
> org.apache.cocoon.sitemap.ContentAggregator.generate(ContentAggregator.java:148)
>
> at
> org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java(Compiled
> Code))
> at
> org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingStreamPipeline.java:399)
>
> ...
> at java.lang.Thread.run(Thread.java:498)
>
>
>
> *which only goes away if I restart Tomcat, but NOT the Xindice Server,
> which leads me to believe it is a resource problem with Client side. I
> am reasonably confident that it is not caused by me doing something
> different, Because once it is unable to find the XMLDB Resource, all
> subsequent requests give the same exception.
> *
> *3. I created an indexer object that had some problem (not sure what
> it was), now when I startup Xindice I get this exception:*
>
> org.apache.xindice.core.indexer.CannotCreateException: Cannot create
> Index 'regref'
> at
> org.apache.xindice.core.indexer.IndexManager.register(IndexManager.java:262)
>
> at
> org.apache.xindice.core.indexer.IndexManager$1.process(IndexManager.java:133)
>
> at
> org.apache.xindice.util.Configuration.processChildren(Configuration.java:684)
>
> at
> org.apache.xindice.core.indexer.IndexManager.setConfig(IndexManager.java:128)
>
> at org.apache.xindice.core.Collection.setConfig(Collection.java:199)
> at
> org.apache.xindice.core.CollectionManager$1.process(CollectionManager.java:96)
>
> at
> org.apache.xindice.util.Configuration.processChildren(Configuration.java:684)
>
> at
> org.apache.xindice.core.CollectionManager.setConfig(CollectionManager.java:92)
>
> at org.apache.xindice.core.Collection.setConfig(Collection.java:216)
> at
> org.apache.xindice.core.CollectionManager$1.process(CollectionManager.java:96)
>
> at
> org.apache.xindice.util.Configuration.processChildren(Configuration.java:684)
>
> at
> org.apache.xindice.core.CollectionManager.setConfig(CollectionManager.java:92)
>
> at org.apache.xindice.core.Collection.setConfig(Collection.java:216)
> at org.apache.xindice.core.Database.setConfig(Database.java:195)
> at
> org.apache.xindice.server.services.XindiceService.initialize(XindiceService.java:106)
>
> at
> org.apache.xindice.server.standard.StdServiceManager.addService(StdServiceManager.java:166)
>
> at
> org.apache.xindice.server.standard.StdServiceManager$1.process(StdServiceManager.java:104)
>
> at
> org.apache.xindice.util.Configuration.processChildren(Configuration.java:684)
>
> at
> org.apache.xindice.server.standard.StdServiceManager.setConfig(StdServiceManager.java:90)
>
> at org.apache.xindice.server.Kernel.loadAPI(Kernel.java:336)
> at org.apache.xindice.server.Kernel.<init>(Kernel.java:150)
> at org.apache.xindice.server.Kernel.<init>(Kernel.java:117)
> at org.apache.xindice.server.Xindice.main(Xindice.java:99)
>
> How do I delete the bad indexer?
>
>
> Please help. I would love to use Xindice, but if its not stable I'll
> have to find another solution.
>
> Thanks,
>
> Mark Miller
> Moondance LTD
>
******************************************************************************
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful.
Please note that emails to, from and within RTÉ may be subject to the Freedom
of Information Act 1997 and may be liable to disclosure.
******************************************************************************