JE Backend Error on version 4.x

This topic has 3 replies, 4 voices, and was last updated 4 years, 4 months ago by Shivharsh.

  • Author
    Posts
  • #14058
     Ram
    Participant

    dsconfig create-backend –backend-name cts-store –set base-dn:dc=cts,dc=cc,dc=com –set enabled:true –type je –trustAll –port xxxx –no-prompt –propertiesFilePath /tmp/opendj.properties

    The JE Backend could not be created because of the following reason:

    * Unwilling to Perform: The Directory Server is unwilling to add
    configuration entry ds-cfg-backend-id=cts-store,cn=Backends,cn=config
    because one of the add listeners registered with the parent entry
    cn=Backends,cn=config rejected this change with the message:
    Configuration attribute ds-cfg-db-cache-percent has a value of 50% but
    the JVM has only 0% available

    Could you please help me to overcome this

    #14059
     Mark Craig
    Participant

    When using multiple backends, you’ll want to adjust the db-cache-percent values so they add up to 100 or less as described in the docs at https://forgerock.org/opendj/doc/bootstrap/admin-guide/index.html#create-database-backend.

    #18789
     eshraiman
    Participant

    I have exactly the same error:

    * Unwilling to Perform: Entry
    ds-cfg-backend-id=userRoot,cn=Backends,cn=config cannot be modified
    because one of the configuration change listeners registered for that
    entry rejected the change: Configuration attribute
    ds-cfg-db-cache-percent has a value of 50% but the JVM has only 0%
    available

    The answer given above done not make any sense. The percent of allocated cache is NOT more than 100%. I have only one userRoot backend with 50% for cache. Its the Java VM that seems to have 0% allocation.

    Please help, how do I increase the JVM cache percentage?

    #18828
     Shivharsh
    Participant

    Hi,

    The cause of your issue seems to be that there is no heap memory left for the caching. You need to set JVM size keeping in consideration the total size of the backend DB(S). For optimal performance, the “db-cache-size” should be larger than the sum of the DB file sizes. For instance, if the total backend size is 1GB, then you might want to set JVM size to at least 2GB with db-cache-percent set at 50%.

    You can adjust the minimum and maximum heap size using “start-ds.java-args” property in java.properties file located in path_to_Opendj/config/.
    start-ds.java-args=-server -Xms2g -Xmx2g

    You can use dsconfig command to set the db-cache-percent as per your requirements.
    ./dsconfig set-backend-prop --port4444 ---bindPassword password --backend-name userRoot --set db-cache-percent:60 --trustAll --no-prompt

    Alternatively, you can also use “db-cache-size” property in java.properties file to provide a specific amount (such as 2GB) of heap for caching.

    You may refer to following link for further details: “https://backstage.forgerock.com/knowledge/kb/book/b74223337/a70365000”

    Hope this helps !

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?