I have a web application with an applet. Applet is being used for opening of documents in the native viewer. Basically the applet connects to a servlet and downloads the byte array and stores the content in the user machine and then opens the same in the naative viewer (ex:, word, excel,ppt etc.). We have been running this application from past one year without any problem.
Few months back, our company merged with another one (say company2). Company2 users are willing to use our application. Now the problem arised when the company2 users started using the application, it started freezing.
What I have observed is that the applet actually takes 4 to 5 minutes to initialize and till the time applet is initialized whole application freezes. Once the applet load everythign work fine. However this application works perfectly fine for the company1 users for which the application was originally designed.
We have checked all the server ips involved and made sure that nothing is blocked on the network and no security issue is causing any problem.
User System details:
Users are using IE9 on windows 7 enterprise with Java 1.7_05 in both the company networks.
Application UI is developed in GWT and backend is Java/J2EE. Applet is compiled on Java 1.7_05.
Has anyone else faced similar issue?
Does anyone have any suggestion on how to fix this issue please?
Well, I think most responders will want you to post code for this. Some baseline-simple Applet code that exhibits the problem, without necessarily including any trade secrets, or a lot of code which must be read-through to understand, and get confusing. In fact, the first thing you might consider to debug this, is to get a simplified version of the applet, and see if you can make the same problem happen on both environments.
That being said (and this is hazarding a guess, which is risky), when I hear this, my gut is saying "environment". And, when you write "freezes", but then "until...", that does not sound like it is freezing, but rather just slow. You need to differentiate between 'working slowly', and 'completely frozen'. It might appear frozen for that duration, because you are doing too much work in the event thread, instead of loading the document in a background thread. And it could be that your Company2 users have a very much slower environment that makes this more obvious.
So, bottom line:
* Please be very specific about what the bad behavior is.
* Please make simplified version of code that does same thing.
* Please post said code.
If a chicken that is half full crosses the road, will anyone hear it?