Unable to bind into JNDI Naming context during SAR deployment in JBoss EAP 6.0

Solution Verified - Updated -

Issue

  • We have a sar that tries to bind some entries into JNDI at deployment time but is unable because the naming context is read-only: AS7-5584

  • We are seeing this exception when deploying our sar with an MBean:

 java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
    at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)
    at org.jboss.as.naming.WritableServiceBasedNamingStore.createSubcontext(WritableServiceBasedNamingStore.java:116)
    at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:345)
    at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:353)
    ...

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.0.0
    • 6.0.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.