Jasper Repo explorer connection to JRS server failing

Posted on March 16, 2020 at 5:30am

Hi, I am using JRS7.5 Enterprise version on evaluation licence. JRS running on AWS (deployed using Jasper AWS AMI single instance using default cloud formation template). JRS server working fine. I can access through browser & and do all operations as admin jrsadmin.Can generate reports etc. But not able to connecto server through studio.

JRS professional studio /Repository explorer/Servers : connection is failing with 404 error (see attached file for error in details).

However 'open in browser' option works well with same config.

URL- http://ec2-xx-xxx-xxx-xx.compute-1.amazonaws.com/jasperserver-pro/ 
 
user: jasperadmin
 
Error msg: 
 
 
 
AxisFault
 
 faultCode: {http://xml.apache.org/axis/}HTTP
 
 faultSubcode: 
 
 faultString: (404)
 
 faultActor: 
 
 faultNode: 
 
 faultDetail: 
 
            {}:return code:  404
 
 
 
 
 
            {http://xml.apache.org/axis/}HttpErrorCode:404
 
 
 
(404)
 
            at com.jaspersoft.ireport.jasperserver.ws.http.JSSCommonsHTTPSender$3.handleResponse(JSSCommonsHTTPSender.java:245)
 
            at com.jaspersoft.ireport.jasperserver.ws.http.JSSCommonsHTTPSender$3.handleResponse(JSSCommonsHTTPSender.java:1)
 
            at org.apache.http.client.fluent.Response.handleResponse(Response.java:90)
 
            at com.jaspersoft.ireport.jasperserver.ws.http.JSSCommonsHTTPSender.invoke(JSSCommonsHTTPSender.java:221)
 
            at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
 
            at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
 
            at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
 
            at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
 
            at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
 
            at org.apache.axis.client.Call.invoke(Call.java:2767)
 
            at org.apache.axis.client.Call.invoke(Call.java:2443)
 
            at org.apache.axis.client.Call.invoke(Call.java:2366)
 
            at org.apache.axis.client.Call.invoke(Call.java:1812)
 
            at com.jaspersoft.ireport.jasperserver.ws.RepositorySoapBindingStub.list(RepositorySoapBindingStub.java:328)
 
            at com.jaspersoft.ireport.jasperserver.ws.WSClient.getVersion(WSClient.java:150)
 
            at com.jaspersoft.studio.server.protocol.soap.SoapConnection.getServerInfo(SoapConnection.java:104)
 
            at com.jaspersoft.studio.server.protocol.soap.SoapConnection.connect(SoapConnection.java:145)
 
            at com.jaspersoft.studio.server.protocol.ProxyConnection.connect(ProxyConnection.java:102)
 
            at com.jaspersoft.studio.server.WSClientHelper.checkConnection(WSClientHelper.java:92)
 
            at com.jaspersoft.studio.server.wizard.ServerProfileWizard.connect(ServerProfileWizard.java:94)
 
            at com.jaspersoft.studio.server.wizard.ServerProfileWizard.access$1(ServerProfileWizard.java:89)
 
            at com.jaspersoft.studio.server.wizard.ServerProfileWizard$2.run(ServerProfileWizard.java:68)
 
            at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

pls see attached file for more config information.

I have disabled the heartbeat popup on property file already and checked access to EC2 instance via AWS SG on port 80 is open. Browser access works fine.

any help appreciated. thanks

Attachments: