Discussion:
[Exist-open] internal servlet error
Jürgen Niehoff
2001-11-30 08:42:02 UTC
Permalink
hi,
i use eXist-0.7beta2 and i get following error:
type internal-servlet-error:
"
message Internal servlet error

description Cocoon was not initialized.

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

request-uri

/exist/admin.xsp

embedded exception

org.xml.sax.SAXNotSupportedException: Property:
http://xml.org/sax/properties/lexical-handler

embedded exception stacktrace

org.xml.sax.SAXNotSupportedException: Property:
http://xml.org/sax/properties/lexical-handler
at java.lang.Throwable.(Throwable.java:96)
at java.lang.Exception.(Exception.java:44)
at org.xml.sax.SAXException.(SAXException.java:45)
at
org.xml.sax.SAXNotSupportedException.(SAXNotSupportedException.java:39)
at
org.apache.crimson.parser.XMLReaderImpl.setProperty(XMLReaderImpl.java:248)

at
org.apache.cocoon.components.parser.JaxpParser.parse(JaxpParser.java:67)

at org.apache.cocoon.Cocoon.configure(Cocoon.java:216)
at org.apache.cocoon.Cocoon.initialize(Cocoon.java:160)
at
org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:634)

at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:164)

at
org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
at org.apache.tomcat.core.Handler.init(Handler.java:215)
at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296)
at org.apache.tomcat.core.Handler.service(Handler.java:243)
at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:371)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:786)

at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:732)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)

at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:407)

at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)

at java.lang.Thread.run(Thread.java:498)


exception

org.apache.avalon.framework.configuration.ConfigurationException: Error
trying to load configurations

stacktrace

org.apache.avalon.framework.configuration.ConfigurationException: Error
trying to load configurations
at java.lang.Throwable.(Throwable.java:96)
at java.lang.Exception.(Exception.java:44)
at
org.apache.avalon.framework.CascadingException.(CascadingException.java:40)

at
org.apache.avalon.framework.configuration.ConfigurationException.(ConfigurationException.java:41)

at org.apache.cocoon.Cocoon.configure(Cocoon.java:220)
at org.apache.cocoon.Cocoon.initialize(Cocoon.java:160)
at
org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:634)

at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:164)

at
org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
at org.apache.tomcat.core.Handler.init(Handler.java:215)
at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296)
at org.apache.tomcat.core.Handler.service(Handler.java:243)
at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:371)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:786)

at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:732)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)

at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:407)

at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)

at java.lang.Thread.run(Thread.java:498)

"
Whats wrong?

mfg Jürgen Niehoff
Wolfgang Meier
2001-11-30 14:25:09 UTC
Permalink
Hi,
Post by Jürgen Niehoff
http://xml.org/sax/properties/lexical-handler
your CLASSPATH contains the crimson XML parser which is loaded before Xerces.
The exception is generated because crimson does not support the
lexical-handler property. I would suggest to check your CLASSPATH and remove
crimson.

Regards,

Wolfgang


-------------------------
Wolfgang Meier
Darmstadt University of Technology
Dept. of Soc., Residenzschloss
D-64283 Darmstadt, Germany
+49 6151 16 6564
-------------------------
Wolfgang Meier
2001-12-03 08:17:03 UTC
Permalink
Hi,

output of build, server.sh and startup.sh looks good. The
NoClassDefFoundError during build is ok, because you don't need the Antlr
parser generator unless you are changing the parser.

You may also ignore tomcat's error message "cannot load servlet name: jsp". I
can't suppress this message, but it does not do any harm, because eXist
doesn't use jsp.

Have you tried to access http://localhost:8080/exist/index.xml, query.xml?

Regards,

Wolfgang
Post by Wolfgang Meier
Hi,
Post by Jürgen Niehoff
http://xml.org/sax/properties/lexical-handler
your CLASSPATH contains the crimson XML parser which is loaded before
Xerces. The exception is generated because crimson does not support the
lexical-handler property. I would suggest to check your CLASSPATH and
remove crimson.
Hi again,
i removed crimson, but then eXist doesn't start. I attached a file, which
contains the build, server.sh and startup.sh output. Perhaps you can see
whats wrong?
mfg Jürgen Niehoff
P.S.: i removed "crimson.jar" to the original place again
(/usr/lib/jdk1.3/jre/lib/ext/)
___________________________________________________________________________
___ Geben Sie Ihren Lottotipp gerne auf den letzten Drücker ab?Beim WEB.DE
Lottoservice gibt's keine Warteschlangen. http://tippen2.web.de/?x=9
--
-------------------------
Wolfgang Meier
Darmstadt University of Technology
Dept. of Soc., Residenzschloss
D-64283 Darmstadt, Germany
+49 6151 16 6564
-------------------------
Wolfgang Meier
2001-12-05 12:51:04 UTC
Permalink
Hi,
i removed crimson, but then eXist doesn't start. I attached a file, which
contains the build, server.sh and startup.sh output. Perhaps you can see
whats wrong?
Another idea: Maybe you're using jdk1.4? It comes with it's own XML parser,
which is crimson. I guess, you have to use JDK1.3 or define which parser to
use. See Java JAXP docs.

Regards,

Wolfgang
Michael Beddow
2001-12-07 12:22:19 UTC
Permalink
I've hit a new problem with eXist 0.7b2 on Mandrake 8.1

After working fine for several hours, the server suddenly starts returning
the same error to all queries (whether via java command-line, XML-RPC or
httpd) I have verified that it is a server problem, rather than my data, by
preparing scripts with the queries "pre-cooked". The same scripts that work
fine when the server is behaving itself all start to fail once the
malfunction begins.

Output is
<exist:result xmlns:exist="http://exist.sourceforge.net/NS/exist"
hitCount="0" err
code="6"><exist:message>java.lang.ArrayIndexOutOfBoundsException</exist:mess
age></
exist:result>

A typical server log:

