exist-open — Open discussion

Re: [Exist-open] Running eXist-db Docker containers on AWS (Winona Salesky)

[Winona S. <wsa...@gm...>]

Thanks Duncan,
We are giving these a try today to see if we can sort this out. Your tips
have been very helpful.
-Winona


On Mon, Mar 1, 2021 at 10:32 AM Duncan Paterson <du...@ex...> wrote:

> HI,
>
> so from your responses I m still curious about the arguments used to start
> and set the memory allocation of the containers. I’ve recently had the
> chance to debug a clients app and test this part intensively (nothing like
> a reproducer) dynamic memory allocation worked great, so did recovering
> from crashes.
>
> There are essentially two immediate  options:
> 1) Killer Query / memory leak
>
> the instances a container will start eating over 10 GB
>
> sounds like that. Nothing to do with the orchestration, just plain old
> programming error, or adventurous users. Check with latest and the logs to
> see if there is a bad query or a hopefully fixed memory-leak.
>
> 2) ECS is stumbling when trying to reallocate memory leading to stuck
> memory. Basically the external commands to the container, and its internal
> reporting are out of sync. To test that you can run a single container in a
> minimum memory environment locally do some light browsing / editing, if you
> see crashes or runaway memory allocation that’s your problem. You need to
> adjust the start commands (i.e. modify or override JAVA_TOOL_OPTIONS) to
> your deployment scenario. Adjusting, e.g.
>
> -XX:MaxRAMFraction=1
>
> to 2, should ensure that no internal external conflicts are occurring. You
> can then continue to play with other commands to tweak it more, or this
> might already be a suitable solutions to your problem, depending on your
> overall load profile.
>
> If none of that helps, I’d need to take a deeper look into your system, as
> part of a proper consultancy arrangement. I m very short on time at the
> moment.
>
> Hope that helps
> Duncan
>
>
>
>
> Ceterum censeo exist-db.org esse conriganda
>
>
>
> On 1. Mar 2021, at 16:09, Woods, Jonathan <jon...@Va...>
> wrote:
>
> Hey!
>
> I didn’t get that email. Not sure I get the replies.
>
> There aren’t 7 instances. There are 2 instances that are running 7/8 task
> within ECS. Each service runs one task for the container. The containers
> themselves aren’t dependent on each other. They all live within the same
> network (VPC), but that is it. For memory allocations, I don’t have max
> (aka – hard) limits on the containers. This allow the containers to use
> whatever memory they need. The instance the containers are running on are
> running out of memory, yes, but in theory there are 4 containers running on
> a 16 GB instance and while monitoring the instances a container will start
> eating over 10 GB of memory causing it to max out and then restart the
> container. As for storage, we are using the rexray plug-in to have
> consistent storage for the containers. We allocated 30 GB for each
> container and they aren’t even close to utilizing that space.
>
> Hopefully that makes sense.
>
> *Jonathan Woods*
> Cloud Engineer, Cloud Services
> Information Technology | Vanderbilt University
>
> *From:* Winona Salesky <wsa...@gm...>
> *Sent:* Monday, March 1, 2021 9:05 AM
> *To:* Duncan Paterson <du...@ex...>
> *Cc:* exist-open <exi...@li...>; Woods, Jonathan <
> jon...@Va...>
> *Subject:* Re: [Exist-open] Running eXist-db Docker containers on AWS
> (Winona Salesky)
>
> Hi Duncan,
> Thanks for getting back to me, I missed this over the weekend, so sorry
> for the delay in responding. I'm looping in Jonathan Woods on this email as
> he has handled the AWS installations.
> Here is my understanding of our set up:
> 1. The 7 instances run permanently
> 2.  There are no cross-dependencies between the containers.
> Jonathan, perhaps you can answer the other questions having to do with
> memory?
>
> I have not yet tried running them on :latest, as I was hoping to hold out
> until the next official release, perhaps I will give it a try and see if it
> addresses any issues.
>
> Thanks for your help,
> -Winona
>
>
>
> On Sat, Feb 27, 2021 at 7:47 AM Duncan Paterson <du...@ex...>
> wrote:
>
> Hi Winona,
>
> i m afraid the topology isn’t quite clear to me yet, from your
> description. Are all 7 instances supposed to run permanently, or on-demand?
>
> Are there cross-dependencies between the containers? Do they all live on
> the same network? What memory arguments are you using to run the
> containers? What are the max and min memory allocations per container?
> Are they running out of memory due to something that happens inside exist,
> or due to ECS memory reallocations?
> The logs you shared on slack actually look more like there is an IO issues
> with disk spaces, what do the logs say that make you think its memory
> related?
>
> Have you tried to switch to :latest as many bug fixes are in
> 5.3.0-SNAPSHOT to see if the problem persists there? Are you provisioning
> your own base images?
>
> Greetings
> Duncan
>
>
>
> We are moving our eXist-db v5.2 based applications to AWS using docker and
> are experiencing some performance issues.
>
> We have an ECS cluster running two t3a.xlarge which have 16gb, each. The
> ECS service/task are running on a spread deployment where it tries to load
> each task/container evenly between the nodes. We are running 7 eXist-db
> based docker images.
>
> The apps all start out running fine, but eventually run out of memory,
> which can cause an unclean shutdown. This seems to happen every few days.
>
> Any help debugging our setup would be greatly appreciated.
> Thank you,
> -Winona
>
> Ceterum censeo exist-db.org
> <https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fexist-db.org%2F&data=04%7C01%7Cjonathan.woods%40vanderbilt.edu%7C87ff6a1d6b4c4b18eb1108d8dcc35861%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C637502078853258332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=szkt1r50J%2BPNwd4oMtGfOpi5Wp3Pm3aZ7xMElJEXJA8%3D&reserved=0>
>  esse conriganda
>
>
>
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=04%7C01%7Cjonathan.woods%40vanderbilt.edu%7C87ff6a1d6b4c4b18eb1108d8dcc35861%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C637502078853258332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=LEDbYsD8a6xTqe39I4QpMF%2FsTYni85z%2FTTKwMZTQbtA%3D&reserved=0>
>
>
>

[Exist-open] Recommended IDE for eXist-db development

[Jo C. <Jo....@ha...>]

Hi all,

I think I recall NetBeans as being the IDE of choice for eXist dev work.
Is that so?   I have a specific interest in writing Java extension code for
XQuery modules.

Best regards, -- Jo

Re: [Exist-open] installing xsltforms on eXist 5.2

[Craig B. <cra...@ma...>]

> On Mar 1, 2021, at 8:25 AM, Ihe Onwuka <ihe...@gm...> wrote:
> 
> Great. So how do I install that?

As I said up-thread, "So you could try building that and then just installing the resulting XAR via package manager like you would do for any locally-developed package."  Since it has a build.xml, you will likely need to build it with ant by typing "ant" at the command line of a local copy of the repository.  If all goes well, you should get a file with a .xar extension in the build/ subdirectory.  Click on the Upload button in Package Manager and select that file to install it.

> 
> On Mon, Mar 1, 2021 at 8:58 AM Craig Berry <cra...@ma...> wrote:
> On Mar 1, 2021, at 6:57 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > 
> > Craig the package installed XSLTForms rev 594, the one you linked to is rev 565.
> 
> Using that versioning scheme, the one I linked to is 652.  See:
> 
> <https://github.com/eXist-db/xsltforms-xar/commit/6423aef11a73988202807a8fab302553a1c31d71>
> 
> I don't know why there are two versioning schemes or why there are a variety of inconsistent version numbers scattered throughout the project's build files.
> 
> > 
> > On Mon, Mar 1, 2021 at 7:52 AM Craig Berry <cra...@ma...> wrote:
> > 
> > 
> > > On Mar 1, 2021, at 12:43 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > > 
> > > That's older than what the package installed. I think I need at least 629 because that's when support for AVT's came in.
> > 
> > Version 1.3 is not older than version 0.1 in any versioning scheme I've ever seen.
> > 
> > > 
> > > On Sun, Feb 28, 2021 at 6:51 PM Craig Berry via Exist-open <exi...@li...> wrote:
> > > 
> > > > On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > > > 
> > > > Next question. How do I upgrade to a more recent XSLTForms release - at least 629 rather than 594 which is on the package. 
> > > 
> > > Never used it myself, but it looks like what's available online via Package Manger is from 2014, i.e., a very old version. It lists both 565 and 0.1 as its version numbers, which sound like Subversion revision number and actual version number, respectively. My guess would be that the repository from which that package is built is no longer maintained.
> > > 
> > > There appears to be a repository here:
> > > 
> > > https://github.com/eXist-db/xsltforms-xar
> > > 
> > > that has version 1.3.  So you could try building that and then just installing the resulting XAR via package manager like you would do for any locally-developed package. 
> > > 
> > > I don't know who owns the exist-db.org/apps extension delivery mechanism or why it would be serving such an old version.
> > > 
> > > 
> > > ________________________________________
> > > Craig A. Berry
> > > 
> > > "... getting out of a sonnet is much more
> > >  difficult than getting in."
> > >                  Brad Leithauser
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Exist-open mailing list
> > > Exi...@li...
> > > https://lists.sourceforge.net/lists/listinfo/exist-open
> > 
> > ________________________________________
> > Craig A. Berry
> > 
> > "... getting out of a sonnet is much more
> >  difficult than getting in."
> >                  Brad Leithauser
> > 
> 
> ________________________________________
> Craig A. Berry
> 
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
> 

________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Re: [Exist-open] Running eXist-db Docker containers on AWS (Winona Salesky)

[Duncan P. <du...@ex...>]

HI,

so from your responses I m still curious about the arguments used to start and set the memory allocation of the containers. I’ve recently had the chance to debug a clients app and test this part intensively (nothing like a reproducer) dynamic memory allocation worked great, so did recovering from crashes. 

There are essentially two immediate  options: 
1) Killer Query / memory leak
> the instances a container will start eating over 10 GB
sounds like that. Nothing to do with the orchestration, just plain old programming error, or adventurous users. Check with latest and the logs to see if there is a bad query or a hopefully fixed memory-leak. 

2) ECS is stumbling when trying to reallocate memory leading to stuck memory. Basically the external commands to the container, and its internal reporting are out of sync. To test that you can run a single container in a minimum memory environment locally do some light browsing / editing, if you see crashes or runaway memory allocation that’s your problem. You need to adjust the start commands (i.e. modify or override JAVA_TOOL_OPTIONS) to your deployment scenario. Adjusting, e.g. 
> -XX:MaxRAMFraction=1
to 2, should ensure that no internal external conflicts are occurring. You can then continue to play with other commands to tweak it more, or this might already be a suitable solutions to your problem, depending on your overall load profile. 

If none of that helps, I’d need to take a deeper look into your system, as part of a proper consultancy arrangement. I m very short on time at the moment. 

Hope that helps
Duncan




Ceterum censeo exist-db.org esse conriganda



> On 1. Mar 2021, at 16:09, Woods, Jonathan <jon...@Va...> wrote:
> 
> Hey! 
>  
> I didn’t get that email. Not sure I get the replies.
>  
> There aren’t 7 instances. There are 2 instances that are running 7/8 task within ECS. Each service runs one task for the container. The containers themselves aren’t dependent on each other. They all live within the same network (VPC), but that is it. For memory allocations, I don’t have max (aka – hard) limits on the containers. This allow the containers to use whatever memory they need. The instance the containers are running on are running out of memory, yes, but in theory there are 4 containers running on a 16 GB instance and while monitoring the instances a container will start eating over 10 GB of memory causing it to max out and then restart the container. As for storage, we are using the rexray plug-in to have consistent storage for the containers. We allocated 30 GB for each container and they aren’t even close to utilizing that space.
>  
> Hopefully that makes sense. 
>  
> Jonathan Woods
> Cloud Engineer, Cloud Services
> Information Technology | Vanderbilt University
>  
> From: Winona Salesky <wsa...@gm...> 
> Sent: Monday, March 1, 2021 9:05 AM
> To: Duncan Paterson <du...@ex...>
> Cc: exist-open <exi...@li...>; Woods, Jonathan <jon...@Va...>
> Subject: Re: [Exist-open] Running eXist-db Docker containers on AWS (Winona Salesky)
>  
> Hi Duncan, 
> Thanks for getting back to me, I missed this over the weekend, so sorry for the delay in responding. I'm looping in Jonathan Woods on this email as he has handled the AWS installations. 
> Here is my understanding of our set up: 
> 1. The 7 instances run permanently
> 2.  There are no cross-dependencies between the containers. 
> Jonathan, perhaps you can answer the other questions having to do with memory? 
>  
> I have not yet tried running them on :latest, as I was hoping to hold out until the next official release, perhaps I will give it a try and see if it addresses any issues. 
>  
> Thanks for your help,
> -Winona
>  
>  
>  
> On Sat, Feb 27, 2021 at 7:47 AM Duncan Paterson <du...@ex... <mailto:du...@ex...>> wrote:
> Hi Winona, 
> 
> i m afraid the topology isn’t quite clear to me yet, from your description. Are all 7 instances supposed to run permanently, or on-demand? 
> Are there cross-dependencies between the containers? Do they all live on the same network? What memory arguments are you using to run the containers? What are the max and min memory allocations per container?
> Are they running out of memory due to something that happens inside exist, or due to ECS memory reallocations? 
> The logs you shared on slack actually look more like there is an IO issues with disk spaces, what do the logs say that make you think its memory related?
> 
> Have you tried to switch to :latest as many bug fixes are in 5.3.0-SNAPSHOT to see if the problem persists there? Are you provisioning your own base images? 
> 
> Greetings
> Duncan
> 
> 
> 
> We are moving our eXist-db v5.2 based applications to AWS using docker and
> are experiencing some performance issues.
> 
> We have an ECS cluster running two t3a.xlarge which have 16gb, each. The
> ECS service/task are running on a spread deployment where it tries to load
> each task/container evenly between the nodes. We are running 7 eXist-db
> based docker images.
> 
> The apps all start out running fine, but eventually run out of memory,
> which can cause an unclean shutdown. This seems to happen every few days.
> 
> Any help debugging our setup would be greatly appreciated.
> Thank you,
> -Winona
> 
> Ceterum censeo exist-db.org <https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fexist-db.org%2F&data=04%7C01%7Cjonathan.woods%40vanderbilt.edu%7C87ff6a1d6b4c4b18eb1108d8dcc35861%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C637502078853258332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=szkt1r50J%2BPNwd4oMtGfOpi5Wp3Pm3aZ7xMElJEXJA8%3D&reserved=0> esse conriganda
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li... <mailto:Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-open <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=04%7C01%7Cjonathan.woods%40vanderbilt.edu%7C87ff6a1d6b4c4b18eb1108d8dcc35861%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C637502078853258332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=LEDbYsD8a6xTqe39I4QpMF%2FsTYni85z%2FTTKwMZTQbtA%3D&reserved=0>

Re: [Exist-open] Running eXist-db Docker containers on AWS (Winona Salesky)

[Winona S. <wsa...@gm...>]

Hi Duncan,
Thanks for getting back to me, I missed this over the weekend, so sorry for
the delay in responding. I'm looping in Jonathan Woods on this email as he
has handled the AWS installations.
Here is my understanding of our set up:
1. The 7 instances run permanently
2.  There are no cross-dependencies between the containers.
Jonathan, perhaps you can answer the other questions having to do with
memory?

I have not yet tried running them on :latest, as I was hoping to hold out
until the next official release, perhaps I will give it a try and see if it
addresses any issues.

Thanks for your help,
-Winona



On Sat, Feb 27, 2021 at 7:47 AM Duncan Paterson <du...@ex...> wrote:

> Hi Winona,
>
> i m afraid the topology isn’t quite clear to me yet, from your
> description. Are all 7 instances supposed to run permanently, or on-demand?
> Are there cross-dependencies between the containers? Do they all live on
> the same network? What memory arguments are you using to run the
> containers? What are the max and min memory allocations per container?
> Are they running out of memory due to something that happens inside exist,
> or due to ECS memory reallocations?
> The logs you shared on slack actually look more like there is an IO issues
> with disk spaces, what do the logs say that make you think its memory
> related?
>
> Have you tried to switch to :latest as many bug fixes are in
> 5.3.0-SNAPSHOT to see if the problem persists there? Are you provisioning
> your own base images?
>
> Greetings
> Duncan
>
>
>
> We are moving our eXist-db v5.2 based applications to AWS using docker and
> are experiencing some performance issues.
>
> We have an ECS cluster running two t3a.xlarge which have 16gb, each. The
> ECS service/task are running on a spread deployment where it tries to load
> each task/container evenly between the nodes. We are running 7 eXist-db
> based docker images.
>
> The apps all start out running fine, but eventually run out of memory,
> which can cause an unclean shutdown. This seems to happen every few days.
>
> Any help debugging our setup would be greatly appreciated.
> Thank you,
> -Winona
>
> Ceterum censeo exist-db.org esse conriganda
>
>
>
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] installing xsltforms on eXist 5.2

[Ihe O. <ihe...@gm...>]

Great. So how do I install that?

On Mon, Mar 1, 2021 at 8:58 AM Craig Berry <cra...@ma...> wrote:

> On Mar 1, 2021, at 6:57 AM, Ihe Onwuka <ihe...@gm...> wrote:
> >
> > Craig the package installed XSLTForms rev 594, the one you linked to is
> rev 565.
>
> Using that versioning scheme, the one I linked to is 652.  See:
>
> <
> https://github.com/eXist-db/xsltforms-xar/commit/6423aef11a73988202807a8fab302553a1c31d71
> >
>
> I don't know why there are two versioning schemes or why there are a
> variety of inconsistent version numbers scattered throughout the project's
> build files.
>
> >
> > On Mon, Mar 1, 2021 at 7:52 AM Craig Berry <cra...@ma...> wrote:
> >
> >
> > > On Mar 1, 2021, at 12:43 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > >
> > > That's older than what the package installed. I think I need at least
> 629 because that's when support for AVT's came in.
> >
> > Version 1.3 is not older than version 0.1 in any versioning scheme I've
> ever seen.
> >
> > >
> > > On Sun, Feb 28, 2021 at 6:51 PM Craig Berry via Exist-open <
> exi...@li...> wrote:
> > >
> > > > On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...>
> wrote:
> > > >
> > > > Next question. How do I upgrade to a more recent XSLTForms release -
> at least 629 rather than 594 which is on the package.
> > >
> > > Never used it myself, but it looks like what's available online via
> Package Manger is from 2014, i.e., a very old version. It lists both 565
> and 0.1 as its version numbers, which sound like Subversion revision number
> and actual version number, respectively. My guess would be that the
> repository from which that package is built is no longer maintained.
> > >
> > > There appears to be a repository here:
> > >
> > > https://github.com/eXist-db/xsltforms-xar
> > >
> > > that has version 1.3.  So you could try building that and then just
> installing the resulting XAR via package manager like you would do for any
> locally-developed package.
> > >
> > > I don't know who owns the exist-db.org/apps extension delivery
> mechanism or why it would be serving such an old version.
> > >
> > >
> > > ________________________________________
> > > Craig A. Berry
> > >
> > > "... getting out of a sonnet is much more
> > >  difficult than getting in."
> > >                  Brad Leithauser
> > >
> > >
> > >
> > > _______________________________________________
> > > Exist-open mailing list
> > > Exi...@li...
> > > https://lists.sourceforge.net/lists/listinfo/exist-open
> >
> > ________________________________________
> > Craig A. Berry
> >
> > "... getting out of a sonnet is much more
> >  difficult than getting in."
> >                  Brad Leithauser
> >
>
> ________________________________________
> Craig A. Berry
>
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
>
>

