Bugs item #742400, was opened at 2003-05-23 17:21
Message generated for change (Comment added) made by tstanczak
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742400&group_id=22866

Category: JBossWeb
Group: v3.2
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Chris Bonham (bonhamcm)
Assigned to: Scott M Stark (starksm)
Summary: java:comp not bound when java2ClassLoadingCompliance false

Initial Comment:
Tested in both JBoss 3.2.0RC4 Tomcat 4.1.18 and 
JBoss 3.2.2beta Tomcat 4.1.24, Win2K, Sun JDK 
1.4.1_02.

When java2ClassLoadingCompliance is set to false in 
jboss-web.xml, the java:comp context cannot be 
accessed.  It appears that that the ENC context is 
loaded by the FactoryURLClassLoader before the 
application has read the jboss-web.xml file to see that it 
should actually be loaded by the WebAppClassLoader 
since java2ClassLoadingCompliance is false.

javax.naming.NameNotFoundException: comp not bound
        at org.jnp.server.NamingServer.getBinding
(NamingServer.java:495)
        at org.jnp.server.NamingServer.getBinding
(NamingServer.java:503)
        at org.jnp.server.NamingServer.getObject
(NamingServer.java:509)
        at org.jnp.server.NamingServer.lookup
(NamingServer.java:253)
        at org.jnp.interfaces.NamingContext.lookup
(NamingContext.java:500)
        at org.jnp.interfaces.NamingContext.lookup
(NamingContext.java:479)
        at javax.naming.InitialContext.lookup
(InitialContext.java:347)
        at 
org.jboss.test.classloader.scoping.override.web.log4j113.
ENCServlet.processRequest(ENCServlet.java:56)
        at 
org.jboss.test.classloader.scoping.override.web.log4j113.
ENCServlet.doGet(ENCServlet.java:35)
        at javax.servlet.http.HttpServlet.service
(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service
(HttpServlet.java:853)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:247)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
        at 
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:256)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
        at 
org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
        at 
org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
        at 
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
        at 
org.apache.catalina.valves.CertificatesValve.invoke
(CertificatesValve.java:246)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:641)
        at 
org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
        at 
org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
        at 
org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2415)
        at 
org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
        at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:171)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:641)
        at 
org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:641)
        at 
org.apache.catalina.valves.AccessLogValve.invoke
(AccessLogValve.java:509)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:641)
        at 
org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
        at 
org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
        at 
org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:174)
        at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
        at 
org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
        at 
org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
        at 
org.apache.coyote.tomcat4.CoyoteAdapter.service
(CoyoteAdapter.java:223)
        at 
org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:594)
        at 
org.apache.coyote.http11.Http11Protocol$Http11Connect
ionHandler.processConnection(Http11Protocol.java:392)
        at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:565)
        at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunna
ble.run(ThreadPool.java:619)
        at java.lang.Thread.run(Thread.java:536)

Also, in jboss-web.xml, if java2ClassLoadingCompliance 
is set to true, then the application still behaves as if it 
were false.

A simple testcase is attached.

----------------------------------------------------------------------

Comment By: Tomasz Stanczak (tstanczak)
Date: 2003-08-19 15:08

Message:
Logged In: YES 
user_id=757539

Take a look at the bug# 791202, the jboss_web_3_2.dtd ist 
wrong, so if you make you jboss_web.xml along the dtd you 
can't get the expected results. 

Use servlet23ClassLoading attribute instead of 
java2ClassLoadingCompliance and you'll see the difference.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-06-02 20:29

Message:
Logged In: YES 
user_id=175228

I'm working on this in the context of some other scoped
class loading issues.

----------------------------------------------------------------------

Comment By: RE (emberson)
Date: 2003-05-30 21:23

Message:
Logged In: YES 
user_id=543347

 JBoss 3.2.1 jetty:
if the attribute Java2ClassLoadingCompliance is set to "true"
in deploy/jbossweb-jetty.sar/META-INF/jboss-service.xml,
then the jmx-console page shows up with all of the mbeans.
if Java2ClassLoadingCompliance is set to "false", then none
of the mbean information shows up!!!!
In JBoss 3.04 it worked with Java2ClassLoadingCompliance equal
to false - the mbean information showed up.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742400&group_id=22866


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to