Jump to content
We've recently updated our Privacy Statement, available here ×

sendarnav

Members
  • Posts

    16
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Posts posted by sendarnav

  1. Hi,

    I am scheduling jasper report using  rest API, report is getting sceduled , but the parameters are not getting passeed to report, hence the report is failing. Iam using the following Job XML for scheduling

    TestPrintTestPrintTest_217100PDF
    1
    217100
    /reports/TestPrint
    /reports/Scheduled_Reportstruefalse0
    2013-01-25T20:55 57-08:00010

    I don't understand why the parameters are not getting passed to report, although paramater tag is there job XML.

    Any help is really appreciated.

     

  2. Hi Lucian,

     

    This setting works, i appreciate for putting this in Forum. The memory consumption is very high when scheduling big reports, I have allocated 3 GB of memory for JVM, 1 report has taken 1.5 GB of memory.The report has came back pretty fast i got around 70000 rows(35 MB) report in 7 minutes. Is there a way i can get rid of memory issues, I am already using visualizer, i don't mind if the report comes back more time, need have minimize the memory consumption

     

  3. Hi Sherman,

    The Jasper server is getting hanged when running a big  report, 1 report is consuming almost 3GB of memory, wondering why Jasper server is taking almost 3 GB for 1 report even if the query is very slow. I don't mind if it takes more time to generate big reports, but memory consumption should be reasonable.

    Any help is really appreciated

  4. We are migrating reports from Crystal  to Jasper Server, we have more than 100 reports, 15 reports may hit server simultanously. In QA we have allocated 3GB, while load testing 1 of the report has taken almost 3 GB memmory server got hanged, the Stored procedure which generates the report is slow. It hard to believe 1 report has consumed 3 GB of memory no matter hoe bad is the procedure. I don't mind if big report takes time to generate, but it take more memory other reports are going to get effected since server gets hanged.

    Any help is appreciated.

  5. We are Migrating the reports from Crystal to Jasper, There are multiple big reports in our application. We are using Jasper Server 4.0 and allocated 3 GB memory for JVM on Linux. One of the report is very big the SQL which generates the report is very slow.The report has consumed almost 3 GB of memory and Jasper Server has hanged after some time.

    Its Hard to believe 1 report has consumed almost 3 GB of memory, no matter how bad the query is, i think i might messed some property or Driver is not good.

    Does any one has faced similar problem, any help is really appreciated

     

    Thanks,

    Surya

     

  6. I have made the following configuration change in Jasper Server ..

    <bean id="fileVirtualizerFactory" class="com.jaspersoft.jasperserver.api.engine.common.service.impl.SwapFileVirtualizerFactory">

            <property name="maxSize" value="400"></property>

    <!--        <property name="directory" value="${java.io.tmpdir}"></property> -->

     </bean>

     

    How do i know the virtualizer is getting used while report generation.

  7. What is the default is it RAMJobStore or JDBC-JobStoreTX. In quartz-1.5.1-jaspersoft.jar file of Jasper server, there is property defined org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore. Does this mean jobstore is Ram, if override the  the jobstore property in js.quartz.base file to org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX in jasper server is going make the jobstore to JDBC.

    What is the ideal job store when we need schdule 50 simultanous reports, in that 10 will be long running

  8. I am getting out of sweep error when running 23 simultanous reports. The follwing is the error

    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    # java.lang.OutOfMemoryError: requested 65536000 bytes for GrET in /BUILD_AREA/jdk6_18/hotspot/src/share/vm/utilities/growableArray.cpp. Out of swap space?
    #
    #  Internal Error (allocation.inline.hpp:39), pid=6376, tid=177642384
    #  Error: GrET in /BUILD_AREA/jdk6_18/hotspot/src/share/vm/utilities/growableArray.cpp
    #
    # JRE version: 6.0_18-b07
    # Java VM: Java HotSpot Server VM (16.0-b13 mixed mode linux-x86 )
    # An error report file with more information is saved as:
    # /apps03/jasper/apache-tomcat/bin/hs_err_pid6376.log
    #
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    #

    The following is my memory setting

    export JAVA_OPTS="$JAVA_OPTS -Xms3072m -Xmx3072m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled"
    export JAVA_OPTS="$JAVA_OPTS -Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl -Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFactoryImpl -Djavax.xml.soap.SOAPFactory=org.apache.axis.soap.SOAPFactoryImpl -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl"

    and Iam giving 15 as thread count and  1800000(30 minuets) as misfire threshold to make job wait in case long running reports

    org.quartz.threadPool.threadCount=15
    org.quartz.threadPool.threadPriority=5
    org.quartz.jobStore.misfireThreshold=1800000

    and using database pool size as 20.
     

    What is idea configuration to make 50 job to run simultanously in that 10 will be long running.

    Any help is appreciated

     

     

     

  9. Hi,

    We are migrating crystal reports to jasper. The application has more 100 reports, some of them has huge data. We are using webservices exposed by Jasper server community version.  We are using ReportSchedulerSoapBindingStub, JServer, WSClient for scheduling the report.

    The reports are getting scheduled when we run one after the other, but server is getting hanged when we try to multiple reports at a time.

    The following is memory setting for the server

    export JAVA_OPTS="$JAVA_OPTS -Xms2048m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=512m"

    and we have changed the follwing property in js.quartz.base.properties to 30, default was 3

    org.quartz.threadPool.threadCount=30

    and also changed dataSourceObjectPoolFactory to 10, default was 2

    <bean id="dataSourceObjectPoolFactory" class="org.apache.commons.pool.impl.GenericObjectPoolFactory">
            <constructor-arg type="org.apache.commons.pool.PoolableObjectFactory"><null/></constructor-arg>
            <constructor-arg type="int" value="10"/>
    </bean>

     

    I am thinking the resources are not getting realeased when run multiple reports in parallel

    Does any know the idea settings for memory and any other setting i need to make for scheduling multiple reports.

    Any Help is really appreciated.

  10. 1) I have report designed via ireport deployed in a server.

    2) The report has lets say 50 columns

    3) While generating the report, i want to remove certian columns from the report  and downlaod it to excel

    4) we can do it in Crystal reports by passing @#CustomDeleteFields parameters, want to know whether there is similar way to do it jasper(method etc ..)

     

    Its urgent task, any help is appreciated

     

×
×
  • Create New...