Null pointer exception on AWS data source from Jaspersoft Studio 6.0.1.final and 6.0.3.final

[stuart.r.andrews]

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)

 

 

[stuart.r.andrews]

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.

java.lang.ClassNotFoundException 

 - klass: 'java/lang/ClassNotFoundException'

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  Internal Error (exceptions.cpp:424), pid=21650, tid=140486969075456

#  fatal error: ExceptionMark destructor expects no pending exceptions

#

# JRE version: Java SE Runtime Environment (7.0_67-b01) (build 1.7.0_67-b01)

# Java VM: Java HotSpot 64-Bit Server VM (24.65-b04 mixed mode linux-amd64 compressed oops)

# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# /home/randrews/TIBCOJaspersoftStudio-6.0.1.final/hs_err_pid21650.log

#

# If you would like to submit a bug report, please visit:

#   http://bugreport.sun.com/bugreport/crash.jsp

#

 

JVM terminated. Exit code=13

/home/randrews/TIBCOJaspersoftStudio-6.0.1.final//features/jre.linux.gtk.x86_64.feature_1.7.0.u71/jre/bin/java

-Xms128m

-Xmx1024m

-XX:PermSize=128M

-XX:MaxPermSize=256M

-XX:+CMSClassUnloadingEnabled

-XX:+UseConcMarkSweepGC

-Dfile.encoding=UTF-8

-Djava.net.preferIPv4Stack=true

-Dorg.eclipse.swt.browser.DefaultType=mozilla

-jar /home/randrews/TIBCOJaspersoftStudio-6.0.1.final//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar

-os linux

-ws gtk

-arch x86_64

-showsplash

-launcher /home/randrews/TIBCOJaspersoftStudio-6.0.1.final/Jaspersoft Studio

-name Jaspersoft Studio

--launcher.library /home/randrews/TIBCOJaspersoftStudio-6.0.1.final//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807/eclipse_1502.so

-startup /home/randrews/TIBCOJaspersoftStudio-6.0.1.final//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar

--launcher.overrideVmargs

-exitdata 71800d

-data @noDefault

-vm /home/randrews/TIBCOJaspersoftStudio-6.0.1.final//features/jre.linux.gtk.x86_64.feature_1.7.0.u71/jre/bin/java

-vmargs

-Xms128m

-Xmx1024m

-XX:PermSize=128M

-XX:MaxPermSize=256M

-XX:+CMSClassUnloadingEnabled

-XX:+UseConcMarkSweepGC

-Dfile.encoding=UTF-8

-Djava.net.preferIPv4Stack=true

-Dorg.eclipse.swt.browser.DefaultType=mozilla

-jar /home/randrews/TIBCOJaspersoftStudio-6.0.1.final//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar 

[stuart.r.andrews]

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.

[stuart.r.andrews]

Successfully installed 6.0.3 of studio which is not interoperating with 6.0.1 of the server on refreshing the repository tree.

AxisFault

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode: 

 faultString: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50; White spaces are required between publicId and systemId.

 faultActor: 

 faultNode: 

 faultDetail: 

{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50; White spaces are required between publicId and systemId.

at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)

...snip...

at com.jaspersoft.studio.server.ServerProvider.listServer(ServerProvider.java:385)

at com.jaspersoft.studio.server.ServerProvider.access$0(ServerProvider.java:381)

at com.jaspersoft.studio.server.ServerProvider$1.run(ServerProvider.java:328)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

 

{http://xml.apache.org/axis/}hostname:Rich-X240

 

org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50; White spaces are required between publicId and systemId.

at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)

...snip...

at com.jaspersoft.studio.server.ServerProvider$1.run(ServerProvider.java:328)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

 

Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50; White spaces are required between publicId and systemId.

at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)

...snip...

at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)

... 19 more

 

 

[stuart.r.andrews]

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?

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)

 

[marianol]

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

 

 

[stuart.r.andrews]

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.