On Fri, 2002-09-06 at 23:02, Kevin Pearcey wrote:
> I have an odd problem with an Axis servlet handler. Something gets stuck
> in a loop when I try to do a JNDI lookup causing
>
> java.lang.OutOfMemoryError
> <<no stack trace available>>
>
> Any suggestions as to how I can start to find out whats looping? The
> code all works fine until I add a line such as:
>
> Object beanObject = context.lookup("java:comp/env/ejb/ConfigBean");
>
> The context env values seems ok:
>
> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
> java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
>
> Whats the best place to start tracking this down?
I've just managed to track the problem with this one. Looks like the
lookup code doesn't check for circular references - Could this be seen
as a bug?
What I had in my jboss-web.xml was:
<ejb-ref>
<ejb-ref-name>ejb/ConfigBean</ejb-ref-name>
<jndi-name>java:comp/env/ejb/ConfigBean</jndi-name>
</ejb-ref>
Rather than:
<ejb-ref>
<ejb-ref-name>ejb/ConfigBean</ejb-ref-name>
<jndi-name>ejb/ConfigBean</jndi-name>
</ejb-ref>
Kevin.
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
