|
|
|
Error: 500006: ... Reason: 200018:The application could not connect to the Runtime Service.
Technical Note USA12080
Created 21-Apr-2006
Applies To
Synapta Services Builder for 3270 & 5250
Symptoms
Error: "500006: Configuration from local file C:\Documents and Settings\Administrator\cfg\TaskConfigurations.xml failedConfiguration - serverAddress=localhost
Reason:
200018:The application could not connect to the Runtime Service."
Error occurs intermittently
Error typically occurs when the Runtime Service and Client application are installed on the same machine, and the Runtime Service is under heavy load (potentially with over 50 simultaneous Task requests). And while a majority of the Tasks requests succeed, a small subset of the Task requests fail with the error message above (500006 Error).
Fix
Caveat: This solution applies only if the reported error message (500006 Error) is intermittent. If the issue is not intermittent (that is, if the issue occurs with each Task execution), then this solution will be of no use.The solution essentially increases the queue size for the socket that the Runtime Service listens on for Task requests. This is also known as increasing the socket backlog.
Assuming the Operating System is Microsoft Windows NT or 2000 server, the maximum value for a socket's backlog is 200. (The default used by Synapta is 50.)
Steps to resolve:
1. In a text editor, open the file: {Synapta Install Dir}\EAI\ScreenConnectors\screen.properties
2. Add the following property/value pair: server.backlog=200
3. Save and close the screen.properties file
4. Stop and Start the Runtime Service for Screens
