Null pointer exception on AWS data source from Jaspersoft Studio 6.0.1.final and 6.0.3.final
Posted on April 9, 2015 at 3:41pm
Connecting Studio to Jaspersoft Reports and Analytics (Jaspersoft-pro) for AWS 6.0.1.
Have created and tested and used an AWS RDS data source via the JRS web ui. Also did the same for a JDBC based data source to MSSQLServer. Everything works.
However, from Jaspersoft Studio, the AWS RDS data source is shown in the repository, but cannot be manipulated. The follow NPE occurs. The MSSQLServer one is fine in studio.
java.lang.NullPointerException
at org.eclipse.core.databinding.beans.PojoObservables.observeValue(PojoObservables.java:71)
at org.eclipse.core.databinding.beans.PojoObservables.observeValue(PojoObservables.java:53)
at com.jaspersoft.studio.server.wizard.resource.page.datasource.DatasourceAWSPageContent.createContent(DatasourceAWSPageContent.java:167)
at com.jaspersoft.studio.server.wizard.resource.EditResourcePage.createControl(EditResourcePage.java:54)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at com.jaspersoft.studio.server.action.resource.PropertiesAction.run(PropertiesAction.java:71)
at com.jaspersoft.studio.server.ServerProvider.doubleClick(ServerProvider.java:287)
at com.jaspersoft.studio.repository.RepositoryView$2$1.run(RepositoryView.java:135)
Joined: Jan 26 2015 - 11:33am
Last seen: 7 years 11 months ago
Posted on April 15, 2015 at 3:41pm
The issue root cause was from a noob lack of understanding: It was assumed that the datasources proxied through JRS. So no datasource defined on the server would work for a typical deployment configuration where the server is in AWS and the datasources are in AWS. Though the MSSQLServer datasource was inspectable in Studio (either community or pro), the AWS datasource was not, and the NPE was distracting. The AWS datasource should be inspectable even if it cannot be used locally due to firewalls and AWS IAM security.
The ultimate solution is to not expect to use datasources locally in an AWS deployment configuration. The report designer should instead rely on a domain that was previously created. Domains are working fine for both MSSQLServer and AWS RDS datasources.
Joined: Jan 26 2015 - 11:33am
Last seen: 7 years 11 months ago
Observed that 6.0.1.final is out of date and attempted to upgrade to 6.0.3 via 6.0.1's updater which apparently failed and destroyed the install of 6.0.1. Will re-install from scratch.
Successfully installed 6.0.3 of studio which is not interoperating with 6.0.1 of the server on refreshing the repository tree.
The above error is because the aws instance shutdown and our http proxy returned an unexpected http response when studio 6.0.3 was connecting.
Studio 6.0.3 still shows the NPE on inspecting an AWS datasource. Both it and the server we restarted and the NPE verified. Guessing this becomes a bug?
I will look further into this but the AWS datasources are not understood by Jaspersoft Studio since JasperServer uses the AWS IAM role to connect and view those RDS connections and since Studio is installed locally you will need to have a tunnel to your RDS instance or have the RDS Security Groups enabled to allow access from your computer's IP
Are you using Jaspersoft Studio Pro? You know that since you are an Jaspersoft for AWS customer you can download it form the support portal if you register with your AWS account ID check here: http://www.jaspersoft.com/aws_signup/ the link is also in the home page of your AWS instance.
http://community.jaspersoft.com/jaspersoft-aws