Kbase P120646: The ASP messenger (wsasp.dll) hangs intermittently
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/25/2010 |
|
Status: Unverified
SYMPTOM(s):
The ASP messenger (wsasp.dll) hangs intermittently
Needs to restart the WebSpeed broker
The web server also needs to be restarted
The WebSpeed transaction server version is 3.1D08
The WebSpeed messenger version is 3.1E04
Both components are installed on the same machine
The enhanced messenger log shows the following error:
MCCL CON-BKR Msngr: the specified service name does not exist or has a bad format. (5825): Service: "<Application Service Name>", Error 0
The messenger is set to communicate through the NameServer
The broker stay registered to the NameServer even after the http request times out
FACT(s) (Environment):
WebSpeed 3.1D
WebSpeed 3.1E
OpenEdge 10.x
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
The workaround is to set the wsasp.dll messenger to communicate directly to the WebSpeed broker. This feature is only available on WebSpeed version 3.1E or OpenEdge 10.
Here are the steps to configure the messenger to by pass the NameServer:
Using Progress Explorer:
1. Click on the + node on the messenger folder
2. Right mouse click on the WSASP messenger > choose Properties
3. On the Controlling NameServer page, uncheck the "Connect USing NameServer" check box
4. On the WebSpeed Transaction Server Location, supply the Host name or IP address (if the broker is not on the same machine), and the tcp port number > click OK to save the changes
5. Restart the IIS
If the Web server machine only have messenger installed, the Progress Explorer component will not be available. In this case, need to modify the ubroker.properties file manually.
Steps to modify the ubroker.properties file manually:
1. Open the ubroker.properties file with notepad from %DLC%\properties folder
2. Copy the following properties from the [WebSpeed.Messengers] section and paste it under the existing properties i=on the [WebSpeed.Messengers.WSASP] section:
Host=localhost
Port=3055
registerNameServer=1
3. Change the registerNameServer to 0 (zero) and specify the appropriate host name and the port number.
4. Save the changes and restart the IIS.