Problems with opening jrxml files after upgrading from 6.3 to 6.4 with apache httpd and mod_jk

0

Hi

I have the problem, whenever i want to open a jrxml file with jaspersoft studio 6.4.0 that i get the following error:

java.lang.NullPointerException
    at java.lang.Class.isAssignableFrom(Native Method)
    at org.glassfish.jersey.message.internal.MessageBodyFactory.isCompatible(MessageBodyFactory.java:699)
    at org.glassfish.jersey.message.internal.MessageBodyFactory._getMessageBodyReader(MessageBodyFactory.java:736)
    at org.glassfish.jersey.message.internal.MessageBodyFactory.getMessageBodyReader(MessageBodyFactory.java:664)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:215)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154)
    at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124)
    at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:851)
    at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:783)
    at org.glassfish.jersey.client.ClientResponse.readEntity(ClientResponse.java:326)
    at org.glassfish.jersey.client.InboundJaxrsResponse$1.call(InboundJaxrsResponse.java:111)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
    at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:399)
    at org.glassfish.jersey.client.InboundJaxrsResponse.readEntity(InboundJaxrsResponse.java:108)
    at com.jaspersoft.studio.server.protocol.restv2.ARestV2ConnectionJersey.toObj(ARestV2ConnectionJersey.java:45)
    at com.jaspersoft.studio.server.protocol.restv2.RestV2ConnectionJersey.setMainReportFlag(RestV2ConnectionJersey.java:421)
    at com.jaspersoft.studio.server.protocol.restv2.RestV2ConnectionJersey.get(RestV2ConnectionJersey.java:397)
    at com.jaspersoft.studio.server.protocol.ProxyConnection.get(ProxyConnection.java:172)
    at com.jaspersoft.studio.server.WSClientHelper.getResource(WSClientHelper.java:241)
    at com.jaspersoft.studio.server.WSClientHelper.getResource(WSClientHelper.java:226)
    at com.jaspersoft.studio.server.action.resource.OpenInEditorAction.dorun(OpenInEditorAction.java:126)
    at com.jaspersoft.studio.server.action.resource.OpenInEditorAction$1.runInWorkspace(OpenInEditorAction.java:103)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

I have updatet my jaspersoft server from 6.3.0 to 6.4.0, it worked perfectly fine before the upgrade.

When I connect directly on the tomcat server it without SSL it works.
When i connect directly on the tomcat server with SSL it works also.
But when I try to conect via the Apache Webservice and mod_jk it does not work and I get the error i posted.

Anyone knows why this error happens?

I'm using those:

Windows Server 2016
Apache Tomcat 8.5.11
Apache/2.4.25 (Win64) OpenSSL/1.0.2k mod_jk/1.2.42
Java 1.8.0_131
Jasperserver Professional 6.4.0 with hotfix_JRSPro6.4.0_cumulative_20171013_0301

thomas.vollenweider's picture
Joined: Sep 18 2015 - 2:58am
Last seen: 7 months 3 weeks ago

2 Answers:

0

Hi, 
I see you are mentioning a version of JRS professional. I suggest you open a ticket through the official support channel.
It might be necessary to investigate further on how to possibly reproduce the error since you mentioned it worked fine with/without SSL, but not with Apache Webservice and mod_jk. In this way the issue will be addressed in a proper way.

Regards,
Massimo.

mrabbi's picture
11528
Joined: Oct 31 2011 - 9:20am
Last seen: 2 weeks 10 hours ago
0

Hello Massimo

 

Thanks for your Answer.
I thought it would not hurt to ask if someone hat this problem before and it's not Tibcos fault but ours (configuration, etc).
I will open a ticket next week and then see how the problem can be solved.

Best Regards

Thomas

thomas.vollenweider's picture
Joined: Sep 18 2015 - 2:58am
Last seen: 7 months 3 weeks ago
Feedback
randomness