Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Latest showcase test_runner.sh fails

    PROBLEM: I'm trying to reproduce an error and wanted to use the showcase examples to reproduce my problem, but I cannot get the showcase application to run. I ran the test_runner.sh script which gives me the same HSQLDB failure, which it does not understand the symbol SQL_TEXT_UCC in the isomorphic.script file.

    I have added the err logs

    SETUP:
    1. SNAPSHOT_v11.0d_2016-03-02/Enterprise Deployment 2016-03-02)
    Attached Files
    Last edited by michaeljseo; 3 Mar 2016, 10:29. Reason: Inserted comment indicating that err logs have been added

    #2
    From the logs it appears you're running on OS X - is this correct? What specific version? Are you saying that the showcase runs (i.e. start_embedded_server.sh) while test_runner.sh fails, or that they both fail?

    Note also that you should post a separate reply, rather than editing your post, when making a signficiant change such as adding logs

    Comment


      #3
      We've confirmed that the specific build you referenced works fine on Mavericks (OS X 10.9.5) - both start_embedded_server.sh and test_runner.sh.

      Note that SC 11.0d uses a newer version of the HSQLDB JAR, version 2.3.3, as opposted to SC 10.1p, which uses HSQLDB JAR version 2.2.9. If somehow you tried to run the 11.0d SDK installation with the older JAR, that may cause the issue you observed. Is it possible you have a mixed installation? Look at the test_runner.sh script at what HSQLDB JAR is referenced in that script.

      Comment


        #4
        It looks like you've modified the default log4j.isc.config.xml to generate more DEBUG logs that don't add anything to the picture. In particular, our default file sets logging for com.isomorphic.datasource.PoolableDataSourceFactory and com.isomorphic.pool.ISCKeyedObjectPool to INFO level. Reverting to these settings would allow you avoid having to post so many separate files.

        Comment


          #5
          I am on Mac OS X 10.11.3. I just downloaded your nightly build (SNAPSHOT_v11.0d_2016-03-07/Enterprise Deployment 2016-03-07)

          I ran test_runner.sh and still have the same problems. Am I suppose to run extra scripts to allow test_runner.sh to execute without errors? Also, I'm not able to find "start_embedded_server.sh" script. I did execute:
          find . -name start_embedded_server.sh

          in the smartgwt-6.0d folder.

          BTW, I have not modified any log files. So the verbosity is the original configuration of the download.

          Please advise.

          Comment


            #6
            I think I need to backup here. What I'm trying to do is to use the showcase examples with a slight twist to test whether I may have a bug or not. The showcase.war file has the same problems (shown in the logs) as the test_runner.sh script when I deploy it with my tomcat server.

            Thus the question about test_runner.sh.

            Perhaps, I just need to know how to deploy the showcase app. Then I can add the slight twist to one of the examples to test my understanding of the API I'm exploring.

            Comment


              #7
              From your previous posts and your choice of this subforum, it wasn't apparent that you were using SmartGWT. We do see an issue with test_runner.sh in SmartGWT EE and are investigating.

              Comment


                #8
                My apologies for not framing the context better. Your help is much appreciated!

                Comment


                  #9
                  We've verified that test_runner.sh works fine in the latest SGWT 6.0d Eval build (2016-03-16) on Mavericks (OS X 10.9.5).

                  So, as above, we'd like to reassert that this is likely an issue with the wrong HSQLDB.JAR being picked up, 2.3.3 vs. 2.2.9, due to some mixed installation or modifications you've made. If you look at the bottom of the test_runner.sh script it should be clear from the classpath what JARs are being picked up.

                  We're unable to reproduce any problem.

                  Comment


                    #10
                    Thank you! The showcase now runs out of the box.

                    Comment

                    Working...
                    X