BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

db:add fails to add large XML file
by Han (US), Paul P 20 Nov '18

20 Nov '18

Hello, We encountered the following error intermittently when using db:add within the XQuery on a large XML. Regards, Paul 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]POST failed with response 400: Improper use? Potential bug? Your feedback is welcome: 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT Contact: basex-talk(a)mailman.uni-konstanz.de 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT Version: BaseX 9.1 beta 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT Java: Oracle Corporation, 1.8.0_162 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT OS: Linux, amd64 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT Stack Trace: 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT java.lang.RuntimeException: Data Access out of bounds: 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT - pre value: 2053429413 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT - table size: -2143755530 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT - first/next pre value: -2143755776/-2143755530 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT - #total/used pages: 8403171/8403171 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT - accessed page: 8403170 (8403171 > 8403170] 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.util.Util.notExpected(Util.java:61) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.io.random.TableDiskAccess.cursor(TableDiskAccess.java:456) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.io.random.TableDiskAccess.read4(TableDiskAccess.java:165) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.data.Data.id(Data.java:294) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.data.Data.insert(Data.java:828) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.query.up.primitives.db.DBAdd.apply(DBAdd.java:67) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.query.up.DataUpdates.apply(DataUpdates.java:175) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.query.up.ContextModifier.apply(ContextModifier.java:120) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.query.up.Updates.apply(Updates.java:156) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.query.QueryContext.iter(QueryContext.java:350) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.query.QueryProcessor.iter(QueryProcessor.java:90) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.core.cmd.AQuery.query(AQuery.java:109) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.core.cmd.XQuery.run(XQuery.java:22) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.core.Command.run(Command.java:257) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.http.rest.RESTCmd.run(RESTCmd.java:105) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.http.rest.RESTQuery.query(RESTQuery.java:69) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.http.rest.RESTQuery.run0(RESTQuery.java:37) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.http.rest.RESTCmd.run(RESTCmd.java:70) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.core.Command.run(Command.java:257) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.core.Command.execute(Command.java:93) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.core.Command.execute(Command.java:116) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.http.rest.RESTServlet.run(RESTServlet.java:27) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.basex.http.BaseXServlet.service(BaseXServlet.java:59) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.filters.CorsFilter.handleNonCORS(CorsFilter.java:419) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.filters.CorsFilter.doFilter(CorsFilter.java:169) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:474) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:783) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:798) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1434) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) 2018-11-19T16:10:45.80-0800 [APP/PROC/WEB/0]OUT at java.lang.Thread.run(Thread.java:748)

2 1

Fulltext index not applied
by Sebastian Zimmer 16 Nov '18

16 Nov '18

Hi, I'm working on a query where the full-text index is not applied, even though it could be (see attached test.xql). I'm sorry for the somewhat complicated look of the example with data-specific XPaths and so on. I really have tried to simplify it as much as I could, but when I further simplify it, the fulltext index actually will be applied or the query is optimized to () due to cached evaluations. But if you take the expression of the variable $number and inline it into below where the variable is referenced, you may see what I mean. The result is an equivalent query (see attached test-ft.xql) to the original one, but now the fulltext index *is* applied. I'm using the BaseX 9.1 snapshot from 2018-11-05. Best, Sebastian -- Sebastian Zimmer sebastian.zimmer(a)uni-koeln.de <mailto:sebastian.zimmer@uni-koeln.de> CCeH Logo <http://cceh.uni-koeln.de> Cologne Center for eHumanities <http://cceh.uni-koeln.de> DH Center at the University of Cologne Twitter Logo <https://twitter.com/CCeHum>@CCeHum <https://twitter.com/CCeHum>

2 4

BaseX on Eclipse OpenJ9?
by vincent van der leun 16 Nov '18

16 Nov '18

Hello, I've been reading for quite some time. Some time back, I was looking for a way to play with XQuery and came across BaseX database system. Being intrigued, I've been following its development since. I found a use-case for a personal web application, which will be querying BaseX for documents stored in XML. A scheduled cron task will be adding new documents to the database from time to time. At the moment my default JVM is Eclipse OpenJ9 (previously IBM J9), based on OpenJDK 8, as it's promising lower memory consumption in many use-cases than Oracle's HotSpot JVM. My first small tests seem to confirm this. Has anyone else been running BaseX on either OpenJ9 or IBM J9? Thanks and keep up the good work. Kind regards, Vincent

2 1

Support for XML with different file extension in GUI
by Kevin Cline 15 Nov '18

15 Nov '18

Hello, In the GUI, is there any way to set the query context to an XML file that has an extension other than .xml ? Renaming the file works, obviously, but this isn't ideal, as the source of the data exports to and imports from another extension. Also, is it possible to enable syntax highlighting for XML files without changing the extension? I added the extension in Options->Preferences->File Filter, but nothing changed. Thank you for your help.

3 8

BaseX 9.1 behaviour of fn:trace
by Kittelmann, Maike 12 Nov '18

12 Nov '18

Dear fellow users, I updated to BaseX 9.1 and I observe an unexpected behaviour of fn:trace http://docs.basex.org/wiki/XQuery_3.1#fn:trace I inserted logging statements to give warnings in case important content is missing, like so: declare function local:my-function ( $id as xs:string?, $value as xs:string? ) as xs:string? { if ( $ value != '' ) then "foo" else trace( $id, 'No foo given for this record! ') } ; So far, the fn:trace output could be read in the Info window of BaseX. Now, the id-value of the above call to trace is ALSO output to the Result window. Even though the documentation states that the behaviour of trace is implementation-dependent, this behaviour seems unexpected and unhelpful. The extra output to result is hard to notice and destroys a possibly fully valid result file (the trace call is only a warning, there is not necessarily an actual error). 1. Is there anything wrong with my XQuery? 2. Why is trace behaving this way in BaseX 9.1? 3. How to best achieve the desired output? (Desired output is: result file unchanged and warning in Info window.) Thank you and best regards, MK

2 1

restxq
by Giuseppe G. A. Celano 11 Nov '18

11 Nov '18

I am trying to make a RESTXQ webservice I created with BaseX 8.3 available in Basex 9.2. I simply copied my "file.xqm" into the webapp folder but, when I type the path of a function contained in it, it does not work ("No function found that matches the request."). Strangely enough, when I minimally modify restxq.xqm, the modifications do not apply either. Any idea about what the problem might be? Thanks.

4 5

Issue with HTTP Server
by Shaun Flynn 09 Nov '18

09 Nov '18

Hello there, I am using BaseX 9.1, and Java version 8. When I use the basexhttp command, the server appears to start fine, but when I navigate to http:\\localhost:8984\rest, I get the following response below. What am I doing wrong? HTTP ERROR 500 Problem accessing /rest. Reason: Server Error Caused by: java.lang.NoSuchMethodError: org.basex.util.TokenBuilder.<init>(Ljava/lang/String;)V at org.basex.http.HTTPConnection.status(HTTPConnection.java:427) at org.basex.http.HTTPConnection.error(HTTPConnection.java:187) at org.basex.http.BaseXServlet.service(BaseXServlet.java:64) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:503) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) at java.lang.Thread.run(Unknown Source) ------------------------------ Powered by Jetty:// 9.4.12.v20180830 <http://eclipse.org/jetty> ------------------------------ <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

getting the type of an arbitrary node
by Graydon Saunders 09 Nov '18

09 Nov '18

Hi! I am overcome with the cabbage-nature today, because I can't find this in the docs. I am convinced there's a way to go: (//some-element/node()) ! fn:node-type(.) and get a sequence of "element(),element(),text()..." but do not know what the actual function is called. (it's not node-type()!) How ought I to be approaching this? Thanks! Graydon

3 5

create db with options from command line
by Günter Dunz-Wolff 08 Nov '18

08 Nov '18

Hi all, I just set up my first basex-Server on DigitalOcean. So far, everything is working, but I have no experience, how I could create db with options on the command line, I always did it with the GUI. So how is the syntax for CREATE DB xxx /path with Options - CHOP no - Indices for Text, Attributes and Tokens - Fulltext-Index with Language German, Case Sensitive and Diacritics Thanks for any help. Guenter

2 3

Perceived performance of REST API
by Sebastian Zimmer 07 Nov '18

07 Nov '18

Hi, I'm looking for a way to increase the *perceived* performance of the REST API. On my web page there's a results list that is updated automatically when the text content of an input field is changed. This means that on each keystroke by the user, a GET request to the REST API api is sent to obtain the new results list. One GET request takes about 800 ms, which is acceptable to me given the complexity of the query and the amount of data. The problem is that when the user types faster than the queries are executed, the app starts to respond very slowly, because there are now several requests pending. BaseX seems to execute all of them in parallel and it may well take up to 14 seconds until it returns the results of the most recent search query. Is there a way to tell BaseX to abort running queries (by a specific user) to privilege the most recent query (of this user)? Could this be done with the Jobs module? Or is there a better way to implement such a search? Best regards, Sebastian -- Sebastian Zimmer sebastian.zimmer(a)uni-koeln.de <mailto:sebastian.zimmer@uni-koeln.de> Cologne Center for eHumanities <http://cceh.uni-koeln.de> DH Center at the University of Cologne @CCeHum <https://twitter.com/CCeHum>

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk