Applet hangs after hibernation

Question

Hi,
i've made a DLL that hibernates the computer. When I run a simply Java program that loads the DLL, It runs perfectly. The computer hibernates and return aftes 70 seconds, that's the time I have configured.
Now, I need to run this DLL by an applet. And after the hibernation the applet hangs, I have to kill the browser process.
I found this bug on Java http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4916767
I don't know if it is the problem I had. Anyway, they said it was fixed. I'm using jdk 1.6.
Can anyone help me?
My code is:
public class AppletExecutora extends Applet {
     private String mensagem;
     // conectores para uso da dll
     private ConectorTesteAcpi conectorAcpi;
     // botoes que acionam os testes
     private Button botaoAcpi;
     public void init() {
          mensagem = "";
          // copiar arquivos .dll para o diretorio windows.system32.
          copiarBibliotecas("acpi.dll");
          // inicia conector para a biblioteca .dll
          conectorAcpi = new ConectorTesteAcpi();
          //inicia botoes                    
          botaoAcpi = new Button("Teste Acpi");
          botaoAcpi.setVisible(true);
          criarEventoTesteAcpi();
          add(botaoAcpi);          
     private void criarEventoTesteAcpi() {
          ActionListener tratarEvento = new ActionListener(){               
               public void actionPerformed(ActionEvent e) {
                    getAppletContext().showStatus("Testando Acpi...");     
                    conectorAcpi.testarAcpi(70);
                    int resultadoTeste = conectorAcpi.getResultadoTeste();
                    if (resultadoTeste == ConectorTesteAcpi.FALHA){
                         exibirMensagem("FALHA NO TESTE DA ACPI.");
                    }else{
                         exibirMensagem("TESTE DA ACPI FINALIZADO COM SUCESSO.");
                    getAppletContext().showStatus("Concluído");
          botaoAcpi.addActionListener(tratarEvento);
     public void copiarBibliotecas(String arquivo) {
          try {
               InputStream sOrigem = this.getClass().getResourceAsStream("/lib/"+arquivo);
               File destino = new File("/WINDOWS/System32/"+arquivo);
               destino.createNewFile();
               OutputStream sDestino = new FileOutputStream(destino);
               byte[] buf = new byte[1024];
               int len;
               while ((len = sOrigem.read(buf)) > 0) {
                    sDestino.write(buf, 0, len);
               sOrigem.close();
               sDestino.close();
          } catch (Exception except) {
               exibirMensagem(except.getMessage());
     public void start() {
          exibirMensagem("Escolha o teste a ser realizado...");
     public void stop() {
          exibirMensagem("Interrompendo o executor do teste... ");
     public void destroy() {
          exibirMensagem("Finalizando o executor do teste...");
     void exibirMensagem(String mensagem) {
          this.mensagem = mensagem;
          invalidate();
          repaint();
     public void paint(Graphics g) {
          g.drawRect(0, 0, getWidth() - 1, getHeight() - 1);          
          g.drawString(mensagem, 5, getHeight()/2);
}

Answer 1

Do the following:
1. On client machine, exit all open browsers.
2. If you are running Developer Suite, stop OC4J.
3. Manually delete JAR cache. Delete all files in:
C:\Documents and Settings\<USER NAME>\Oracle Jar Cache
4. Delete the following file (your JInitiator version may be different):
C:\Documents and Settings\<USER NAME>\jinitiator13129.trace
5. Open the Jinitiator Control Panel which can be found on the Windows Control Panel and add the following to the "Java Runtime Parameters" on the Basic tab:
-Djavaplugin.trace=true -Djavaplugin.trace.option=basic
Click on Apply and exit the Control Panel
6. On the server, add the following to the formsweb.cfg:
WebUtilLogging=on
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
6. If the server is a Unix platform, recompile the form and ensure that you use the COMPILE_ALL=YES option.
7. Retest one time. Do not try more than one time as this will create too many entries in the trace file.
8. After the failure has reproduced, exit the form and the browser. Open the new jinitiator13129.trace file and carefully review. It is likey you will find the cause of the problem in this file. At minimum, a hint should be offered.