what's different between standalone mode and stardard mode(start by bin\startup.bat)?

classic Classic list List threaded Threaded
31 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

what's different between standalone mode and stardard mode(start by bin\startup.bat)?

lin_xd
Hi,sir,
  I found existdb started by bin\startup.bat , a costly query will cause fellow-up query queued.(do query in exide)

 but the standalone mode can process fellow-up query well.(do xquery in java client) 

  so, what's different between these two mode?
---------------
and I want to know: startup.bat and client.bat  run in the same dir using same log file : an error occured when start two program(trunk version).

when do costly query got error on console: 

2017-04-05 18:41:17,646 qtp208184824-23 ERROR Unable to delete file D:\opt\exist\webapp\WEB-INF\logs\exist.log: java.nio.file.FileSystemException D:\opt\ex
ist\webapp\WEB-INF\logs\exist.log: other program still using this file ,process can't access  (另一个程序正在使用此文件,进程无法访问。)

2017-04-05 18:41:18,422 qtp208184824-23 ERROR Unable to move file D:\opt\exist\webapp\WEB-INF\logs\exist.log to D:\opt\exist\webapp\WEB-INF\logs\exist.20170405184118.log: java.nio.file.FileSystemException D:\opt\exist\webapp\WEB-INF\logs\exist.log -> D:\opt\exist\webapp\WEB-INF\logs\exist.20170405184118.log:
另一个程序正在使用此文件,进程无法访问。



many log produced: with error:

2017-04-05 18:40:04,730 [qtp208184824-23] WARN  (XQueryWatchDog.java [proceed]:156) - Query exceeded predefined timeout (21,252 ms.): attribute::{}value 
2017-04-05 18:40:04,731 [qtp208184824-23] ERROR (NativeStructuralIndexWorker.java [findDescendantsByTagName]:207) - Error while searching structural index: exerr:ERROR The query exceeded the predefined timeout and has been killed. [at line 3, column 25] 
org.exist.xquery.TerminatedException$TimeoutException: exerr:ERROR The query exceeded the predefined timeout and has been killed. [at line 3, column 25]
at org.exist.xquery.XQueryWatchDog.proceed(XQueryWatchDog.java:159) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.XQueryContext.proceed(XQueryContext.java:2296) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.structural.NativeStructuralIndexWorker$FindDescendantsCallback.indexInfo(NativeStructuralIndexWorker.java:392) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1847) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1763) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1763) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1763) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.btree.BTree$BTreeNode.access$1200(BTree.java:907) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.btree.BTree.query(BTree.java:383) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.storage.structural.NativeStructuralIndexWorker.findDescendantsByTagName(NativeStructuralIndexWorker.java:205) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.LocationStep.getAttributes(LocationStep.java:657) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.LocationStep.eval(LocationStep.java:440) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.GeneralComparison.quickNodeSetCompare(GeneralComparison.java:689) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.GeneralComparison.eval(GeneralComparison.java:470) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.modules.range.Lookup.eval(Lookup.java:317) ~[exist-index-range.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.InternalFunctionCall.eval(InternalFunctionCall.java:41) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.PathExpr.eval(PathExpr.java:276) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.Predicate.selectByNodeSet(Predicate.java:450) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.Predicate.evalPredicate(Predicate.java:326) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.LocationStep.processPredicate(LocationStep.java:256) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.LocationStep.applyPredicate(LocationStep.java:243) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.LocationStep.eval(LocationStep.java:474) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.pragmas.Optimize.eval(Optimize.java:170) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.ExtensionExpression.eval(ExtensionExpression.java:70) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.PathExpr.eval(PathExpr.java:276) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.XQuery.execute(XQuery.java:253) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xquery.XQuery.execute(XQuery.java:185) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.doQuery(RpcConnection.java:246) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.lambda$null$539(RpcConnection.java:1672) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.function.XmlRpcCompiledXQueryFunction.apply(XmlRpcCompiledXQueryFunction.java:41) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.lambda$compileQuery$601(RpcConnection.java:3515) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.lambda$queryP$540(RpcConnection.java:1672) ~[exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.function.XmlRpcFunction.apply(XmlRpcFunction.java:45) [exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.withDb(RpcConnection.java:3771) [exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.withDb(RpcConnection.java:3755) [exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.queryP(RpcConnection.java:1642) [exist.jar:3.2.0-SNAPSHOT]
at org.exist.xmlrpc.RpcConnection.queryP(RpcConnection.java:3393) [exist.jar:3.2.0-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_71]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_71]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_71]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_71]
at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.invoke(ReflectiveXmlRpcHandler.java:115) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:106) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:46) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:86) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:200) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(XmlRpcServletServer.java:112) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(XmlRpcServlet.java:196) [xmlrpc-server-3.1.3.jar:3.1.3]
at org.exist.xmlrpc.RpcServlet.doPost(RpcServlet.java:67) [exist.jar:3.2.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [servlet-api-3.1.jar:3.1.0]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [servlet-api-3.1.jar:3.1.0]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566) [jetty-security-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:159) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:74) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.exist.http.urlrewrite.Forward.doRewrite(Forward.java:50) [exist-optional.jar:3.2.0-SNAPSHOT]
at org.exist.http.urlrewrite.XQueryURLRewrite.service(XQueryURLRewrite.java:219) [exist-optional.jar:3.2.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [servlet-api-3.1.jar:3.1.0]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) [jetty-security-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:396) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.Server.handle(Server.java:524) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_71]



------
and also I found the query timeout setting has no using for starting by run startup.bat mode

--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。


 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Adam Retter
Standalone mode - i.e. server.sh should probably not be used any more
Standard mode - i.e. startup.sh is what we use these days.

On 5 April 2017 at 07:17, 林晓东 <[hidden email]> wrote:

> Hi,sir,
>   I found existdb started by bin\startup.bat , a costly query will cause
> fellow-up query queued.(do query in exide)
>
>  but the standalone mode can process fellow-up query well.(do xquery in java
> client)
>
>   so, what's different between these two mode?
> ---------------
> and I want to know: startup.bat and client.bat  run in the same dir using
> same log file : an error occured when start two program(trunk version).
>
> when do costly query got error on console:
>
> 2017-04-05 18:41:17,646 qtp208184824-23 ERROR Unable to delete file
> D:\opt\exist\webapp\WEB-INF\logs\exist.log:
> java.nio.file.FileSystemException D:\opt\ex
> ist\webapp\WEB-INF\logs\exist.log: other program still using this file
> ,process can't access  (另一个程序正在使用此文件,进程无法访问。)
>
> 2017-04-05 18:41:18,422 qtp208184824-23 ERROR Unable to move file
> D:\opt\exist\webapp\WEB-INF\logs\exist.log to
> D:\opt\exist\webapp\WEB-INF\logs\exist.20170405184118.log:
> java.nio.file.FileSystemException D:\opt\exist\webapp\WEB-INF\logs\exist.log
> -> D:\opt\exist\webapp\WEB-INF\logs\exist.20170405184118.log:
> 另一个程序正在使用此文件,进程无法访问。
>
>
>
> many log produced: with error:
>
> 2017-04-05 18:40:04,730 [qtp208184824-23] WARN  (XQueryWatchDog.java
> [proceed]:156) - Query exceeded predefined timeout (21,252 ms.):
> attribute::{}value
> 2017-04-05 18:40:04,731 [qtp208184824-23] ERROR
> (NativeStructuralIndexWorker.java [findDescendantsByTagName]:207) - Error
> while searching structural index: exerr:ERROR The query exceeded the
> predefined timeout and has been killed. [at line 3, column 25]
> org.exist.xquery.TerminatedException$TimeoutException: exerr:ERROR The query
> exceeded the predefined timeout and has been killed. [at line 3, column 25]
> at org.exist.xquery.XQueryWatchDog.proceed(XQueryWatchDog.java:159)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.XQueryContext.proceed(XQueryContext.java:2296)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at
> org.exist.storage.structural.NativeStructuralIndexWorker$FindDescendantsCallback.indexInfo(NativeStructuralIndexWorker.java:392)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1847)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1763)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1763)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.storage.btree.BTree$BTreeNode.query(BTree.java:1763)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.storage.btree.BTree$BTreeNode.access$1200(BTree.java:907)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.storage.btree.BTree.query(BTree.java:383)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at
> org.exist.storage.structural.NativeStructuralIndexWorker.findDescendantsByTagName(NativeStructuralIndexWorker.java:205)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.LocationStep.getAttributes(LocationStep.java:657)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.LocationStep.eval(LocationStep.java:440)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at
> org.exist.xquery.GeneralComparison.quickNodeSetCompare(GeneralComparison.java:689)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.GeneralComparison.eval(GeneralComparison.java:470)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.modules.range.Lookup.eval(Lookup.java:317)
> ~[exist-index-range.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.InternalFunctionCall.eval(InternalFunctionCall.java:41)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.PathExpr.eval(PathExpr.java:276)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.Predicate.selectByNodeSet(Predicate.java:450)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.Predicate.evalPredicate(Predicate.java:326)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.LocationStep.processPredicate(LocationStep.java:256)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.LocationStep.applyPredicate(LocationStep.java:243)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.LocationStep.eval(LocationStep.java:474)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.pragmas.Optimize.eval(Optimize.java:170)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.ExtensionExpression.eval(ExtensionExpression.java:70)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.PathExpr.eval(PathExpr.java:276)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.XQuery.execute(XQuery.java:253)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xquery.XQuery.execute(XQuery.java:185)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.doQuery(RpcConnection.java:246)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.lambda$null$539(RpcConnection.java:1672)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at
> org.exist.xmlrpc.function.XmlRpcCompiledXQueryFunction.apply(XmlRpcCompiledXQueryFunction.java:41)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at
> org.exist.xmlrpc.RpcConnection.lambda$compileQuery$601(RpcConnection.java:3515)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.lambda$queryP$540(RpcConnection.java:1672)
> ~[exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.function.XmlRpcFunction.apply(XmlRpcFunction.java:45)
> [exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.withDb(RpcConnection.java:3771)
> [exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.withDb(RpcConnection.java:3755)
> [exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.queryP(RpcConnection.java:1642)
> [exist.jar:3.2.0-SNAPSHOT]
> at org.exist.xmlrpc.RpcConnection.queryP(RpcConnection.java:3393)
> [exist.jar:3.2.0-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_71]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_71]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_71]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_71]
> at
> org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.invoke(ReflectiveXmlRpcHandler.java:115)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at
> org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:106)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at
> org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:46)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:86)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at
> org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:200)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at
> org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(XmlRpcServletServer.java:112)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(XmlRpcServlet.java:196)
> [xmlrpc-server-3.1.3.jar:3.1.3]
> at org.exist.xmlrpc.RpcServlet.doPost(RpcServlet.java:67)
> [exist.jar:3.2.0-SNAPSHOT]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> [servlet-api-3.1.jar:3.1.0]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> [servlet-api-3.1.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566)
> [jetty-security-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:159)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:74)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.exist.http.urlrewrite.Forward.doRewrite(Forward.java:50)
> [exist-optional.jar:3.2.0-SNAPSHOT]
> at
> org.exist.http.urlrewrite.XQueryURLRewrite.service(XQueryURLRewrite.java:219)
> [exist-optional.jar:3.2.0-SNAPSHOT]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> [servlet-api-3.1.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837)
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)
> [jetty-security-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:396)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
> [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
> [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_71]
>
>
>
> ------
> and also I found the query timeout setting has no using for starting by run
> startup.bat mode
>
> --
> 此致
>
>    林晓东
>
> 莫愁前路无知己,天下谁人不识君。
>
>
>



--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Dannes Wessels-3
In reply to this post by lin_xd




On 5 Apr 2017, at 13:17 , 林晓东 <[hidden email]> wrote:

2017-04-05 18:41:17,646 qtp208184824-23 ERROR Unable to delete file D:\opt\exist\webapp\WEB-INF\logs\exist.log: java.nio.file.FileSystemException D:\opt\ex
ist\webapp\WEB-INF\logs\exist.log: other program still using this file ,process can't access  (另一个程序正在使用此文件,进程无法访问。)

2017-04-05 18:41:18,422 qtp208184824-23 ERROR Unable to move file D:\opt\exist\webapp\WEB-INF\logs\exist.log to D:\opt\exist\webapp\WEB-INF\logs\exist.20170405184118.log: java.nio.file.FileSystemException D:\opt\exist\webapp\WEB-INF\logs\exist.log -> D:\opt\exist\webapp\WEB-INF\logs\exist.20170405184118.log:

i expect the log file exist.log is open in  an application/editor/… ; please close it or check the permissions of the file or directory.

regards

Dannes

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Joe Wicentowski
In reply to this post by Adam Retter
Hi Adam,

> Standalone mode - i.e. server.sh should probably not be used any more
> Standard mode - i.e. startup.sh is what we use these days.

I admit I don't entirely understand what Standalone is, but should we
discuss deprecating Standalone mode and/or the server.sh method of
starting eXist up?

Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Dannes Wessels-3
Hi

On 6 Apr 2017, at 4:24 , Joe Wicentowski <[hidden email]> wrote:

Standalone mode - i.e. server.sh should probably not be used any more
Standard mode - i.e. startup.sh is what we use these days.

I admit I don't entirely understand what Standalone is, but should we
discuss deprecating Standalone mode and/or the server.sh method of
starting eXist up?

Yes, I think we can deprecate it; it makes the codebase more complex, and things can achieved in a different way….

it saves us test effort and maintenance….

D.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

lin_xd
Thanks.

But I want to know, do xquery on a costly one (without index optimized) and an optimized xquery on stardard mode and standalone moed is differ:

the standalone mode will not queue the optimized one after an no optimized one, and the standard mode will do.

do an query like this:  
declare default element namespace "urn:sc-wst:v1";
//DataSet[HDSN00.01.014/@value="20131201"][HDSN00.01.002/@value="test"]
this will do about 3min, for no index optimized. before this finish, do an query with optimized:
declare default element namespace "urn:sc-wst:v1";
//DataSet[HDSN00.01.013/@value="ED42F7DF7AE33943ABC075270F6195D4"]

standard mode will do longtime ,but standalone mode only 200ms. 

why?


--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-08 02:39:38,"Dannes Wessels" <[hidden email]> 写道:
Hi

On 6 Apr 2017, at 4:24 , Joe Wicentowski <[hidden email]> wrote:

Standalone mode - i.e. server.sh should probably not be used any more
Standard mode - i.e. startup.sh is what we use these days.

I admit I don't entirely understand what Standalone is, but should we
discuss deprecating Standalone mode and/or the server.sh method of
starting eXist up?

Yes, I think we can deprecate it; it makes the codebase more complex, and things can achieved in a different way….

it saves us test effort and maintenance….

D.



 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Dannes Wessels-3
Hi,


On 8 Apr 2017, at 15:47 , 林晓东 <[hidden email]> wrote:

the standalone mode will not queue the optimized one after an no optimized one, and the standard mode will do.

eXist-db will not behave different, these start scripts start in the end the same software. There is no magic.
The only thing I could think of is that the memory settings are a bit different.

Cheers

Dannes

--
eXist-db Native XML Database


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

lin_xd
but the startup.bat mode  using more memory. not the more the better? 




--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-09 04:15:21,"Dannes Wessels" <[hidden email]> 写道:
Hi,


On 8 Apr 2017, at 15:47 , 林晓东 <[hidden email]> wrote:

the standalone mode will not queue the optimized one after an no optimized one, and the standard mode will do.

eXist-db will not behave different, these start scripts start in the end the same software. There is no magic.
The only thing I could think of is that the memory settings are a bit different.

Cheers

Dannes

--
eXist-db Native XML Database



 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

lin_xd
In reply to this post by Dannes Wessels-3
I think it's not the case ,I have tested for many times,  for about 200000 xml record , the first query will postphone the next one in startup mode, but not in standalone mode.

and I have confused this for a long time , do a time  costly query for a large number of files will causing the server stop response.  we have discussed this before ,and you setup  a test server for testing , I don't know why ,your server is weill ,but my server still not do well for large number file database.
my conf file is: 

 <db-connection cacheSize="2048M" checkMaxCacheSize="true" collectionCache="128M" database="native"
        files="webapp/WEB-INF/data" pageSize="4096" nodesBuffer="1000" cacheShrinkThreshold="10000"
        doc-ids="default" minDiskSpace="128M">
       <query-pool max-stack-size="64" size="128" timeout="150000"                
                    timeout-check-interval="3000"/>

windows 10, java 1.8. develop version.

--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-09 04:15:21,"Dannes Wessels" <[hidden email]> 写道:
Hi,


On 8 Apr 2017, at 15:47 , 林晓东 <[hidden email]> wrote:

the standalone mode will not queue the optimized one after an no optimized one, and the standard mode will do.

eXist-db will not behave different, these start scripts start in the end the same software. There is no magic.
The only thing I could think of is that the memory settings are a bit different.

Cheers

Dannes

--
eXist-db Native XML Database



 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Dannes Wessels-3
Hi,

On 9 Apr 2017, at 14:43 , 林晓东 <[hidden email]> wrote:

I think it's not the case 

I can't provide an other answer :-P

D.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: what's different between standalone mode and stardard mode(start by bin\startup.bat)?

Adam Retter
In reply to this post by lin_xd
> I think it's not the case ,I have tested for many times,  for about 200000
> xml record , the first query will postphone the next one in startup mode,
> but not in standalone mode.
>
> and I have confused this for a long time , do a time  costly query for a
> large number of files will causing the server stop response.  we have
> discussed this before ,and you setup  a test server for testing , I don't
> know why ,your server is weill ,but my server still not do well for large
> number file database.

Okay so we would need much more information from you. eXist makes use
of shared and exclusive locks on both Collections and Documents.

If you have two queries that require the same exclusive (WRITE) locks
on the same documents and collections, then one query will have to
wait for the other to release the lock. This is true of any
multi-threaded system that uses locking.

eXist itself is able to service many users at the same time across
many resources. Dannes I believe is correct, there is no difference
between startup.sh or server.sh in that regard.

If you are creating a deadlock or livelock situation then please send
us the stacktrace so that we can further discuss this.


--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

open test server,please give some advices!

lin_xd

 I have setup a test existdb server at:  http://118.122.165.33:8091/exist/apps/dashboard/index.html with admin/pass account. 

I hope all give me some advice,
I have import about 627385 files into the existdb under /db/ehr/v2.  and which contains about 1660000 records like:

    <DataSet code="HSDB04.02" displayName="糖尿病患者随访信息数据集" codeSystem="WS365-2011" codeSystemName="城乡居民健康档案基本数据集">
    <HDSN00.01.013 dataelementName="文档编号" value="c989d15d-f73e-4044-bf6f-4742f9943a05"/>
    <HDSN00.01.014 dataelementName="文档生成日期" value="20131201"/>
    <HDSN00.01.001 dataelementName="记录日期" value="19760522"/>
    <HDSN00.01.002 dataelementName="记录人姓名" value="张xx"/>
    <HDSN00.01.003 dataelementName="记录人编号" value="110510000019542"/>
    <HDSN00.01.004 dataelementName="记录人联系电话" value="休息休息"/>
    <HDSN00.01.005 dataelementName="记录人所属机构名称" value="新型医院"/>
    <HDSN00.01.006 dataelementName="记录人所属机构代码" value="451134681"/>
    <HDSN00.01.007 dataelementName="记录人所属机构地址" value="xxx泰山北路一段173"/>
    <HDSN00.01.008 dataelementName="文档保管机构名称" value="卫生局健康档案管理中心"/>
    <HDSN00.01.009 dataelementName="文档保管机构代码" value="008380431"/>
    <HDSN00.01.010 dataelementName="文档保管机构地址" value="xxx路二段299号"/>
    <HDSN00.01.011 dataelementName="文档保管机构联系电话 " value="xxx999"/>
    <HDSN00.01.032 dataelementName="源ID" value="0839e6fd-3425-143f-1b83-cb408e4bd36b"/>
    <HDSD00.01.001 dataelementName="城乡居民健康档案编号" value="0085008509175450"/>
    <HDSD00.01.484 dataelementName="II型糖尿病患者随访服务记录编号" value="0839e6fd-3425-143f-1b83-cb408e4bd36b"/>
    <HDSD00.01.002 dataelementName="本人姓名" value="洗衣机"/>
    <HDSD00.01.008 dataelementName="本人电话号码" value="xxx-1234-5678"/>
    <HDSD00.01.003 dataelementName="性别代码" code="2" displayName="女性" codeSystem="2.16.156.10011.2.3.3.4" codeSystemName="生理性别代码表(GB/T 2261.1)"/>
    <HDSD00.01.004 dataelementName="出生日期" value="19000101"/>
    <HDSD00.01.006 dataelementName="身份证件号码" value="xxx"/>
    <HDSD00.01.599 dataelementName="家庭地址省" value="xxx省"/>
    <HDSD00.01.600 dataelementName="家庭地址市" value="德xxx市"/>
    <HDSD00.01.601 dataelementName="家庭地址县" value="xxx"/>
    <HDSD00.01.602 dataelementName="家庭地址乡" value=""/>
    <HDSD00.01.603 dataelementName="家庭地址村" value="xxx街"/>
    <HDSD00.01.604 dataelementName="家庭地址门牌号" value="55号2栋2单元"/>
    <HDSD00.01.424 dataelementName="邮政编码" value="618000"/>
    <HDSD00.01.017 dataelementName="婚姻状况代码" code="20" displayName="已婚" codeSystem="2.16.156.10011.2.3.3.5" codeSystemName="婚姻状况代码表"/>
    <HDSD00.01.012 dataelementName="民族" code="01" displayName="汉族" codeSystem="2.16.156.10011.2.3.3.3" codeSystemName="民族代码表(GB 3304)"/>
    <HDSD00.01.044 dataelementName="责任医师姓名" value="xxx"/>
    <HDSD00.01.467 dataelementName="随访方式代码" code="1" displayName="门诊随访" codeSystem="2.16.156.10011.2.3.1.183" codeSystemName="随访方式代码表"/>
    <HDSD00.01.466 dataelementName="本次随访日期" value="20110212"/>
    <HDSD00.01.046 dataelementName="症状代码" code="R00" displayName="心脏搏动异常" codeSystem="2.16.156.10011.2.3.3.11.1" codeSystemName="症状代码表(ICD-10 R)"/>
    <HDSD00.01.047 dataelementName="症状名称" value="心脏搏动异常"/>
    <HDSD00.01.342 dataelementName="收缩压" value="120"/>
    <HDSD00.01.343 dataelementName="舒张压" value="60"/>
    <HDSD00.01.056 dataelementName="体重(kg)" value="60"/>
    <HDSD00.01.209 dataelementName="目标体重(kg)" value="60"/>
    <HDSD00.01.055 dataelementName="身高(cm)" value=""/>
    <HDSD00.01.058 dataelementName="体质指数" value="23"/>
    <HDSD00.01.468 dataelementName="目标体质指数" value="23"/>
    <HDSD00.01.485 dataelementName="足背动脉搏动标志" value="false"/>
    <HDSD00.01.469 dataelementName="其他阳性体征" value="略"/>
    <HDSD00.01.071 dataelementName="日吸烟量(支)" value="5"/>
    <HDSD00.01.470 dataelementName="目标日吸烟量(支)" value="7"/>
    <HDSD00.01.075 dataelementName="日饮酒量(两)" value="2"/>
    <HDSD00.01.471 dataelementName="目标日饮酒量(两)" value="2"/>
    <HDSD00.01.065 dataelementName="运动频率代码" code="1" displayName="每天" codeSystem="2.16.156.10011.2.3.1.23" codeSystemName="身体活动频率代码表"/>
    <HDSD00.01.472 dataelementName="目标运动频率代码" code="1" displayName="每天" codeSystem="2.16.156.10011.2.3.1.23" codeSystemName="身体活动频率代码表"/>
    <HDSD00.01.066 dataelementName="运动时长(min)" value="30"/>
    <HDSD00.01.473 dataelementName="目标运动时长(min)" value="30"/>
    <HDSD00.01.486 dataelementName="日主食量(g)" value="5"/>
    <HDSD00.01.487 dataelementName="目标日主食量(g)" value="5"/>
    <HDSD00.01.476 dataelementName="心理调整评价结果代码" code="1" displayName="良好" codeSystem="2.16.156.10011.2.3.2.26" codeSystemName="心理调整评价结果代码表"/>
    <HDSD00.01.477 dataelementName="随访遵医行为评价结果代码" code="1" displayName="良好" codeSystem="2.16.156.10011.2.3.2.27" codeSystemName="随访遵医行为评价结果代码表"/>
    <HDSD00.01.148 dataelementName="空腹血糖值(mmol/L)" value="3"/>
    <HDSD00.01.149 dataelementName="餐后两小时血糖值(mmol/L)" value="2"/>
    <HDSD00.01.153 dataelementName="糖化血红蛋白值(%)" value="3"/>
    <HDSD00.13.01>
      <row>
        <HDSD00.01.478 dataelementName="辅助检查项目" value="略"/>
        <HDSD00.01.460 dataelementName="辅助检查结果" value="略"/>
        <HDSD00.01.479 dataelementName="检查(测)人员姓名" value="刘欢"/>
        <HDSD00.01.045 dataelementName="检查(测)日期" value="20121201"/>
      </row>
    </HDSD00.13.01>    
    <HDSD00.01.200 dataelementName="服药依从性代码" code="1" displayName="规律" codeSystem="2.16.156.10011.2.3.2.12" codeSystemName="服药依从性代码表"/>
    <HDSD00.01.480 dataelementName="药物不良反应标志" value="true"/>
    <HDSD00.01.481 dataelementName="药物不良反应描述" value="发烧,腿疼等不良反应"/>
    <HDSD00.01.488 dataelementName="低血糖反应代码" code="1" displayName="无" codeSystem="2.16.156.10011.2.3.2.28" codeSystemName="低血糖反应代码表"/>
    <HDSD00.01.482 dataelementName="随访评价结果代码" code="2" displayName="控制不满意" codeSystem="2.16.156.10011.2.3.1.150" codeSystemName="随访评价结果代码表"/>
    <HDSD00.13.02>
      <row>
        <HDSD00.01.193 dataelementName="中药类别代码" code="1" displayName="未使用" codeSystem="2.16.156.10011.2.3.1.157" codeSystemName="中药使用类别代码表"/>
        <HDSD00.01.194 dataelementName="药物名称" value="氢氯噻臻"/>
        <HDSD00.01.195 dataelementName="药物使用频率" value="3"/>
        <HDSD00.01.196 dataelementName="药物使用剂量单位" value="mg"/>
        <HDSD00.01.197 dataelementName="药物使用次剂量" value="20"/>
        <HDSD00.01.198 dataelementName="药物使用总剂量" value="30"/>
        <HDSD00.01.199 dataelementName="药物使用途径代码" code="1" displayName="口服" codeSystem="2.16.156.10011.2.3.1.158" codeSystemName="用药途径代码表"/>
      </row>
    </HDSD00.13.02>
    <HDSD00.13.04>
      <row>
        <HDSD00.01.489 dataelementName="胰岛素用药种类" value="胰岛素种类"/>
        <HDSD00.01.490 dataelementName="胰岛素用药使用频率(次/d)" value="3"/>
        <HDSD00.01.491 dataelementName="胰岛素用药次剂量(U)" value="20"/>
      </row>
    </HDSD00.13.04>
    <HDSD00.01.281 dataelementName="转诊标志" value="true"/>
    <HDSD00.13.03>
      <row>
        <HDSD00.01.284 dataelementName="转诊原因" value="原因:呼吸困难,病情加重"/>
        <HDSD00.01.282 dataelementName="转入医疗机构名称" value="德阳市妇幼保健院"/>
        <HDSD00.01.283 dataelementName="转入机构科室名称" value="内科"/>
      </row>
    </HDSD00.13.03>    
    <HDSD00.01.483 dataelementName="下次随访日期" value="20112430"/>
    <HDSD00.01.330 dataelementName="随访医师姓名" value="张政"/>
  </DataSet>
===================================
and has config some index like:
  <index xmlns:scwst="urn:sc-wst:v1">
        <!-- Range indexes -->
        <range>
            <create qname="scwst:DataSet" type="xs:string">
                <field name="pid" match="scwst:HDSD00.01.006/@value" type="xs:string"/>
                <field name="pname" match="scwst:HDSD00.01.002/@value" type="xs:string"/>
                <field name="psex" match="scwst:HDSD00.01.003/@code" type="xs:string"/>
                <field name="ehrid" match="scwst:HDSN00.01.013/@value" type="xs:string"/>
                <field name="ehrhid" match="scwst:HDSD00.01.001/@value" type="xs:string"/>
                <field name="eorgid" match="scwst:HDSN00.01.006/@value" type="xs:string"/>
                <field name="etime" match="scwst:HDSN00.01.001/@value" type="xs:string"/>
                
                <!--field name="val" match="//@value" type="xs:string"/-->
                <field name="ftype" match="@code" type="xs:string"/>
            </create>
        </range>
    </index>

I want confirm, when do a query without index optimized, this query will causing the other index based query stop response till the first finished, something like queuing or no concurrent query .  all the indexs are working.


thanks. 
--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

At 2017-04-13 07:55:44, "林晓东" <[hidden email]> wrote:

Please give some advice for the install at http://118.122.165.33:8091/exist/apps/dashboard/index.html (admin/pass)

Thanks




--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-12 14:26:33,"林晓东" <[hidden email]> 写道:

yes. index is ok.
 you can access it.

<collection xmlns="http://exist-db.org/collection-config/1.0">
    <index xmlns:scwst="urn:sc-wst:v1">
        <!-- Range indexes -->
        <range>
            <create qname="scwst:DataSet" type="xs:string">
                <field name="pid" match="scwst:HDSD00.01.006/@value" type="xs:string"/>
                <field name="pname" match="scwst:HDSD00.01.002/@value" type="xs:string"/>
                <field name="psex" match="scwst:HDSD00.01.003/@code" type="xs:string"/>
                <field name="ehrid" match="scwst:HDSN00.01.013/@value" type="xs:string"/>
                <field name="ehrhid" match="scwst:HDSD00.01.001/@value" type="xs:string"/>
                <field name="eorgid" match="scwst:HDSN00.01.006/@value" type="xs:string"/>
                <field name="etime" match="scwst:HDSN00.01.001/@value" type="xs:string"/>
                
                <!--field name="val" match="//@value" type="xs:string"/-->
                <field name="ftype" match="@code" type="xs:string"/>
            </create>
        </range>
    </index>
</collection>



--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-12 14:15:15,"Dannes Wessels" <[hidden email]> 写道:
do you define "scwst:" in collection.xconf?

On Tue, Apr 11, 2017 at 6:08 PM, 林晓东 <[hidden email]> wrote:

        <range>
            <create qname="scwst:DataSet" type="xs:string">
                <field name="pid" match="scwst:HDSD00.01.006/@value" type="xs:string"/>
                <field name="pname" match="scwst:HDSD00.01.002/@value" type="xs:string"/>
                <field name="psex" match="scwst:HDSD00.01.003/@code" type="xs:string"/>
                <field name="ehrid" match="scwst:HDSN00.01.013/@value" type="xs:string"/>
                <field name="ehrhid" match="scwst:HDSD00.01.001/@value" type="xs:string"/>
                <field name="eorgid" match="scwst:HDSN00.01.006/@value" type="xs:string"/>
                <field name="etime" match="scwst:HDSN00.01.001/@value" type="xs:string"/>                
                <!--field name="val" match="//@value" type="xs:string"/-->
                <field name="ftype" match="@code" type="xs:string"/>
            </create>
        </range>



--
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624


 





 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: open test server,please give some advices!

Joe Wicentowski
Hi Xiaodong,

> I want confirm, when do a query without index optimized, this query will causing the other index based query stop response till the first finished, something like queuing or no concurrent query .  all the indexs are working.

When you say "query without index optimized," do you mean that the
query relies on data in the database but does not use indexes?  Or
just a query that (perhaps because it involves in-memory comparisons)
cannot be index-optimized?  Maybe we need some more information about
your query?  What leads you to think that this query is the one that
is "causing the other index based query stop response till the first
finished"?

If the query you're asking about does rely on data in the database but
does not use indexes, is there a reason you have not defined an index
on these structures in question?  I assume you've read Wolfgang's
Query Tuning article (at
http://exist-db.org/exist/apps/doc/tuning.xml)?  Let me quote the
section on the importance of defining range indexes on strongly typed
data or short strings for certain queries: "As long as no index is
defined, eXist-db [may have] to scan over every... element in the
db..."

I can imagine that as a database grows in size, this task of "scanning
over every element in the db" must also grow.  Thus, I would expect
queries that need to read data from the database that are not backed
by indexes could cause performance to suffer.

Finally, this probably has no direct bearing on your issue, but I
noticed that (in the quoted portion below my signature) you've got
duplicate indexes on the following paths:

- scwst:HDSN00.01.001/@value ("etime" and "ehrhid" - note that the
only value for this element's @dataelementName attribute is "记录日期")
- scwst:HDSD00.01.006/@value ("pid" and "eorgid" - note that the only
value for this element's @dataelementName attribute is "身份证件号码")

Joe

> and has config some index like:
>   <index xmlns:scwst="urn:sc-wst:v1">
>         <!-- Range indexes -->
>         <range>
>             <create qname="scwst:DataSet" type="xs:string">
>                 <field name="pid" match="scwst:HDSD00.01.006/@value"
> type="xs:string"/>
>                 <field name="pname" match="scwst:HDSD00.01.002/@value"
> type="xs:string"/>
>                 <field name="psex" match="scwst:HDSD00.01.003/@code"
> type="xs:string"/>
>                 <field name="ehrid" match="scwst:HDSN00.01.013/@value"
> type="xs:string"/>
>                 <field name="ehrhid" match="scwst:HDSD00.01.001/@value"
> type="xs:string"/>
>                 <field name="eorgid" match="scwst:HDSN00.01.006/@value"
> type="xs:string"/>
>                 <field name="etime" match="scwst:HDSN00.01.001/@value"
> type="xs:string"/>
>
>                 <!--field name="val" match="//@value" type="xs:string"/-->
>                 <field name="ftype" match="@code" type="xs:string"/>
>             </create>
>         </range>
>     </index>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: open test server,please give some advices!

lin_xd
Thanks.
    I think , when you have a large database, perhaps you have done a query without index based.(which mean's no index has defined for it,it's impossible for define  indexes for any query,I think.  ),so, the query may cost many time to scan db, that's normal,  but I think ,that should not stop other query working ,but now ,I found the exist-db server will stop other query(or maybe it's very slow) , and some app like the monex will stop response ,etc.. 

what you have asked:  say "query without index optimized," means some query has not index to using,just a costly query,

these is not different index: scwst:HDSN00.01.001 and scwst:HDSD00.01.006, one is '..N', one is '...D'
>- scwst:HDSN00.01.001/@value ("etime" and "ehrhid" - note that the
>only value for this element's @dataelementName attribute is "记录日期")
>- scwst:HDSD00.01.006/@value ("pid" and "eorgid" - note that the only
>value for this element's @dataelementName attribute is "身份证件号码")




--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。


At 2017-04-16 10:58:45, "Joe Wicentowski" <[hidden email]> wrote: >Hi Xiaodong, > >> I want confirm, when do a query without index optimized, this query will causing the other index based query stop response till the first finished, something like queuing or no concurrent query . all the indexs are working. > >When you say "query without index optimized," do you mean that the >query relies on data in the database but does not use indexes? Or >just a query that (perhaps because it involves in-memory comparisons) >cannot be index-optimized? Maybe we need some more information about >your query? What leads you to think that this query is the one that >is "causing the other index based query stop response till the first >finished"? > >If the query you're asking about does rely on data in the database but >does not use indexes, is there a reason you have not defined an index >on these structures in question? I assume you've read Wolfgang's >Query Tuning article (at >http://exist-db.org/exist/apps/doc/tuning.xml)? Let me quote the >section on the importance of defining range indexes on strongly typed >data or short strings for certain queries: "As long as no index is >defined, eXist-db [may have] to scan over every... element in the >db..." > >I can imagine that as a database grows in size, this task of "scanning >over every element in the db" must also grow. Thus, I would expect >queries that need to read data from the database that are not backed >by indexes could cause performance to suffer. > >Finally, this probably has no direct bearing on your issue, but I >noticed that (in the quoted portion below my signature) you've got >duplicate indexes on the following paths: > >- scwst:HDSN00.01.001/@value ("etime" and "ehrhid" - note that the >only value for this element's @dataelementName attribute is "记录日期") >- scwst:HDSD00.01.006/@value ("pid" and "eorgid" - note that the only >value for this element's @dataelementName attribute is "身份证件号码") > >Joe > >> and has config some index like: >> <index xmlns:scwst="urn:sc-wst:v1"> >> <!-- Range indexes --> >> <range> >> <create qname="scwst:DataSet" type="xs:string"> >> <field name="pid" match="scwst:HDSD00.01.006/@value" >> type="xs:string"/> >> <field name="pname" match="scwst:HDSD00.01.002/@value" >> type="xs:string"/> >> <field name="psex" match="scwst:HDSD00.01.003/@code" >> type="xs:string"/> >> <field name="ehrid" match="scwst:HDSN00.01.013/@value" >> type="xs:string"/> >> <field name="ehrhid" match="scwst:HDSD00.01.001/@value" >> type="xs:string"/> >> <field name="eorgid" match="scwst:HDSN00.01.006/@value" >> type="xs:string"/> >> <field name="etime" match="scwst:HDSN00.01.001/@value" >> type="xs:string"/> >> >> <!--field name="val" match="//@value" type="xs:string"/--> >> <field name="ftype" match="@code" type="xs:string"/> >> </create> >> </range> >> </index>


 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: open test server,please give some advices!

Joe Wicentowski
Hi Xiaodong,

>     I think , when you have a large database, perhaps you have done a query
> without index based.(which mean's no index has defined for it,it's
> impossible for define  indexes for any query,I think.  ),so, the query may
> cost many time to scan db, that's normal,  but I think ,that should not stop
> other query working ,but now ,I found the exist-db server will stop other
> query(or maybe it's very slow) , and some app like the monex will stop
> response ,etc..
>
> what you have asked:  say "query without index optimized," means some query
> has not index to using,just a costly query,

For the purposes of understanding the bottleneck you are trying to
describe, we need to distinguish between database-backed queries and
non-database-backed queries.  A non-database-backed query cannot be
optimized by indexes.  A database-backed query *could* be (but not
necessarily).  It sounds like your query is a case where you could
apply an index, but where it's not convenient to, since reindexing
itself is an expensive and blocking operation.  Is that right?

So your question is really:

Does a database-backed query without indexes block other queries on
the same collections?

Is that right?

> these is not different index: scwst:HDSN00.01.001 and scwst:HDSD00.01.006,
> one is '..N', one is '...D'

Sorry, you're right!

Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

回复:open test server,please give some advices!

lin_xd
yes, but I dont know whether the query on different collection affect each other,from my experience,it is the case.
and the index is necessary,but not always satisfy the query.
reindexis can be think as an exception,

发自网易邮箱大师

2017年04月16日 22:28[hidden email] 写道:
Hi Xiaodong,

>     I think , when you have a large database, perhaps you have done a query
> without index based.(which mean's no index has defined for it,it's
> impossible for define  indexes for any query,I think.  ),so, the query may
> cost many time to scan db, that's normal,  but I think ,that should not stop
> other query working ,but now ,I found the exist-db server will stop other
> query(or maybe it's very slow) , and some app like the monex will stop
> response ,etc..
>
> what you have asked:  say "query without index optimized," means some query
> has not index to using,just a costly query,

For the purposes of understanding the bottleneck you are trying to
describe, we need to distinguish between database-backed queries and
non-database-backed queries.  A non-database-backed query cannot be
optimized by indexes.  A database-backed query *could* be (but not
necessarily).  It sounds like your query is a case where you could
apply an index, but where it's not convenient to, since reindexing
itself is an expensive and blocking operation.  Is that right?

So your question is really:

Does a database-backed query without indexes block other queries on
the same collections?

Is that right?

> these is not different index: scwst:HDSN00.01.001 and scwst:HDSD00.01.006,
> one is '..N', one is '...D'

Sorry, you're right!

Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 回复:open test server,please give some advices!

lin_xd
first do in exide, no index can be used: 
declare default element namespace "urn:sc-wst:v1";
collection('/db/ehr/v2/510682')//DataSet[HDSN00.01.017/@value="51062310120201001001"]
then,this can be index optimized:
declare default element namespace "urn:sc-wst:v1";
 collection('/db/ehr/v2/008500')//DataSet[HDSN00.01.013/@value="a894317f-53da-486f-a1df-cea23200273d"]     

the second will waiting..., just do this ,only need 0.004s





--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-17 05:59:57,"林晓东" <[hidden email]> 写道:
yes, but I dont know whether the query on different collection affect each other,from my experience,it is the case.
and the index is necessary,but not always satisfy the query.
reindexis can be think as an exception,

发自网易邮箱大师

2017年04月16日 22:28[hidden email] 写道:
Hi Xiaodong,

>     I think , when you have a large database, perhaps you have done a query
> without index based.(which mean's no index has defined for it,it's
> impossible for define  indexes for any query,I think.  ),so, the query may
> cost many time to scan db, that's normal,  but I think ,that should not stop
> other query working ,but now ,I found the exist-db server will stop other
> query(or maybe it's very slow) , and some app like the monex will stop
> response ,etc..
>
> what you have asked:  say "query without index optimized," means some query
> has not index to using,just a costly query,

For the purposes of understanding the bottleneck you are trying to
describe, we need to distinguish between database-backed queries and
non-database-backed queries.  A non-database-backed query cannot be
optimized by indexes.  A database-backed query *could* be (but not
necessarily).  It sounds like your query is a case where you could
apply an index, but where it's not convenient to, since reindexing
itself is an expensive and blocking operation.  Is that right?

So your question is really:

Does a database-backed query without indexes block other queries on
the same collections?

Is that right?

> these is not different index: scwst:HDSN00.01.001 and scwst:HDSD00.01.006,
> one is '..N', one is '...D'

Sorry, you're right!

Joe



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 回复:open test server,please give some advices!

Dominique Rabeuf
Get connected to
But warning
App sources can be read without login
One of them seems to contain password !

2017-04-17 17:00 GMT+02:00 林晓东 <[hidden email]>:
first do in exide, no index can be used: 
declare default element namespace "urn:sc-wst:v1";
collection('/db/ehr/v2/510682')//DataSet[HDSN00.01.017/@value="51062310120201001001"]
then,this can be index optimized:
declare default element namespace "urn:sc-wst:v1";
 collection('/db/ehr/v2/008500')//DataSet[HDSN00.01.013/@value="a894317f-53da-486f-a1df-cea23200273d"]     

the second will waiting..., just do this ,only need 0.004s





--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-17 05:59:57,"林晓东" <[hidden email]> 写道:
yes, but I dont know whether the query on different collection affect each other,from my experience,it is the case.
and the index is necessary,but not always satisfy the query.
reindexis can be think as an exception,

发自网易邮箱大师

2017年04月16日 22:28[hidden email] 写道:
Hi Xiaodong,

>     I think , when you have a large database, perhaps you have done a query
> without index based.(which mean's no index has defined for it,it's
> impossible for define  indexes for any query,I think.  ),so, the query may
> cost many time to scan db, that's normal,  but I think ,that should not stop
> other query working ,but now ,I found the exist-db server will stop other
> query(or maybe it's very slow) , and some app like the monex will stop
> response ,etc..
>
> what you have asked:  say "query without index optimized," means some query
> has not index to using,just a costly query,

For the purposes of understanding the bottleneck you are trying to
describe, we need to distinguish between database-backed queries and
non-database-backed queries.  A non-database-backed query cannot be
optimized by indexes.  A database-backed query *could* be (but not
necessarily).  It sounds like your query is a case where you could
apply an index, but where it's not convenient to, since reindexing
itself is an expensive and blocking operation.  Is that right?

So your question is really:

Does a database-backed query without indexes block other queries on
the same collections?

Is that right?

> these is not different index: scwst:HDSN00.01.001 and scwst:HDSD00.01.006,
> one is '..N', one is '...D'

Sorry, you're right!

Joe



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open




--
Dominique Rabeuf

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 回复:open test server,please give some advices!

lin_xd
password : pass, user :admin




--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-17 23:18:23,"Dominique Rabeuf" <[hidden email]> 写道:
Get connected to
But warning
App sources can be read without login
One of them seems to contain password !

2017-04-17 17:00 GMT+02:00 林晓东 <[hidden email]>:
first do in exide, no index can be used: 
declare default element namespace "urn:sc-wst:v1";
collection('/db/ehr/v2/510682')//DataSet[HDSN00.01.017/@value="51062310120201001001"]
then,this can be index optimized:
declare default element namespace "urn:sc-wst:v1";
 collection('/db/ehr/v2/008500')//DataSet[HDSN00.01.013/@value="a894317f-53da-486f-a1df-cea23200273d"]     

the second will waiting..., just do this ,only need 0.004s





--
此致

   林晓东

莫愁前路无知己,天下谁人不识君。

在 2017-04-17 05:59:57,"林晓东" <[hidden email]> 写道:
yes, but I dont know whether the query on different collection affect each other,from my experience,it is the case.
and the index is necessary,but not always satisfy the query.
reindexis can be think as an exception,

发自网易邮箱大师

2017年04月16日 22:28[hidden email] 写道:
Hi Xiaodong,

>     I think , when you have a large database, perhaps you have done a query
> without index based.(which mean's no index has defined for it,it's
> impossible for define  indexes for any query,I think.  ),so, the query may
> cost many time to scan db, that's normal,  but I think ,that should not stop
> other query working ,but now ,I found the exist-db server will stop other
> query(or maybe it's very slow) , and some app like the monex will stop
> response ,etc..
>
> what you have asked:  say "query without index optimized," means some query
> has not index to using,just a costly query,

For the purposes of understanding the bottleneck you are trying to
describe, we need to distinguish between database-backed queries and
non-database-backed queries.  A non-database-backed query cannot be
optimized by indexes.  A database-backed query *could* be (but not
necessarily).  It sounds like your query is a case where you could
apply an index, but where it's not convenient to, since reindexing
itself is an expensive and blocking operation.  Is that right?

So your question is really:

Does a database-backed query without indexes block other queries on
the same collections?

Is that right?

> these is not different index: scwst:HDSN00.01.001 and scwst:HDSD00.01.006,
> one is '..N', one is '...D'

Sorry, you're right!

Joe



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open




--
Dominique Rabeuf


 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 回复:open test server,please give some advices!

Joe Wicentowski
In reply to this post by lin_xd
Hi Xiaodong,

I can confirm your results when running your two queries in eXide:

1. The first, non-index-based ("slow") query takes ~25s
2. The second, index-backed ("fast") query returns in ~.004s
3. Starting the "fast" query after having submitted the "slow" query
(in eXide) causes the results of the "fast" to be delayed until after
the "slow" one is completed.

Also, I saved your two queries as /db/test1.xq (slow) and /db/test2.xq
(fast), and noticed *different* results:

4. Running the two queries outside of eXide, by directly requesting
http://118.122.165.33:8091/exist/rest/db/test1.xq and
http://118.122.165.33:8091/exist/rest/db/test2.xq - allowed test2.xq
to complete quickly and without delay, while test1.xq took the same
~25s to complete.  Running a 3rd query involving no database hits or ,
just "1" (to return the same input)

Attached are two screenshots showing how these requests appear to
queue in eXide (under Chrome 57.0.2987.133).

This suggests that some of the "queueing" you're seeing has something
to do with eXide's ajax execution, and that eXist is capable of
performing the two queries at the same time.

Joe


> declare default element namespace "urn:sc-wst:v1";
> collection('/db/ehr/v2/510682')//DataSet[HDSN00.01.017/@value="51062310120201001001"]
>
> then,this can be index optimized:
>
> declare default element namespace "urn:sc-wst:v1";
> collection('/db/ehr/v2/008500')//DataSet[HDSN00.01.013/@value="a894317f-53da-486f-a1df-cea23200273d"]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

01-requests-pending.png (28K) Download Attachment
02-requests-completed.png (46K) Download Attachment
12
Loading...