Issues fixed in MarkLogic Server 11.3.4

MLE-151

MarkLogic Spark Connector could fail when querying system views (such as sys.sys_tables) via Optic, resulting in an SQL-NOCOLUMN error.

MLE-14286

The Basic.xqy template does not use path-based routing because its basepath value is always empty. As a result, all generated links are absolute rather than relative. This causes the Admin/REST UI pages that depend on this template to break when deployed behind a reverse proxy, since absolute paths no longer resolve correctly.

MLE-17289

When a REST server's content database is configured as a replica via database replication (dbrep), accessing the server root (e.g., http://host:port/) returns an error on the replica cluster.

MLE-18102

When accessing the MarkLogic Server Management API through the PDC URL path that includes an extra /manage segment (e.g., .../manage/manage/), the resulting page displays incorrect API links. All links are generated as absolute paths and do not incorporate the additional base path, causing them to break in this context.

MLE-21760

/manage/v2/amps returned XML that did not conform to the published schema, causing validation failures.

MLE-21761

/manage/v2/certificate-authorities returned XML that did not conform to the published schema, causing validation failures.

MLE-21762

/manage/v2/certificates returned XML that did not conform to the published schema, causing validation failures.

MLE-21763

/manage/v2/external-security returned XML that did not conform to the published schema, causing validation failures.

MLE-21764

/manage/v2/logs returned XML that did not conform to the published schema, causing validation failures.

MLE-21765

/manage/v2/mimetypes returned XML that did not conform to the published schema, causing validation failures.

MLE-21766

/manage/v2/privileges returned XML that did not conform to the published schema, causing validation failures.

MLE-21767

/manage/v2/protected-collections returned XML that did not conform to the published schema, causing validation failures.

MLE-21768

/manage/v2/protected-paths returned XML that did not conform to the published schema, causing validation failures.

MLE-21769

/manage/v2/roles returned XML that did not conform to the published schema, causing validation failures.

MLE-21770

/manage/v2/tasks-server returned XML that did not conform to the published schema, causing validation failures.

MLE-21771

/manage/v2/tasks returned XML that did not conform to the published schema, causing validation failures.

MLE-21772

/manage/v2/tickets returned XML that did not conform to the published schema, causing validation failures.

MLE-21773

/manage/v2/users returned XML that did not conform to the published schema, causing validation failures.

MLE-21823

/manage/v2?view=health returned XML that did not conform to the published schema, causing validation failures.

MLE-21824

/manage/v2?view=metrics returned XML that did not conform to the published schema, causing validation failures.

MLE-21834

The servers-raw.xml documents stored in the Meters database are not valid against meters.xsd. Several elements appear in the XML that are not defined in the schema, causing validation failures. Running validation (e.g., cts:uri-match("*/server-raw.xml")[1] ! xdmp:validate(doc(.))) produces XDMP-VALIDATEUNEXPECTED errors, such as unexpected elements like fs-schema-cache-hits that are not permitted by the schema definition.

MLE-21835

The usage.xml documents generated in the Meters database are not valid against the usage-meters.xsd schema. Running schema validation (e.g., cts:uri-match("*/usage.xml")[1] ! xdmp:validate(doc(.))) produces XDMP-VALIDATEUNEXPECTED errors because the XML includes elements, such as os-version, that are not defined in the usage-meters.xsd schema.

MLE-21836

The forest-raw.xml documents generated in the Meters database are missing the required <forest-status> element. All data appears directly under <forest-statuses>, causing schema validation to fail. Running validation (e.g., cts:uri-match("*/forest-raw.xml")[1] ! doc(.) ! xdmp:validate(.)) produces XDMP-VALIDATEMISSINGELT errors indicating that the schema expects one or more <forest-status/> elements, but none are present.

MLE-21837

The host-raw.xml documents produced in the Meters database are not valid against meters.xsd. Schema validation (e.g., cts:uri-match("*/host-raw.xml")[1] ! doc(.) ! xdmp:validate(.)) reports XDMP-VALIDATEUNEXPECTED errors due to unexpected elements appearing in the XML. For example, elements like query-read-rate appear in locations where the schema expects a different set of child elements.

MLE-22873

Monitoring history database detail page could take a long time to render and could trigger OOM errors when viewing larger time ranges.

MLE-23601

xdmp:collections() returns only 10 fixed collection IDs despite documentation stating it should return all collection IDs.

MLE-24052

Filtering on the notnull column in the sys.sys_columns system view fails in MarkLogic 11.3.x with an XDMP-COMPARE type-mismatch error. Although sys.sys_columns.notnull is defined as an xs:unsignedInt containing values 0 or 1, attempting to compare it to a numeric literal results in an invalid comparison against a boolean value.

SELECT * FROM sys.sys_columns 
  WHERE sys.sys_columns.notnull = 0;

returns:

XDMP-COMPARE: (err:XPTY0004) sys.sys_columns.notnull eq fn:false()  
  Items not comparable: xs:int(1) = xs:boolean("false")

MLE-24384

When serializing HTML, MarkLogic incorrectly outputs a closing tag for the <track> element, even though <track> is a void element under the HTML specification and must not have an end tag.

MLE-24411

On EC2 environments after upgrading to MarkLogic Server 12.0.0, OS I/O tunables (such as read-ahead and max sectors) were not applied as expected at startup, and logs could report changes that did not persist.

MLE-24416

Deeply nested SQL set operations (such as SQLUnion, SQLIntersect, and SQLNegationJoin) can cause severe performance degradation due to repeated and recursive calls to analyze() during query planning.

MLE-24534

Queries against partially indexed TDEs could show inconsistent execution times.

MLE-24797

The mlcmd script is not compatible with Java 17 because it still uses the deprecated JVM option -XX:+UseConcMarkSweepGC, which is removed in Java 17.

MLE-24866

The logout pages on some App Servers (such as ports 8000 and 8002) did not display the configured UI header or label, even though it appeared correctly during authenticated sessions and on other App Servers.

MLE-24922

Diagnostic execution plans for Optic queries could incorrectly report a join result count of zero, even when the join produced results at runtime.

MLE-24995

The "Now" button on the Monitoring web page will function off local time rather than server time. If the local user is on a different time zone than the server, the history graph could be missing recent results.

MLE-25672

Clearing forests following a label/journal mismatch (XDMP-BADSTARTUPTOKEN) could result in segmentation fault.

MLE-26335

The SPARQL optimizer could generate execution plans using SPARQLZeroOrOne with scatter joins that failed to apply available scatter constraints, leading to performance degradation.

MLE-27127

In the MarkLogic systemd-based AMIs, the MarkLogic service starts too early in the boot sequence before EC2 UserData is executed. Since UserData scripts run later under cloud-final.service, MarkLogic starts without required configuration values, causing incorrect or failed initialization on AWS.

MLE-27319

JWT validation fails when the JWKS payload lacks an x5c field because the JWKS processing logic attempts to reconstruct the public key unconditionally. This causes errors between JWKS retrieval and token verification.