bfundak

Veaceslav, Do you want the stack trace? The error I get is the one I have listed in my post. It throws an exception and then states: Reason: Parameter "REPORT_PARAMETERS_MAP" does not exist. I looked at the source code for the latest version of JasperReports/JasperServer, and this is due to code in the JRAbstractQueryExecuter. If the code can't find the parameter in question, it throws this error. But how can I create the parameter on the report if I can't connect to the datasource? I tried to create a REPORT_PARAMETERS_MAP reference on the report, but that did not work. Brandt

So I managed to connect to my data source, but when I actually attempt to use it I get the following error: Parameter "REPORT_PARAMETERS_MAP" does not exist. Does anyone know what's going on here? I tried to search for a solution, but I'm not finding anything. Any help is greatly appreciated. Brandt

It turns out I was not specifying the jar in the data adapter wizard. That problem solved, now for my next one...

Hopefully someone can help me here, because I am not certain what I am doing wrong. I have created a new Java project in Eclipse (I am using the JasperStudio plugin) and I have added ojdbc6.jar to my build path. When I try to create a data adapter in JasperStudio and test the connection, I get a java.lang.ClassNotFoundException:oracle.jdbc.driver.OracleDriver error. What am I missing here? Shouldn't it find the driver since it is on the build path? Any help would be greatly appreciated. Thanks. Brandt

When calling WSClient.runReport, you need to convince the ManagementService object inside of it that it is an Axis stub (which it is) and call the Stub.setTimeout method to the value you want. So do something like the code below where timeout is the amount of time you want the timeout to last in milliseconds. (minutes * 60 * 1000) The timeout is the Axis default timeout. This code will circumvent it. hth. Brandt Code:wsClient = jServer.getWSClient();ms = wsClient.getManagementService();((org.apache.axis.client.Stub)ms).setTimeout(timeout);

I checked the forum to see if this had been discussed before and I didn't see any discussion about this in the documentation, so I thought I would ask. When a report is rendered in JasperServer, does it collect all of the data from its data source and then render or does it do them simultaneously? Currently we have reports that are running 40+ minutes and my contention is that it is because of the data source--poorly written SQL in views, stored procedures and queries, lack of indices, etc. However, the person I am reporting to believes that since we query the RunTimeJobState object and it comes back as "COMPLETE" that all of the data must have been collected and it is the rendering that takes 40 minutes. Personally, I find that hard to believe. It is apparent to me that there is a disconnect between the RunTimeJobStates and what Jasper is actually doing. But if I knew what Jasper was doing during the rendering process, it would be easier for me to propose a better solution. Thanks for any enlightnment you all can give me. Brandt

Sherman, Thanks so much for this information and for the link to the Trigger object. This is exactly what we were looking for. Brandt

I've searched extensively trying to find out more about the RuntimeJobState object in the API, but I still have questions. If anyone can enlighten me, I'd really appreciate it. I am currently writing a servlet that would rely on knowing the job state to let another system know if a report had been generated or not. I have noted that I can get RuntimeJobState from the JobSummary object. Does the RuntimeJobState change in the JobSummary if the state changes, or is the RuntimeJobState going to be an indication of the moment in time that the JobSummary object is instantiated? Potentially, we would like to periodically like to check the status of a Job, since we have some larger reports that are being generated and eventually another system is going to attempt to access the output. My thought was to use the RuntimeJobState to maintain and break the checking loop. If it is possible to use RuntimeJobState in such a manner, I have a couple of questions about the states themselves: If RuntimeJobState == RuntimeJobState.COMPLETE, does that mean that the report has been rendered? The way we currently check, we query the MySQL DB to find out if the DB thinks the job is done. The problem is that even though the DB thinks it is done, Jasper is usually still rendering the report, so we have to constantly check if the file has actually appeared in the output repository. I would like to just base it off of the RuntimeJobState if possible. Also, I think I understand what all of the RuntimeJobStates are, with the exception of RuntimeJobState.NORMAL. What is this state indicative of? Is it a queued job or something else? I have also noted that there is a RuntimeJobState.PAUSED. I checked the API (albeit briefly) looking to see if there was a way to pause a job through the API and didn't immediately notice anything but this is functionality that I would be very interested in for this project. I am sorry if these questions are totally daft, but I am new to the Jasper environment and have only been programming in Java for a few years now. I'm being asked to leap tall buildings in a single bound, but am not sure I can do it. Thanks for any help you can give. Brandt