You're right. It wasn't that line. That was just the line logged prior to the error. There was no more in the stack trace - just the line I included below:

ERROR - LoggingAdvice.invoke(111) |2012-02-10 10:13:16,108| An error occurred while executing this method. Error message: Java heap space
java.lang.OutOfMemoryError: Java heap space

This occurred somewhere during execution of HibernateTestingDao.generateTestDataSet (after the table names were logged, clearly), but no more information as to where...

Mike


On 02/10/2012 11:58 AM, Darius Jazayeri wrote:
Hi Mike,

Thanks for exploring this further!

Can you provide more of the stack trace and logging of the out of memory error? Because line 107 of HibernateTestingDAO is just:
    log.warn("tables to dump: " + tablesToDump);
and that's just an ArrayList<String>, so I don't see how that particular line could be where the memory runs out...

-Darius

On Fri, Feb 10, 2012 at 7:18 AM, Michael Seaton <[email protected] <mailto:[email protected]>> wrote:

    FYI - I tried this out today, and found that I get this same error
    on the destination server (eg. the 1.9 standalone).  Looking into
    this a little more, I see that on my source server (eg. the
    existing 1.6 instance I want to test), I am getting an out of
    memory error during the HibernateTestingDao.generateTestDataSet
    method (specifically line 107):

    ERROR - LoggingAdvice.invoke(111) |2012-02-10 10:13:16,108| An
    error occurred while executing this method. Error message: Java
    heap space
    java.lang.OutOfMemoryError: Java heap space

    So, this is likely the source of the problem...

    Mike



    On 01/23/2012 02:23 AM, Lara Kellett wrote:

        Did a bit of experimenting with different scenarios over the
        weekend.

        Seeing the "Unexpected end of ZLIB input stream" every time I
        try to use the testing function in conjunction with a 1.6
        database. It appears to be falling over at the import test
        data section of the process and therefore never reaches the
        import modules part.

        If I try using the testing function from a database that has
        been upgraded to 1.9 then I get the following issues when
        trying to import my modules. Zipped up my modules folder
        (currently we run about 29 modules in production) and it is
        16.3MB.

        ERROR - TestInstallUtil.addZippedTestModules(172) |2012-01-22
        14:10:08,747| An error occured while copying modules to the
        test system:
        java.util.zip.ZipException: error in opening zip file
               at java.util.zip.ZipFile.open(Native Method)
               at java.util.zip.ZipFile.<init>(ZipFile.java:127)
               at java.util.zip.ZipFile.<init>(ZipFile.java:144)
               at
        
org.openmrs.web.filter.initialization.TestInstallUtil.addZippedTestModules(TestInstallUtil.java:144)
               at
        
org.openmrs.web.filter.initialization.InitializationFilter$InitializationCompletion$1.run(InitializationFilter.java:1490)
               at java.lang.Thread.run(Thread.java:680)
        Jan 22, 2012 5:23:31 PM
        org.apache.coyote.http11.Http11Protocol destroy
        INFO: Stopping Coyote HTTP/1.1 on http-8082
        Jan 22, 2012 5:23:31 PM
        org.apache.catalina.core.StandardContext listenerStop
        SEVERE: Exception sending context destroyed event to listener
        instance of class org.openmrs.web.Listener
        org.openmrs.api.APIException: contextDAO is null
               at
        org.openmrs.api.context.Context.getContextDAO(Context.java:171)
               at
        org.openmrs.api.context.Context.closeSession(Context.java:722)
               at
        org.openmrs.web.Listener.contextDestroyed(Listener.java:497)
               at
        
org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4011)
               at
        org.apache.catalina.core.StandardContext.stop(StandardContext.java:4615)
               at
        org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
               at
        org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
               at
        org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
               at
        org.apache.catalina.startup.Embedded.stop(Embedded.java:867)
               at
        org.openmrs.standalone.TomcatManager.stop(TomcatManager.java:86)
               at
        
org.openmrs.standalone.ApplicationController.stopServer(ApplicationController.java:395)
               at
        
org.openmrs.standalone.ApplicationController.access$500(ApplicationController.java:29)
               at
        
