Hey I have what is apparently a weird question (based on my lack of search results):
I'm trying to setup opendj on AWS EC2. I can get it to launch a primary and then any further nodes find a prior node and add themselves to the replication lists, that works great. But if i terminate anode without dsreplication disable, it stays in the list and i can't add a new replicant (timeouts i think).
(1) is there any way to force-detach a deceased replicant by running a command/commands on the remaining nodes?
(2) is there any configurable timeout for how long a node can be unreachable for replication before it gets dropped from the replication lists? (I don't know if such a setting exists, but if it does can it be configured)
We found a problem in OpenIDM with Configure->Authentication not loading, it seems to be missing the codemirror folder?
It gets 404s on:
There is no "codemirror" folder in /path/to/openidm/ui/admin/default/libs/.
Link Configure->Social ID Providers gets a 404 on admin/libs/codemirror/mode/xml/xml.js
Link Configure->System Preferences gets the same 404s as Configure->Authentication (same 4).
Is there a missing folder that someone forgot to put into the zip?