Issue #1 Description

During instance initialization, the PostgreSQL 14.x service doesn’t start automatically after yum update. As a result, after Tomcat service starts, JasperReports Server can not connect to its repository and the application fails to start.

Impacted products

• Jaspersoft Reporting and Analytics for AWS (BYOL)
  • CloudFormation Template - BYOL Jaspersoft Stack VPC deployment of versions 8.2.0, 9.0.0 
  • Amazon Machine Image (AMI) - AMI for versions 8.2.0, 9.0.0
• Jaspersoft Reporting and Analytics for AWS (Hourly)
  • CloudFormation Template - Jaspersoft Instance in a VPC of versions 8.2.0, 9.0.0
  • Amazon Machine Image (AMI) - AMI of versions 8.2.0, 9.0.0
• Jaspersoft for AWS with Multi-Tenancy (Hourly)
  • CloudFormation Template - Jaspersoft Multi-tenancy Instance in a VPC of versions 8.2.0, 9.0.0
  • Amazon Machine Image (AMI) - AMI of versions 8.2.0, 9.0.0

Issue resolution

Using CloudFormation Jaspersoft Reporting and Analytics version 9.0.0 

Automated fix (using CloudFormation Jaspersoft Reporting and Analytics)

The fix for this issue is already available only for CloudFormation Templates version 9.0.0.

If you do not have a JasperReports Server instance installed, the new CloudFormation template installation from AWS Marketplace automatically configures everything.

Manual fix

To fix the issue for already created 9.0.0 instance from CloudFormation Templates:

1. Download the CloudFormation Templates file from the marketplace page of your product.

2. Find the cloud formation stack.

3. From Actions, select Update → Replace Existing template → Upload template file (from step 1) → Next → Accept. 

4. Restart the JasperReports Server ec2 instance. You can find the instance name in the stack Output tab.

Using CloudFormation Jaspersoft Reporting and Analytics version 8.2.0 

CloudFormation version 8.2.0 template is publicly available. However, there are some issues that must be fixed manually before using it.

To fix the CloudFormation version 8.2.0 template manually:

1. If you have JasperReports Server version 8.2.0 already deployed using CloudFormation template, then download the template file. Else:

    a. Subscribe for version 8.2.0 template

    b. On AWS Stack, create a Stack page.

    c. Download version 8.2.0 template from the mentioned S3 bucket.

2. Open the CFT file in the text editor.

3. Navigate to Resources → JRSEC2Instance → Configure → Commands. You can see the list of commands that are used to initialize the JasperReports Server instance.

4. Edit the list and add the following command before “1-setInitialPassword”:             

 "1-restart-postgres" : {
            "command" : { "Fn::Join" : ["", ["systemctl restart postgresql"]]},
             "ignoreErrors" : "false",
                     "test" : "test ! -e /etc/jasperserver/initializationMarker.log"
              },

5. In every command, increment the step number, to have commands such as:   

"1-restart-postgres","2-setInitialPassword","3-disableAndExpireUsers","4-pullLicense","5-pullCustomizations","6-WriteInitializationMarker","7-Restart Tomcat"

6. Find the list of commands used during instance restart: 

"commands" : ["1-setInitialPassword","2-disableAndExpireUsers","3-pullLicense","4-pullCustomizations","5-WriteInitializationMarker","6- Restart Tomcat"]

7. Change the commands to:   

"commands" : ["1-restart-postgres","2-setInitialPassword","3-disableAndExpireUsers","4-pullLicense","5-pullCustomizations","6- WriteInitializationMarker", "7-Restart Tomcat"]

Automated fix using CloudFormation Jaspersoft Reporting and Analytics

If you do not have a JasperReports Server instance installed, the new CloudFormation template installation, using the template file that was fixed using the steps described in the earlier section, automatically configures everything.

Manually applying the fix

To fix the issue for already created 8.2.0 instance from CloudFormation Template:

1. Get the fixed CloudFormation version 8.2.0 template (described in the earlier section).

2. Find the cloud formation stack.

3. From Actions, select Update → Replace Existing template → Upload template file (from step 1) → Next → Accept.

4. Restart the JasperReports Server ec2 instance. You can find the instance name in the stack Output tab.

Using Amazon Machine Image (AMI)

In this case, the fix must be applied manually for both versions, 8.2.0 and 9.0.0.

1. Install JasperReports Server version 8.2.0 or 9.0.0 using AMI from AWS Marketplace or use the one that is already installed.

2. Find the /etc/jasperserver/jrs_init_marker.log file and delete it.

3. Use the following commands to restart the PostgreSQL and Tomcat services:

• PostgreSQL:

  sudo systemctl restart postgresql

• Tomcat:

  sudo systemctl restart tomcat

   

4. Restart ec2 instance. After the restart is completed, the installation script configures the instance.

Issue #2 Description

An issue with JasperReports Server clustered instances was also found because of the PostgreSQL 14 upgrade. Few JNDI connections stopped working for JasperReports Server, and there were exceptions when accessing JasperReports Server Home or Search pages.

Impacted products

• Jaspersoft Reporting and Analytics for AWS (BYOL)
  • CloudFormation Template -  Jaspersoft BYOL Cluster of version 9.0.0 
• Jaspersoft Reporting and Analytics for AWS (Hourly)
  • CloudFormation Template - JasperReports Server (Hourly) cluster of version 9.0.0
• Jaspersoft for AWS with Multi-Tenancy (Hourly)
  • CloudFormation Template - JasperReports Server MT Hourly cluster of version 9.0.0

Issue resolution

This issue is resolved by adding additional JNDI resources configuration into CloudFormation template.

Using CloudFormation Jaspersoft Reporting and Analytics version 9.0.0 

Automated fix (using CloudFormation Jaspersoft Reporting and Analytics)

The fix for this issue is already available for CloudFormation Templates version 9.0.0.
If you do not have a JasperReports Server instance installed, the new CloudFormation template installation from AWS Marketplace automatically configures everything.

Manual fix

To fix the issue for already created 9.0.0 instance from CloudFormation Templates:
1. Download the CloudFormation Templates file from the marketplace page of your product.
2. Find the cloud formation stack.
3. From Actions, select Update → Replace Existing template → Upload template file (from step 1) → Next → Accept. 
4. In the Auto Scaling group of the cluster, set Desired Capacity to zero. Wait till all the instances stop, and set it to the required size.