Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-1172

JNDI

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.1.Final
    • 7.0.0.CR1
    • Naming
    • None
    • Hide

      In standalone-preview.xml, add:

      <jms-queue name="BuggyDestination">
      <entry name="/jms/BuggyDestination" />
      </jms-queue>

      Start bin/standalone.sh --server-config=standalone-preview.xml

      Open JConsole, invoke jboss.naming.JNDIView.list(true)

      Show
      In standalone-preview.xml, add: <jms-queue name="BuggyDestination"> <entry name="/jms/BuggyDestination" /> </jms-queue> Start bin/standalone.sh --server-config=standalone-preview.xml Open JConsole, invoke jboss.naming.JNDIView.list(true)

    Description

      If a JMS destination is created with a JNDI name starting with "/jms/", the JNDI View issues an error message. The destination appears to be up and running fine though.

      <h1>java: Namespace</h1>
      <pre>
      +- topic (class: javax.naming.Context)

      +- test (class: org.jboss.as.naming.context.ModularReference)
      +- app (class: javax.naming.Reference)
      +- module (class: javax.naming.Reference)
      +- comp (class: javax.naming.Reference)
      +- queue (class: javax.naming.Context)
      +- test (class: org.jboss.as.naming.context.ModularReference)
      +- jms (class: javax.naming.Context)
      Failed to lookup: jms, errmsg=Name 'jms' not found in context ''
      +- global (class: javax.naming.Reference)

      Attachments

        Activity

          People

            johnbailey_jira John Bailey (Inactive)
            agattik Alexandre Gattiker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: