Liberty server issues finding JNDI

[los-rottweilers]

Starting the Liberty server via the plugin fails to locate the JNDI resource, whereas starting it from the terminal works without issues.

[robstryker]

The best way to debug this is to start from the terminal, and then get a process listing of what commands were used to spawn a given process (including vm args and environment variables), and then repeating the same using the tool.

This way we can determine any flags that should have been included but weren't.

[alainrobert]

@robstryker

I am reproducing this problem. this is with a JDK 17
"server.home.dir": "c:\Tools\IBM\wlp24",
"server.http.port": "29001",
"server.liberty.id": "myserver",
"vm.install.path": "C:\Tools\JDK\semeru17"

In the server log there is this error message:
[11/14/25, 14:46:20:511 EST] 00000067 org.apache.aries.jndi.startup.Activator I It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called was already registered. Support for calling new InitialContext() will not be enabled.

In server.xml we have this feature:
jndi-1.0

It might be related to this issue OpenLiberty/open-liberty#18412 apparently jvm options used when running the server command are not initialized when using the the launcher.

I tried to add this in vm.override.string "--add-opens java.naming/javax.naming.spi=ALL-UNNAMED" but that breaks with this error

ERROR   ] CWWKE0701E: FrameworkEvent ERROR org.osgi.framework.BundleException: Exception in org.apache.aries.jndi.startup.Activator.stop() of bundle com.ibm.ws.org.apache.aries.jndi.core.
	at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:895)
	at [internal classes]
Caused by: java.lang.IllegalStateException: java.lang.reflect.InaccessibleObjectException: Unable to make field private static javax.naming.spi.ObjectFactoryBuilder javax.naming.spi.NamingManager.object_factory_builder accessible: module java.naming does not "opens javax.naming.spi" to unnamed module @a4406456
	at org.apache.aries.jndi.startup.Activator.swapStaticField(Activator.java:328)
	... 1 more
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private static javax.naming.spi.ObjectFactoryBuilder javax.naming.spi.NamingManager.object_factory_builder accessible: module java.naming does not "opens javax.naming.spi" to unnamed module @a4406456
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:184)
	at java.base/java.lang.reflect.Field.setAccessible(Field.java:178)
	at org.apache.aries.jndi.startup.Activator.swapStaticField(Activator.java:319)
```

It would be nice to be able to control Liberty with a JDK 17 or 21 in VSCode 

[robstryker]

I'm not really an expert on liberty. I'll need to see what I can find out.