webadmin | This project is now part of this one : neo4j/community | Graph Database library

You need to define an extract-i18n target longside with build and serve targets:

Yes, you can use Spring Batch database tables for this check the documentation here: https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html

max user processes (-u) 35

this seems really low. You should be checking the amount of processes currently run by your user - the exception, to me, seems to indicate that this limit is hit. Thus an increase on user process limits would be needed by someone with admin rights.

Also, this:

max memory size (kbytes, -m) 200000

isn't much either for a java app. You only get 200M total, which for most java web apps isn't enough.

Your production account seems to be configured to really low amount of resources, which would either need to be increased, or then you need to change your approach for the app and start developing it for a low-resource environment, instead of regular environment.

Traditional JREs no longer exist since Java 9 (although some vendors offer JRE-like packages). In order to get a Java runtime to run your application you can use the jlink tool, which also comes with JDK 17, like this for a modular application:

I just reverted all the changes, made an Docker container and put that on the server.

you have to add z-index property to your .dropdown-log-content class. as below

Try below Query

I am trying to define virtual user & group data in hiera, and then realize it only on the nodes where it's needed, by defining user lists and group lists on a per-host basis.

Ok, that's not unreasonable.

Note: I am using the accounts module from puppet forge, and it utilizes the accounts:: name space in hiera.

You can use the puppetlabs/accounts module, but you cannot use its accounts class to manage users or groups if you want to stick to your plan, because it does not provide for declaring those virtually. That is a function of the Puppet code of the declarations, not (directly) of any data the class consumes.

You can still use the Accounts::User defined type, the module's various custom data types, and its custom functions. These perhaps provide enough of a value-add relative to Puppet's core User resource type to make the module worth it. You're probably looking at the core Group resource type in any case. You would need to declare Accounts::User (or User) and Group resources virtually, and then realize the wanted ones based on your per-host lists.

But there are other alternatives. You clarified in comments that your objective is to centralize master lists of user and group properties, from which you can select subsets on a per-machine basis. You can do all of that directly in Hiera with the help of Hiera's alias() interpolation function.

You would do this with a two- (at least) level hierarchy. The user and group details would go into an hierarchy level shared by all hosts, and perhaps accounts::user_defaults and accounts::group_defaults would go there too, if you use them. The accounts::user_list and accounts::group_list would go in a per-host or an otherwise more specific hierarchy level, interpolating elements from the central list. Example:

common.yaml