ejb-ref Bug in JBoss 3.0.6?

[perunthachan]

Hello,
We are using JBoss 3.0.6 [with the Tomcat 4.1.18 bundle]. For some beans there are quite a few ejb-ref tags defined and one would expect them to be accessible under the java:/comp/env namespace. However, lookups for some beans under this namespace are giving name not found exceptions. This is despite the fact that the server debug log showing that the internal JNDI reference has been created. There appears to be no specific pattern to the type of beans [entity/session] or the position of the ejb-ref definition.

Any ideas would be greatly appreciated.

Many thanks

Peru

[prajod]

Hi Perum Thacha,
You can check if your beans are visible in the JNDI tree of Jboss. Log on using the JMX console: http://yourhost:8080/jmx-console

[perunthachan]

I thought internal JNDI references do not show up in the JMX Console. Aren't they just bound to the local namespace of the bean/component delcaring them?

[bman917]

Do you know that you can do away whith the ejb-ref thing? Sometimes when the session gets deployed first before the ejb-link entity bean, I get a class not found exception. Anyway, I have written several session beans which accesses entities though their JNDI name which is the ejb-name you gave them and they work just fine.