jeremy.suiter

I appreciate your help but I'm afraid that won't work either as this has nothing to do with a text field. I don't even use the variable on the report it's just a total that I want to use to not print the group header & footer. This is probably just a limitation of the way Jasper works in that the variable is evaulated after the header is printed so what I want to do just isn't possible. Jeremy

Hi, I'm afraid that won't work as the logic is dependent on a variable total for the group which will always be zero when the group header prints. The print when logic for the group footer is $V{group_total}!=0.00 and when this suppresses the group footer I want the group header to suppress as well. Regards Jeremy

Hi, I've got a problem where I want to stop a group header from printing bsed on a total calculated for that group. The SQL query returns line items only and I cannot do any pre-totalling and that cannot change. So I have a total calculating for a group and when it's zero I do not want to print that group at all. No problem using the print when expression for the footer but I cannot find a way to stop the group header from printing. I've tried everything using sub datasets and sub reports but I cannot find a way to pre-calculate the total so I can use it or link the header and footer together so when the footer is suppresses so is the header. As I mentioned before I cannot pre-calculate these totals in the SQL query at all. Can anyone help me? Many thanks Jeremy

For anyone interested I finally found a solution to my problem. The Tomcat version running Jasper Server is 8 and JNDI data source variables changed from version 7 to 8 except I couldn't find that anywhere in the docs. It wasn't clear in the Tomcat docs either but after many Google attempts I found a post about it. So the variable MaxActive changed to MaxTotal and I didn't know. The default number of threads for the MaxTotal variable was 8, the problem I had. Changed the JNDI data source definition in context.xml from MaxActive=100 to MaxTotal=100 and problem solved! Jeremy

Does anyone have any ideas for me? I'm about to unleash 250+ users on Jasper and some of the reports take hours to run so I need to get the right amount of people logged in and working. TIA Jeremy

Hi, I can't seem to run more than 8 reports concurrently whether they are using the scheduler or dierctly in the browser. I've been through all the settings and searched the Wiki/Forums and changed settings where necessary and still cannot run more than 8. Can someone point me in the right direction as to where it might be going wrong. Details of settings I have changed below. Database Jasper Server points to is MySQL set to accept 200 connection maximum. Jasper Server 6.2.1 (community edition) JNDI data source set to 100 connections in Context.xml 100 thread count set in js.quartz.properties (org.quartz.threadPool.threadCount=100 ) 100 thread count set in js.quartz.base.properties (org.quartz.threadPool.threadCount=100) dataSourceObjectPoolFactory set to 100 in ApplicationContext.xml Many Thanks Jeremy

I've figured it out. As my TOC is always on Page 2 of the report I've managed to put a link on every page that uses the following settings: Link Target: Self Link Type: Local Page Hyperlink Page Expression: 2 And it works perfectly. Jeremy

I love report books and the TOC it creates. What I would like to do is have on every page a link that will jump BACK to the table of contents. This would be very useful especially for large reports that are 100's of pages long. Does anyone already know how to do this? Thanks Jeremy

See my post above. The system caches by just the SQL query alone so they have to be slightly different if you want consistent results. Jeremy

I've solved my problem but I would class this as a bug. The two input controls run exactly the same SQL query even though they are on different reports pointing to different databases. So the server is caching results based on the SQL query alone and respecting nothing else. I altered the two queries so they are now slightly differenty and now they work fine. The system should cache queries based on the query and the data source they point to otherwise I would never have come across this problem so that's why I class it as a bug. Jeremy

Hi, I have a problem with single select query input controls that seems to be caching the same data between two reports. The reports both use an input control with the same prompt text ('Select Client') but that is all that is the same between them. Everything else is different including parameters, ID's etc. Once you go into one report then the data the query returns is all you now get when you go into the other report. I've disbaled modrian cahcing but to no effect. Only thing that seems to clear the cahce data is by logging out and in again which isn't practicle. Any help would be appreciated. Thanks Jeremy