-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI.
When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects javax.naming.OperationNotSupportedException thrown out, but java.lang.UnsupportedOperationException is thrown out.
13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289) at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238) at org.wildfly.naming.client.remote.RemoteServerTransport.handleMessage(RemoteServerTransport.java:126) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData(RemoteConnectionChannel.java:430) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute(EndpointImpl.java:991) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) 13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160) at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309) at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236) at org.wildfly.naming.client.remote.RemoteServerTransport.handleMessage(RemoteServerTransport.java:129) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData(RemoteConnectionChannel.java:430) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute(EndpointImpl.java:991) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748)
From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities:
The container must ensure that the application component instances have only read access to their naming context. The container must throw the javax.naming.OperationNotSupportedException from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.
For more information and reproducer, please refer to WFLY-13459
- clones
-
WFLY-14311 javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
- Closed
- is incorporated by
-
JBEAP-19476 [GSS](7.3.z) Remote Naming bind / rebind / unbind / rename / createSubcontext / destroySubcontext does not throw exception back to client
- Closed