com.sun.enterprise.security.LoginException: Unable to connect to datasource jdbc/komodo_G3 for database user null. Why this only happens after the first user logs in, I don't know. Here's the full set of error messages around the login failure: [#|2008-01-11T04:03:07.028-0500|FINEST|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-1208 0-0;ClassName=com.sun.enterprise.security.auth.LoginContextDriver;MethodName=login;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Processing login with credentials of type: class com.sun.enterprise.security.auth.login.PasswordCredential|#] [#|2008-01-11T04:03:07.028-0500|FINE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-12080- 0;ClassName=com.sun.enterprise.security.auth.LoginContextDriver;MethodName=doPasswordLogin;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Log ging in user [komodo] into realm: GeckoRealm using JAAS module: jdbcRealm|#] [#|2008-01-11T04:03:07.028-0500|FINE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-12080- 0;ClassName=com.sun.appserv.security.AppservPasswordLoginModule;MethodName=initialize;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Login mo dule initialized: class com.sun.enterprise.security.auth.login.JDBCLoginModule|#] [#|2008-01-11T04:03:07.029-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-1208 0-0;komodo;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|SEC1112: Cannot validate user [komodo] for JDBC realm.|#] [#|2008-01-11T04:03:07.030-0500|FINE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-12080- 0;ClassName=com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm;MethodName=isUserValid;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Canno t validate user com.sun.enterprise.security.LoginException: Unable to connect to datasource jdbc/komodo_G3 for database user null.

Oracle Community | cupahjoe | 9 years ago
  1. 0

    JDBC Realm stops working after first login

    Oracle Community | 9 years ago | cupahjoe
    com.sun.enterprise.security.LoginException: Unable to connect to datasource jdbc/komodo_G3 for database user null. Why this only happens after the first user logs in, I don't know. Here's the full set of error messages around the login failure: [#|2008-01-11T04:03:07.028-0500|FINEST|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-1208 0-0;ClassName=com.sun.enterprise.security.auth.LoginContextDriver;MethodName=login;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Processing login with credentials of type: class com.sun.enterprise.security.auth.login.PasswordCredential|#] [#|2008-01-11T04:03:07.028-0500|FINE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-12080- 0;ClassName=com.sun.enterprise.security.auth.LoginContextDriver;MethodName=doPasswordLogin;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Log ging in user [komodo] into realm: GeckoRealm using JAAS module: jdbcRealm|#] [#|2008-01-11T04:03:07.028-0500|FINE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-12080- 0;ClassName=com.sun.appserv.security.AppservPasswordLoginModule;MethodName=initialize;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Login mo dule initialized: class com.sun.enterprise.security.auth.login.JDBCLoginModule|#] [#|2008-01-11T04:03:07.029-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-1208 0-0;komodo;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|SEC1112: Cannot validate user [komodo] for JDBC realm.|#] [#|2008-01-11T04:03:07.030-0500|FINE|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=19;_ThreadName=httpSSLWorkerThread-12080- 0;ClassName=com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm;MethodName=isUserValid;_RequestID=0eb67820-9ba6-4b42-88e7-7f7a22c68341;|Canno t validate user com.sun.enterprise.security.LoginException: Unable to connect to datasource jdbc/komodo_G3 for database user null.
  2. 0

    JDBC Realm stops working after first login

    Oracle Community | 9 years ago | cupahjoe
    java.lang.ClassCastException: org.hibernate.impl.SessionFactoryImpl
  3. 0

    根据bean获取AnnotationSessionFactoryBean - ITeye问答

    iteye.com | 11 months ago
    java.lang.ClassCastException: org.hibernate.impl.SessionFactoryImpl cannot be cast to org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    WA6 6.1 Applications istalls fine but wont start

    Google Groups | 10 years ago | malin...@capgemini.com
    com.ibm.ejs.container.ContainerEJBException: Failed to stop - caught Throwable
  6. 0

    Screwdriver render Crash

    GitHub | 3 years ago | jem991
    java.lang.ClassCastException: mrtjp.projectred.core.ItemScrewdriver cannot be cast to buildcraft.transport.ItemPipe

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.ClassCastException

      org.hibernate.impl.SessionFactoryImpl

      at com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm.getConnection()
    2. Security Core Classes
      JDBCRealm.getConnection
      1. com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm.getConnection(JDBCRealm.java:467)
      1 frame