Jump to content
We've recently updated our Privacy Statement, available here ×

Michael Bielkiewicz

Jaspersoft Staff
  • Posts

    104
  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Posts posted by Michael Bielkiewicz

  1. There are several ways to attempt the upgrade. Our docs present one way. What I usually recommend is to install the new server (9.0) on it's own, then export ALL from the old server (either via command line or the UI), then import that export into your new 9.0 server. With no customizations, this should work ok. If your test worked and you've tested all your reports and resources, you should be fine to continue down that route as well. Good luck!

    -Mike

    • Like 1
  2. On 11/28/2023 at 4:09 PM, rturnquist said:

    Mike - Thanks for the tip about posting it to the Tracker feature. I am able to see previously-reported issues with Jaspersoft Studio, but I don't see a way for me to post something new - and yes, I'm logged in. Any help would be appreciated. In the meantime, I'll try the ladybug method. Thanks.

    Can you let me know if you now see a "Create" option at the top of the screen when on our community website? There were some issues with it not displaying for everyone, but I do see it now myself (where I didn't before).

    -Mike

  3. I've never had this problem myself, so I'm not exactly sure what the issue could be, however you used to be able to report bugs via the ladybug icon from within the application (on the toolbar). I believe that essentially posted the bug to the old community site so now that we've just moved over, I'm not sure if that still works. Please give it a try and I will ping our Studio team internally to see if someone can chime in.

    In the meantime, I do see we have our Tracker feature here on the new site - I would post this issue there as a bug with Studio and perhaps the Studio team can get to it that way.

    -Mike

  4. I've never had this problem myself, so I'm not exactly sure what the issue could be, however you used to be able to report bugs via the ladybug icon from within the application (on the toolbar). I believe that essentially posted the bug to the old community site so now that we've just moved over, I'm not sure if that still works. Please give it a try and I will ping our Studio team internally to see if someone can chime in.

     

    -Mike

  5. This is a very vague issue, to be honest. There are many things that could possibly be wrong - if Tomcat is running (you can verify this by following above instructions), and you still can't reach Jaspersoft, that means the Jaspersoft application did not startup properly or you aren't hitting the correct URL. I don't want to repeat everything from earlier in this old thread, so can you post your specific issue and include anything you see in the catalina.out log that looks like an error on startup? That's really the only way to troubleshoot this issue.

  6. While I don't have much experience running JSS on Linux, I'm thinking you can try to increase the memory allocated to Studio on startup. It could be running out of space. This is done in the "Jaspersoft Studio Professional.ini" file in the installed location. You can also try to change out the Garbage collection method identified in that file to G1GC as that's generally a bit better at keeping memory consumption issues down. See https://community.jaspersoft.com/wiki/changing-garbage-collection-g1-tibco-jasperreports-server for more details on that (same settings should work for Studio in the ini file noted above). I don't believe the Java version would be an issue, however our JRS product only supports up to Java 11 at this time...you could try an older version than the one you are currently running, but I'd try the memory/GC settings first. I hope this helps.

    -Mike

  7. It seems to me that something is wrong with your compiled JAR. I do not sign any custom JARs that I create - I would try to recompile it with various options - should be pretty plain/vanilla. Also, ensure you are compiling to the same version of Java that you have deployed on your server (i.e. if you are running JRS with Java 8, make sure your IDE is using Java 8 to build the JAR file. I hope this helps.

  8. Are you saying that in your output table, the two rows identified by "row_number = 198" should be returning on the one row? And it repeats the behavior every 99 rows? That could possibly be a bug - you are using a very old version of JRS, is there any way for you to update to a later version to at least test? You can pretty easily install the latest community version (i.e. free) to your machine with our bundled installer and test your report there.

  9. @lunchtimeres was very thorough in their response to your issue. Without the exact data that you are returning from your query, it's hard to test this issue. I would look again, in detail, at the font, size of text, size of box, etc because if the text doesn't wholly fit within the box, that could cause your issue. I've seen this happen only on export as well (since we have different code to produce exports than what you see on the page - essentially you see an HTMLExport of the report when looking in your browser, but PDFExporter, ExcelExporter, etc will be used to generate the other formats). I realize you only changed the sorting, but it could be something else changed in the schema for our reports. Are you using the same version of JSS to edit the report? If not, remember there is a compatibility setting in JSS you can set to force it to use the older code - give that a shot as well.

    -Mike

  10. David,

    I'm not sure if you're referring to a previous thread when you say you spoke too soon as I don't see prior info here. With that said, if you are seeing data in Studio but not once you publish the report to the server, the first thing I would check is the data source. Make sure the data adapter definition in Studio is the same (or what you'd expect) from the Data Source that the report is using on JRS. This can be checked by editing the published report on JRS and checking its Data Source tab. Then, of course, you can check the Data Source definition wherever it's located in JRS to ensure it's pointing the the correct DB. Since we don't have access to your database, it's hard to verify this information. I hope this helps.

    -Mike

×
×
  • Create New...