500 error when displaying WKT & GML

[maccraymer]

In the Details view of CRS items, the "Show WKT" & "Show GML" links that top-right of the page give an HTTP Status 500 error when selected.

[ronaldtse]

Ping @phuonghuynh can you help fix this?

[ronaldtse]

e.g.
human-readable: https://geodetic.isotc211.org/item/83f9b452-ab4b-43de-923c-e317518f036a

GML: https://geodetic.isotc211.org/item/83f9b452-ab4b-43de-923c-e317518f036a/gml
=> 500 error

Type Exception Report

Message Handler dispatch failed; nested exception is java.lang.NoClassDefFoundError: Could not initialize class net.opengis.gml32.GMLPackage

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Root Cause

java.lang.NoClassDefFoundError: Could not initialize class net.opengis.gml32.GMLPackage
	org.iso.registry.persistence.io.gml.GmlExporter.exportCrs(GmlExporter.java:145)
	org.iso.registry.client.controller.registry.RegisterItemController.viewItemAsGml(RegisterItemController.java:308)
	org.iso.registry.client.controller.registry.RegisterItemController$$FastClassBySpringCGLIB$$9bd34516.invoke(<generated>)
	org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
	org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
	org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
	org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
	org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282)
	org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
	org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
	org.iso.registry.client.controller.registry.RegisterItemController$$EnhancerBySpringCGLIB$$d8c67a7c.viewItemAsGml(<generated>)

WKT: https://geodetic.isotc211.org/item/83f9b452-ab4b-43de-923c-e317518f036a/wkt
=> 500 error

HTTP Status 500 – Internal Server Error

Type Exception Report

Message Handler dispatch failed; nested exception is java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.xtext.common.TerminalsRuntimeModule

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Root Cause

java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.xtext.common.TerminalsRuntimeModule
	org.eclipse.xtext.common.TerminalsStandaloneSetupGenerated.createInjector(TerminalsStandaloneSetupGenerated.java:40)
	org.eclipse.xtext.common.TerminalsStandaloneSetupGenerated.createInjectorAndDoEMFRegistration(TerminalsStandaloneSetupGenerated.java:34)
	org.eclipse.xtext.common.TerminalsStandaloneSetup.doSetup(TerminalsStandaloneSetup.java:11)
	de.bespire.io.wkt.WellKnownTextStandaloneSetupGenerated.createInjectorAndDoEMFRegistration(WellKnownTextStandaloneSetupGenerated.java:21)
	de.bespire.io.wkt.WellKnownTextStandaloneSetup.doSetup(WellKnownTextStandaloneSetup.java:15)
	org.iso.registry.persistence.io.wkt.WktExporter.exportCrs(WktExporter.java:104)
	org.iso.registry.client.controller.registry.RegisterItemController.viewItemAsWkt(RegisterItemController.java:282)
	org.iso.registry.client.controller.registry.RegisterItemController$$FastClassBySpringCGLIB$$9bd34516.invoke(<generated>)

[phuonghuynh]

Yep, @ronaldtse

[phuonghuynh]

Update: Checked this, fixed the WKT error, but GMT still happening. This error only happens on aws env, local is good. I still investigating the error of GMT

[phuonghuynh]

Found reason that causes 500 error in GML view, Eclipse EMF Framework have issue with Linux server (not PC distro like Ubuntu) when running with Java8

When I downgrade to previous version of Isoregistry, java7, it just works

cc @ronaldtse @florianesser

[phuonghuynh]

@maccraymer staging has been updated. Could you help to check this issue on Stating instance before deploying to Production instance.

[ronaldtse]

@phuonghuynh can you help deploy to production? I can confirm it works on Staging now. Thanks.