Webspeed returns 200 HTTP response when broker is unavailabl

Posted by chrisrichardson on 20-Nov-2014 09:30

I have created some custom error messages for when there is an issue on the WebSpeed broker - http://knowledgebase.progress.com/articles/Article/P125848.  This works fine.  However if the broker is down or unavailable the Webspeed messenger returns the standard error message as follows:

WebSpeed error from messenger process (6019)

Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -66

It also returns a HTTP response of 200 (OK).

Does anyone know if the messenger be amended to return a different HTTP response (e.g. 500), and also can the content be amended?

OE 10.2B.  Webspeed messenger on w2008 IIS 7.  Webspeed brokers are on Solaris.

Cheers!

All Replies

Posted by Fabio Anijs on 25-Nov-2014 04:52

Hi Chris,

One thing you need to understand is, whenever you see the yellow messenger screen, the HTTP response is always 200 (OK).

This means that the IIS Web Server correctly executed the messenger.

It's the messenger's communication with the (name server and/or) Webspeed broker which may have issues, which is outside of the Web Server's scope.

Secondly, the article that you mentioned explains how to modify server side messages.

Not messages coming from the Webspeed messenger.

Messenger errors can be modified using the WebSpeed Error Message Customization Utility,

as explained in following articles:

knowledgebase.progress.com/.../000024679

knowledgebase.progress.com/.../P11509

As for the message itself, you can change both the 6019 and 5804 messages using this tool.

Hope this helps.

This thread is closed