13 Replies Latest reply on May 21, 2007 10:24 AM by kukeltje

    login to jbpm_console failed

    naseem.k

      Hi,

      I am facing problem at the login page in jbpm-console (jbpm-jpdl-suite-3.2.GA). I changed the database to oracle, executed oracle script file jbpm-jpdl-suite-3.2.GA\jbpm-jpdl-3.2.GA\db\jbpm.jpdl.oracle.sql.

      Connection to oracle is fine. SessionFactory is successfully created and server starts without any exception.

      Next I inserted few users in the jbpm_id_user table by following query.

      insert into JBPM_ID_USER (ID_,CLASS_, NAME_, EMAIL_, PASSWORD_)
      values ('2', 'U', 'ernie', 'ernie@xyz.com, 'ernie');


      Now when I tried to login in jbpm_console application by ernie/ernie, login failed.

      Anybody else faced this problem

      Thanks

        • 1. Re: login to jbpm_console failed
          kukeltje

          look at the gettingstarted document. you need to inser more than just a user

          • 2. Re: login to jbpm_console failed
            naseem.k

            Hi Ronald,

            I found one link where configuration required for database change is given, but there as well just inserts are made only in jbpm_id_user table. Here is the link:

            http://docs.jboss.com/jbpm/v3.2/userguide/html/thejbpmdatabase.html

            Can you please provide me the link of jbpmstarted which you are talking about.

            Thanks
            Naseem

            • 3. Re: login to jbpm_console failed
              kukeltje

              it's the second sticky post in this forum... you can't miss it (hmmm..... )

              • 4. Re: login to jbpm_console failed

                Ronald, I can't figure out what you're trying to get Naseem to see. All I ever have to do is add users and stir.

                Naseem, at the risk of seeming insulting... did you commit?

                -Ed Staub

                • 5. Re: login to jbpm_console failed
                  sergey.rybets

                  Hi.

                  I've got similar problem as Naseem - after migration from hsqldb to oracle I can't login to console. Records with users and passwords are present in jbpm_id_user (commit was done ;) ). Server starts without exceptions, datasource is configured properly. Everything was done like described in jBPM jPDL User Guide.

                  Thank you for your time

                  • 6. Re: login to jbpm_console failed
                    sergey.rybets

                    may be some additional data should be provided in db like groups, memberships?

                    • 7. Re: login to jbpm_console failed
                      kukeltje

                      @sergey: correct

                      @ed: with jboss you have this login-config.xml or something like that. This makes sure you atuhenticate user users against the jbpm databbase. You have to do something similar for wannaBea Weblogic.

                      • 8. Re: login to jbpm_console failed
                        kukeltje

                        sorry.... the weblogic statement was wrong here.... wrong topic

                        • 9. Re: login to jbpm_console failed
                          naseem.k

                          Hi Guys,

                          Finally I am able to login to jbpm-console page by adding records in JBPM_ID_MEMBERSHIP table for the new users I created and assigned them to a group by groupid as a foreign key.

                          Now I am getting exception at the time of process start.

                          First time when I start a new process, it works fine. There is no exception on the console. Second time when I start the same process version, exception is generated on the console saying...


                          15:32:26,701 DEBUG [JbpmContext] closing JbpmContext
                          15:32:26,701 DEBUG [Services] closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@1fa2b3e
                          15:32:26,701 DEBUG [DbPersistenceService] committing hibernate transaction
                          15:32:26,717 WARN [JDBCExceptionReporter] SQL Error: 1, SQLState: 23000
                          15:32:26,717 ERROR [JDBCExceptionReporter] ORA-00001: unique constraint (RND.SYS_C0014481) violated

                          15:32:26,717 WARN [JDBCExceptionReporter] SQL Error: 1, SQLState: 23000
                          15:32:26,717 ERROR [JDBCExceptionReporter] ORA-00001: unique constraint (RND.SYS_C0014481) violated

                          15:32:26,732 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session
                          org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
                          at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
                          at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
                          at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249)
                          at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:92)
                          at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87)
                          at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:218)
                          at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2106)
                          at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2503)
                          at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:51)
                          at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
                          at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
                          at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139)
                          at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.ja
                          va:297)


                          I got this exception only with oracle database. With hypersonic database, there was no exception.

                          Please help. What could be the cause?

                          Thanks
                          Naseem

                          • 10. Re: login to jbpm_console failed
                            kukeltje

                            two things:
                            - STFF (e.g. with google) for the oracle and unique constraint problem
                            - search the jira for comparable things

                            Only if this does not turn up anything post in a NEW topic

                            hint: the orcale/unique constraint thing has been previously addressed

                            • 11. Re: login to jbpm_console failed
                              naseem.k

                              Thanks Ronald,

                              I resolved the problem. In fact it became quite easier to find out the problem after your post.

                              Basically problem was in the process instance table, unique constraint was imposed on (ID_, PROCESSDEFINITION_) composite column. I just removed unique constraint and it worked.

                              Thanks once again

                              Regards
                              Naseem

                              • 12. Re: login to jbpm_console failed

                                Naseem,

                                I suggest that you crank up the logging out of hibernate, so that you can see what SQL is failing.

                                FWIW, I'd guess that the key generation for the process instance isn't working. I don't know why it would fail, though!

                                -Ed Staub

                                • 13. Re: login to jbpm_console failed
                                  kukeltje

                                  @Ed, I think it was/is just related to the known issue. It is in the Jira for 3.2.1. Take a look there for more info