![]() ![]()
Is there a way to read bytes instead of strings so this kind of thing can be ignored in my code?Īlso, if I use socket. hi, I've been using elinks for quite some time now without major problems, but after an update to this version: CUT ELinks 0.11.7 (built on 17:03:57) Features: Standard, IPv6, gzip, bzip2, Periodic Saving, Timer, Cascading Style Sheets, Protocol (File, FTP, HTTP, URI rewrite, User protocols), SSL (OpenSSL), MIME (Option system, Mailcap, Mimetypes files), LED indicators. ELINKS ERROR READING FROM SOCKET CODEThe value being read when this error is thrown: 1 data is apparently in codepage cp437, and I don’t really care about this string, but I am unable to ignore this line as the entire code collapses here. Press the Enter key, and select Option 3 from the menu. Step 1: On the operating system command line, type the following: NETSTAT. The first thing we want to determine is if the server is running. :739: in method 'run'įunnily enough it was not throwing this error yesterday from the same device but is throwing the error today… Not sure if it is a code change I made or the value changed on the device today (could be some date stamp related bytes). I will also assume the TCP/IP interface on the Power Systems is active. How Does It Work Typically, an FTP server runs on a specific machine and has a socket set to a specific port number. A socket is bound to a port number that the TCP layer can identify the application that data is destined to be sent. :9: in function 'wrapped_coroutine_resume' A socket is defined as one endpoint of a two-way communication link between two programs running on the network. The error being thrown: Lua: deserialize error: invalid value: byte array, expected a string The code: local s, status, partial = tcp:receive() Therefore you would need to test whether the database is still connected when you encounter one. But there is still the problem that you can just trap STOP conditions but you never know what caused it. But in order to implement this you would need to change the application and introduce a consistent error handling ( trapping STOP conditions ) in all your programs. If the database is connected after the session has been started in a dedicated procedure then there is something you might do: You can trap STOP conditions and handle them so that you don't fall back that the first procedure in the session is re-run. When they are connected at start up of the application and the first procedure in the session already references database object ( which I've seen to be very common ) then you are hosed. Now, it depends on how the databases are connected. I’m afraid I have little experience of OpenEdge, the Case Management system is supported by the company who develop it, but they have been unable to suggest anything other than fix the underlying problem, but that could take time as myself and two support companies are at a bit of loss to explain the drop outs.Īny suggestions would be much appreciated.ĪFAIK when that happens it is a STOP condition for the client session - which means it re-runs the first procedure in the session. We use the OpenEdge graphical client 10.2B and I was wondering is there anything we can do to improve resilience, so rather than a crash the client just reconnects to its database session when the network comes back. What happens is this PC’s once or twice a day momentarily lose their connection to the network, this causes no problems for Outlook, file shares etc as they automatically recover but it causes havoc with our Case Management system and its Progress dB, our users are bombed out with the following error message…Įrror reading socket, ret=10053, errno=2. ELINKS ERROR READING FROM SOCKET SOFTWAREWe have a slight network problem at the moment which we are trying to resolve, it could be a PC software problem, perhaps our AV/Firewall software or a physical network issues, but I’m confident we will tack it down eventually. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |