sdemelis
-
Posts
18 -
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
Everything posted by sdemelis
-
As requested, here's the code of the jndi class: public static Connection getJNDIConnection(String db) throws Exception { String connString =""; InitialContext ctx = new InitialContext(); connString = "java:comp/env/jdbc/".concat(db); DataSource ds = (DataSource)ctx.lookup(connString); return ds.getConnection(); } The input string is the name of the jndi connection defined in Tomcat.
-
A workaround is to use a jndi connection instead of the jdbc connection for the subreport. Maybe it's not "elegant" but at least the connection is managed by an application server and it will be closed based on the parameters defined in the jndi connection.
-
Hi icecreaming, thanks for your time :) If someone else has some clue about this problem, here some more info: the server version is 4.0 and the chart is in a subreport that contains only this chart, nothing else. Its datasource is a subdataset of a javabean that is the datasource for the main report. Also the main report contains 16 subreports (yes, it's full of data...), but the total number of pages for the entire report is about 7 or 8.
-
If the chart height is less than 700, I have the same temporary files as you. If it's 700 or more, the server creates a different type of temporary files, something like virt9195358_210345_23410_1291982944. Post Edited by sdemelis at 04/23/2012 04:05
-
Hello, thanks for your answer, but my problem is not the disk quota error. I could increase the quota but at the next execution I will reach the new limit. The report generates more than 100000 temporary files for each execution: my problem is the number of temporary files generated. I don't understand why changing the chart height from 650 to 700 causes this problem. Post Edited by sdemelis at 04/21/2012 12:35
-
Hello, I have a problem with a chart that seems too big for my server. I increased the size of the chart putting the Height property=700. When I executed the report, the server started to create temporary files and it stopped only when it reached the maximum number of files in the folder (returning the error " Disk quota exceeded"). I decresead the Height to 650 and the report works fine. Do you have any suggestion to fix the problem? thanks
-
I found how to do it. I posted some comment in this post http://jasperforge.org/plugins/espforum/view.php?group_id=83&forumid=101&topicid=96461
-
I found the solution. It's quite simple.....if you know what to do... I'll post it, maybe it could help someone else without loosing 2 days: 1- I configured 2 JNDI connections on my JasperServer/Tomcat 2- I created a simple java class where I access the JNDI pool and I deployed it on Jasper Server 3- In the subreport, instead of passing as connection expression the standard string java.sql.DriverManager.getConnection ("jdbc:mysql://mydb", "user","pwd") I used my custom class myClass.myJNDIconnection("selectedDB") Now when I execute the report, the connections are closed after 4 or 5 seconds.
-
Hello, is it possible to use a JNDI connection with a subreport? I need to use connections different from the main report and if I use a standard JDBC connection for the subreport, I have too many open connection on mySql. thanks
-
Hi mgeise, thanks for your answer. Once the JNDI datasource is created, how can I access it from a subreport that uses a different database/connection from the main report?
-
Hello, my report contains a lot of subreports and I have a problem with the number of open connections managed by subreports. The main report uses a javabean datasource, shared by some subreport, but there are a lot of subreports that use different connections to 2 differents DB. I used the connection expression parameter to define the connection for my subreports, but in this way I don't have any control on the connection and they don't use any connection pool managed by Jasper Server. If I run the report x times, I receive a "too many connection" error from mySql because the subreports connections are still open. Any suggestion how to reduce the number of connections or to reduce the time they are open? thanks
-
Problems making reports with subreports working
sdemelis replied to danielferreira's topic in Products
Open the main report you uploaded, go in the Subreport properties and verify that the subreport expression is "repo:report_name.jrxml". Sometimes when you upload it in the server, it keeps the local path "c:\...". -
....found it....I didn't put anything in the closeconnection method :)
-
Hello yamrx135, you can use the links posted by srl_user as reference. srl_user , I followed the same examples you found, so I know that they are not so clear, but finally worked :) What error do you have when you try to use your bean? Post Edited by sdemelis at 11/10/2011 14:03
-
Hello, I'm using a custom data source and it works fine the first time jasper server creates the report: if I change some input control and generate a new report, it keeps in memory the previous dataset. As result, I have 2 pages instead of 1, the first page with the old dataset and the second page with the new dataset. If I try 10 times, I have 10 pages, one for each dataset. Any suggestion about how to '"clean" the previous dataset? Thanks
-
Nvm....I found the answer in another post.
-
Hi proaugust, could you explain me how did you read the input controls from the javabean datasource? thanks
-
Hello, I created my javabean datasource and it works with both iReport and Jasper Server. Now I'm trying to read report parameters from the javabean object, to use them to filter data. My problem is: how to pass input controls/report parameters to the javabean object? I looked everywhere but I didn't find any hint. thanks