07 Dec 2001 14:09:47,059 INFO (HttpServer.java [run]:50) - connection from
10.1.1.7
07 Dec 2001 14:09:47,116 DEBUG (HttpServerConnection.java
[processParameters]:421)
-
_xpath=document(*)%20//cit%20%5b//quote%26=%22bon%22%5d&_indent=true&_howman
y=10
07 Dec 2001 14:09:47,119 DEBUG (HttpServerConnection.java
[processParameters]:441
- parameter: _xpath = document(*) //cit [//quote&="bon"]
07 Dec 2001 14:09:47,123 DEBUG (HttpServerConnection.java
[processParameters]:441)
- parameter: _indent = true
07 Dec 2001 14:09:47,125 DEBUG (HttpServerConnection.java
[processParameters]:441)
- parameter: _howmany = 10
07 Dec 2001 14:09:47,129 DEBUG (BFile.java [findValuePosition]:467) - tid 20
not found. page: page: 2; file = collections.dbx; address = 3000; page
header = 64; data start = 3040; pos: 3592; last-tid: 33
07 Dec 2001 14:09:47,133 DEBUG (HttpServerConnection.java [search]:614) -
java.lang.ArrayIndexOutOfBoundsException
java.lang.ArrayIndexOutOfBoundsException
at exist.ByteConversion.byteToInt(ByteConversion.java:93)
at exist.BFile$FindCallback.indexInfo(BFile.java:574)
at org.dbxml.core.filer.BTree$BTreeNode.query(BTree.java:807)
at org.dbxml.core.filer.BTree.query(BTree.java:222)
at exist.BFile.getEntries(BFile.java:326)
at exist.NativeBroker.getAllDocuments(NativeBroker.java:468)
at exist.parser.XPathParser.document_function(XPathParser.java:268)
at exist.parser.XPathParser.xpath_expr(XPathParser.java:133)
at exist.parser.XPathParser.expr(XPathParser.java:118)
at exist.HttpServerConnection.search(HttpServerConnection.java:582)
at exist.HttpServerConnection.doGet(HttpServerConnection.java:364)
at exist.HttpServerConnection.get(HttpServerConnection.java:332)
at exist.HttpServerConnection.run(HttpServerConnection.java:181)
<exist:result xmlns:exist="http://exist.sourceforge.net/NS/exist"
hitCount="0" err
code="6"><exist:message>java.lang.ArrayIndexOutOfBoundsException</exist:mess
age></
exist:result>

Stopping and starting the server doesn't help. If find I have to stop the
server, and reindex all the documents with the -l switch via the java
command-line interface. Once that's done, everything works again for another
few hours.

Any suggestions?

Michael
---------------------------------------------------------
Michael Beddow http://www.mbeddow.net/
XML and the Humanities page: http://xml.lexilog.org.uk/
The Anglo-Norman Dictionary http://anglo-norman.net/
---------------------------------------------------------
Michael Beddow
2001-12-07 16:47:03 UTC
Permalink
Post by Michael Beddow
Stopping and starting the server doesn't help. If find I have to stop the
server, and reindex all the documents with the -l switch via the java
command-line interface. Once that's done, everything works again for
another
Post by Michael Beddow
few hours.
In addition, I find I have to delete the entire contents of exists /data
directory before reindexing the document.

IN case it's of any interest, resending the exact same query once the
document has been reindexed produces the following from the server logs
instead of the error messages and stack trace in my earlier message

7 Dec 2001 18:36:28,769 INFO (HttpServer.java [run]:50) - connection from
10.1.1.7
07 Dec 2001 18:36:28,810 DEBUG (HttpServerConnection.java
[processParameters]:421)
-
_xpath=document(*)%20//cit%20%5b//quote%26=%22bon%22%5d&_indent=true&_howman
y=10
07 Dec 2001 18:36:28,816 DEBUG (HttpServerConnection.java
[processParameters]:441)
- parameter: _xpath = document(*) //cit [//quote&="bon"]
07 Dec 2001 18:36:28,819 DEBUG (HttpServerConnection.java
[processParameters]:441)
- parameter: _indent = true
07 Dec 2001 18:36:28,822 DEBUG (HttpServerConnection.java
[processParameters]:441)
- parameter: _howmany = 10
07 Dec 2001 18:36:29,372 DEBUG (NativeBroker.java [getAllDocuments]:502) -
loading 1 documents took 150ms.
07 Dec 2001 18:36:29,439 INFO (HttpServerConnection.java [search]:583) -
query: (descendant::cit[((descendant::quote) &= 'bon'))])
07 Dec 2001 18:36:29,492 DEBUG (NativeTextEngine.java
[getNodesContaining]:163) -
found: 94 in 49ms.
07 Dec 2001 18:36:29,600 DEBUG (NativeBroker.java
[findElementsByTagName]:936) - f
ound 5683 in 69ms.
07 Dec 2001 18:36:29,770 DEBUG (LocationStep.java [getDescendants]:171) -
getDesce
ndants found 5683 in 167
07 Dec 2001 18:36:29,875 DEBUG (NativeBroker.java
[findElementsByTagName]:936) - f
ound 5526 in 65ms.
07 Dec 2001 18:36:29,917 DEBUG (LocationStep.java [getDescendants]:171) -
getDescendants found 5525 in 39
07 Dec 2001 18:36:29,927 DEBUG (HttpServerConnection.java [search]:594) -
evaluation took 485ms.


After which the expected results are returned instead of the previous error
return.

Michael
s***@web.de
2001-12-09 08:09:02 UTC
Permalink
Hi,

this seems to be a bug in the btree and storage classes. All "tid not found" messages indicate that one of the pointers used to connect btree values with data records is broken. Have you done lots of removals, updates or just queries?

Wolfgang


______________________________________________________________________________
Lotto online tippen! Egal zu welcher Zeit, egal von welchem Ort.
Mit dem WEB.DE Lottoservice. http://tippen2.web.de/?x=5

Loading...