FULL PRODUCT VERSION :
java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
Before 6u10 it was possible to use java beans from a windows program through the ActiveX bridge and at the same time embeds an Internet Explorer plugin where Applets are shown.

With the new java plugin that was introduce in 6u10, this is not possible anymore. If an ActiveX application has been loaded before, then trying to load a page with applets into a browser control in the same process will cause the Applet not to be painted. When scrolling the browser control (and thereby triggering repaints on the Applet), the following Exception is thrown many times: java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207795767, now ts: 12207795790, dT 23.

This problem is quite serious for us, since we have both Applets and ActiveX-Bridge based controls regularly running in the same application. Any workaround that makes the Bridge work with the new plugin would be highly appreciated.


ERROR MESSAGES/STACK TRACES THAT OCCUR :
Java Plug-in 1.6.0_12
Verwendung der JRE-Version 1.6.0_12 Java HotSpot(TM) Client VM
Home-Verzeichnis des Benutzers = C:\Documents and Settings\steich2c

----------------------------------------------------
c: Konsole löschen
f: Objekte in Finalisierungswarteschlange finalisieren
g: Speicherbereinigung
h: Diese Hilfemeldung anzeigen
l: ClassLoader-Liste ausgeben
m: Speicherbelegung anzeigen
o: Protokollierung auslösen
p: Proxy-Konfiguration neu laden
q: Konsole ausblenden
r: Richtlinien-Konfiguration neu laden
s: System- und Bereitstellungseigenschaften ausgeben
t: Threadliste ausgeben
v: Thread-Stack ausgeben
x: ClassLoader-Cache löschen
0-5: Trace-Stufe auf <n> setzen
----------------------------------------------------

java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207795767, now ts: 12207795790, dT 23
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207812102, now ts: 12207812123, dT 21
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207827759, now ts: 12207827778, dT 19
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207843813, now ts: 12207843835, dT 22
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207859838, now ts: 12207859857, dT 19
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207875807, now ts: 12207875828, dT 21
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 12207900296, now ts: 12207900321, dT 25
at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
at sun.plugin2.message.transport.NamedPipeTransport.signalDataWritten(Unknown Source)
at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
at sun.plugin2.message.Pipe.send(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessageDirect(Unknown Source)
at sun.plugin2.main.server.JVMInstance.sendMessage(Unknown Source)
at sun.plugin2.main.server.JVMInstance.setAppletSize(Unknown Source)
at sun.plugin2.main.server.JVMManager.setAppletSize(Unknown Source)
at sun.plugin2.main.server.IExplorerPlugin.SetObjectRects(Unknown Source)


REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
Attached seperatly
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
The problem does not occur, if the new java plugin is turned off in the Java control panel.

SUPPORT :
YES

Release Regression From : 6u7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.