02-08-2010 11:28 AM
By pressing F5 repeatedly I just "accelerate the time".
I see the same issues when I'm running the VI in "embedded" mode but the time of them is undefined. It is may be immedeatly or after a long time.
To show You the error I just speed up the process. If such an error occures in the software, customer will kill me like an incorrect request kills LabView.
02-09-2010 10:11 AM
Hi Kolan,
I still don't understand why you or your customer would be continuously refreshing the web page--embedded mode will show the running VI, and there would be absolutely no reason to refresh the page, especially as much as you are in this testing. If you are seeing this problem when just running embedded mode, without refreshing, then we can investigate further to see if this is actually a bug. I searched our CAR (corrective action request) database and saw nothing reported.
Please let me know if you are seeing this crash under normal circumstances--and if so, then post your code and I'll be happy to test it out on my computer. However, since refreshing in this manner is not a feasible use case, I hesitate to say that this performance is indicative of what you see in normal operation. In other words, I really don't think you are speeding up the process by pressing F5, rather, I think that this is what is causing the crash.
Cheers,
02-09-2010 10:20 AM
kolan,
You posted something to some offbeat hosting service. Don't do that. Post your code here with the 'Add Aattachments' option.
Nothing that I've written with LabVIEW 9 shows any problems with the web server. Perhaps it's unique to your network settings?
02-09-2010 12:35 PM - edited 02-09-2010 12:41 PM
2 The Chancenator: for the 1'st paragraph I can say that there are no reasons to press F5 repeatedly of course, I'm not an idiot, ha
If it was a problem I have just to say to customer: "Please don't do that!" and this may be a crooked solution but a solution.
The issue arise without this action but if I shall to save a video of this crash example it will be to big to send because I don't determine time of the crash exactly.
Why do I press F5? It simulates simple disconnect from the VI and connect a few time later. The User(customer) may want to see the remote panel on other PC so he must do this action. Or another reason: connection can be lost thanks to provider. And there are a lot of different reasons.
The problem on the surface: when we close the browser or when we mv to other web-page in the browser client's engine receive some events/properties that the user have not to send. They are may be incorrect. And the engine must handle them and refuse and don't send to the server engine.
2 Dennis Knutson: I know about offbeat hosting service but very slow internet was in that day and after 20-30 attempt I have surrender. But rapidshare defines greater timeout so I have uploaded there.
Network settings... I don't think so. I have tested this example without any network (except 127.0.0.1 localhost) and on different computers too.
03-26-2010 08:09 AM - edited 03-26-2010 08:10 AM
It is seems the problem is with licenses. I have registered version (pro), but 8.6.1 version and don't see this troubles now.
But I don't mark as a solved because some errors ocure, not critical.
Practically it is nearly solved.
08-20-2010 03:39 AM
It is assured on 100 % that the problem dares licensing of remote panels.