Issues fixed in MarkLogic Server 11.3.2
- Last Updated: April 6, 2026
- 7 minute read
- MarkLogic Server
- Documentation
Released: Oct 7, 2025
The following issues have been addressed in this release:
| Bug ID |
Description |
|---|---|
| MLE-23752 |
When using the document patch capability of the |
| MLE-23733 |
In Optic queries using XQuery, calling |
| MLE-23160 |
When installing the MarkLogic 12.0.0 RPM or the MarkLogic 11.3.1 RHEL9 package on RHEL 8 and 9 systems, the server automatically starts immediately after the installation completes. This behavior was not present in previous (non-RHEL9 compatible) RPMs (e.g. 11.3.1 on RHEL 7 or 8). |
| MLE-22899 |
Certain SPARQL queries that use inference within an Optic query that also does a join can result in a segmentation fault. |
| MLE-22870 |
Exporting Optic pipelines that include JS-JAVASCRIPT: fn.string(container.pathExpression), -- Error running JavaScript request: TypeError: Cannot read property 'pathExpression' of undefined. |
| MLE-22316 |
Automatic cache sizing on machines with NUMA CPU architecture and 376GB or more of RAM will result in an invalid number of compressed tree cache partitions. This can cause the Admin UI to throw a XDMP-LEXVAL: gr:memory-partitions("33") -- Invalid lexical value "33" with namespace '[http://marklogic.com/xdmp/group|http://marklogic.com/xdmp/group] ' using schema 'group.xsd' |
| MLE-22010 |
When using the Amazon Linux 2023 AMIs, the secondary network interface is not detected correctly. |
| MLE-22005 |
There is a startup issue with MarkLogic Server version 11.3 when installed on AWS EC2 instances running RHEL 8.10 or 8.9. The server fails to start due to a missing Java JVM, which is required for EC2 integration. This issue does not occur in MarkLogic Server versions 11.1 and 11.2. Workaround: Create a configuration file |
| MLE-21731 |
There is a rounding error in the swap size calculation when running MarkLogic AMIs on AWS. This can lead to invalid warnings in the error log indicating that the recommended swap space is not configured. |
| MLE-21507 |
The |
| MLE-21504 |
When using the |
| MLE-21458 |
Backups and other operations against AWS S3 in large clusters may be very slow and result in timeouts. |
| MLE-21414 |
|
| MLE-21078 |
Coupling clusters when running 11.3.1 may result in an error due to the presence of the |
| MLE-20182 |
mlcp import fails with an |
| MLE-19860 |
The |
| MLE-19853 |
There is host IP caching at the XDQP protocol layer that prevents MarkLogic database replication from working across networks that use NAT and there is no mechanism to disable this caching. |
| MLE-19759 |
Under certain circumstances, there may be a long delay in forest failover due to other hosts in the cluster trying to run the "detect indexes" process against hosts that are not available. |
| MLE-19338 |
Element word queries that specify multiple element QNames as the first argument only use the last QName in the array/sequence. Queries will only match documents that have words in elements that are in the last QName in the specified array/sequence. If using a version that does not contain this fix, split the element word queries into an OR query with multiple element word queries, each only specifying a single QName. |
| MLE-19270 |
Returning JSON results in Query Console that have certain encoded strings in the property values (e.g. |
| MLE-19203 |
In the Admin UI App Server "Status" page, when the hyperlink for the database is clicked, it goes to the correct database status page but the Database section in the left-hand navigation tree does not expand as it should. |
| MLE-19198 |
On the Admin UI database "Configure" page, when the "Get Default Values" button is clicked, instead of just getting the default values for the in-memory settings and changing the color to red to indicate that they will be updated, the values are persisted without the user clicking the "OK" button. |
| MLE-19186 |
An inadvertent breaking change to the external security API |
| MLE-19110 |
The MarkLogic Server and corresponding converters RPMs for RHEL 7 and 8 will not install on RHEL 8 if FIPS enabled at the OS level. The workaround is to use the |
| MLE-18255 |
Under heavy request load, the reported app server task queue may go beyond the max task queue size when the task queue is full. |
| MLE-18073 |
When using database replication, configuration changes on the replica cluster, even if made against other databases that are not part of replication, will trigger index detection events on the primary cluster. For systems under heavy load, this can have a negative impact on performance. |
| MLE-17401 |
The JWKS URI configuration option for OAuth external security is ignored and does not function as expected. |
| MLE-17287 |
When under heavy load, incremental backup may not correctly create the "catalog" of documents and then on a subsequent restore, the |
| MLE-17131 |
The Optic XQuery |
| MLE-16678 |
When deleting a database that has forests that are attached, the attached forests are detatched automatically but the message |
| MLE-15576 |
In Optic, given a string column which is compared with [1.0-ml] XDMP-COMPARE: (err:XPTY0004) col1 eq 0 -- Items not comparable: xs:string(" ") = xs:integer(0) |
| MLE-2883 |
If multiple security databases are configured, Query Console gets a |
| MLE-2880 |
In Query Console, if a developer enters text into the query window, and selects another workspace, when the developer returns to the original workspace, the newly entered text can be lost, unless the developer either ran the query or switched to another tab first. |
| MLE-789 |
In the footer of the XCC Javadocs, there is a link to |
| MLE-773 |
The PDF conversion process may throw an XDMP-ATTRSEQ error when creating XML from XHTML that contains empty anchors tags. |
| MLE-735 |
When importing a workspace in Query Console, the query tabs that were open when the workspace was exported will not be automatically opened after importing. |
| MLE-24431 |
SQL queries that use large numbers of nested |
| MLE-24430 |
Optic queries that use SQL statements that include |
| MLE-24429 |
SQL queries that use |
| MLE-24409 |
The deprecated "IUS" yum repo is configured in the MarkLogic AMI but it is not used. |
| MLE-23851 |
When switching quickly from the Monitoring Dashboard to Monitoring History, the following error appears in the browser console: |
| MLE-23803 |
|
| MLE-23565 |
Optic, SQL or SPARQL queries that use the hybrid hash join operator (disk based join) may give wrong results if the lazy sequence returned from |
| MLE-23181 |
In the Admin UI cluster status page, if there are large binary files, the reported database size is different than the size reported on the database status page because the size reported on the database status page includes the size of the large binary data as well. |
| MLE-22158 |
There is a mismatch between the documented and actual required |
| MLE-21042 |
Under conditions where a time correction happens while MarkLogic is in the process of starting, log messages reporting the wrong value for |
| MLE-20256 |
Coercion of XML elements to typed variables does not work correctly when done in an XQuery inline function. For example:
xquery version "1.0-ml";
declare function local:extract($source as node()) {
function() {
let $ret as xs:string := $source/b
return $ret
}()
};
local:extract(<a target="_blank"><b>C</b></a>)
Returns |
| MLE-18359 |
When upgrading to a version of MarkLogic 11 prior to 11.3.2, if an hourly scheduled task was created without specifying a priority in the previous install, the upgrade will fail with the following error: XDMP-LEXVAL: gr:task-priority("") -- Invalid lexical value "" with namespace 'http://marklogic.com/xdmp/group' using schema 'group.xsd' |
| MLE-17860 |
Optic queries that do not have a |
| MLE-436 |
Optic queries issued via the Java Client API that access a TDE view may create unnecessary locks under certain conditions. Even after this fix, this may still happen if all of the columns in the TDE view are nullable. To prevent this, be sure at least one column in the TDE view is not nullable. |
| MLE-23211 |
Restore of an incremental backup with an external large data path writes the data alongside the large directory, instead of inside it, resulting in an improper restore of the large data directory. |
CVEs Addressed
- CVE-2011-4969
- CVE-2012-6708
- CVE-2015-9251
- CVE-2019-11358
- CVE-2020-7656
- CVE-2020-11022
- CVE-2020-11023
- CVE-2022-42898
- CVE-2023-2976
- CVE-2024-7254
- CVE-2024-47072
- CVE-2024-47535
- CVE-2025-48734
- CVE-2025-58754