Re: [Exist-open] installing xsltforms on eXist 5.2

[Craig B. <cra...@ma...>]

On Mar 1, 2021, at 6:57 AM, Ihe Onwuka <ihe...@gm...> wrote:
> 
> Craig the package installed XSLTForms rev 594, the one you linked to is rev 565.

Using that versioning scheme, the one I linked to is 652.  See:

<https://github.com/eXist-db/xsltforms-xar/commit/6423aef11a73988202807a8fab302553a1c31d71>

I don't know why there are two versioning schemes or why there are a variety of inconsistent version numbers scattered throughout the project's build files.

> 
> On Mon, Mar 1, 2021 at 7:52 AM Craig Berry <cra...@ma...> wrote:
> 
> 
> > On Mar 1, 2021, at 12:43 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > 
> > That's older than what the package installed. I think I need at least 629 because that's when support for AVT's came in.
> 
> Version 1.3 is not older than version 0.1 in any versioning scheme I've ever seen.
> 
> > 
> > On Sun, Feb 28, 2021 at 6:51 PM Craig Berry via Exist-open <exi...@li...> wrote:
> > 
> > > On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > > 
> > > Next question. How do I upgrade to a more recent XSLTForms release - at least 629 rather than 594 which is on the package. 
> > 
> > Never used it myself, but it looks like what's available online via Package Manger is from 2014, i.e., a very old version. It lists both 565 and 0.1 as its version numbers, which sound like Subversion revision number and actual version number, respectively. My guess would be that the repository from which that package is built is no longer maintained.
> > 
> > There appears to be a repository here:
> > 
> > https://github.com/eXist-db/xsltforms-xar
> > 
> > that has version 1.3.  So you could try building that and then just installing the resulting XAR via package manager like you would do for any locally-developed package. 
> > 
> > I don't know who owns the exist-db.org/apps extension delivery mechanism or why it would be serving such an old version.
> > 
> > 
> > ________________________________________
> > Craig A. Berry
> > 
> > "... getting out of a sonnet is much more
> >  difficult than getting in."
> >                  Brad Leithauser
> > 
> > 
> > 
> > _______________________________________________
> > Exist-open mailing list
> > Exi...@li...
> > https://lists.sourceforge.net/lists/listinfo/exist-open
> 
> ________________________________________
> Craig A. Berry
> 
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
> 

________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Re: [Exist-open] installing xsltforms on eXist 5.2

[Ihe O. <ihe...@gm...>]

Craig the package installed XSLTForms rev 594, the one you linked to is rev
565.

On Mon, Mar 1, 2021 at 7:52 AM Craig Berry <cra...@ma...> wrote:

>
>
> > On Mar 1, 2021, at 12:43 AM, Ihe Onwuka <ihe...@gm...> wrote:
> >
> > That's older than what the package installed. I think I need at least
> 629 because that's when support for AVT's came in.
>
> Version 1.3 is not older than version 0.1 in any versioning scheme I've
> ever seen.
>
> >
> > On Sun, Feb 28, 2021 at 6:51 PM Craig Berry via Exist-open <
> exi...@li...> wrote:
> >
> > > On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > >
> > > Next question. How do I upgrade to a more recent XSLTForms release -
> at least 629 rather than 594 which is on the package.
> >
> > Never used it myself, but it looks like what's available online via
> Package Manger is from 2014, i.e., a very old version. It lists both 565
> and 0.1 as its version numbers, which sound like Subversion revision number
> and actual version number, respectively. My guess would be that the
> repository from which that package is built is no longer maintained.
> >
> > There appears to be a repository here:
> >
> > https://github.com/eXist-db/xsltforms-xar
> >
> > that has version 1.3.  So you could try building that and then just
> installing the resulting XAR via package manager like you would do for any
> locally-developed package.
> >
> > I don't know who owns the exist-db.org/apps extension delivery
> mechanism or why it would be serving such an old version.
> >
> >
> > ________________________________________
> > Craig A. Berry
> >
> > "... getting out of a sonnet is much more
> >  difficult than getting in."
> >                  Brad Leithauser
> >
> >
> >
> > _______________________________________________
> > Exist-open mailing list
> > Exi...@li...
> > https://lists.sourceforge.net/lists/listinfo/exist-open
>
> ________________________________________
> Craig A. Berry
>
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
>
>

Re: [Exist-open] installing xsltforms on eXist 5.2

[Craig B. <cra...@ma...>]

> On Mar 1, 2021, at 12:43 AM, Ihe Onwuka <ihe...@gm...> wrote:
> 
> That's older than what the package installed. I think I need at least 629 because that's when support for AVT's came in.

Version 1.3 is not older than version 0.1 in any versioning scheme I've ever seen.

> 
> On Sun, Feb 28, 2021 at 6:51 PM Craig Berry via Exist-open <exi...@li...> wrote:
> 
> > On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...> wrote:
> > 
> > Next question. How do I upgrade to a more recent XSLTForms release - at least 629 rather than 594 which is on the package. 
> 
> Never used it myself, but it looks like what's available online via Package Manger is from 2014, i.e., a very old version. It lists both 565 and 0.1 as its version numbers, which sound like Subversion revision number and actual version number, respectively. My guess would be that the repository from which that package is built is no longer maintained.
> 
> There appears to be a repository here:
> 
> https://github.com/eXist-db/xsltforms-xar
> 
> that has version 1.3.  So you could try building that and then just installing the resulting XAR via package manager like you would do for any locally-developed package. 
> 
> I don't know who owns the exist-db.org/apps extension delivery mechanism or why it would be serving such an old version.
> 
> 
> ________________________________________
> Craig A. Berry
> 
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
> 
> 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Re: [Exist-open] installing xsltforms on eXist 5.2

