Apache Hop version?
SNAPSHOT-20260901
Java version?
21
Operating system
Docker
What happened?
After #8119, Hop Web uses a separate VFS namespace for each session.
However, switching/enabling a project still calls:
ProjectsUtil.enableProject() → HopVfs.setBootstrapVariables()
If named VFS providers were already registered, setBootstrapVariables() calls the global HopVfs.reset().
HopVfs.reset() calls HopVfsNamespaces.reset(), which closes all existing VFS namespaces in the JVM.
As a result, enabling a project in session B can invalidate the VFS namespace currently used by session A.
This appears to be a remaining global reset path after #8119.
Codex suggests this cause, but it still needs confirmation.
Issue Priority
Priority: 2
Issue Component
Component: Hop Web
Apache Hop version?
SNAPSHOT-20260901
Java version?
21
Operating system
Docker
What happened?
After #8119, Hop Web uses a separate VFS namespace for each session.
However, switching/enabling a project still calls:
ProjectsUtil.enableProject() → HopVfs.setBootstrapVariables()
If named VFS providers were already registered, setBootstrapVariables() calls the global HopVfs.reset().
HopVfs.reset() calls HopVfsNamespaces.reset(), which closes all existing VFS namespaces in the JVM.
As a result, enabling a project in session B can invalidate the VFS namespace currently used by session A.
This appears to be a remaining global reset path after #8119.
Codex suggests this cause, but it still needs confirmation.
Issue Priority
Priority: 2
Issue Component
Component: Hop Web