oracle java sun 1.6.0
Oracle E-Business and Java 1.6.0.7 plus
19-Oct-09 14:52 Arkiveret i:
isss
1. After upgrading to Sun Java from
Jinitiator the results have been relatively smooth...
apart from one issue which came under way as the latest request was to have the ”latest” version of Sun Java... and not the 1.6.0.7 version that we have tested initially....
It appears that the latest versions from Sun have an issue which can lead to hang-ups, freezes, successful load the first time
you log into a system, but subsequest log-ins leads to hang-ups and freezes... _unless_ you have disabled cache...
The solution is to uncheck the "Enable the next-generation Java Plug-in" !
For some reason this can lead to weird problems.....
Alternatively there is the following excerpt from Metalink:
Detailed Results of Problem Analysis:
-------------------------------------
To reproduce, set the Swap file size to min 512MB and max to any higher
value. NB It is only the min setting of 512MB that causes a problem as
setting max 4096MB does not make a difference and the problem still
reproduces.
Using system managed or set min and max sizes equal to at least system memory
appears to get around the problem.
This points to a more generic issue with the next generation Java technology
and possible interaction with the Windows Virtual memory model.
From Metlink Bug Number: 7834901
(My underlining and ”bold”ification)
apart from one issue which came under way as the latest request was to have the ”latest” version of Sun Java... and not the 1.6.0.7 version that we have tested initially....
It appears that the latest versions from Sun have an issue which can lead to hang-ups, freezes, successful load the first time
you log into a system, but subsequest log-ins leads to hang-ups and freezes... _unless_ you have disabled cache...
The solution is to uncheck the "Enable the next-generation Java Plug-in" !
For some reason this can lead to weird problems.....
Alternatively there is the following excerpt from Metalink:
Detailed Results of Problem Analysis:
-------------------------------------
To reproduce, set the Swap file size to min 512MB and max to any higher
value. NB It is only the min setting of 512MB that causes a problem as
setting max 4096MB does not make a difference and the problem still
reproduces.
Using system managed or set min and max sizes equal to at least system memory
appears to get around the problem.
This points to a more generic issue with the next generation Java technology
and possible interaction with the Windows Virtual memory model.
From Metlink Bug Number: 7834901
(My underlining and ”bold”ification)
|