[Ihe O. <ihe...@gm...>]

That's older than what the package installed. I think I need at least 629
because that's when support for AVT's came in.

On Sun, Feb 28, 2021 at 6:51 PM Craig Berry via Exist-open <
exi...@li...> wrote:

>
> > On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...> wrote:
> >
> > Next question. How do I upgrade to a more recent XSLTForms release - at
> least 629 rather than 594 which is on the package.
>
> Never used it myself, but it looks like what's available online via
> Package Manger is from 2014, i.e., a very old version. It lists both 565
> and 0.1 as its version numbers, which sound like Subversion revision number
> and actual version number, respectively. My guess would be that the
> repository from which that package is built is no longer maintained.
>
> There appears to be a repository here:
>
> https://github.com/eXist-db/xsltforms-xar
>
> that has version 1.3.  So you could try building that and then just
> installing the resulting XAR via package manager like you would do for any
> locally-developed package.
>
> I don't know who owns the exist-db.org/apps extension delivery mechanism
> or why it would be serving such an old version.
>
>
> ________________________________________
> Craig A. Berry
>
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] installing xsltforms on eXist 5.2

[Craig B. <cra...@ma...>]

> On Feb 26, 2021, at 9:27 AM, Ihe Onwuka <ihe...@gm...> wrote:
> 
> Next question. How do I upgrade to a more recent XSLTForms release - at least 629 rather than 594 which is on the package. 

Never used it myself, but it looks like what's available online via Package Manger is from 2014, i.e., a very old version. It lists both 565 and 0.1 as its version numbers, which sound like Subversion revision number and actual version number, respectively. My guess would be that the repository from which that package is built is no longer maintained.

There appears to be a repository here:

https://github.com/eXist-db/xsltforms-xar

that has version 1.3.  So you could try building that and then just installing the resulting XAR via package manager like you would do for any locally-developed package. 

I don't know who owns the exist-db.org/apps extension delivery mechanism or why it would be serving such an old version.


________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Re: [Exist-open] Running eXist-db Docker containers on AWS (Winona Salesky)

[Duncan P. <du...@ex...>]

Hi Winona, 

i m afraid the topology isn’t quite clear to me yet, from your description. Are all 7 instances supposed to run permanently, or on-demand? 
Are there cross-dependencies between the containers? Do they all live on the same network? What memory arguments are you using to run the containers? What are the max and min memory allocations per container?
Are they running out of memory due to something that happens inside exist, or due to ECS memory reallocations? 
The logs you shared on slack actually look more like there is an IO issues with disk spaces, what do the logs say that make you think its memory related?

Have you tried to switch to :latest as many bug fixes are in 5.3.0-SNAPSHOT to see if the problem persists there? Are you provisioning your own base images? 

Greetings
Duncan



We are moving our eXist-db v5.2 based applications to AWS using docker and
are experiencing some performance issues.

We have an ECS cluster running two t3a.xlarge which have 16gb, each. The
ECS service/task are running on a spread deployment where it tries to load
each task/container evenly between the nodes. We are running 7 eXist-db
based docker images.

The apps all start out running fine, but eventually run out of memory,
which can cause an unclean shutdown. This seems to happen every few days.

Any help debugging our setup would be greatly appreciated.
Thank you,
-Winona

Ceterum censeo exist-db.org esse conriganda

Re: [Exist-open] installing xsltforms on eXist 5.2

[Ihe O. <ihe...@gm...>]

Yeah. Logging out and back in again gave me that screen.
Do you want to put that answer on SO so I can accept it.

Next question. How do I upgrade to a more recent XSLTForms release - at
least 629 rather than 594 which is on the package.




On Fri, Feb 26, 2021 at 10:11 AM Joe Wicentowski <jo...@gm...> wrote:

> Ihe,
>
> When logged in as admin, you should be seeing the admin view of the
> dashboard, including an entry for Package Manager (see screenshot below).
> Could you try logging out of the admin user and logging back in? How about
> if you go directly to http://localhost:8080/exist/apps/dashboard/admin?
> Do you see the left sidebar as shown in my screenshot?
>
> Joe
>
> [image: Screen Shot 2021-02-26 at 10.09.18 AM.png]
>
> On Fri, Feb 26, 2021 at 3:04 AM Ihe Onwuka <ihe...@gm...> wrote:
>
>> I am always logged in as admin. There aren't any other users set up on
>> this database. This has always been the screen that I get.
>>
>> [image: image.png]
>>
>>
>>
>> On Thu, Feb 25, 2021 at 9:27 PM Craig Berry <cra...@ma...> wrote:
>>
>>>
>>>
>>> > On Feb 25, 2021, at 3:25 PM, Ihe Onwuka <ihe...@gm...> wrote:
>>> >
>>> >
>>> https://stackoverflow.com/questions/66375942/installing-xsltforms-on-exist-db-5-2
>>> >
>>> > Happy to take answers here too if anyone can help.
>>>
>>> From stackoverflow:
>>>
>>> > Given that the package manager is not offered on the eXist-db 5.2
>>> dashboard (at least not on mine) how does one install XSLTForms on an
>>> eXist-db 5.2 installation running on an AWS EC2 instance.
>>>
>>>
>>> But the package manager *is* offered on the 5.2 Dashboard.  You do have
>>> to be logged in as admin to see it.  And in default 5.2 without any module
>>> updates, the admin user must not be a member of any groups other than admin
>>> (that and a number of other bugs in core modules have been fixed since 5.2).
>>>
>>> ________________________________________
>>> Craig A. Berry
>>>
>>> "... getting out of a sonnet is much more
>>>  difficult than getting in."
>>>                  Brad Leithauser
>>>
>>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>

Re: [Exist-open] installing xsltforms on eXist 5.2

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

Ihe,

