DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24588>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24588 NullPointerException from ProxyDirContext Summary: NullPointerException from ProxyDirContext Product: Tomcat 4 Version: 4.1.29 Platform: Other OS/Version: AIX Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm trying to imagine ways in which my code could be causing this and coming up blank. java.lang.NullPointerException at org.apache.naming.resources.ProxyDirContext.cacheLoad(ProxyDirContext.java(Compiled Code)) at org.apache.naming.resources.ProxyDirContext.cacheLookup(ProxyDirContext.java(Compiled Code)) at org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java(Compiled Code)) at org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java(Compiled Code)) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java(Compiled Code)) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java(Compiled Code)) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java(Compiled Code)) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java(Compiled Code)) at com.pronto.presentation.action.order.SearchOrdersAction.getParameters(SearchOrdersAction.java:58) at com.pronto.presentation.action.order.SearchOrdersAction.execute(SearchOrdersAction.java:44) at com.pronto.presentation.EProntoController.doGet(EProntoController.java:62) line 58 of SearchOrdersAction.java is: SearchOrderParameters params = new SearchOrderParameters(); SearchOrderParameters extends from Object, and has the default constructor. It contains no imports of any classes that I would consider significant. The problem was constantly reproducable while the webapp was running, but in a most infuriating manner, the problem has resolved itself after performing a stop/start in the manager app. I don't like problems that resolve themselves without any apparent intervention. Looking at the code for ProxyDirContext.cacheLoad, the objects referenced are: entry - null is checked for in the cacheLookup method, immediately prior to this method call. dirContext - the public constructor would throw null if this was null, the protected constructor would let it through though. attributes - could dirContext.getAttributes(entry.name) be returning null? My understanding is that it would throw a NamingException rather than return null. If it does return null, line 1492 will throw a nullpointer. object - same situation here. If dirContext.lookup(name) can return null, 1507 throws nullpointer. If the toString() method on that object returns null, 1514 will throw. is - could entry.resource.streamContent() return null? if so, 1530 throws. None of those stand out as likely suspects to me. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
