If you specify the name attribute in the @EJB annotation to bind it directly under java:global (and not a sub context), the JNDI view operation in the management console will fail. To reproduce, follow the steps at https://docs.jboss.org/author/display/AS71/JNDI+Reference and deploy an EJB like: -- package com.example; import javax.ejb.EJB; import javax.ejb.Stateless; @Stateless @EJB(name = "java:global/MyBean", beanInterface = MyBean.class) public class MyBean { } -- Then go to the management console, and JNDI View. If the @EJB name specifies a sub-context (e.g. java:global/xxx/MyBean) it will work, so that is a work-around
This is fixed by AS7-6060, in the master (AS 7.2) branch
Verified on EAP 6.1.0.ER2. Just a note. The problematic case is more likely this one: @Stateless @EJB(name = "java:global/MyBean", beanInterface = MyBeanInterface.class) public class MyBean implements MyBeanInterface { ... }
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html