geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3609) JNDI lookup problem on fowarded calls in Jetty
Date Tue, 20 Nov 2007 04:09:43 GMT


Jarek Gawor commented on GERONIMO-3609:

First, we are dealing with two different web application
contexts (/console and /MonitoringPortlet) and both web app contexts
have different JNDI trees with different resources. The console is
basically forwarding a request from /console to /MonitoringPortlet. It
looks like on Jetty when a request is forwarded from one context to
another, the JNDI tree associated with the current thread does NOT
change for the duration of the call. That means, when a monitoring
portlet looks for resources in JNDI it actaully gets /console JNDI
tree instead of its own.
Your portlet works on Tomcat as Tomcat appears to be properly
switching the JNDI trees during the call.

> JNDI lookup problem on fowarded calls in Jetty
> ----------------------------------------------
>                 Key: GERONIMO-3609
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 2.0.x, 2.1
>            Reporter: Jarek Gawor
> I am having trouble looking up a DataSource from an EAR containing a
> WAR (which is where the lookup takes place) using JNDI. I find it to
> be really weird, because I can look up the DataSource fine if I do it
> through a JSP page or a servlet. However, when I try to look it up in
> portlet code, the jndi name does not seem to be visible, although it
> is visible in the JNDI viewer. Additionally, I have successfully
> looked it up through jsp and servlets.
> This is only a problem in Jetty, because the same code works fine for Tomcat.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message