How do I resolve "Network Communication Error"?

[Saradhi.Potharaju]

How do I resolve "Network Communication Error" in the Controller UI?

Table of Contents

Syptoms

Diagnosis

Solution

Symptoms

The following "Network Communication Error" appears in the Controller UI:

Diagnosis

Error message in <controller_home>/logs/server.log:

[INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.l ogging|_ThreadID=58;_ThreadName=Thread-5;|[BlazeDS] 05/24/2017 16:07:50.527 [ERROR] [Endpoint.General] Unexpected error encountered in Message Broker servlet 
flex.messaging.security.SecurityException: Secure endpoint '/messagebroker/amfsecure' must be contacted via a secure protocol. 
at flex.messaging.endpoints.AbstractEndpoint.validateRequestProtocol(AbstractEndpoint.java:1368) 
at flex.messaging.endpoints.AbstractEndpoint.service(AbstractEndpoint.java:935) 
at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:312) 
at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:373) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770) 
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343 ) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) 
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:89) 
at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119) 
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133) 
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130) 
at com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203) 
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter[INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.l ogging|_ThreadID=58;_ThreadName=Thread-5;|[BlazeDS] [ERROR] [Endpoint.General] Unexpected error encountered in Message Broker servlet 
flex.messaging.security.SecurityException: Secure endpoint '/messagebroker/amfsecure' must be contacted via a secure protocol. 
at flex.messaging.endpoints.AbstractEndpoint.validateRequestProtocol(AbstractEndpoint.java:1368) 
at flex.messaging.endpoints.AbstractEndpoint.service(AbstractEndpoint.java:935) 
at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:312) 
at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:373) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770) 
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343 ) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) 
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:89) 
at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119) 
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133) 
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130) 
at com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203) 
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256 ) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) 
at com.singularity.ee.controller.servlet.CsrfFilter.doFilter(CsrfFilter.java:84) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256 ) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217) 
at com.singularity.ee.controller.servlet.RequestOriginMarkingFilter.doFilter(RequestOriginMarkingFi lter.java:26)

Solution

This issue occurs when an SSL-terminating proxy is redirecting requests to the Controller and the Controller is not configured to handle these requests.

To resolve this issue, follow the steps int the documentation under "Configure the Controller for SSL Termination at the Proxy."