geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Created: (GERONIMO-243) NoClassDefFoundError using demo application
Date Thu, 10 Jun 2004 18:01:14 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-243

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-243
    Summary: NoClassDefFoundError using demo application
       Type: Bug

     Status: Unassigned
   Priority: Trivial

    Project: Apache Geronimo
 Components: 
             security
             web

   Assignee: 
   Reporter: Philip Mark Donaghy

    Created: Thu, 10 Jun 2004 11:00 AM
    Updated: Thu, 10 Jun 2004 11:00 AM
Environment: Java 1.4.2_01-b06 Sun Microsystems Inc.
Linux 2.4.20-8 i386

Description:
Using 2004/06/04 Start Geronimo using the command.

java -jar bin/server.jar org/apache/geronimo/Demo

Access the address http://localhost:8080/demo/auth/logon.html

Login using user george password bone

19:46:31,389 WARN  [ServletHandler] Error for /demo/auth/j_security_check
java.lang.NoClassDefFoundError: org/mortbay/jaas/callback/DefaultCallbackHandler
        at org.apache.geronimo.jetty.JAASJettyRealm.authenticate(JAASJettyRealm.java:81)
        at org.apache.geronimo.jetty.JettyServer$RealmDelegate.authenticate(JettyServer.java:78)
        at org.mortbay.jetty.servlet.FormAuthenticator$FormCredential.authenticate(FormAuthenticator.java:287)
        at org.mortbay.jetty.servlet.FormAuthenticator.authenticate(FormAuthenticator.java:138)
        at org.mortbay.jetty.servlet.ServletHttpContext.jSecurityCheck(ServletHttpContext.java:114)
        at org.mortbay.jetty.servlet.ServletHttpContext.checkSecurityConstraints(ServletHttpContext.java:130)
        at org.apache.geronimo.jetty.JettyWebApplicationContext.checkSecurityConstraints(JettyWebApplicationContext.java:210)
        at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:411)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:512)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1442)
        at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:490)
        at org.apache.geronimo.jetty.JettyWebApplicationContext.handle(JettyWebApplicationContext.java:193)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1394)
        at org.mortbay.http.HttpServer.service(HttpServer.java:879)
        at org.mortbay.http.HttpConnection.service(HttpConnection.java:821)
        at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:988)
        at org.mortbay.http.HttpConnection.handle(HttpConnection.java:838)
        at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:212)
        at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:315)
        at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:510)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message