cancel
Showing results for 
Search instead for 
Did you mean: 

JBAS011859: Naming context is read-only

wade_zeng
Champ in-the-making
Champ in-the-making
Hi all,

i got the following error when deployed application with activiti in jboss-as-7.1.1.Final,  and found answer in
http://stackoverflow.com/questions/20881496/java-lang-unsupportedoperationexception-jbas011859-namin...
but the got the error after set '-Dorg.apache.activemq.broker.jmx.createConnector=false' in jboss.

any suggests are appreciated, thanks.


16:53:31,847 INFO  [org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl] (MSC service thread 1-2) Found 1 auto-discoverable Process Engine Configurators
16:53:31,851 INFO  [org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl] (MSC service thread 1-2) Found 1 Process Engine Configurators in total:
16:53:31,853 INFO  [org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl] (MSC service thread 1-2) class org.activiti.management.jmx.JMXConfigurator (priority:10000)
16:53:31,855 INFO  [org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl] (MSC service thread 1-2) Executing beforeInit() of class org.activiti.management.jmx.JMXConfigurator (priority:10000)
16:53:32,606 INFO  [org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl] (MSC service thread 1-2) Executing configure() of class org.activiti.management.jmx.JMXConfigurator (priority:10000)
16:53:32,633 ERROR [stderr] (jmxConnectorStarterThread) Exception in thread "jmxConnectorStarterThread" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only

16:53:32,636 ERROR [stderr] (jmxConnectorStarterThread)    at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)

16:53:32,640 ERROR [stderr] (jmxConnectorStarterThread)    at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:56)

16:53:32,643 ERROR [stderr] (jmxConnectorStarterThread)    at org.jboss.as.naming.NamingContext.bind(NamingContext.java:221)

16:53:32,645 ERROR [stderr] (jmxConnectorStarterThread)    at org.jboss.as.naming.InitialContext.bind(InitialContext.java:161)

16:53:32,647 ERROR [stderr] (jmxConnectorStarterThread)    at org.jboss.as.naming.NamingContext.bind(NamingContext.java:230)

16:53:32,649 ERROR [stderr] (jmxConnectorStarterThread)    at javax.naming.InitialContext.bind(InitialContext.java:419)

16:53:32,651 ERROR [stderr] (jmxConnectorStarterThread)    at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)

16:53:32,653 ERROR [stderr] (jmxConnectorStarterThread)    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)

16:53:32,656 ERROR [stderr] (jmxConnectorStarterThread)    at org.activiti.management.jmx.DefaultManagementAgent$1.run(DefaultManagementAgent.java:224)

16:53:32,658 ERROR [stderr] (jmxConnectorStarterThread)    at java.lang.Thread.run(Thread.java:745)
1 REPLY 1

wade_zeng
Champ in-the-making
Champ in-the-making
more info below:
<code>
17:14:09,172 INFO  [org.activiti.engine.impl.ProcessEngineImpl] (MSC service thr
ead 1-1) ProcessEngine default created
17:14:09,176 INFO  [org.activiti.engine.ProcessEngines] (MSC service thread 1-1)
initialised process engine default
17:14:09,196 ERROR [org.apache.catalina.core.StandardContext] (MSC service threa
d 1-8) Context [/sealmachine-standard] startup failed due to previous errors: ja
va.lang.IllegalArgumentException: Child container with name default already exis
ts
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:804) [jbossweb-7.0.13.Final.jar:]
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:79
2) [jbossweb-7.0.13.Final.jar:]
        at org.apache.catalina.core.StandardContext.addChild(StandardContext.jav
a:1878) [jbossweb-7.0.13.Final.jar:]
        at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBo
ssContextConfig.java:438) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(J
BossContextConfig.java:169) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
        at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:41
7) [jbossweb-7.0.13.Final.jar:]
        at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfi
g.java:182) [jbossweb-7.0.13.Final.jar:]
        at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossCo
ntextConfig.java:162) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:115) [jbossweb-7.0.13.Final.jar:]
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:3
790) [jbossweb-7.0.13.Final.jar:]
        at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentS
ervice.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1811)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1746)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1145) [rt.jar:1.7.0_79]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:615) [rt.jar:1.7.0_79]
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
<code>