lbor

Yes, I can start it manually. You may be right about postgresql. This is in the /jasperserver log: 2018-02-04 09:49:20,909 ERROR JDBCExceptionReporter,localhost-startStop-1:101 - Connection rejected: could not fork new process for connection: Unknown error . 2018-02-04 09:49:20,924 ERROR JDBCExceptionReporter,localhost-startStop-1:101 - Connection rejected: could not fork new process for connection: Unknown error . 2018-02-04 09:49:20,940 ERROR ContextLoader,localhost-startStop-1:331 - Context initialization failed org.springframework.dao.DataAccessResourceFailureException: Cannot open connection; nested exception is org.hibernate.exception.JDBCConnectionException: Cannot open connection at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:631) ..... So the solution may be to somehow delay or retry the start of /jasperserver web. Any ideas? Server specs are: Windows Server 2008 64bit, Intel Xeon E7530 2 cores at 1.87 GHz 8 GB RAM Think it may be a virtual server as that Xeon model has 6 cores.

This is driving my nuts. Just a default installation on a Windows Server 2008. Everything looks ok, but after reboot the jasperserver webapp doesn't start. This is what is in my log on shutdown: 04-Feb-2018 09:45:54.784 INFO [Thread-89] org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina 04-Feb-2018 09:45:55.406 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [/jasperserver] registered the JDBC driver [org.teiid.jdbc.TeiidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [Thread-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.lang.Object.wait(Unknown Source) com.jaspersoft.jasperserver.war.themes.ThemeCache$RefreshThread.run(ThemeCache.java:316) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [CascadeCacheCleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [bitronix-task-scheduler] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Thread.sleep(Native Method) bitronix.tm.timer.TaskScheduler.run(TaskScheduler.java:245) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [bufferManager Cleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:120) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [scheduled-eviction-thread-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source) java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [Mondrian Monitor] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(Unknown Source) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source) java.util.concurrent.ArrayBlockingQueue.take(Unknown Source) mondrian.server.MonitorImpl$Actor.run(MonitorImpl.java:973) java.lang.Thread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [mondrian.rolap.agg.SegmentCacheManager$ACTOR] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(Unknown Source) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source) java.util.concurrent.ArrayBlockingQueue.take(Unknown Source) mondrian.rolap.agg.SegmentCacheManager$Actor.run(SegmentCacheManager.java:921) java.lang.Thread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [mondrian.rolap.RolapResultShepherd#timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [mondrian.rolap.agg.SegmentCacheManager$ACTOR] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(Unknown Source) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source) java.util.concurrent.ArrayBlockingQueue.take(Unknown Source) mondrian.rolap.agg.SegmentCacheManager$Actor.run(SegmentCacheManager.java:921) java.lang.Thread.run(Unknown Source) 04-Feb-2018 09:45:55.421 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [mondrian.rolap.RolapResultShepherd#timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) After reboot I get 04-Feb-2018 09:47:22.885 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:Jaspersoftjasperreports-server-cp-6.3.0apache-tomcatwebappsjasperserver 04-Feb-2018 09:49:21.096 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Error listenerStart 04-Feb-2018 09:49:21.096 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/jasperserver] startup failed due to previous errors 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [/jasperserver] registered the JDBC driver [org.teiid.jdbc.TeiidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [Thread-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.lang.Object.wait(Unknown Source) com.jaspersoft.jasperserver.war.themes.ThemeCache$RefreshThread.run(ThemeCache.java:316) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [dataSnapshots] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [pool-3-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(Unknown Source) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source) java.util.concurrent.PriorityBlockingQueue.take(Unknown Source) jmxlogger.tools.JmxLogService$3.run(JmxLogService.java:214) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [CascadeCacheCleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [bitronix-task-scheduler] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Thread.sleep(Native Method) bitronix.tm.timer.TaskScheduler.run(TaskScheduler.java:245) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [bufferManager Cleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:120) java.util.TimerThread.mainLoop(Unknown Source) java.util.TimerThread.run(Unknown Source) 04-Feb-2018 09:49:21.783 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [scheduled-eviction-thread-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source) java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 04-Feb-2018 09:49:21.799 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [/jasperserver] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: 04-Feb-2018 09:49:21.799 SEVERE [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [/jasperserver] created If I go into the Tomcat Web Application Manager I can start the /jasperserver webapp from there, but I really want it to autostart since I have no control over the reboots. Any idea how to handle this?

That link hints that you can use net.sf.jasperreports.export.xls.sheet.name to obtain that, but does not really explain how. A little trial&error testing in Jasper Studio 6.4.0.final using a simple report with column header and detail band, revealed that JS was very picky about where to place it. I could only get it to work if I placed it inside a reportElement: <detail> <band height="14" splitType="Stretch"> <textField> <reportElement x="0" y="0" width="70" height="14" uuid="e0777908-52d5-4c52-8fb3-fcb3c31633bb"> <property name="com.jaspersoft.studio.unit.y" value="pixel"/> <property name="com.jaspersoft.studio.unit.height" value="pixel"/> <propertyExpression name="net.sf.jasperreports.export.xls.sheet.name"><![CDATA[$V{SheetDetail}]]></propertyExpression> </reportElement> <textFieldExpression><![CDATA[$F{REP_AAR}]]></textFieldExpression> </textField> <textField> <reportElement x="70" y="0" width="85" height="14" uuid="b0d57d3b-0c00-4eb2-a106-d845732c8015"/> $V{SheetDetail} is just a variable I created to hold the name of the sheet. It could also be a field. Furthermore, it did not matter in which field i placed the "sheet name", so I just placed it in the first field.

Very useful, but one crucial bit of information is missing from the "subreport-method": The sum variable in the main report has to have its Calculation set to "System" - cost me a few hours of desperation.

Ok, found some solutions: 1. Use older driver (max version 1.5.6). 2. Add defaultHoldable = true in Connection Properties for Data Adapter. 2) is obviously the way to go.

Hi I can't seem to get subreports working with Jaybird (jaybird-full-2.2.12.jar - see error at the bottom). I tried creating a separate data adaptor specific for the subreport. The error dissapears but no data is displayed. Also tried to do a hardcoded query (no parameters) for the subreport, and while it displays fine in subreport preview, there's no subreport data in the main report. I should mention that I am able to create a subreport using the sample data adaptor (org.hsqldb.jdbcDriver), it's just the Firebird jdbc that seems to not work. Anyone got this working? --------------------- et.sf.jasperreports.engine.JRException: net.sf.jasperreports.engine.JRException: Unable to get next record from result set.at com.jaspersoft.studio.editor.preview.view.control.ReportControler.fillReport(ReportControler.java:548)at com.jaspersoft.studio.editor.preview.view.control.ReportControler.access$20(ReportControler.java:523)at com.jaspersoft.studio.editor.preview.view.control.ReportControler$5.run(ReportControler.java:404)at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)Caused by: net.sf.jasperreports.engine.JRException: Unable to get next record from result set.at net.sf.jasperreports.engine.JRResultSetDataSource.next(JRResultSetDataSource.java:145)at net.sf.jasperreports.engine.fill.JRFillDataset.advanceDataSource(JRFillDataset.java:1538)at net.sf.jasperreports.engine.fill.JRFillDataset.next(JRFillDataset.java:1387)at net.sf.jasperreports.engine.fill.JRFillDataset.next(JRFillDataset.java:1366)at net.sf.jasperreports.engine.fill.JRBaseFiller.next(JRBaseFiller.java:1085)at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReport(JRVerticalFiller.java:117)at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:582)at net.sf.jasperreports.engine.fill.BaseFillHandle$ReportFill.run(BaseFillHandle.java:123)at java.lang.Thread.run(Thread.java:745)Caused by: org.firebirdsql.jdbc.FBSQLException: The result set is closedat org.firebirdsql.jdbc.AbstractResultSet.checkOpen(AbstractResultSet.java:231)at org.firebirdsql.jdbc.AbstractResultSet.checkCursorMove(AbstractResultSet.java:220)at org.firebirdsql.jdbc.AbstractResultSet.next(AbstractResultSet.java:280)at net.sf.jasperreports.engine.JRResultSetDataSource.next(JRResultSetDataSource.java:141)... 8 more