[looking to migrate existing .rdf files into jasper reports]

similar question...  https://community.jaspersoft.com/questions/1072741/migrate-oracle-reports-jasper-reports

[Migrate from Oracle reports to Jasper reports]

https://www.jaspersoft.com/resource/oracle-reports-tibco-jasperreports-dummies

[Does JasperReports Server support TomCat 9.0.22 ?]

https://www.jaspersoft.com/supported-platforms

[Version 6.0 Documentation release]

The version 6 documentation will be posted to the community site shortly.

[Jaspersoft AWS EC2 TCP/IP CONNECTION ISSUE]

If the server is reachable from AWS, there should not be a problem. If it is behind a firewall that your AWS account does not have the ability to get through via a VPC, then it won't be able to connect. You could try pinging the DB server from your AWS server or connecting from the command line to verify that it is reachable. It may also be that you are using a domain name for the server that AWS can not find and you may need to try using the IP address instead.

[Community edition? v5.6.0 or v5.5.0]

Sorry, I see what you were seeing...It was just labeled wrong.  I fixed it.  the 5.6 that you saw should have been labeled as a community edition as well.

[Unable to render a report using visualize.js in JSFIDDLE]

also see: http://community.jaspersoft.com/wiki/visualizejs-troubleshooting

[Unable to render a report using visualize.js in JSFIDDLE]

Try using 127.0.0.1 instead of localhost

[Unable to render a report using visualize.js in JSFIDDLE]

are you seeing any errors in the server logs?

[Do not work the ireport.]

I highly recommend using Jaspersoft studio instead (and java 1.7) - iReport is being phased out.  

As far as licensing, in general if you are only using Jaspersoft Studio to develop reports and Jasper Reports Library in your application, you will not need a commercial license.  If you are planning to use JasperReports Server in a commercial application, then you would need a commercial license.  It is best to consult your legal department to review the appropriate licenses in light of your planned usage.

[Report export containing more than 255 columns]

Could be a page size issue...if you are designing a report, the size of the overall report width is defined like a page size.  If the columns are 50 pixels and the report is 1200 pixels, your report could be running off the side of the page.

[user, role and permission]

Make sure that the role has execute permissions on all of the resources used by the report.  For visibility to the report, make sure that they have read access to all of the subdirectories too.  See if that works.

[Jasper community is not filtering Spam messages]

Thanks...we are putting additional tools in place. We have been busy getting our release posted, etc. and will have this issue under control very soon.

[Text Fileld in TITLE]

What is the error you are getting?  Does the field referenced within it exist and is it populated by your main query?

[AWS and Jaspersoft Reporting and Analytics for AWS (Hourly)]

When you go through the Amazon Marketplace page, you should be given a set of instance sizes to choose from.  You can see the list and associated pricing on this page: https://aws.amazon.com/marketplace/pp/B00B527JQ0/ref=jaspersoft_ptnr_aws_web

Additional information on getting started can be found here: http://community.jaspersoft.com/jaspersoft-aws

[The item value is too long. The maximum length is 30 characters.]

If the values are stored in the database already, you might consider using a query based input control. Aside from that you would be likely looking at increasing the size of some DB columns and trying to modify the form validation.

[Converting Some Reports To PDF Takes A Long Time]

Assuming that it is not just a giant report and it will occassionally return fast and sometimes slow - When it happens, you may want to check the memory utilization on your server.  It is likely that you are running low on memory.  Systems can slow down when they start utilizing the swap space.  This could be caused by other people running alot of concurrent reports combined with reports running on a schedule, etc.  Running your server with plenty of memory and tuning your garbage collection, etc. (Some of the recommended parameters are found in the installation guide) can improve the performance of your reports quite a bit.

[Migration from Trial to Licensed Jaspersoft Studio Pro]

Absolutely...going from the trial of the commercial edition to a fully licensed version is a simple matter of putting a license key in place.

[Jasper Reports Server 5.5.0 versus 5.5.0a]

5.5.0a is simply a repackaging of 5.5.0.  If you are already running 5.5.0, there is no need to change...however if you are installing new, 5.5.0a is the current packaging of the 5.5.0 release.

[Null pointer exceptions accessing jasperserver 5.5.0 login page]

Your issues are very likely caused by a conflict in Glassfish 4.  Glassfish is not certified for the community edition and only for versions 2.1, 3.0, and 3.1.2 for the commercial edition.  http://www.jaspersoft.com/sites/default/files/Jaspersoft%20Platform%20Support%20V5.5.pdf

[Jaspersoft AWS EC2 TCP/IP CONNECTION ISSUE]

It is likely that your DB is not accepting connections from the AWS instance.  If your DB is also on AWS you will need to make sure that it is in the same security group, that the security group has the appropriate permissions on the port you are trying to connect to, etc.  

I hope this helps

[unable to run the report in Jasper Server]

Is it possible that you are looking at the wrong query?  It seems to be complaining about the query for the "Comparison Graph."  Potentially this is a query that is generated from a subreport or a chart that you added separate from the main report query.  You might try turning the logging up on the server or even try catching the query in the DB to see what the actual query is.  It is definitely a problem with the query that is getting sent to the DB.

Poking around the internet a bit, I found that this has been seen and the response was:

I got this error when I was using PostgreSQL to query an Amazon Redshift database. To fix it, I had to change the RANK function to this Redshift-specific function:

SUM (1) OVER ( PARTITION BY field1 ORDER BY field2 ROWS UNBOUNDED PRECEDING)

Another item that I found that shows why this might happen is this:

In the result, the database returns four records. If we want to get only one entry for every name, we can use DISTINCT:

 SELECT DISTINCT name FROM customer INTERSECT SELECT DISTINCT name FROM sales;

 

In the example, we have to use DISTINCT in both SELECT statements; otherwise, an error is displayed:

SELECT DISTINCT name FROM customer INTERSECT SELECT name FROM sales

ERROR: get_sortgroupclause_tle: ORDER/GROUP BY expression not found in targetlist

 

[Will jasper reamins same as it now as TIBCO aquired it ?]

Sorry about that. Our engineers have been very busy finalizing our next release...when that happens, their ability to focus on answering questions for our community, etc. tapers off a bit.

[Will jasper reamins same as it now as TIBCO aquired it ?]

Our products, services, support, and commitment to our community and commercial open source, subscription software will remain unchanged.  We will be a product group within Tibco, operating as the same team with the same focus on our customers/community and their needs.

[Is Jasper affected by Heartbleed bug (http://heartbleed.com/)?]

JasperReports Server does not actually ship with OpenSSL.  It would be library that is on the actual server shipped within the operating system (not within JasperReports Server).  If you have OpenSSL installed on your server, you should be able to do a simple update to it to ensure that you are not vulnerable.  The following has some information on how to run the update on various operating systems.  https://www.digitalocean.com/community/articles/how-to-protect-your-server-against-the-heartbleed-openssl-vulnerability

If your concern is not about the product, but instead about our websites (jaspersoft.com, community.jaspersoft.com, etc), we updated our OpenSSL version very quickly, within the first day of when heartbleed was announced.  We do not feel that any user information has been corrupted, however we recommend that you change your passwords just as recommended by most sites base on this issue.   Regularly changing your passwords is always a good practice to improve security.