org.openmrs.standalone.ApplicationController$2.construct(ApplicationController.java:158)
               at
        org.openmrs.standalone.SwingWorker$2.run(SwingWorker.java:125)
               at java.lang.Thread.run(Thread.java:680)
        [MysqldResource] stopping mysqld (process: 18576)
        [MysqldResource] shutdown complete
        ________________________________________
        From: [email protected] <mailto:[email protected]>
        [[email protected] <mailto:[email protected]>] On Behalf Of Darius
        Jazayeri [[email protected] <mailto:[email protected]>]
        Sent: Friday, January 20, 2012 6:32 PM
        To: [email protected]
        <mailto:[email protected]>
        Subject: Re: [OPENMRS-DEV] 1.9.1 Beta standalone and Release
        Testing Helper

        We should track down why the regular testing process didn't
        work for Lara. Maybe too many modules so the zip got too big?

        Lara, can you manually zip your modules folder and let us know
        how big it is?

        -Darius (by phone)

        On Jan 20, 2012 9:18 AM, "Wyclif Luyima"<[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>>  wrote:
        So you are succeeding in loading the imported sql script but
        the liquibase upgrade from 1.6 to 1.9 is failing, right?

        It would good if you could find out which changeset is failing.

        Wyclif

        On Fri, Jan 20, 2012 at 3:12 AM, Lara Kellett<[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>>  wrote:
        Hi Wyclif,

        Okay I tried trashing everything and starting again. The test
        install is still failing, I was trying to import from my local
        dev environment so internet connection is not going to be the
        issue given it is going from localhost to localhost.

        With a clean standalone install I am now able to connect
        directly to my dev database (which you can do through the
        advanced setup option by changing the connection details). The
        Migration scripts are still failing going from 1.6 to 1.9 but
        expected that anyway and at least now I am getting sql errors
        so can start working my way through those.

        Thanks,

        Lara
        ________________________________________
        From: [email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>  [[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>] On Behalf Of Wyclif Luyima
        [[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>]
        Sent: Thursday, January 19, 2012 11:11 PM
        To: [email protected]
        
<mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>
        Subject: Re: [OPENMRS-DEV] 1.9.1 Beta standalone and Release
        Testing Helper

        Hi Lara,

        First of all you cannot select advanced option and try to
        connect to an existing database at the same time, i wonder how
        you are managing to do it. If you attempt to do a test install
        and it fails,  i would suggest you stop the standalone  and
        clear the database directory in the root of the standalone.
        FYI the embedded MySQL instance could have stayed running,
        kill it before trying again if this is the case.

        Off the top of my head, the cause of the failure could be
        because the zipped temp sql dump file is not downloaded fully
        from your remote system hence failing to read its contents.
        How good is your internet connection?

        Wyclif

        On Thu, Jan 19, 2012 at 9:32 AM, Lara Kellett<[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>><mailto:[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>>>  wrote:
        Hi,

        I am trying to use the 1.9.1 Beta standalone in conjunction
        with the Release Testing Module.

        I am trying to import the database from my local dev
        environment which is running a custom build of 1.6.4 (Build
        18038). My dev database is a de-identified database from our
        production servers which are also on the same 1.6.4 build.

        When I try to import test data into the standalone I am seeing
        the following error in the tomcat logs

        WARN -
        InitializationFilter$InitializationCompletion$1.run(1507)
        |2012-01-19 15
        <tel:2012-01-19%2015><tel:2012-01-19%2015>:56:08,844| Error
        while trying to import test data
        java.io.EOFException: Unexpected end of ZLIB input stream
              at
        java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:223)
              at
        java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141)
              at
        java.util.zip.ZipInputStream.read(ZipInputStream.java:154)
              at java.io.FilterInputStream.read(FilterInputStream.java:90)
              at
        org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1025)
              at org.apache.commons.io.IOUtils.copy(IOUtils.java:999)
              at
        
org.openmrs.web.filter.initialization.InitializationFilter.importTestDataSet(InitializationFilter.java:1025)
              at
        
org.openmrs.web.filter.initialization.InitializationFilter.access$400(InitializationFilter.java:87)
              at
        
org.openmrs.web.filter.initialization.InitializationFilter$InitializationCompletion$1.run(InitializationFilter.java:1454)
              at java.lang.Thread.run(Thread.java:680)

        Does anyone have any suggestions as to the cause of the
        problem or where I can start looking? I am seeing the same
        problems if I try the advanced option and try to connect the
        standalone directly to my dev database.

        Thanks,

        Lara
        _________________________________________

        To unsubscribe from OpenMRS Developers' mailing list, send an
        e-mail to [email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>><mailto:[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>>  with "SIGNOFF
        openmrs-devel-l" in the  body (not the subject) of your e-mail.

        [mailto:[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>><mailto:[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>>?body=SIGNOFF%20openmrs-devel-l]

        ________________________________
        Click here to unsubscribe<mailto:[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>?body=SIGNOFF%20openmrs-devel-l>
         from OpenMRS Developers' mailing list

        _________________________________________

        To unsubscribe from OpenMRS Developers' mailing list, send an
        e-mail to [email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>  with "SIGNOFF
        openmrs-devel-l" in the  body (not the subject) of your e-mail.

        [mailto:[email protected]
        <mailto:[email protected]><mailto:[email protected]
        <mailto:[email protected]>>?body=SIGNOFF%20openmrs-devel-l]

        ________________________________
        Click here to unsubscribe<mailto:[email protected]
        <mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l>
         from OpenMRS Developers' mailing list
        ________________________________
        Click here to unsubscribe<mailto:[email protected]
        <mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l>
         from OpenMRS Developers' mailing list

        _________________________________________

        To unsubscribe from OpenMRS Developers' mailing list, send an
        e-mail to [email protected]
        <mailto:[email protected]> with "SIGNOFF
        openmrs-devel-l" in the  body (not the subject) of your e-mail.

        [mailto:[email protected]
        <mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l]


    _________________________________________

    To unsubscribe from OpenMRS Developers' mailing list, send an
    e-mail to [email protected]
    <mailto:[email protected]> with "SIGNOFF
    openmrs-devel-l" in the  body (not the subject) of your e-mail.

    [mailto:[email protected]
    <mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l]


------------------------------------------------------------------------
Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to