js-ant import-minimal-ce fails

[alanm]

Hi

I'm upgrading jasper server 4.2 to 6.2

I'm upgrading using the war file

Going smoonthly until js-ant import-minimal-ce

This fails. Log is:

import-minimal-ce:
     [echo]
     [echo] Property values (in install.xml):
     [echo]  archiveArg = --input-zip=C:/Install/jasperreports-server-cp-6.2.1-b
in/buildomatic/install_resources/export/js-catalog-postgresql-minimal-ce.zip
     [echo]  dbType = postgresql
     [echo]  jdbcJar = postgresql-9.2-1002.jdbc4.jar
     [echo]  currentConf = C:/Install/jasperreports-server-cp-6.2.1-bin/buildoma
tic/build_conf/default
     [echo]  importExportConfig = C:/Install/jasperreports-server-cp-6.2.1-bin/b
uildomatic/conf_source/ieCe
     [echo]
     [echo] Validating JasperServer database connection at jdbc:postgresql://loc
alhost:5432/jasperserver. Phase: [import-export-test]
     [echo] For JDBC driver the artifactId and version properties are set:
     [echo]   maven.jdbc.artifactId=postgresql
     [echo]   maven.jdbc.version=9.2-1002.jdbc4
     [echo]   Specified JDBC driver jar exists
[advanced-sql] Executing commands
[advanced-sql] 1 of 1 SQL statements executed successfully
     [echo] Connection OK
     [java] Error occurred during initialization of VM
     [java] Could not reserve enough space for object heap
     [java] Error: Could not create the Java Virtual Machine.
     [java] Error: A fatal exception has occurred. Program will exit.

BUILD FAILED
C:Installjasperreports-server-cp-6.2.1-binbuildomaticbinimport-export.xml:327: The following error occurred while executing this line:
C:Installjasperreports-server-cp-6.2.1-binbuildomaticbinimport-export.xml:203: Java returned: 1

Total time: 1 second

I've played withe the import-export.xml. Line 327 points to 203. I've played with the memory sizes to no avail

  203              <java classname="${class}" fork="true" failonerror="true" inputstring="">
                        <arg value="--@{type}"/>
                        <arg value="${archiveArg}"/>
                        <args/>
                        <!-- add arg that tells oracle JDBC driver to use utf-8 types; won't hurt anyone else -->
                        <jvmarg value="-Doracle.jdbc.defaultNChar=true"/>
                        <!-- add this to handle properly import catalogs with utf-8 names -->
                        <jvmarg value="-Dfile.encoding=UTF-8"/>
                        <!-- disable ehcache -->
                        <jvmarg value="-Dnet.sf.ehcache.disabled=true"/>
                        <!-- set this var to avoid certain network exceptions in OS X -->
                        <jvmarg value="-Djava.net.preferIPv4Stack=true"/>
                        <jvmarg value="-Xms1024m"/>
                        <jvmarg value="-Xmx2048m"/>
                        <jvmarg value="-XX:PermSize=512m"/>
                        <jvmarg value="-XX:MaxPermSize=1024m"/>

                        <!-- Uncomment to debug remotely     -->
                        <!--<jvmarg value="-Xdebug"/>
                        <jvmarg value="-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"/>-->

                        <classpath>
                            <!--
                                TODO
                                we should put currentConf first so it can pick up the files generated based on
                                db settings, etc., but if you do that, beans don't get recognized because
                                the Spring context loader uses a pattern of "applicationContext*.xml", which
                                is sensitive to the order of the classpath.
                                We should use one of the args such as -configResources to pass a pattern
                                that is more explicit for Spring, doing something like this:
                                -configResources=file:blah/import-export/dir/applicationContext*.xml
                              -->
                            <pathelement location="${importExportConfig}"/>
                            <fileset dir="${importExportLibDir}" includes="*.jar"/>
                            <fileset dir="${currentDbJDBCDir}" includes="${jdbcJar}"/>
                            <pathelement location="${currentConf}"/>
                        </classpath>
                    </java>

Any hints or ideas?

The server is current Win 2003, 4Gb  RAM and just jasper server running

I wanted to upgrade this version then move the database and repository to a new Win 2012 R2 server I have ready

Or is there a better way for me to do the upgrade/move?

Cheers

Al.

 

[alanm]

I think I've found the answer

I copied the version 4.2 export zip file from the older server to the new server

At a command prompt in the buildomatic directory of the fresh install I typed:

js-ant import-upgrade-ce -DimportFIle=<filepath>

The data was imported and so far it's working well

Hope this helps someone

Al.

[ken.jin]

It maybe your RAM is not enought to creat JVM. So you need to set your java memory in tomcats smallers.

Open command line, cd C:Jaspersoftjasperreports-server-cp-5.6.0apache-tomcatbin

Goto C:Jaspersoftjasperreports-server-cp-5.6.0apache-tomcatbin

 

you can see tomcat7w or tomcat6w (depend on your Tomcat version).

In command line (see in below picture)

jasperreportstomcat propertise show up,

in java tab, Java Options, you will see

-Xms1024M
-Xmx2045M
-Xss2M
-Dcatalina.base=C:JASPER~1JASPER~1.0APACHE~1
-Dcatalina.home=C:JASPER~1JASPER~1.0APACHE~1
-Djava.endorsed.dirs=C:JASPER~1JASPER~1.0APACHE~1endorsed
-XX:PermSize=128m
-XX:MaxPermSize=256m
-XX:+UseConcMarkSweepGC
-XX:+CMSClassUnloadingEnabled
 

Adjust -Xms1024M and -Xmx2045M with smaller value (may be 512 and 1024) then apply.

After that goto services and restart jasperreportstom