Getting java.lang.UnsupportedOperationException: Naming context is read-only

[nitinkhekare]

I am getting exception java.lang.UnsupportedOperationException while creating my own JMX MBean server.

This is working fine in jboss 4.2.3.

18:21:09,127 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-1) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serverConnector' defined in class path resource [ext.xml]: Invocation of init method failed; nested exception is java.lang.UnsupportedOperationException: Naming context is read-only

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409) [spring-2.5.6.jar:]

    at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_11]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:423) [spring-2.5.6.jar:]

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728) [spring-2.5.6.jar:]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380) [spring-2.5.6.jar:]

    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255) [spring-2.5.6.jar:]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) [spring-2.5.6.jar:]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) [spring-2.5.6.jar:]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.1.Final]

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.1.Final]

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)

    at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_11]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_11]

    at java.lang.Thread.run(Thread.java:619) [:1.6.0_11]

Caused by: java.lang.UnsupportedOperationException: Naming context is read-only

    at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:227)

    at javax.naming.InitialContext.rebind(InitialContext.java:408) [:1.6.0_11]

    at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:623) [:1.6.0_11]

    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412) [:1.6.0_11]

    at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:168) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369) [spring-2.5.6.jar:]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335) [spring-2.5.6.jar:]

    ... 24 more

But as the exception suggests is Creating own JMX MBean server not supported in this version of jboss?

Attaching the spring xml

[erhard]

See

https://issues.jboss.org/browse/AS7-421

http://community.jboss.org/thread/173409

http://community.jboss.org/thread/172649

http://community.jboss.org/message/614395

http://echelog.matzon.dk/logs/browse/jboss-as7/1310335200

for more information on this issue.

[alllle]

Section EE.5.3.4 of the Java EE spec says:

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.

I wonder anyone understand the reason behind it? It seems pretty natual and handy to allow one application publish something to the JNDI at runtime and let other application to access it.

[sfcoy]

I believe that this is talking about the component/module/app/global environment naming contexts (as in java:comp/env/...), not JNDI in general.

After doing a bit of homework I can see that the OP is trying to bind an RMIJRMPServerImpl stub into JNDI with the name:

rmi://localhost:3309/myrmi

It would seem to be a bug if this fails.