1 Reply Latest reply on Aug 28, 2002 2:29 PM by Adrian Brock

    New JMX Name Rules in 3.0.2

    Corby Page Newbie

      The release notes for JBoss 3.0.2 note the following change:

      Build the jndiName component of the JMX name from the remote home jndi name if it exists, else use the local home jndi name. This fixes a problem with multiple deployments of an ejb that only has local interfaces.

      However, this change seems to break the deployment of my entity beans. My entity beans expose only local interfaces, and so I bind the local-jndi-name as java:/SomethingEB

      This yields the following deployment error:

      org.jboss.deployment.DeploymentException: Could not create deployment: file:/C:/Java/jboss-3.0.2/server/allocations/tmp/deploy/server/allocations/deploy/30-Allocation.ear/73.30-Allocation.ear-contents/SomethingEB.jar; - nested throwable:
      (java.lang.Error: Invalid ObjectName: jboss.j2ee:service=EJB,jndiName=java:/SomethingEB; javax.management.MalformedObjectNameException: malformed key/value
      pair: jndiName=java:/SomethingEB)

      Am I now prohibited from binding my EJB's only to a local jndi namespace?