SPA ACARS Version 1.4 Released
9 years 3 months ago #12746
by jer029
Replied by jer029 on topic SPA ACARS Version 1.4 Released
Thanks Steve,
Not sure this ever was a "pissing contest". In fact these last two program versions have been in an effort to identify and mitigate issues you've mentioned regarding FSUIPC disconnect. I had thought you mentioned another ACARS program that also identified a FSUIPC disconnect - perhaps I misunderstood.
Perhaps email or TS exchange would have been a better forum throughout this exchange, including the log sending. Although I appreciate the additional information and your assist in troubleshooting.
While it's true that the SPAACARS is the application affected according to your event log, the first issue according to your log was related to routine process request sent to FSUIPC that was not caught through the normal error handling process I followed based on the SDK:
at FSUIPC.FSUIPCConnection.Process(Byte, System.Collections.Generic.IEnumerable`1)
It's very likely the other programs are not using the .net FSUIPC library I'm using (based on the programming language there are a number of dll's that are used to interact with FSUIPC), and this error appears to be one that was not expected by the developer of that library either as it's not mentioned in the SDK, and probably would have to be handled at the dll level to prevent a .net crash, where I think all I can do is gracefully exit my program by the time it gets back to SPAACARS - and that would be too late if it's already brought .net to its knees.
But then again, I'm not programming expert - so I might be wrong on some of this. All I know is a call to FSUIPCConnection.process should not bring down .net, and that's something I'd probably have to ask Paul Hently about.
Again I might suggest you see what those FSUIPC and WideFS logs are saying too, as it might be necessary for me to have Pete Dowson (or more likely Paul Hently) look at them to see if they can find the problem, if you'd be so kind to send them to me. I'm sure they would need to know what those logs said as well as your event log in order to identify and solve the problem wherever it might be.
John
Not sure this ever was a "pissing contest". In fact these last two program versions have been in an effort to identify and mitigate issues you've mentioned regarding FSUIPC disconnect. I had thought you mentioned another ACARS program that also identified a FSUIPC disconnect - perhaps I misunderstood.
Perhaps email or TS exchange would have been a better forum throughout this exchange, including the log sending. Although I appreciate the additional information and your assist in troubleshooting.
While it's true that the SPAACARS is the application affected according to your event log, the first issue according to your log was related to routine process request sent to FSUIPC that was not caught through the normal error handling process I followed based on the SDK:
at FSUIPC.FSUIPCConnection.Process(Byte, System.Collections.Generic.IEnumerable`1)
It's very likely the other programs are not using the .net FSUIPC library I'm using (based on the programming language there are a number of dll's that are used to interact with FSUIPC), and this error appears to be one that was not expected by the developer of that library either as it's not mentioned in the SDK, and probably would have to be handled at the dll level to prevent a .net crash, where I think all I can do is gracefully exit my program by the time it gets back to SPAACARS - and that would be too late if it's already brought .net to its knees.
But then again, I'm not programming expert - so I might be wrong on some of this. All I know is a call to FSUIPCConnection.process should not bring down .net, and that's something I'd probably have to ask Paul Hently about.
Again I might suggest you see what those FSUIPC and WideFS logs are saying too, as it might be necessary for me to have Pete Dowson (or more likely Paul Hently) look at them to see if they can find the problem, if you'd be so kind to send them to me. I'm sure they would need to know what those logs said as well as your event log in order to identify and solve the problem wherever it might be.
John
Please Log in to join the conversation.
9 years 3 months ago #12756
by jer029
Replied by jer029 on topic SPA ACARS Version 1.4 Released
Thanks Steve,
Perhaps so, but don't count on that...could be Larry discovered a contributing factor too. I'll put out a 1.6 that should fix pirep upload problem and help prevent other possible error conditions (unless I create a few more errors some place else ).
John
Perhaps so, but don't count on that...could be Larry discovered a contributing factor too. I'll put out a 1.6 that should fix pirep upload problem and help prevent other possible error conditions (unless I create a few more errors some place else ).
John
Please Log in to join the conversation.
Time to create page: 0.057 seconds