Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Problem after jetty migration from 6.1.25 to 8.1.3 !

404 not found means your context isn't there.
Likely means either nothing is deployed, or not on the context path you expect.

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
www.webtide.com
Developer advice, services and support
from the Jetty & CometD experts.



On Mon, Jun 25, 2012 at 12:02 AM, Abhishek Singh <abhisheksingh.bits@xxxxxxxxx> wrote:
Hi all,

For my project I have migrated from Jetty 6.1.25 to Jetty 8.1.3.

After the migration, i am getting the following error for all my requests to my Web Application:

HTTP ERROR 404 Problem accessing /command-executor/j_security_check. Reason:  Not Found  Powered by Jetty://

Am i missing something ?

i am using LdapLoginModule for authentication and provided correct configuration and Realm Name (which is same as in web.xml):

 <Call name="addBean">
    <Arg>
      <New class="org.eclipse.jetty.plus.jaas.JAASLoginService">
     <Set name="name">Command Executor Realm</Set>
     <Set name="LoginModuleName">ldaploginmodule</Set>
   </New>
    </Arg>
  </Call

Everything works perfect in Jetty 6.1.25.

Please help me in resolving this issue in jetty 8.1.3. 

Thanks and Regards,
Abhishek Singh

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users



Back to the top