build from source failing

 
1
0
-1

Hello,

I'm trying to build Joget from source following the instructions from KB and it keeps failing on wflow-directory, more specifically the build fails the below tests:

Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 3.604 sec <<< FA
ILURE!
Results :
Tests in error:
  testUsersAndGroups(org.joget.directory.model.service.TestDirectoryManager)
  testOrganizationChart(org.joget.directory.model.service.TestDirectoryManager)
  testDeletion(org.joget.directory.model.service.TestDirectoryManager)
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0

The instructions followed:

Building from Source and Joget Workflow Source Code, including watching the tutorial video for building v3 from source. The issues encountered here: none of the written instructions include all steps required (note that in the video there are extra instructions that weren't included in the written text), also the "updated" instructions from v5 are blatantly incomplete. Speaking from experience of a person, who's been actively training people and writing manuals as part of my job.

Yes, I've seen the thread below:

"Build failed" when run setup-maven.xml with ant.bat and switching to older version of Maven (2.2.1) made no difference.

I've also seen a thread below:

/questions/23003312/answers/23003342 and in spite of building each module individually as suggested (through command line not eclipse) the build of wflow-directory still fails. It seems peculiar that the author notes failing build on Windows 7 64bit, which is what I am using too. I will be testing the build on Linux based machine to see what happens.

Yes, I have followed the written instructions (as already stated above) and have everything installed what's needed. Also I have already searched the Knowledge Base but if there are articles that I haven't found and aren't listed above, please let me know.

Any indicators will be really appreciated.

Many thanks,

Kasia

    CommentAdd your comment...

    6 answers

    1.  
      3
      2
      1

      Hi Oren,

      I wasn't planning on it - I'm running Joget on virtual machine at work and having put up with failing tests I just continued with the project due to time constraints. You're right though, the instructions are not the best, so I'm thinking about cracking the problem once the project is complete and have more time at home to dig into it.

      It might take a few weeks though. (sad)

      Is it urgent and what kind of people are you thinking about, who would need it?

       

      Thanks,

      Kasia

      1. Wimmer Robin

        Hi Kasia, Did you find out the problem why the Server is Shutdown during the wflow-core build? Got the same Problem... My configuration and file locations are all correct, i just can figure out why it needs to shutdown the server... Of course the other builds are giving this hibernate dialect error if no database is up which can be connected... Thanks, Robin

      CommentAdd your comment...
    2.  
      1
      0
      -1

      Kasia,

      Thank you for willingness to do that. The install document is very thin but it seems that you was able to overcome it and know what needs to be done.

      So whenever you get the chance.

      Thanks again,

      Oren

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Kasia,

        Will you be willing to put together a more detailed installation instruction document than the very thin document available so far?

        Thanks anyways!

          CommentAdd your comment...
        1.  
          1
          0
          -1

          Hello,

          It looks like the cause of the problem is this:

          Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'setupSessionFactory' defined in class path resource [commonsApplicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set.

          Unfortunately I am not familiar with Hibernate so this is of not much help - I check if the right database is up and running with the right credentials and on the right port every time I try to build the thing. Also I checked the commonsApplicationContext.xml file - the setupDataSource bean appears to be fine; the only property out of whack is missing value for password property - whether it's present or not it doesn't matter because the tests fail either way.

          Having changed the database settings to original schema that was set up when running first instance of Joget and uncommenting this line:

          hibernate.dialect=org.hibernate.dialect.MySQLDialect in jdbc.properties in wflow-directory/src/main/resources

          resulted in successful build and passed tests for wflow-directory and wflow-wfengine. The wflow-core build failed thanks to the server being shut down during wflow-core tests. After restarting the server the build was successful and tests passed.

          I am not sure why the server was shut down during the tests but here's the dump for perusal:

          FROM DIESXIFNEKPI.err:
              2016-02-17T09:06:08  0  Note  C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Normal shutdown
              2016-02-17T09:06:08  0  Note  Giving 4 client threads a chance to die gracefully
              2016-02-17T09:06:08  0  Note  Shutting down slave threads
              2016-02-17T09:06:10  0  Note  Forcefully disconnecting 3 remaining clients
              2016-02-17T09:06:10  0  Warning  C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Forcing close of thread 3  user: 'root'
              2016-02-17T09:06:10  0  Warning  C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Forcing close of thread 4  user: 'root'
              2016-02-17T09:06:10  0  Warning  C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Forcing close of thread 6  user: 'root'
              2016-02-17T09:06:10  0  Note  Event Scheduler: Purging the queue. 0 events
              2016-02-17T09:06:10  0  Note  Binlog end
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'ngram'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'partition'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'BLACKHOLE'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'ARCHIVE'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'PERFORMANCE_SCHEMA'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'MRG_MYISAM'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'MyISAM'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_VIRTUAL'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_DATAFILES'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_TABLESPACES'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_FOREIGN'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_FIELDS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_COLUMNS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_INDEXES'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_TABLESTATS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_SYS_TABLES'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_FT_INDEX_TABLE'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_FT_INDEX_CACHE'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_FT_CONFIG'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_FT_BEING_DELETED'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_FT_DELETED'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_METRICS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_BUFFER_PAGE'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_CMP_PER_INDEX'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_CMPMEM_RESET'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_CMPMEM'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_CMP_RESET'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_CMP'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_LOCK_WAITS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_LOCKS'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'INNODB_TRX'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'InnoDB'
              2016-02-17T09:06:10  0  Note  InnoDB: FTS optimize thread exiting.
              2016-02-17T09:06:10  0  Note  InnoDB: Starting shutdown...
              2016-02-17T09:06:10  0  Note  InnoDB: Dumping buffer pool(s) to C:\ProgramData\MySQL\MySQL Server 5.7\Data\ib_buffer_pool
              2016-02-17T09:06:10  0  Note  InnoDB: Buffer pool(s) dump completed at 160217 10:06:10
              2016-02-17T09:06:10  0  Note  InnoDB: Shutdown completed; log sequence number 31383989
              2016-02-17T09:06:10  0  Note  InnoDB: Removed temporary tablespace data file: "ibtmp1"
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'MEMORY'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'CSV'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'sha256_password'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'mysql_native_password'
              2016-02-17T09:06:10  0  Note  Shutting down plugin 'binlog'
              2016-02-17T09:06:10  0  Note  C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Shutdown complete

          Thanks!

           

          1. Hugo

            You will need to make sure that the profile configuration file located in your [home]/wflow/ folder exists and pointing to a valid database. See http://dev.joget.org/community/display/KBv5/Joget+Workflow+Source+Code#JogetWorkflowSourceCode-4.ConfigureDatasourceforTestCase posted earlier.

          CommentAdd your comment...
        2.  
          1
          0
          -1

          Hi,

          Like I said, I followed the instructions, including this step (and checked out this link: Custom Database Configuration) and double checking it quite few times. In spite of database up and running, and connectivity tested the build is always successful (when skip tests set to true in pom) yet it always fails on testing. Also I have no problems whatsoever to connect to the very same database when running Joget. Trying different datasources also fails.

          The only time the whole build succeeds is when tests are skipped during building wflow-directory, wflow-wfengine and wflow-core.

          The question is: how (if at all) failure to pass tests will affect writing plugins in future? Are there any impacts that you know about?

          Thanks,

          Kasia

           

          1. Julian

            Hi, The failure to pass those tests should not affect the development of your own plugins. Having said that, it shouldn't fail in the first place. Maybe you can share the details of the test reports which should contain detailed error messages and stacktraces which would shed light on what kind of problem you're encountering.

          CommentAdd your comment...
        3.  
          1
          0
          -1

          Hi,

          You can check the details of the test failures in the Maven test/surefire-reports directory. I'm guessing that it is due to database connection errors, so you may want to double check the datasource configuration step at Joget Workflow Source Code#4.ConfigureDatasourceforTestCase

           

            CommentAdd your comment...