Server returned FAILURE with no error message performing operation 'messagingSend'.

[senordhuff]

Hi,

We are checking out the new smartclient 10.0. We are now seeing this message when we expose the dev console which wasn't happening in 9.1. I'm using Google Chrome.

"Server returned FAILURE with no error message performing operation 'messagingSend'."

Is this related to the realtime messaging module?

[Isomorphic]

Yes, that message comes from the Messaging module and could be caused by, for example, not installing the MessagingServlet at all, or having it immediately crash for some reason. We'd need more details to comment further.

[senordhuff]

Thanks, it appears to be the opposite problem here. We choose to not load the Real-time messaing module client-side in some cases. And, that was causing the dev console to complain if the Messaging Servlet was running. Is it now necessary to load the messaging module client-side at all times? This hasn't been an issue prior to smartclient 10.0.

[Isomorphic]

When you open the Developer Console we will check for the presence of the Messaging servlet as part of the new Remote Debugging feature. However, you shouldn't see an error message even if MessagingServlet absent - it just disables the feature.

Can you be specific about exactly where you're seeing the error message?

[senordhuff]

The Messaging Servlet is not absent. We are just not normally loading the realtimemessaging modules client-side. When I add the realtimemessaing module client-side , this error goes away. It occurs the first time we open up the dev console.

[Isomorphic]

If by "we are just not normally loading the realtimemessaging modules client-side" you actually mean that you remove ISC_RealtimeMessaging.js from *both* the "modules" and "development" directories, the latter removal would cause this problem.

[senordhuff]

Hello, we are still seeing this error message every time we open the dev console for the firs time when using Smartclient 10.0

"Server returned FAILURE with no error message performing operation 'messagingSend'."

I've confirmed that isc_realtimemessaing.js is in both the modules and development directory and we have the messagingServlet installed and configured as follows.

Any idea what could be causing that message to show up when we open the dev console and how to resolve?

<servlet>
        <servlet-name>MessagingServlet</servlet-name>
        <servlet-class>com.isomorphic.messaging.MessagingServlet</servlet-class>
 </servlet>

    <!-- //>RealtimeMessaging -->
    <!-- Messaging uses this URL by default -->
    <servlet-mapping>
        <servlet-name>MessagingServlet</servlet-name>
        <url-pattern>/isoversion/10.0.10.15.14/isomorphic/messaging/*</url-pattern>
    </servlet-mapping>
    <!-- //<RealtimeMessaging -->

[Isomorphic]

Can you be specific about where exactly you're seeing the message?

[Isomorphic]

A little extra context to see if we can track this down:

The page containing the app will not attempt to use RealtimeMessaging for remote debugging unless you explicitly ask for remote debugging to be on using one of the methods described here:

http://www.smartclient.com/docs/10.0...emoteDebugging

If you're seeing this error logged in the Results tab of the Developer Console, the attempt must be coming from the app window. Do you have remote debugging enabled via one of the methods described in the link above?

Also, the current expectation for the Remote Debugging case is that the Messaging servlet resides at its default URL- and you've changed that in the servlet mapping.

While setting your own URL for Messaging is supported, there's no clean way to do it for the case of Remote Debugging because the RealtimeMessaging module is either loaded by the Log.html file (in the case of the Developer Console) or dynamically via FileLoader in the main app.

Finally, if the messaging endpoint is just not where we expect it to be, the server will typically return a 404 error code which we would map to a TRANSPORT_ERROR. The fact that you see a FAILURE, means something is responding at the default /isomorphic/messaging URL with a structured, SmartClient-aware error code. Can you share more of your web.xml and possibly some server logs around this?

[Isomorphic]

Just closing this out for public record - the thread went private so we could get a copy share configuration information.

This problem was ultimately traced to a bug in a custom MessageDispatcher class in the application - the code worked fine for streaming messages to the client (browser), but not if the messages originated from the client (browser) as they do in the remote debug setup.