-- Home -- Links -- Sjon -- calendar -- Jobs to do --
-- Previous week -- This week -- Next week --
It was a generally nice day; weather wise that is. Starting off at 6h00 with a cool 7C but rising fast and going back down to 16C at around 17h30. No rain at all and lots of sun.
We had no new problems from America.
The 'socket error' problem did not occur as often as the previous day. I counted 18 instances but quite some were duplicates, that is the user gets one crash but the application reacts by automatically restarting, and crashing again. On the AS/400 that results in two crashed jobs but if you check the timing and IP addresses in the logs you can combine some logs to form such a double crash. Peter called America and they have started some kind of 'sniffer' on the network to look for potential lethal events. I guess we will get a report tomorrow or at least by next week.
And the people from Progress seem to have been kicked into action. Wilbert is back and he sent a mail to Progress containing the mail that I sent to America. Maybe that's what convinced them we need a solution.All in all I again lost some hours slogging trough joblogs and assisting Wilbert. Lovely :(
I did have time for the French problem. And it is one of those mystery problems all programmers love. Sven, from OLI had given me a profile for logging in on the French machine and ha also gave me a few item numbers and addresses. I had copied the item number wrongly but I found a good phased out item after some querying. I made a few orders and the phased out item was trapped each time. So I couldn't reproduce the problem there and I could not reproduce the problem here. Who is fooling who here? I got the manager in France on the phone and he guided me trough the process, with another phased out item and lo, it passed all the test and resulted in a logistics order. After some searching we found that there was still some stock for that item so it should pass as it did. No problem.
Just to make sure, I try to be thorough, we removed all the stock for the item. This time it should generate an error, preventing the order from being released. Only it didn't. It just passed on to logistics as if, well just like that. So we do have a problem.
Some items behave as they should, some sneak trough depending on the position they are in.Debugging remotely was out of the question so I checked and rechecked the code and I munched the data. All to no avail. As a last resort I ran the data trough a virtual computer (that is that wet grey stuff called a brain) stepping trough the lines of code on by one. I did find a problem that may cause the symptoms we are seeing. Actually it is the coincidence of two independent errors. I will correct that tomorrow an let the French test it.
And then Peter came around with two new adaptations to include in OMSI-3. I am not yet out of work.
I have been having problems with connecting to the ISP here. The problem is that they had a very good and well performing service. So many new clients got attracted causing the performance to drop. In the first four months I never got a busy signal and the line was never dropped. The last month (September) I often got dropped lines and gradually I got more and more busy signals. Every day of the last week I had to try several time to get a connection. Yesterday I tried about 10 times between 21h00 and 24h00 and I never got a connection.
So if you missed my day note, I am not getting lazy, I am just not getting a connection..I tried today about 5 times between 19h40 and 21h00 without success. Maybe I cannot post today either. I am not feeling happy about this but there is not much I can do at the moment.