Salut,
the 404 is set by the ThemeServlet, not the Container. Where can I find
the source of that Servlet? It seems the ThemeServlet invoke sendError,
which is the root of the 404
> com.sun.grizzly.tcp.Response.setStatus(Response.java:252)
> org.apache.catalina.connector.Response.sendError(Response.java:1313)
> org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:499)
> com.sun.webui.theme.ThemeServlet.doGet(ThemeServlet.java:258)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
> org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
> com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
> com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
> org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:307)
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:226)
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:178)
> com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:610)
> com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:547)
> com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:783)
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
> com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
> com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
> com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
Thanks,
-- Jeanfrancois
Anissa Lam wrote:
>
> Here is the steps and the issue is updated:
>
> I don't think the web container is started when we access the admin
> console.
>
> Here is the step:
> - Make sure your workspace is updated and build successfully
> - start domain
> - go to http://localhost:4848
>
> you will get the 404 error.
>
> Before i update my workspace today around lunch, the login page will
> not give 404 and our code can then hide it and bring you to common task
> page.
>
>
> thanks
> Anissa.
>
> Jeanfrancois Arcand wrote:
>> Salut
>>
>> Anissa Lam wrote:
>>>
>>> I will say no. Why do you want to turn off the test ? It is a valid
>>> test and the system is indeed has problem. There is no way to bring
>>> up the admin console now. Jan is looking into the issue and think
>>> that may be related to the Grizzly integration.
>>
>> Naaa ;-) Can you tell me if the WebContainer is started when the 404
>> is produced. Actually can someone update the bug to describe the exact
>> steps :-)
>>
>> Thanks
>>
>> --Jeanfrancois
>>
>>
>>>
>>> thanks
>>> Anissa.
>>>
>>> Marina Vatkina wrote:
>>>> Anissa,
>>>>
>>>> Can we turn off Admin Console QL until you find the fix?
>>>>
>>>> thanks,
>>>> -marina
>>>>
>>>> Anissa Lam wrote:
>>>>>
>>>>> Thanks to Jason, Admin Console QL is now turned on. If you
>>>>> update your workspace, your QL run will also include admin console
>>>>> QL.
>>>>> As of now, admin console QL is failing because there is problem in
>>>>> the system. We can't access the login page and thus cannot bring
>>>>> up the console. It sure does the job :)
>>>>>
>>>>> An issue has been filed,
>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=6131
>>>>> Hopefully we will be able to catch this kind of issue sooner now
>>>>> that the test is in place.
>>>>>
>>>>> thanks
>>>>> Anissa.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>