So that we don't waste our time suggesting things you tried already, could you itemize all of the things you tried during that several hours?
posted 8 years ago
Thanks Paul for your kind reply.
I tried yesterday and got it to work smoothly. I Cleared the cache such that the "no enough space on disk" got cleared.
I was successfully able to launch the applet.
Thank you for your response .
But i want to get cleared off something from you.The Applet gets stored on the local cache when loaded through JNLP and because of that we need to clear the cache to get proper outputs.
When getting this into live production,it is a bit difficult to prompt the users to clear the cache memory.
Is there any better solution for this?
I am newly using this protocol (JNLP) and i wish to get something clarified.
I am desiging an alarm management system for a network .The Server in which i have the application has connectivity to all the nodes that i want to make notification of the alarms when something goes wrong in that node.The Applet that is launced through JNLP will initially contain the alarms fetched from the database.Suppose that i have a new entry in my database(when anything goes wrong in any node it will automatically fill my database) ,is it possible to update the Applet that the client is looking at without actually refreshing the application again.Is this possible through JNLP.
I have had Web Start applications in production at work constantly for a year or two now and we don't have that problem. If your app is causing the cache to overflow then either your app is far too large or the cache settings are far too small. Or else you are doing something so that lots of different resources are being cached. So run your app for a while, then view the cache and see what's in there, particularly under the Resources section.
As for your design question, sure, the database entries don't have to be hard-coded in the applet. It's perfectly possible for the applet to read them from the database and store them in memory.