Hi Christian and Florian,

I recall that the DBA web interface didn’t like the YAJSW log files, although that didn’t seem surprising because the YAJSW log files are in a different format than BaseX log files. It’s been a while since I tried this so I don’t have the details now. YAJSW can be configured to save its log files in a different location.

Kind regards,

Vincent

_____________________________________________

Vincent M. Lizzi

Head of Information Standards | Taylor & Francis Group

vincent.lizzi@taylorandfrancis.com

Information Classification: General

From: Christian Grün <christian.gruen@gmail.com>
Sent: Thursday, May 12, 2022 8:03 AM
To: Florian Schmitt <ml-basex@florian-schmitt.net>; Lizzi, Vincent <Vincent.Lizzi@taylorandfrancis.com>
Cc: BaseX <basex-talk@mailman.uni-konstanz.de>
Subject: Re: [basex-talk] First steps with client/server on Linux - bulk import; error message in dba

Thanks for the observation, Florian.

> After modifying permissions for the $basexhome/data/.logs directory, i now have a logfile showing the following entry:

I hope the latest snapshot resolves the Yajsw/.logs bug [1].

> [POST] /dba/log?name=wrapper-basex&page=1; Unexpected error: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@mailman.uni-konstanz.de Version: BaseX 9.7.1 Java: Private Build, 11.0.15 OS: Linux, amd64 Stack Trace: java.lang.NullPointerException at

I’ve added Vincent Lizzi to the conversation, who has gratefully added
the documentation on YAJSW: Maybe it would be sensible to move the
wrapper-basex.log file out of the .logs directory? I don’t expect any
complications if it’s stored in data/.

I’ll additionally check if we can prevent admin:logs from crashing if
the log input does not conform to the usual pattern.

Best,
Christian

[1] https://github.com/BaseXdb/basex/issues/2105

> [POST] /dba/log?name=wrapper-basex&page=1; Unexpected error: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@mailman.uni-konstanz.de Version: BaseX 9.7.1 Java: Private Build, 11.0.15 OS: Linux, amd64 Stack Trace: java.lang.NullPointerException at org.basex.query.func.admin.AdminLogs$1.next(AdminLogs.java:84) at org.basex.query.QueryContext.next(QueryContext.java:358) at org.basex.query.func.fn.FnReverse.iter(FnReverse.java:61) at org.basex.query.expr.gflwor.For$1.next(For.java:112) at org.basex.query.expr.gflwor.Let$LetEval.next(Let.java:144) at org.basex.query.expr.gflwor.Where$1.next(Where.java:41) at org.basex.query.expr.gflwor.GFLWOR.value(GFLWOR.java:82) at org.basex.query.expr.gflwor.Let$LetEval.next(Let.java:146) at org.basex.query.expr.gflwor.GFLWOR$1.next(GFLWOR.java:68) at org.basex.query.scope.MainModule$1.next(MainModule.java:67) at org.basex.http.restxq.RestXqResponse.serialize(RestXqResponse.java:87) at org.basex.http.web.WebResponse.create(WebResponse.java:58) at org.basex.http.restxq.R...

> That NPE is thrown if i try to access the wrapper-basex log using the DBA web interface. Accessing the BaseX logs works fine.