When logged in as admin, you should be seeing the admin view of the
dashboard, including an entry for Package Manager (see screenshot below).
Could you try logging out of the admin user and logging back in? How about
if you go directly to http://localhost:8080/exist/apps/dashboard/admin? Do
you see the left sidebar as shown in my screenshot?

Joe

[image: Screen Shot 2021-02-26 at 10.09.18 AM.png]

On Fri, Feb 26, 2021 at 3:04 AM Ihe Onwuka <ihe...@gm...> wrote:

> I am always logged in as admin. There aren't any other users set up on
> this database. This has always been the screen that I get.
>
> [image: image.png]
>
>
>
> On Thu, Feb 25, 2021 at 9:27 PM Craig Berry <cra...@ma...> wrote:
>
>>
>>
>> > On Feb 25, 2021, at 3:25 PM, Ihe Onwuka <ihe...@gm...> wrote:
>> >
>> >
>> https://stackoverflow.com/questions/66375942/installing-xsltforms-on-exist-db-5-2
>> >
>> > Happy to take answers here too if anyone can help.
>>
>> From stackoverflow:
>>
>> > Given that the package manager is not offered on the eXist-db 5.2
>> dashboard (at least not on mine) how does one install XSLTForms on an
>> eXist-db 5.2 installation running on an AWS EC2 instance.
>>
>>
>> But the package manager *is* offered on the 5.2 Dashboard.  You do have
>> to be logged in as admin to see it.  And in default 5.2 without any module
>> updates, the admin user must not be a member of any groups other than admin
>> (that and a number of other bugs in core modules have been fixed since 5.2).
>>
>> ________________________________________
>> Craig A. Berry
>>
>> "... getting out of a sonnet is much more
>>  difficult than getting in."
>>                  Brad Leithauser
>>
>> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Running eXist-db Docker containers on AWS

[Winona S. <wsa...@gm...>]

We are moving our eXist-db v5.2 based applications to AWS using docker and
are experiencing some performance issues.

We have an ECS cluster running two t3a.xlarge which have 16gb, each. The
ECS service/task are running on a spread deployment where it tries to load
each task/container evenly between the nodes. We are running 7 eXist-db
based docker images.

The apps all start out running fine, but eventually run out of memory,
which can cause an unclean shutdown. This seems to happen every few days.

Any help debugging our setup would be greatly appreciated.
Thank you,
-Winona

Re: [Exist-open] installing xsltforms on eXist 5.2

[Ihe O. <ihe...@gm...>]

I am always logged in as admin. There aren't any other users set up on this
database. This has always been the screen that I get.

[image: image.png]



On Thu, Feb 25, 2021 at 9:27 PM Craig Berry <cra...@ma...> wrote:

>
>
> > On Feb 25, 2021, at 3:25 PM, Ihe Onwuka <ihe...@gm...> wrote:
> >
> >
> https://stackoverflow.com/questions/66375942/installing-xsltforms-on-exist-db-5-2
> >
> > Happy to take answers here too if anyone can help.
>
> From stackoverflow:
>
> > Given that the package manager is not offered on the eXist-db 5.2
> dashboard (at least not on mine) how does one install XSLTForms on an
> eXist-db 5.2 installation running on an AWS EC2 instance.
>
>
> But the package manager *is* offered on the 5.2 Dashboard.  You do have to
> be logged in as admin to see it.  And in default 5.2 without any module
> updates, the admin user must not be a member of any groups other than admin
> (that and a number of other bugs in core modules have been fixed since 5.2).
>
> ________________________________________
> Craig A. Berry
>
> "... getting out of a sonnet is much more
>  difficult than getting in."
>                  Brad Leithauser
>
>

Re: [Exist-open] installing xsltforms on eXist 5.2

[Craig B. <cra...@ma...>]

> On Feb 25, 2021, at 3:25 PM, Ihe Onwuka <ihe...@gm...> wrote:
> 
> https://stackoverflow.com/questions/66375942/installing-xsltforms-on-exist-db-5-2
> 
> Happy to take answers here too if anyone can help.

From stackoverflow:

> Given that the package manager is not offered on the eXist-db 5.2 dashboard (at least not on mine) how does one install XSLTForms on an eXist-db 5.2 installation running on an AWS EC2 instance.


But the package manager *is* offered on the 5.2 Dashboard.  You do have to be logged in as admin to see it.  And in default 5.2 without any module updates, the admin user must not be a member of any groups other than admin (that and a number of other bugs in core modules have been fixed since 5.2).

________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

[Exist-open] installing xsltforms on eXist 5.2

[Ihe O. <ihe...@gm...>]

https://stackoverflow.com/questions/66375942/installing-xsltforms-on-exist-db-5-2

Happy to take answers here too if anyone can help.

Re: [Exist-open] Issue with 4.7.1 eXist DB - file Id points to two different collection files

[Kuukka-Härmä R. <Rii...@fi...>]

Hello,

We ended up to do clean eXist-4.7.1 db installation & restored database from backup. After that no references to multiple files, and no errors in backup report.

BR, Riina

From: Roy Walter <gar...@ya...>
Sent: tiistai 16. helmikuuta 2021 17.09
To: Kuukka-Härmä Riina <Rii...@fi...>
Cc: Exist-open <exi...@li...>
Subject: Re: [Exist-open] Issue with 4.7.1 eXist DB - file Id points to two different collection files

Hi,

How about creating an empty file, copying the contents of one of the problem files to it and then deleting the donor file.

Regards,
Roy


On Tuesday, 16 February 2021, 14:56:01 GMT, Kuukka-Härmä Riina <rii...@fi...<mailto:rii...@fi...>> wrote:



Hello,



Thank you for an answer. I tested the query setting



let $id := 11240



And it returned the path to same two XML files as using search with xs:string.



BR, Riina



From: Michael Westbay <wes...@ja...<mailto:wes...@ja...>>
Sent: tiistai 16. helmikuuta 2021 14.52
To: Kuukka-Härmä Riina <Rii...@fi...<mailto:Rii...@fi...>>
Cc: Exi...@li...<mailto:Exi...@li...>
Subject: Re: [Exist-open] Issue with 4.7.1 eXist DB - file Id points to two different collection files



Hi Riina,



You are setting you $id to an xs:string, not an xs:integer. Comparing strings of integers to integers often causes strange results.



Hope this helps.



Take care.



2021年2月16日(火) 19:35 Kuukka-Härmä Riina <Rii...@fi...<mailto:Rii...@fi...>>:

