HTTP Status 404 After Adding security-constraint To web.xml

[JiaPei Jen]

My application worked well with

  <login-config>
    <auth-method>FORM</auth-method> 
    <form-login-config> 
      <form-login-page>/signin/logon.jsp</form-login-page>  
      <form-error-page>/signin/logon.jsp?error=true</form-error-page>
    </form-login-config>                  
  </login-config> 

in the web.xml file. I then inserted <security-constraint> preceding the <login-config> element, and inserted <security-role> following the <login-config> element. I got:

HTTP Status 404 -/PracticeVersion
description: The requested resource(/PracticeVersion) is not availabe.

in the browser, and I have this message in the Tomcat log:

LifecycleException: Container StandardContext[/PracticeVersion] has not been started

This was what my web.xml looks like when the problem happened:

  <security-constraint>
    <web-resource-collection>
      <web-resource-name>Administrative</web-resource-name>
        <!-- The URLs to protect -->
        <url-pattern>/do/admin/*</url-pattern>
      </web-resource-collection>
      <auth-constraint>
        <!-- The authorized users -->
        <role-name>administrator</role-name>
        <role-name>contributor</role-name>
      </auth-constraint>
  </security-constraint>
  <login-config>
    <auth-method>FORM</auth-method> 
    <form-login-config> 
      <form-login-page>/signin/logon.jsp</form-login-page>  
      <form-error-page>/signin/logon.jsp?error=true</form-error-page>
    </form-login-config>                  
  </login-config> 
  <security-role>
    <role-name>administrator</role-name>
  </security-role>
  <security-role>
    <role-name>contributor</role-name>
  </security-role>

[JiaPei Jen]

Please help. I am stuck.

[Mike Curwen]

it seems to me there must be more information than just:
LifecycleException: Container StandardContext[/PracticeVersion] has not been started

Look both above and below this entry for a possible 'root cause' of why it's not started.

It is usually an XML configuration error, but I find nothing wrong in your ordering.

What happens when you specify completely different pages for
form-login-page, form-error-page?

I mean don't use the same page with a parameter to tell them apart.

[Mike Curwen]

I am closing this thread, as it seems to have been re-started here