Jahia Cloud - Threads and heap dumps provider icon
Module Id
jahia-cloud-threads-heap-dumps-provider
Group Id
org.jahia.community
Updated
Requires Jahia
8.2.1.0
Author
Florent BOURASSE
Category
Tools and Utilities
Status
COMMUNITY info

Jahia Cloud - Threads and heap dumps provider group_work

Give access to the threads and heap dumps generated automatically on Jahia Cloud

Dependencies & Dependants

Dependants
  • NONE

Changelog 2.0.2

Bug Fixes

Fix RepositoryException: Invalid path for dump folders with colons in their name (SUPPORT-608)

Dump directories generated by Jahia Cloud use ISO 8601 timestamps as folder names
(e.g. 2026-01-22T14:15:28.106Z_cluster_restart). The colon character (:) in those
names is the JCR namespace separator and is illegal in unqualified JCR node names,
causing Jackrabbit to throw a MalformedPathException whenever the external content
store provider tried to look up extension nodes for those folders:

javax.jcr.RepositoryException: Invalid path: … ':' not valid name character
    at org.jahia.modules.external.ExternalNodeImpl.getExtensionNode(…)

Root cause: JCRContentUtils.escapeLocalNodeName() (Jackrabbit's
Text.escapeIllegalJcrChars) escapes % as %25. Because VFS2 returns file paths
in percent-encoded URI form, a file named …T08:44:34… was already represented as
…T08%3A44%3A34… by the time the escape function was applied — causing % to be
re-encoded to %25 (double-encoding), which then confounded extension-node path
resolution under Jahia 8.2.3.0.

Fix: Introduced a package-private Escaping utility class whose
escapeIllegalJcrChars method encodes only the characters that are genuinely illegal
in JCR unqualified names ([ ] * | :), deliberately leaving % untouched. This
prevents double-encoding of paths that VFS2 has already percent-encoded. VFS2's
resolveFile() uses URI semantics and decodes %3A back to : transparently when
accessing the local filesystem, so path resolution is correct regardless of whether
the input carries a bare colon or an encoded one.

Improvements

Privilege check migrated to JCRSessionFactory (SUPPORT-608)

The admin-access check in JahiaCloudDumpDataSource.getPrivilegesNames() was
rewritten to use JCRSessionFactory.getInstance().getCurrentUserSession() +
hasPermission("admin") instead of the deprecated
ServicesRegistry → JahiaGroupManagerService.isAdminMember() call.

FAQ

  • Open the repository explorer and go the mount point
  • Only users member of the systemsite group site-administrators will be able to access the mount point

How To Install

  • Download the jar and deploy it on your instance
  • Go to Administrat -> Server settings -> System components -> Mount points
  • Add a new mount point of the type Jahia Cloud - Threads and heap dumps mount point
    • Give a name to the mount point
    • Specify where to mount it

Images

License

MIT License

Copyright (c) 2022 - present Jahia

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.