Jeremy T. Bouse

I've seen some discussions in the past about building a Docker container image to run ART with Tomcat. I'm looking to build one along with a Helm chart to deploy into our EKS (Kubernetes) cluster and before I started was trying to ascertain if anyone had already began/attempted such an endeavor to keep from completely re-inventing the wheel. I know with the curent versions I can easily changes the config directory (-Dart.configDirectory property setting) along with changing the exportDirectory and...

I'll inquire with boss if I am permitted to share. If it had been something I'd written prior personally and not initially for work it wouldn't be an issue.

Along the lines of my other discussion regarding upgrade paths, much of our environment is run in Kubernetes clusters and ART is the really the only application deployed using Tomcat so it currently has it's own server instance. I've contemplated building a Docker image with Tomcat and ART deployed but this drew me back to the upgrade path issues still. From that discussion I could see where the WEB-INF/work directory could be moved out and a k8s PVC mounted. Has anyone else attempted this? I will...

As a general practice I prefer to place JDBC drivers in the application server lib directory rather than the application itself so yeah that simplifies that part. Also since not using hsqldb can ignore that as well. The issue I see with the Custom Settings, is that they are stored inside the art\WEB-INF\art-custom-settings.json which when the JAR file is updated that path would be destroyed or are you not deploying via JAR file and just exploding the JAR file to create the art\ directory that Tomcat...

I'm looking to see if there is a not a better way to manage ART in order to handle upgrades better. I have an Ansible playbook that handles downloading and installing both Tomcat and ART but it is less than ideal simply because of the way ART behaves. Going over the Upgrading wiki page there is so much stored under the art\WEB-INF webapps directory that Tomcat will remove any time the art.war file is updated that makes automating the upgrade process for ART next to impossible. Is there no way to...

Recent experience with handling upgrades to an existing deployment were that it's not as simple as just dropping the new WAR file into the Tomcat webapps/ directory as Tomcat upon seeing the WAR file timestamp is newer than the exploded directory it deletes it removing all database configuration and any jobs files that the upgrading document says to copy over. I haven't seen any way to be able to maintain the necessary files outside of the exploded WAR directory that would assist in automated deployments...

Inherited an existing ART deployment from before my tenure started, but now have a project to harden the server and get it inline with CIS benchmark checklist. In attempting to do this I've ran into several issues which leave ART completely unable to start. Following 10.6 Enable strict servlet compliance if I add -Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE to the CATALINA_OPTS on Tomcat startup I get lots of errors about "cvc-elt.1: Cannot find the declaration of element 'taglib'." that appear...