Jump to content
Changes to the Jaspersoft community edition download ×

Scheduler is not working correctly


Joe_123

Recommended Posts

Hi All,

I've got 24 schedulers in JasperServer which run an export job every day, every scheduler runs at a different time (with a few minutes of delay).

The schedulers are exporting csv files to the file system, but not every scheduler executes succesfully. Some csv files are always missing (not the same, always different exported reports are missing).

For example: The first scheduled job is executed successfully, then the second fails, then the rest of the 20 schedulers are executed successfully..

The catalina log says:

 

2017-11-01 01:08:19,842 ERROR ReportExecutionJob,quartzScheduler_Worker-1:363 - The report was not completed. An error occurred while executing it. (Error UID: 05c86be7-d68d-405b-81f8-0fefb40469d6)
com.jaspersoft.jasperserver.api.JSException: jsexception.error.creating.connection
Arguments: 
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.createConnection(JdbcDataSourceService.java:64)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.BaseJdbcDataSource.setReportParameterValues(BaseJdbcDataSource.java:49)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.setReportParameterValues(JdbcDataSourceService.java:69)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1784)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1130)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1059)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:954)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:932)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:649)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.executeReportUnitRequest(EngineServiceImpl.java:2045)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.domain.impl.ReportUnitRequest.execute(ReportUnitRequest.java:67)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.execute(EngineServiceImpl.java:529)
    at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.runReport(ReportExecutionJob.java:847)
    at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.executeReport(ReportExecutionJob.java:814)
    at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.executeReport(ReportExecutionJob.java:711)
    at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.executeAndSendReport(ReportExecutionJob.java:496)
    at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.execute(ReportExecutionJob.java:245)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: java.sql.SQLException: monetdbd: an internal error has occurred 'cannot connect: Connection refused', refer to the logs for details, please try again later
    at nl.cwi.monetdb.jdbc.MonetConnection.<init>(MonetConnection.java:289)
    at nl.cwi.monetdb.jdbc.MonetDriver.connect(MonetDriver.java:166)
    at java.sql.DriverManager.getConnection(DriverManager.java:664)
    at java.sql.DriverManager.getConnection(DriverManager.java:247)
    at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDriverManagerConnectionFactory.createConnection(JdbcDriverManagerConnectionFactory.java:36)
    at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
    at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
    at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.TibcoDriverManagerImpl.unlockConnection(TibcoDriverManagerImpl.java:76)
    at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.createConnection(JdbcDataSourceService.java:56)
    ... 18 more
Caused by: nl.cwi.monetdb.mcl.MCLException: monetdbd: an internal error has occurred 'cannot connect: Connection refused', refer to the logs for details, please try again later
    at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:317)
    at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:401)
    at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:258)
    at nl.cwi.monetdb.jdbc.MonetConnection.<init>(MonetConnection.java:268)
    ... 28 more

 

DB log:

2017-11-01 01:07:56 MSG merovingian[1595]: database 'motors' (22338) was killed by signal SIGKILL
2017-11-01 01:08:19 MSG merovingian[1595]: database 'motors' has crashed after start on 2017-11-01 01:05:15, attempting restart, up min/avg/max: 15m/1h/6h, crash average: 1.00 0.80 0.73 (30-8=22)
2017-11-01 01:08:19 MSG motors[31527]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/monetdb/motors --set merovingian_uri=mapi:monetdb://statics:50000/motors --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/motors/.mapi.sock --set monet_vault_key=/var/lib/monetdb/motors/.vaultkey --set gdk_nr_threads=5 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2017-11-01 01:08:19 MSG merovingian[1595]: proxying client localhost:49102 for database 'motors' to mapi:monetdb:///var/lib/monetdb/motors/.mapi.sock?database=motors
2017-11-01 01:08:19 MSG merovingian[1595]: starting a proxy failed: cannot connect: Connection refused
2017-11-01 01:08:19 ERR control[1595]: !monetdbd: an internal error has occurred 'cannot connect: Connection refused'
2017-11-01 01:08:21 MSG motors[31527]: # MonetDB 5 server v11.25.23 "Dec2016-SP5"
2017-11-01 01:08:21 MSG motors[31527]: # Serving database 'motors', using 5 threads
2017-11-01 01:08:21 MSG motors[31527]: # Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers
2017-11-01 01:08:21 MSG motors[31527]: # Found 11.735 GiB available main-memory.
2017-11-01 01:08:21 MSG motors[31527]: # Copyright © 1993-July 2008 CWI.
2017-11-01 01:08:21 MSG motors[31527]: # Copyright © August 2008-2017 MonetDB B.V., all rights reserved
2017-11-01 01:08:21 MSG motors[31527]: # Visit http://www.monetdb.org/ for further information
2017-11-01 01:08:21 MSG motors[31527]: # Listening for UNIX domain connection requests on mapi:monetdb:///var/lib/monetdb/motors/.mapi.sock
2017-11-01 01:08:21 MSG motors[31527]: # MonetDB/SQL module loaded
2017-11-01 01:08:24 ERR merovingian[1595]: client error: cannot connect: Connection refused
2017-11-01 01:09:00 MSG merovingian[1595]: proxying client localhost:49113 for database 'motors' to mapi:monetdb:///var/lib/monetdb/motors/.mapi.sock?database=motors
2017-11-01 01:09:00 MSG merovingian[1595]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2017-11-01 01:10:41 ERR discovery[1595]: cannot retrieve name info: Temporary failure in name resolution

...

The report query:

select date, time, id, engine_type, engine_code, capacity, bore_stroke_rat, valve_gear, max_power_out, spec_out, max_torque, spec_torque, sump, compression_ratio, fuel_system, bmep, max_rpm, coolant, unitary_capacity, aspiration, compressor, intercooler, catalytic_inverter, acceleration60, acceleration80, acceleration100, acceleration160, max_speed, power_to_weight_rat, weight_to_power_rat, fuel_consumption, litres100km, km_litre, uk_mpg, us_mpg, carbon_dioxid_emiss, carfolio_calc_co2, ved_band, engine_position, engine_layout, drive_wheels, steering, brakes, gearbox, rac
from motors.datas
where date = date_to_str(cast($P{param_date} as date), '%Y-%m-%d')
and $X{IN, engine_type, param_engine_type}
order by date, time

If I execute the reports in JasperServer, everything is correct, the reports run successfully.

Can anybody help me with this issue?

Kind regard,

joe_

Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...