5 Replies Latest reply on Jan 7, 2010 8:12 PM by alihamza7

    errors with logging into console - jbpm-4.1

      HI all,

      I am using jbpm-4.1 and had installed mysql with it by using ant -Ddatabase=mysql demo.setup.jboss.I placed the mysql-connector.jar file into the lib folder, also changed build.xml user customizable property to mysql



      But, When I Log into jbpm-console, I get Authentication failed error. Please help.
      I have pasted the server log below :

      13:12:08,820 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
      org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: socket creation error)
      at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)
      at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)
      at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:611)
      at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:257)
      at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:607)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
      at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
      at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
      at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:173)
      at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:206)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
      at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
      at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
      at java.security.AccessController.doPrivileged(Native Method)
      at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
      at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
      at org.jboss.security.plugins.auth.JaasSecurityManagerBase.defaultLogin(JaasSecurityManagerBase.java:552)
      at org.jboss.security.plugins.auth.JaasSecurityManagerBase.authenticate(JaasSecurityManagerBase.java:486)
      at org.jboss.security.plugins.auth.JaasSecurityManagerBase.isValid(JaasSecurityManagerBase.java:365)
      at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:160)
      at org.jboss.web.tomcat.security.JBossWebRealm.authenticate(JBossWebRealm.java:384)
      at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:258)
      at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:417)
      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
      at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
      at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
      at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
      at java.lang.Thread.run(Thread.java:619)
      Caused by: java.sql.SQLException: socket creation error
      at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
      at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)
      at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
      at org.hsqldb.jdbcDriver.connect(Unknown Source)
      at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:207)
      ... 40 more

        • 1. Re: errors with logging into console - jbpm-4.1
          kukeltje

          uhhh..... you know how to read log files and stacktraces do you?

          In case you don't I'll help you once...

          It tries to connect to hsqldb

          • 2. Re: errors with logging into console - jbpm-4.1

            Hi,

            Thanks for your reply. Yes, I could understand that it connects to Hsqldb. But I have made changes to build.xml and also changed mysql.properties. Howcome it still connects to Hsqldb..Is there anything else I should do ?

            • 3. Re: errors with logging into console - jbpm-4.1

              I would say it may have something to do with the jbpm.hibernate.cfg.xml

              • 4. Re: errors with logging into console - jbpm-4.1

                sorry for my poor posting, I read too quickly, did not realize that your question was about the console

                • 5. Re: errors with logging into console - jbpm-4.1
                  alihamza7

                  For future reference, and for others, who might run into this and because I wasted away a few hours getting this to work...

                  You can try a couple of things --

                  1. make sure you edit the properties file in {jbpm.home}/install/jdbc/

                  2. run your server and test the connection to the jpbmd db. Make sure that the db exists in the db server!

                  3. directly look into the deployment folder and search for files like  jbpm-<yoursqldb>-ds.xml, and check the configuration

                  4. cp the jdbc driver in the lib folder. If you deployed in JBoss AS, cp it to the sever/<conf>/lib

                  The reason why i was getting this error was probably because the jbpm-<yoursqldb>-ds.xml was not configured with right credentials and/or the database itself was not created.