Prev: Unable to read after commit () with JPA
Next: SMIL (video+image+text) alternative for Java
From: johan on 13 May 2010 06:54
I am working with some web based COTS product that let's us create a
specific class file to add our edits into. The class file we create
doesn't have to be there, but when it is the edits we have are brought
in and run. The software rests on about 10 different web server
boxes, for failovers and to spread out the loads.

Recently we compiled our java class file with java 1.6. We normally
compile with 1.4.2 since our users are still on that level of java on
their machines for a number of reasons. When the 1.6 went in, the
screen with our edits would not fire at all.

We switched that code out with a version of the same code that was
compiled with 1.4.2. And some users still would get the error like
the did with the 1.6 compiled code. The strange thing about that was
one user connecting to web server A would be fine, and one user
connecting to web server A would get the error.

Is there a setting on a browser that could keep the code in memory?
Typically when we have the user's close down their browser's all the
way the java code is reloaded the next time the screen gets loaded.

Any help or ideas would be appreciated.
 | 
Pages: 1
Prev: Unable to read after commit () with JPA
Next: SMIL (video+image+text) alternative for Java