Hello,





Any ideas that what could be gone wrong are welcomed.



We have an issue in eXist  4.7.1 db-installation . Backup is failing for some files, and after investigating, we found that there is Document ID that is pointing two different files in separate collections.



Failed to access document data

Document ID: 11240



Investigating which file this is with query:



xquery version "3.1";



declare

function local:find($path, $document-id as xs:integer) as xs:string* {

    local:find-in-collection($path, (), $document-id)

};

declare

function local:resource ($collection as xs:string, $resource as xs:string, $document-id as xs:integer) as xs:string? {

    let $path := $collection || '/' || $resource

    let $id := util:document-id($path)

    return

        if ($id eq $document-id)

        then ($path)

        else ()

};

declare

function local:find-in-collection ($collection as xs:string, $sub-collection as xs:string?, $document-id as xs:integer) as xs:string* {

    let $path := string-join(($collection, $sub-collection), '/')

    return

        if (xmldb:collection-available($path))

        then (

            for-each(

                xmldb:get-child-collections($path),

                local:find-in-collection($path, ?, $document-id)

            ),

            for-each(

                xmldb:get-child-resources($path),

                local:resource($path, ?, $document-id)

            )

        )

        else ($path || " not found or insufficient permissions to read")

};

let $id := '11240'

return local:find('/db/APP', $id)



This returns two files:



"/db/APP/ORGANIZATION.A/CODE/INTERNAL/PUBLISHED/1603458557855/TOSELEMENTS/customFields.xml"

"/db/APP/ORGANIZATION.B/CODE/INTERNAL/PUBLISHED/1611822097512/TOSELEMENTS/strongEsignatureText.xml"



Howcome there can be returned two files with same id? How this can be fixed, is there any options than reinstall the database and return the content from backup? Should that fix the fileId:s eventually?



What I know, for some problematic files there is used eXist dashboard copy/paste functionality - but not all copy pasted files are having this issue.



Best Regards, Riina Kuukka-Härmä





_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open




--

Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/
_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] XSLT version in eXist 5.2.0

[Omar S. <Oma...@oe...>]

Short answer: for eXist 5.2.0 git c58d04ec45de50e7738489dee072fcc863dc8b1b
(that is the docker image from docker hub)
the XSL processor is SAXON HE 9.9.1.6

saxonica.com Saxon 9.9 docs say:
Saxon 9.9 includes highly conformant implementations of the current W3C 
Recommendations: XSLT 3.0, XQuery 3.1, XPath 3.1, and XSD 1.1. See 
Standards Conformance for more details.

For various reasons I was asking myself the same question every now and 
then.
I created a RestXq method that prints the answer. Here is a version of this
/db/apps/get-runtime/get-runtime.xqm (world readable and executeable):
xquery version "3.1";

module namespace api="urn:api";

declare
   %rest:path("/get-runtime")
   %rest:GET
function api:runtime-info() as item()+ {
   let $xslt-runtime-info := transform:transform(<_/>,
       document {<xsl:stylesheet 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
     <xsl:output method="xml"/><xsl:template 
match='/'><_><product-name><xsl:value-of 
select="system-property('xsl:product-name')"/></product-name><product-version><xsl:value-of 
select="system-property('xsl:product-version')"/></product-version></_></xsl:template></xsl:stylesheet>}, 
())
   return
   <html xmlns="http://www.w3.org/1999/xhtml">
     <title>Runtime info</title>
     <body>
        <h1>Runtime info</h1>
        <table>
          <tr>
            <td>{system:get-product-name()}</td>
            <td>{system:get-version()} git {system:get-revision()}</td>
          </tr>
          <tr>
<td>{$xslt-runtime-info/*:product-name/text()}</td>
<td>{$xslt-runtime-info/*:product-version/text()}</td>
          </tr>
        </table>
     </body>
   </html>
};
Register it (eg. with 
exrest:register-module(xs:anyURI('/db/apps/get-runtime/get-runtime.xqm')) 
) and
you can the infos in for example at 
http://localhost:8080/exist/restxq/get-runtime

Am 18.02.2021 um 18:12 schrieb Christian Achter:
> Dear all,
>
> sorry to disturb you with this question, but I couldn't find anything 
> about this:
>
> What XSLT version ist running with eXist-db 5.2.0?
>
> We are currently running scripts of XSLT 2.0 which work fine but need 
> to switch to scripts of XSLT 3.0. Will that be possible with eXist 5.2?
>
> Kind regards
> Christian Achter
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open


-- 
Mag. Ing. Omar Siam
Austrian Center for Digital Humanities and Cultural Heritage
Österreichische Akademie der Wissenschaften | Austrian Academy of Sciences
Stellvertretende Behindertenvertrauensperson | Deputy representative for disabled persons
Wohllebengasse 12-14, 1040 Wien, Österreich | Vienna, Austria
T: +43 1 51581-7295
oma...@oe... | www.oeaw.ac.at/acdh

[Exist-open] XSLT version in eXist 5.2.0

[Christian A. <chr...@ge...>]

Dear all,

sorry to disturb you with this question, but I couldn't find anything 
about this:

What XSLT version ist running with eXist-db 5.2.0?

We are currently running scripts of XSLT 2.0 which work fine but need to 
switch to scripts of XSLT 3.0. Will that be possible with eXist 5.2?

Kind regards
Christian Achter

Re: [Exist-open] New range index and matches()

[Alasdair D. <ala...@gm...>]

Hi Andreas,

As Wolfgang said, range:match will work.I use them in one of my functions,
and it works really well and it is quick.

Alasdair

On Wed, Feb 17, 2021 at 9:35 PM Wolfgang Meier <wol...@ex...>
wrote:

> Dear Andreas,
>
> > Now, reading up on the ("new") range index, the page
> https://exist-db.org/exist/apps/doc/newrangeindex says "fn:matches is
> currently not supported due to limitations in Lucene's regular expression
> handling. If you require fn:matches a lot, consider using the old range
> index." Is this still the case?
>
> Yes, but you could try the special function range:matches instead of
> fn:matches and see if it works for you. It supports only a subset, but in
> your case, this might be sufficient?
>
> Best,
>
> Wolfgang
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] New range index and matches()

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

Dear Andreas,

> Now, reading up on the ("new") range index, the page https://exist-db.org/exist/apps/doc/newrangeindex says "fn:matches is currently not supported due to limitations in Lucene's regular expression handling. If you require fn:matches a lot, consider using the old range index." Is this still the case?

Yes, but you could try the special function range:matches instead of fn:matches and see if it works for you. It supports only a subset, but in your case, this might be sufficient?

Best,

Wolfgang

[Exist-open] New range index and matches()

[Andreas W. <And...@em...>]

Dear all,

Is it still the case that the new range index is not recommended to be 
used with matches() queries?


I am currently in the process of speeding up various xquery modules in 
my database. I have found one function that, according to monex 
profiling, is not using any index:

```xquery
matches(@n, '^[A-Za-z0-9\[\]]+$'))
```

It is meant to check if the @n attribute contains alphanumeric 
characters only, eventually combined with square brackets.

Now, reading up on the ("new") range index, the page 
https://exist-db.org/exist/apps/doc/newrangeindex says "fn:matches is 
currently not supported due to limitations in Lucene's regular 
expression handling. If you require fn:matches a lot, consider using the 
old range index." Is this still the case?

If so, would defining an old range index on the @n attribute mess with 
more specific new range index definitions that I need in other places, 
like

```xml
<range>
   <create qname="tei:div">
     <field name="tei.div.n" match="@n" type="xs:string"/>
     <field name="tei.div.type" match="@type" type="xs:string"/>
   </create>
</range>
```

Also, if you suggest defining an old range index, am I right that it 
would look like this (without being wrapped inside a range element):

```xml
<create qname="@n" type="xs:string"/>
```

Thank you for any suggestions,

Andreas


-- 
Dr. Andreas Wagner                          twitter: @anwagnerdreas
Project "The School of Salamanca"           web: http://salamanca.adwmainz.de
Academy of Sciences and Literature, Mainz   fon: +49 (0)69/798-32774
and Institute of Philosophy                 fax: +49 (0)69/798-32794
Goethe University Frankfurt

IGF HP 25 / R 2.455
Norbert-Wollheim-Platz 1
60629 Frankfurt am Main

Re: [Exist-open] Error causing eXist to not start

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

I am not using CQL.  I am trying to comment out it in conf.xml


> On Feb 16, 2021, at 6:11 PM, Joe Wicentowski <jo...@gm...> wrote:
> 
> Hi Loren,
> 
> Are you using the CQL module? If not, you can uncomment it from your conf.xml:
> 
>   https://github.com/eXist-db/exist/blob/5b4692692ab0bf3642c0b0eb0a07024ec9e5f4df/exist-distribution/src/main/config/conf.xml#L995 <https://github.com/eXist-db/exist/blob/5b4692692ab0bf3642c0b0eb0a07024ec9e5f4df/exist-distribution/src/main/config/conf.xml#L995>
> 
> If you're using it, I notice that there aren't any tests for it in the eXist codebase. Perhaps you would be willing to contribute some tests to prevent regressions?
> 
>   https://github.com/eXist-db/exist/search?q=cqlparser <https://github.com/eXist-db/exist/search?q=cqlparser>
> 
> Joe
> 
> 
> On Tue, Feb 16, 2021 at 3:17 PM Loren Cahlander <lor...@gm... <mailto:lor...@gm...>> wrote:
> My client is trying to run exist in a stage environment that is in a Kubernetes image.  I do not think that the problem is exist, because it was working before.  It is, however giving the following error.
> 
> Exist version 5.2
> 
> 16 Feb 2021 18:33:16,441 [main] ERROR (Configuration.java [lookupModuleClass]:504) - Module http://exist-db.org/xquery/cqlparser <http://exist-db.org/xquery/cqlparser> could not be initialized due to a missing dependancy (NoClassDefFoundError): org/z3950/zing/cql/CQLParseException
> java.lang.NoClassDefFoundError: org/z3950/zing/cql/CQLParseException
> at org.exist.xquery.modules.cqlparser.CQLParserModule.<clinit>(CQLParserModule.java:46) ~[exist.uber.jar:5.2.0]
> at java.lang.Class.forName0(Native Method) ~[?:?]
> at java.lang.Class.forName(Class.java:315) ~[?:?]
> at org.exist.util.Configuration.lookupModuleClass(Configuration.java:488) [exist.uber.jar:5.2.0]
> at org.exist.util.Configuration.loadModuleClasses(Configuration.java:454) [exist.uber.jar:5.2.0]
> at org.exist.util.Configuration.configureXQuery(Configuration.java:390) [exist.uber.jar:5.2.0]
> at org.exist.util.Configuration.<init>(Configuration.java:275) [exist.uber.jar:5.2.0]
> at org.exist.util.SingleInstanceConfiguration.<init>(SingleInstanceConfiguration.java:56) [exist.uber.jar:5.2.0]
> at org.exist.util.SingleInstanceConfiguration.<init>(SingleInstanceConfiguration.java:48) [exist.uber.jar:5.2.0]
> at org.exist.jetty.JettyStart.run(JettyStart.java:198) [exist.uber.jar:5.2.0]
> at org.exist.jetty.JettyStart.main(JettyStart.java:95) [exist.uber.jar:5.2.0]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
> at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
> at org.exist.start.Main.invokeMain(Main.java:118) [exist.uber.jar:5.2.0]
> at org.exist.start.Main.runEx(Main.java:248) [exist.uber.jar:5.2.0]
> at org.exist.start.Main.run(Main.java:123) [exist.uber.jar:5.2.0]
> at org.exist.start.Main.main(Main.java:60) [exist.uber.jar:5.2.0]
> Caused by: java.lang.ClassNotFoundException: org.z3950.zing.cql.CQLParseException
> at jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) ~[?:?]
> at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) ~[?:?]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:522) ~[?:?]
> ... 19 more
> 16 Feb 2021 18:33:16,512 [main] INFO  (Configuration.java [configureValidation]:1485) - Add catalog uri file:///exist/etc/webapp//WEB-INF/catalog.xml <>
> 16 Feb 2021 18:33:16,513 [main] INFO  (GrammarPool.java [<init>]:54) - Initializing GrammarPool.
> 16 Feb 2021 18:33:16,515 [main] INFO  (JettyStart.java [run]:2
> 
> 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li... <mailto:Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-open <https://lists.sourceforge.net/lists/listinfo/exist-open>