4 Replies Latest reply on Oct 31, 2014 3:12 PM by mcclane

    JNDI Binding issue in latest AS 7 night build

    Bashir Wichka Newbie

      The latest Jboss fixed the issue of clustering but my bindingings are not working any more.  I am getting error :

      16:25:17,403 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 42) JBAS014613: Operation ("add") failed - address: ([
          ("subsystem" => "naming"),
          ("binding" => "queue_mbQueue")
      ]) - failure description: "JBAS011864: Invaliding binding name queue_mbQueue, name must start with one of [java:global, java:jboss, java:/]"

      when my naming subsystem looks like this :

       

      <subsystem xmlns="urn:jboss:domain:naming:1.2">
                   <bindings>
                      <simple name="queue_mbQueue" value="real_queue"/>
                    </bindings>

      </subsystem>

       

      This was working perfectly fine with jboss AS 7.1.0 final but 7.2..Alpha it is working any more.

       

      Can you comment on this please?

      Thanks,

      Basheer

        • 1. Re: JNDI Binding issue in latest AS 7 night build
          Jay SenSharma Master

          Hi Basheer,

           

               Try to define the "type" attribute as well :

           

          <subsystem xmlns="urn:jboss:domain:naming:1.2">

                 <bindings>

                       <simple name="java:jboss/exported/test" value="100" type="int"/>

                       <simple name="queue_mbQueue" value="real_queue"   type="String"/>

                 </bindings>

          </subsystem>

          • 2. Re: JNDI Binding issue in latest AS 7 night build
            Bashir Wichka Newbie

            It doesn't work. I get the same error.

             

            <subsystem xmlns="urn:jboss:domain:naming:1.2">
                        <bindings>
                            <simple name="queue_mbQueue" value="real_queue" type="String"/>
                        </bindings>

            </subsystem>

             

            11:51:48,049 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 60) JBAS015537: Activating WebServices Extension
            11:51:48,061 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 50) JBAS014613: Operation ("add") failed - address: ([
                ("subsystem" => "naming"),
                ("binding" => "queue_mbQueue")
            ]) - failure description: "JBAS011864: Invaliding binding name queue_mbQueue, name must start with one of [java:global, java:jboss, java:/]"

            • 3. Re: JNDI Binding issue in latest AS 7 night build
              Tomaz Cerar Master

              Just fix the jndi name as the message suggest

               

              <simple name="java:jboss/queue_mbQueue" value="real_queue"/>

               

              or what ever the proper jndi name is...

              • 4. Re: JNDI Binding issue in latest AS 7 night build
                mcclane Newbie

                Hi,

                 

                I've got this problem.

                We've got an EAR with a EJB (jar) and WEB (war) projects.

                We'd like to migrate it from Websphere to JBOSS.

                We've got a binding from name to jndi in a IBM file, and we are traying to find out how.

                 

                First we checked the jboss-web.xml, but thid will only work at web level, we need it al EJB level.

                 

                It seems that is possible to do it at standalone.xml descriptor level, but we'd like todo to it at ejb level.

                 

                So, after playing with jboss-ejb3.xml we can't find how to configurate it. We tried copy / paste from the jboss-web.xml reference binding, but with parser errors. We also tried to include the subsystem proposed condfiguration without success.

                 

                Can anybody help us with that? there's and example (WRONG) of we'd like to do.

                 

                <?xml version="1.1" encoding="UTF-8"?>

                <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"

                               xmlns="http://java.sun.com/xml/ns/javaee"

                               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                               xmlns:c="urn:clustering:1.0"

                               xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"

                               version="3.1"

                               impl-version="2.0">

                    <subsystem xmlns="urn:jboss:domain:naming:1.2">

                        <bindings>

                            <lookup name="Name1" lookup="java:/jdbc/name1"/>

                        </bindings>

                    <remote-naming/>

                    </subsystem>   

                </jboss:ejb-jar>   

                 

                Otherwise, the equivalent of the jboss-web.xml but in the jboss-ejb3-xm:

                 

                <?xml version="1.0" encoding="UTF-8"?> 

                <jboss-web>

                    <resource-ref>

                        <res-ref-name>Name1</res-ref-name>

                        <res-type>javax.sql.DataSource</res-type>

                        <jndi-name>java:/jdbc/name1</jndi-name>

                    </resource-ref>

                </jboss-web>