exist-development — eXist Developer's List

[Exist-development] Broker leak and missuse detector

[Dmitriy S. <sha...@gm...>]

Hi,

I release java agent that help with broker leak and missuse detection.

https://github.com/shabanovd/aXent

-- 
Dmitriy Shabanov

Re: [Exist-development] [Exist-open] Socket.io eXist-db

[W.S. H. <ws...@gm...>]

Don't use exist for ws. Exist depends on writing java and configuring
Jetty, and there's nothing prefab in that area yet AFAIK. Use whatever
you're using in node.js and connect to exist RESTfully. If you do insist on
using Jetty, have a look at cometd.

2016-02-17 22:58 GMT+01:00 Joe Wicentowski <jo...@gm...>:

> Hi Masoud,
>
> > How can I use Socket.io in exist-db?
> > or if no, what is solution for I/O real time apps with eXist-db? (for
> example real time notification)
>
> I'm not sure if this is relevant to your needs or not, but you may
> want to take a look at the Messaging & Replication extension:
>
>   https://github.com/eXist-db/messaging-replication
>
> Joe
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>



-- 

W.S. Hager
Lagua Web Solutions
http://lagua.nl

Re: [Exist-development] Socket.io eXist-db

[Joe W. <jo...@gm...>]

Hi Masoud,

> How can I use Socket.io in exist-db?
> or if no, what is solution for I/O real time apps with eXist-db? (for example real time notification)

I'm not sure if this is relevant to your needs or not, but you may
want to take a look at the Messaging & Replication extension:

  https://github.com/eXist-db/messaging-replication

Joe

[Exist-development] Socket.io eXist-db

[Masoud V. <ma...@gm...>]

Hi all,
How can I use Socket.io in exist-db?
or if no, what is solution for I/O real time apps with eXist-db? (for
example real time notification)

thanks

Re: [Exist-development] Too many CLOSE_WAIT status in jetty

[Masoud V. <ma...@gm...>]

eXist-db version is 2.2
java version is oracle java 1.7
OS is Centos 7


On Tue, Feb 16, 2016 at 12:27 AM, Masoud Vakili <ma...@gm...> wrote:

> Hi all,
> I had configured eXist-db to be behind of an other web server, at the
> first, I configured it to proxying eXist-db behind an Apache web server;
> all of things were good until I understood that the performance has
> decreased very much, though the memory and cpu usage were normal! by
> netstat command I noticed that too many connections are in CLOSE_WAIT
> status and not terminated!! I searched very much and imagined the bug is
> for apache! therefore I change Apache with Nginx web server! but the
> problem not solved!! and after 3 or 4 days, too many connections will be
> stays on CLOSE_WAIT still! the solution is restart the eXist process
> (java)! (right now, 214 connections are in close_wait status!)
> so, I guessing the problem may be from jetty or jvm, therefore I searched
> around this issue and found following link (and some other links
> <https://www.google.com/?gws_rd=ssl#q=jetty+CLOSE_WAIT+>):
>
> http://stackoverflow.com/questions/23644090/too-many-close-wait-in-jetty-9-0-3
>
> http://stackoverflow.com/questions/28875406/why-am-i-seeing-lots-of-sockets-in-close-wait-status-when-webservice-stops-worki
> ...
> now, i want to help for solve this issue! what is the solution?
> (in the first link, writer is mentioned to use closeIdleConnections(0)
> function; is it helpful? Where is it being?)
>
> Thanks
>

[Exist-development] Too many CLOSE_WAIT status in jetty

[Masoud V. <ma...@gm...>]

Hi all,
I had configured eXist-db to be behind of an other web server, at the
first, I configured it to proxying eXist-db behind an Apache web server;
all of things were good until I understood that the performance has
decreased very much, though the memory and cpu usage were normal! by
netstat command I noticed that too many connections are in CLOSE_WAIT
status and not terminated!! I searched very much and imagined the bug is
for apache! therefore I change Apache with Nginx web server! but the
problem not solved!! and after 3 or 4 days, too many connections will be
stays on CLOSE_WAIT still! the solution is restart the eXist process
(java)! (right now, 214 connections are in close_wait status!)
so, I guessing the problem may be from jetty or jvm, therefore I searched
around this issue and found following link (and some other links
<https://www.google.com/?gws_rd=ssl#q=jetty+CLOSE_WAIT+>):
http://stackoverflow.com/questions/23644090/too-many-close-wait-in-jetty-9-0-3
http://stackoverflow.com/questions/28875406/why-am-i-seeing-lots-of-sockets-in-close-wait-status-when-webservice-stops-worki
...
now, i want to help for solve this issue! what is the solution?
(in the first link, writer is mentioned to use closeIdleConnections(0)
function; is it helpful? Where is it being?)

Thanks

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Adam R. <ad...@ex...>]

Hey Joe,

Good question!

Ultimately it is down to a lack of resources to be able to do this.
However, the good news is that you could help ;-)

Leo from BaseX started a test-suite harness for the W3C XQuery Test
Suite, he wrote it in XQuery for BaseX. I started porting it over to
eXist early last year, but never had the time or pressing need to
complete it. My branch with the changes for eXist is here -
https://github.com/adamretter/fots-basex/tree/exist. Whilst a work in
progress, I think I was able to get some tests running. The nice thing
is that EXPath uses the same Test Suite format as W3C, so if we can
get a test harness working, we can run many tests :-)

Perhaps this is something you would like to pick up and work on? I
could certainly offer guidance if you get stuck... but well I think
you are probably a pretty good XQuery programmer ;-)

Cheers Adam.

On 19 January 2016 at 04:33, Joe Wicentowski <jo...@gm...> wrote:
> Hi all,
>
> I notice eXist isn't included in this round of tests.  I'd be
> interested to know what are the barriers or obstacles to running the
> tests and participating in these exercises?
>
> I imagine the release of eXist 3.0 is a higher priority for the
> project than passing a not-yet-final spec, among others.  But I think
> that eXist's presence at some point would help the WG's work and
> strengthen the spec's goal of being supported by many implementations.
> Even if eXist doesn't promise complete XQ3.1 coverage (heck, they keep
> adding new features like templates!), the areas it does support are, I
> think, quite well developed - and this hard work would be worth
> celebrating through inclusion in these tests.
>
> Joe
>
>
> ---------- Forwarded message ----------
> From: O'Neil Delpratt <on...@sa...>
> Date: Mon, Jan 18, 2016 at 9:40 AM
> Subject: Reporting on QT3 test results for the 3.1 Specs
> To: pub...@w3...
>
>
> Dear All,
>
> I have re-generated the reports on the implementation results received
> for the QT3 test suite. See update:
> http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html
> We now have three implementations for XQuery 3.1, with one being
> anonymous. However we only have one for XPath 3.1.
>
> We have been working on the main page today. Specifically the stats on
> the optional features. We found that there were some overlap reported
> in the passes and failures. For example under ‘staticTyping’ it is
> reported that there are 75 test not being passed by any
> implementation. Under the 'higherOrderFunction’ feature we have 18
> test passed by no implementation. If you inspect the
> higherOrderFunction tests more closely we will see that 17 of these
> tests depend on staticTyping therefore the underlying reason for the
> higherOrderFunction failures is to do with staticTyping. With what I
> have said in mind we think it helpful to show the combination of
> optional features for the test case.
>
> I welcome feedback on your preference of presentation on the Optional
> Features section. I find 2) much more useful:
>
> 1) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optFeatures
> 2) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optComboFeatures
>
>
> Using 1) or 2) we observe that we have 75 tests with dependency on
> staticTyping not being passed by any implementation (including those
> with combinations of other dependencies).  I would like to ask if it
> still merits having tests on static typing?
>
> kind regards,
>
>
> -------------------------------
> O'Neil Delpratt
> Software Developer, Saxonica Limited
> Email: on...@sa...
> Twitter: https://twitter.com/ond1
> Tel: +44 118 946 5894
> Web: http://www.saxonica.com
> Saxonica Community site: http://dev.saxonica.com
> Bug tracking site: https://saxonica.plan.io/
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] Reporting on QT3 test results for the 3.1 Specs

[Wolfgang M. <wol...@ex...>]

Hi,

> I notice eXist isn't included in this round of tests.  I'd be
> interested to know what are the barriers or obstacles to running the
> tests and participating in these exercises?

To start with, we would need a clean and reliable implementation of the test suite for XQ3.1 on eXist. There used to be one but I found it to report too many false or at least questionable results, so working through the reports was too tedious.

I estimate it would take me 2 to 3 weeks of concentrated (unpaid) work to implement the test suite and walk through the results to fix the obvious tiny issues, which I would expect to pop up. As you know we cannot afford that right now. It also doesn’t make sense to implement the test suite if nobody is ready to invest time to look into failures afterwards. So I rather spend my time improving the query engine. For specific features I already copied and pasted tests from the XQ3.1 suite into our local test suite though.

Wolfgang

[Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

Hi all,

I notice eXist isn't included in this round of tests.  I'd be
interested to know what are the barriers or obstacles to running the
tests and participating in these exercises?

I imagine the release of eXist 3.0 is a higher priority for the
project than passing a not-yet-final spec, among others.  But I think
that eXist's presence at some point would help the WG's work and
strengthen the spec's goal of being supported by many implementations.
Even if eXist doesn't promise complete XQ3.1 coverage (heck, they keep
adding new features like templates!), the areas it does support are, I
think, quite well developed - and this hard work would be worth
celebrating through inclusion in these tests.

Joe


---------- Forwarded message ----------
From: O'Neil Delpratt <on...@sa...>
Date: Mon, Jan 18, 2016 at 9:40 AM
Subject: Reporting on QT3 test results for the 3.1 Specs
To: pub...@w3...


Dear All,

I have re-generated the reports on the implementation results received
for the QT3 test suite. See update:
http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html
We now have three implementations for XQuery 3.1, with one being
anonymous. However we only have one for XPath 3.1.

We have been working on the main page today. Specifically the stats on
the optional features. We found that there were some overlap reported
in the passes and failures. For example under ‘staticTyping’ it is
reported that there are 75 test not being passed by any
implementation. Under the 'higherOrderFunction’ feature we have 18
test passed by no implementation. If you inspect the
higherOrderFunction tests more closely we will see that 17 of these
tests depend on staticTyping therefore the underlying reason for the
higherOrderFunction failures is to do with staticTyping. With what I
have said in mind we think it helpful to show the combination of
optional features for the test case.

I welcome feedback on your preference of presentation on the Optional
Features section. I find 2) much more useful:

1) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optFeatures
2) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optComboFeatures


Using 1) or 2) we observe that we have 75 tests with dependency on
staticTyping not being passed by any implementation (including those
with combinations of other dependencies).  I would like to ask if it
still merits having tests on static typing?

kind regards,


-------------------------------
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: on...@sa...
Twitter: https://twitter.com/ond1
Tel: +44 118 946 5894
Web: http://www.saxonica.com
Saxonica Community site: http://dev.saxonica.com
Bug tracking site: https://saxonica.plan.io/

Re: [Exist-development] Trying to create an EXPath projection Java and not able to get eXist-db to see the java library

[<wol...@ex...>]

> I have been banging my head against a problem for sometime now.  I am unable to create a Java based EXPath library module that loads into eXist.  I tried doing the echo one and it failed as well.  I am at a loss in what to do next.

One caveat: to load the library into eXist > 2.2, you have to specify a proper dependency, otherwise the class loader will refuse to load it:

<dependency processor="http://exist-db.org" semver-min="3.0.0"/>

> I even just included the jar file in the lib/user folder after updating it to 3.0 RC1 and adding the entry for it in conf.xml.

This should definitely work though.

Wolfgang

[Exist-development] Trying to create an EXPath projection Java and not able to get eXist-db to see the java library

[Loren C. <lor...@gm...>]

Hello folks,

I have been banging my head against a problem for sometime now.  I am unable to create a Java based EXPath library module that loads into eXist.  I tried doing the echo one and it failed as well.  I am at a loss in what to do next.

I even just included the jar file in the lib/user folder after updating it to 3.0 RC1 and adding the entry for it in conf.xml.


Loren

Re: [Exist-development] Convert to org.w3c.dom.Document

[Adam R. <ad...@ex...>]

Take a look at the source code for the xmldb:store extension function,
that takes a document as one of its arguments. Otherwise the
transform:transform extension function is also an example.

On 30 December 2015 at 15:03, Masoud Vakili <ma...@gm...> wrote:
> Hi all,
> I am programming a module with java for extensions.
> My Method works with two String argument. in fact, I read two xml documents
> (in XQuery Side) and then pass them as string serialized to method. but when
> the documents are very long, the java process will be crash!
> by searching, I noticed the java limitation for String data type length!
> therefor, I decided to write a method with two org.w3c.dom.Document datatype
> argument and pass Document to it instead.
> how can I pass doc() xquery result to Java and convert in to Convert to
> org.w3c.dom.Document?
> thanks.
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] Convert to org.w3c.dom.Document

[Masoud V. <ma...@gm...>]

or introduce a extension or module that threats this way,
thanks

On Wed, Dec 30, 2015 at 6:33 PM, Masoud Vakili <ma...@gm...> wrote:

> Hi all,
> I am programming a module with java for extensions.
> My Method works with two String argument. in fact, I read two xml
> documents (in XQuery Side) and then pass them as string serialized to
> method. but when the documents are very long, the java process will be
> crash!
> by searching, I noticed the java limitation for String data type length!
> therefor, I decided to write a method with two org.w3c.dom.Document
> datatype argument and pass Document to it instead.
> how can I pass doc() xquery result to Java and convert in to Convert to
> org.w3c.dom.Document?
> thanks.
>

[Exist-development] Convert to org.w3c.dom.Document

[Masoud V. <ma...@gm...>]

Hi all,
I am programming a module with java for extensions.
My Method works with two String argument. in fact, I read two xml documents
(in XQuery Side) and then pass them as string serialized to method. but
when the documents are very long, the java process will be crash!
by searching, I noticed the java limitation for String data type length!
therefor, I decided to write a method with two org.w3c.dom.Document
datatype argument and pass Document to it instead.
how can I pass doc() xquery result to Java and convert in to Convert to
org.w3c.dom.Document?
thanks.

[Exist-development] Problem with controller.xql

[Sigfrid L. <sl...@kb...>]

Dear Everyone,

I'm writing an application which should contain five different datasets. I've put most of my scripts and modules in the database (which is eXist db 2.2)  in collection which I call /db/cat-site/ and five collections in /db/(cnw|hartw|schm|scht|gw)/

Following http://exist-db.org/exist/apps/doc/urlrewrite.xml I've stored a controller.xql in the database as

/db/cat-site/controller.xql

To access my dataset I've added this to WEB-INF/controller-config.xml

<root pattern=".*/(cnw|hartw|schm|scht|gw)/" path="xmldb:exist:///db/cat-site/" />

After restart of tomcat, I can see no sign whatsoever that exist-db even glances at my controller.xql. No exceptions in the log files

yours,

Sigfrid

[Exist-development] Use the latest version of Jetty

[Masoud V. <ma...@gm...>]

Hi all;
How can I Install the latest version of jetty (9.3.6) and use it in
exist-db as main web server?
Because the version of jetty in exist-db is too old (jetty-8.1.9.v20130131)
and it has some security issues!
Why the exist-db team has not been updated it?
thanks

[Exist-development] versioning defunct

[Chris T. <chr...@gm...>]

Should the eXist-db Documentation - Versioning Module <http://exist-db.org/exist/apps/doc/versioning.xml> be updated to indicate that it is now removed as of June?

Re: [Exist-development] betterform-config.xml update for log4j2?

[Chris T. <chr...@gm...>]

I updated dist-war-log4j.xsl to use the web rootDir when building a war file.




Assuming that log4j can be updated to log-4j-2.4.1 from 2.3 then the above should work for war file distributions. The update to betterform-config.xml needs to be made for all configurations.

Chris






> On Nov 17, 2015, at 12:21 PM, Chris Tomlinson <chr...@gm...> wrote:
> 
> I was remiss in mentioning that I used log4j 2.4.1 for testing
> 
> 
> 
>> On Nov 17, 2015, at 11:54 AM, Chris Tomlinson <chr...@gm... <mailto:chr...@gm...>> wrote:
>> 
>> I notice that:
>> 
>>         <Property name="logs">${web:rootDir}/WEB-INF/logs</Property>
>> 
>> works sensibly when eXist-db is run via war file within Tomcat 8; however, when I simply run via:
>> 
>>     ./bin/startup.sh
>> 
>> just after ./build.sh all, then the logs end up in:
>> 
>>     ${web:rootDir}/logs/exist.log
>> 
>> so it appears that the substitution is at least occurring within the Tomcat container. I haven’t tested the analogous configuration with jetty so I don’t know if the problem is peculiar to jetty or to the way that eXist-db is running “standalone”.
>> 
>> ciao,
>> Chris
>> 
>> 
>>> On Nov 17, 2015, at 10:50 AM, Chris Tomlinson <chr...@gm... <mailto:chr...@gm...>> wrote:
>>> 
>>> Hi Adam,
>>> 
>>> There seem to be two conditions:
>>> 
>>> 1) absolute path is necessary; and
>>> 2) it is necessary to include log4j-web-xxx.jar - 
>>>       per https://logging.apache.org/log4j/2.x/manual/webapp.html <https://logging.apache.org/log4j/2.x/manual/webapp.html>
>>> 
>>> Then logging appears to work except for the log path issue you filed LOG4J2-1050 which now has gone unassigned.
>>> 
>>> ciao,
>>> Chris
>>> 
>>> 
>>>> On Nov 17, 2015, at 4:33 AM, Adam Retter <ad...@ex... <mailto:ad...@ex...>> wrote:
>>>> 
>>>> Chris,
>>>> 
>>>> Have you tried specified the absolute path to the location you want
>>>> your log files placed in log4j2.xml? You can just change this value:
>>>> 
>>>> <Property name="logs">webapp/WEB-INF/logs</Property>
>>>> 
>>>> There are known problems with log4j2 relative log file paths, I have
>>>> an enhancement issue opened with the log4j project:
>>>> 
>>>> https://issues.apache.org/jira/browse/LOG4J2-1050 <https://issues.apache.org/jira/browse/LOG4J2-1050>
>>>> 
>>>> See - https://github.com/eXist-db/exist/pull/637 <https://github.com/eXist-db/exist/pull/637>
>>>> 
>>>> On 16 November 2015 at 20:49, Chris Tomlinson
>>>> <chr...@gm... <mailto:chr...@gm...>> wrote:
>>>>> Hi,
>>>>> 
>>>>> I’m trying again to debug why the logging isn’t working in eXist-sdb 3.0RC1
>>>>> when run from war file in Tomcat 8.
>>>>> 
>>>>> I am seeing the following in the catalina.out:
>>>>> 
>>>>> 17535 [WARN] WebFactory: Could not find
>>>>> /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist/WEB-INF/log4j.xml
>>>>> 
>>>>> and it appears this results from betterform-config.xml line 16-17:
>>>>> 
>>>>>       <property name="log4j.file" value="WEB-INF/log4j.xml"
>>>>>                 description="the location of the log4j configuration file
>>>>> relative to context"/>
>>>>> 
>>>>> When I change to WEB-INF/log4j2.xml the warning no longer occurs.
>>>>> 
>>>>> However, logging is still not happening in WEB-INF/logs :-(
>>>>> 
>>>>> ciao,
>>>>> Chris
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------------------------
>>>>> Presto, an open source distributed SQL query engine for big data, initially
>>>>> developed by Facebook, enables you to easily query your data on Hadoop in a
>>>>> more interactive manner. Teradata is also now providing full enterprise
>>>>> support for Presto. Download a free open source copy now.
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 <http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140>
>>>>> _______________________________________________
>>>>> Exist-development mailing list
>>>>> Exi...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Adam Retter
>>>> 
>>>> eXist Developer
>>>> { United Kingdom }
>>>> ad...@ex... <mailto:ad...@ex...>
>>>> irc://irc.freenode.net/existdb
>>> 
>> 
> 

Re: [Exist-development] betterform-config.xml update for log4j2?

[Chris T. <chr...@gm...>]

I was remiss in mentioning that I used log4j 2.4.1 for testing



> On Nov 17, 2015, at 11:54 AM, Chris Tomlinson <chr...@gm...> wrote:
> 
> I notice that:
> 
>         <Property name="logs">${web:rootDir}/WEB-INF/logs</Property>
> 
> works sensibly when eXist-db is run via war file within Tomcat 8; however, when I simply run via:
> 
>     ./bin/startup.sh
> 
> just after ./build.sh all, then the logs end up in:
> 
>     ${web:rootDir}/logs/exist.log
> 
> so it appears that the substitution is at least occurring within the Tomcat container. I haven’t tested the analogous configuration with jetty so I don’t know if the problem is peculiar to jetty or to the way that eXist-db is running “standalone”.
> 
> ciao,
> Chris
> 
> 
>> On Nov 17, 2015, at 10:50 AM, Chris Tomlinson <chr...@gm... <mailto:chr...@gm...>> wrote:
>> 
>> Hi Adam,
>> 
>> There seem to be two conditions:
>> 
>> 1) absolute path is necessary; and
>> 2) it is necessary to include log4j-web-xxx.jar - 
>>       per https://logging.apache.org/log4j/2.x/manual/webapp.html <https://logging.apache.org/log4j/2.x/manual/webapp.html>
>> 
>> Then logging appears to work except for the log path issue you filed LOG4J2-1050 which now has gone unassigned.
>> 
>> ciao,
>> Chris
>> 
>> 
>>> On Nov 17, 2015, at 4:33 AM, Adam Retter <ad...@ex... <mailto:ad...@ex...>> wrote:
>>> 
>>> Chris,
>>> 
>>> Have you tried specified the absolute path to the location you want
>>> your log files placed in log4j2.xml? You can just change this value:
>>> 
>>> <Property name="logs">webapp/WEB-INF/logs</Property>
>>> 
>>> There are known problems with log4j2 relative log file paths, I have
>>> an enhancement issue opened with the log4j project:
>>> 
>>> https://issues.apache.org/jira/browse/LOG4J2-1050 <https://issues.apache.org/jira/browse/LOG4J2-1050>
>>> 
>>> See - https://github.com/eXist-db/exist/pull/637
>>> 
>>> On 16 November 2015 at 20:49, Chris Tomlinson
>>> <chr...@gm...> wrote:
>>>> Hi,
>>>> 
>>>> I’m trying again to debug why the logging isn’t working in eXist-sdb 3.0RC1
>>>> when run from war file in Tomcat 8.
>>>> 
>>>> I am seeing the following in the catalina.out:
>>>> 
>>>> 17535 [WARN] WebFactory: Could not find
>>>> /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist/WEB-INF/log4j.xml
>>>> 
>>>> and it appears this results from betterform-config.xml line 16-17:
>>>> 
>>>>       <property name="log4j.file" value="WEB-INF/log4j.xml"
>>>>                 description="the location of the log4j configuration file
>>>> relative to context"/>
>>>> 
>>>> When I change to WEB-INF/log4j2.xml the warning no longer occurs.
>>>> 
>>>> However, logging is still not happening in WEB-INF/logs :-(
>>>> 
>>>> ciao,
>>>> Chris
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Presto, an open source distributed SQL query engine for big data, initially
>>>> developed by Facebook, enables you to easily query your data on Hadoop in a
>>>> more interactive manner. Teradata is also now providing full enterprise
>>>> support for Presto. Download a free open source copy now.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
>>>> _______________________________________________
>>>> Exist-development mailing list
>>>> Exi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Adam Retter
>>> 
>>> eXist Developer
>>> { United Kingdom }
>>> ad...@ex...
>>> irc://irc.freenode.net/existdb
>> 
> 

Re: [Exist-development] betterform-config.xml update for log4j2?

[Chris T. <chr...@gm...>]

I notice that:

        <Property name="logs">${web:rootDir}/WEB-INF/logs</Property>

works sensibly when eXist-db is run via war file within Tomcat 8; however, when I simply run via:

    ./bin/startup.sh

just after ./build.sh all, then the logs end up in:

    ${web:rootDir}/logs/exist.log

so it appears that the substitution is at least occurring within the Tomcat container. I haven’t tested the analogous configuration with jetty so I don’t know if the problem is peculiar to jetty or to the way that eXist-db is running “standalone”.

ciao,
Chris


> On Nov 17, 2015, at 10:50 AM, Chris Tomlinson <chr...@gm...> wrote:
> 
> Hi Adam,
> 
> There seem to be two conditions:
> 
> 1) absolute path is necessary; and
> 2) it is necessary to include log4j-web-xxx.jar - 
>       per https://logging.apache.org/log4j/2.x/manual/webapp.html
> 
> Then logging appears to work except for the log path issue you filed LOG4J2-1050 which now has gone unassigned.
> 
> ciao,
> Chris
> 
> 
>> On Nov 17, 2015, at 4:33 AM, Adam Retter <ad...@ex...> wrote:
>> 
>> Chris,
>> 
>> Have you tried specified the absolute path to the location you want
>> your log files placed in log4j2.xml? You can just change this value:
>> 
>> <Property name="logs">webapp/WEB-INF/logs</Property>
>> 
>> There are known problems with log4j2 relative log file paths, I have
>> an enhancement issue opened with the log4j project:
>> 
>> https://issues.apache.org/jira/browse/LOG4J2-1050
>> 
>> See - https://github.com/eXist-db/exist/pull/637
>> 
>> On 16 November 2015 at 20:49, Chris Tomlinson
>> <chr...@gm...> wrote:
>>> Hi,
>>> 
>>> I’m trying again to debug why the logging isn’t working in eXist-sdb 3.0RC1
>>> when run from war file in Tomcat 8.
>>> 
>>> I am seeing the following in the catalina.out:
>>> 
>>> 17535 [WARN] WebFactory: Could not find
>>> /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist/WEB-INF/log4j.xml
>>> 
>>> and it appears this results from betterform-config.xml line 16-17:
>>> 
>>>       <property name="log4j.file" value="WEB-INF/log4j.xml"
>>>                 description="the location of the log4j configuration file
>>> relative to context"/>
>>> 
>>> When I change to WEB-INF/log4j2.xml the warning no longer occurs.
>>> 
>>> However, logging is still not happening in WEB-INF/logs :-(
>>> 
>>> ciao,
>>> Chris
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Presto, an open source distributed SQL query engine for big data, initially
>>> developed by Facebook, enables you to easily query your data on Hadoop in a
>>> more interactive manner. Teradata is also now providing full enterprise
>>> support for Presto. Download a free open source copy now.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>> 
>> 
>> 
>> 
>> -- 
>> Adam Retter
>> 
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
> 

Re: [Exist-development] betterform-config.xml update for log4j2?

[Chris T. <chr...@gm...>]

Hi Adam,

There seem to be two conditions:

1) absolute path is necessary; and
2) it is necessary to include log4j-web-xxx.jar - 
       per https://logging.apache.org/log4j/2.x/manual/webapp.html

Then logging appears to work except for the log path issue you filed LOG4J2-1050 which now has gone unassigned.

ciao,
Chris


> On Nov 17, 2015, at 4:33 AM, Adam Retter <ad...@ex...> wrote:
> 
> Chris,
> 
> Have you tried specified the absolute path to the location you want
> your log files placed in log4j2.xml? You can just change this value:
> 
> <Property name="logs">webapp/WEB-INF/logs</Property>
> 
> There are known problems with log4j2 relative log file paths, I have
> an enhancement issue opened with the log4j project:
> 
> https://issues.apache.org/jira/browse/LOG4J2-1050
> 
> See - https://github.com/eXist-db/exist/pull/637
> 
> On 16 November 2015 at 20:49, Chris Tomlinson
> <chr...@gm...> wrote:
>> Hi,
>> 
>> I’m trying again to debug why the logging isn’t working in eXist-sdb 3.0RC1
>> when run from war file in Tomcat 8.
>> 
>> I am seeing the following in the catalina.out:
>> 
>>  17535 [WARN] WebFactory: Could not find
>> /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist/WEB-INF/log4j.xml
>> 
>> and it appears this results from betterform-config.xml line 16-17:
>> 
>>        <property name="log4j.file" value="WEB-INF/log4j.xml"
>>                  description="the location of the log4j configuration file
>> relative to context"/>
>> 
>> When I change to WEB-INF/log4j2.xml the warning no longer occurs.
>> 
>> However, logging is still not happening in WEB-INF/logs :-(
>> 
>> ciao,
>> Chris
>> 
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Presto, an open source distributed SQL query engine for big data, initially
>> developed by Facebook, enables you to easily query your data on Hadoop in a
>> more interactive manner. Teradata is also now providing full enterprise
>> support for Presto. Download a free open source copy now.
>> http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>> 
> 
> 
> 
> -- 
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb

Re: [Exist-development] betterform-config.xml update for log4j2?

[Adam R. <ad...@ex...>]

Chris,

Have you tried specified the absolute path to the location you want
your log files placed in log4j2.xml? You can just change this value:

 <Property name="logs">webapp/WEB-INF/logs</Property>

There are known problems with log4j2 relative log file paths, I have
an enhancement issue opened with the log4j project:

https://issues.apache.org/jira/browse/LOG4J2-1050

See - https://github.com/eXist-db/exist/pull/637

On 16 November 2015 at 20:49, Chris Tomlinson
<chr...@gm...> wrote:
> Hi,
>
> I’m trying again to debug why the logging isn’t working in eXist-sdb 3.0RC1
> when run from war file in Tomcat 8.
>
> I am seeing the following in the catalina.out:
>
>   17535 [WARN] WebFactory: Could not find
> /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist/WEB-INF/log4j.xml
>
> and it appears this results from betterform-config.xml line 16-17:
>
>         <property name="log4j.file" value="WEB-INF/log4j.xml"
>                   description="the location of the log4j configuration file
> relative to context"/>
>
> When I change to WEB-INF/log4j2.xml the warning no longer occurs.
>
> However, logging is still not happening in WEB-INF/logs :-(
>
> ciao,
> Chris
>
>
>
>
>
> ------------------------------------------------------------------------------
> Presto, an open source distributed SQL query engine for big data, initially
> developed by Facebook, enables you to easily query your data on Hadoop in a
> more interactive manner. Teradata is also now providing full enterprise
> support for Presto. Download a free open source copy now.
> http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

[Exist-development] betterform-config.xml update for log4j2?

[Chris T. <chr...@gm...>]

Hi,

I’m trying again to debug why the logging isn’t working in eXist-sdb 3.0RC1 when run from war file in Tomcat 8.

I am seeing the following in the catalina.out:

  17535 [WARN] WebFactory: Could not find /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist/WEB-INF/log4j.xml

and it appears this results from betterform-config.xml line 16-17:

        <property name="log4j.file" value="WEB-INF/log4j.xml"
                  description="the location of the log4j configuration file relative to context"/>

When I change to WEB-INF/log4j2.xml the warning no longer occurs.

However, logging is still not happening in WEB-INF/logs :-(

ciao,
Chris

Re: [Exist-development] Deleting a collection.xconf and then reindexing the corresponding collection can corrupt an exist system

[<lor...@gm...>]

This happened in the wrapper while eXist was reindexing the collection.

STATUS | wrapper  | 2015/11/13 07:57:14 | Pinging the JVM took 31 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:03:55 | Pinging the JVM took 43 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:03:55 | Pinging the JVM took 39 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:03:55 | Pinging the JVM took 35 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:03:55 | Pinging the JVM took 31 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:04 | Pinging the JVM took 66 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 62 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 58 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 54 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 50 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 46 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 41 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 37 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:20:05 | Pinging the JVM took 33 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 100 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 96 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 92 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 88 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 84 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 80 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 76 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 72 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 68 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 64 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 59 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 55 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 51 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 47 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 43 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 39 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 35 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:36:14 | Pinging the JVM took 31 seconds to respond.
STATUS | wrapper  | 2015/11/13 08:44:41 | JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.
ERROR  | wrapper  | 2015/11/13 08:45:58 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2015/11/13 08:45:58 | JVM did not exit on request, termination requested.
STATUS | wrapper  | 2015/11/13 08:46:06 | JVM exited after being requested to terminate.
STATUS | wrapper  | 2015/11/13 08:46:12 | Launching a JVM...
INFO   | jvm 2    | 2015/11/13 08:46:19 | WrapperManager: Initializing...
INFO   | jvm 2    | 2015/11/13 08:46:20 | jetty.home = ../../../tools/jetty
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,153 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:121) - Configuring eXist from D:\eXist-db\tools\wrapper\bin\..\..\..\conf.xml
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,153 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:123) - Running with Java 1.8.0_60 [Oracle Corporation (Java HotSpot(TM) 64-Bit Server VM) in C:\Program Files\Java\jre1.8.0_60]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,153 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:129) - Running as user 'SVWVMP369$'
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:132) - [eXist Version : 3.0.RC1]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:134) - [eXist Build : 20150707]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:136) - [eXist Home : unknown]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:138) - [Git commmit : HEAD-e34eb95]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:141) - [Operating System : Windows Server 2008 R2 6.1 amd64]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:146) - [jetty.home : ../../../tools/jetty]
INFO   | jvm 2    | 2015/11/13 08:46:30 | 13 Nov 2015 08:46:30,185 [WrapperListener_start_runner] INFO  (JettyStart.java [run]:148) - [log4j.configurationFile : file:../conf/log4j2.xml]
ERROR  | wrapper  | 2015/11/13 09:19:52 | Startup failed: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2015/11/13 09:19:52 | JVM did not exit on request, termination requested.
STATUS | wrapper  | 2015/11/13 09:19:54 | JVM exited after being requested to terminate.
STATUS | wrapper  | 2015/11/13 09:19:55 | Automatic JVM Restarts disabled.  Shutting down.
STATUS | wrapper  | 2015/11/13 09:19:55 | <-- Wrapper Stopped



On Nov 16, 2015, at 1:38 PM, Joe Wicentowski <jo...@gm...> wrote:

>> While I was trying to do some preemptive cleanup on a 3.0 RC1 instance, I caused the indexes to become corrupted.
>> 
>> Let $remove := xmldb:remove('/db/system/config/db/data/foo')
>> Let $reindex := xmldb:reindex('/db/data/foo')
>> 
>> I had a lucene index configured.
> 
> Quoting Adam from earlier today: "Anything in the logs?"

Re: [Exist-development] Deleting a collection.xconf and then reindexing the corresponding collection can corrupt an exist system

[<lor...@gm...>]

What happened was that eXist was running as a service and while the collection was being reindexed, exist became unresponsive and the service manager forced eXist to quit while reindexing.  That is what corrupted the indexes.

Sent from my iPad

On Nov 16, 2015, at 1:38 PM, Joe Wicentowski <jo...@gm...> wrote:

>> While I was trying to do some preemptive cleanup on a 3.0 RC1 instance, I caused the indexes to become corrupted.
>> 
>> Let $remove := xmldb:remove('/db/system/config/db/data/foo')
>> Let $reindex := xmldb:reindex('/db/data/foo')
>> 
>> I had a lucene index configured.
> 
> Quoting Adam from earlier today: "Anything in the logs?"