-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
5.0
-
x86
-
windows_xp
FULL PRODUCT VERSION :
java version "1.5.0_10"
Java (TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
java HotSpot (TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
IBM WebSphere Host On-Demand 8.06 and 9.06 and 10.
A DESCRIPTION OF THE PROBLEM :
IBM Websphere Host On-Demand is a java-enabled terminal emulator. We rely on Sun and IBM JREs (and old MS JVM) to provide the client java environment.
Print screen with our emulator worked in 1.5.0_09 and below.
With the last Sun Java update, we are getting reports that users get an error in the java console when they try to bring up our Print Screen function:
java.lang.NullPointerException
at java.awt.Component$NativeInLightFixer.Install(Unknown source)
at java.awt.Component$NativeInLightfixer.<init> (Unknown source)
at java.awtComponent.addNotify(Unknown source)
at java.Container.addNotive(Uniknown Source)
...
at sun.awt.windows.WPrintDialog.addNotify(UnknownSource)
at java.awt.Dialog.conditionalshow(UnknownSource)
...
The print screen dialog fails to come up.
Can you tell us what you changed in the java code? Did you forget something? or do we need to make a change to accommodate something in your code?
Impact:
Many of our customer rely on your product to run our product. When they get automatic updates of your product and it causes ours to fail, we get calls.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
It would be interesting to see if a simple java applet that when selected File/Print pops up a Windows Print dialog fails.
I am not a developer and cannot provide access to code.
One of our developers says that 1.6 does not display this behavior.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Print dialog should pop up in the foreground and no exceptions should be displayed in the java console.
ACTUAL -
Print dialog fails to appear and exceptions are displayed in the java console.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
java.lang.NullPointerException
at java.awt.Component$NativeInLightFixer.install(Unknown Source)
at java.awt.Component$NativeInLightFixer.<init>(Unknown Source)
at java.awt.Component.addNotify(Unknown Source)
at java.awt.Container.addNotify(Unknown Source)
at java.awt.Window.addNotify(Unknown Source)
at java.awt.Dialog.addNotify(Unknown Source)
at sun.awt.windows.WPrintDialog.addNotify(Unknown Source)
at java.awt.Dialog.conditionalShow(Unknown Source)
at java.awt.Dialog.show(Unknown Source)
at sun.awt.windows.WPrinterJob.displayNativeDialog(Unknown Source)
at sun.awt.windows.WPrinterJob.printDialog(Unknown Source)
at com.ibm.eNetwork.beans.HOD.PrintScreen.?B(Unknown Source)
at com.ibm.eNetwork.beans.HOD.PrintScreen.?B(Unknown Source)
at com.ibm.eNetwork.beans.HOD.PrintScreen.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Use 1.5.0_09 and below or 1.6
Release Regression From : 5.0u9
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.5.0_10"
Java (TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
java HotSpot (TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
IBM WebSphere Host On-Demand 8.06 and 9.06 and 10.
A DESCRIPTION OF THE PROBLEM :
IBM Websphere Host On-Demand is a java-enabled terminal emulator. We rely on Sun and IBM JREs (and old MS JVM) to provide the client java environment.
Print screen with our emulator worked in 1.5.0_09 and below.
With the last Sun Java update, we are getting reports that users get an error in the java console when they try to bring up our Print Screen function:
java.lang.NullPointerException
at java.awt.Component$NativeInLightFixer.Install(Unknown source)
at java.awt.Component$NativeInLightfixer.<init> (Unknown source)
at java.awtComponent.addNotify(Unknown source)
at java.Container.addNotive(Uniknown Source)
...
at sun.awt.windows.WPrintDialog.addNotify(UnknownSource)
at java.awt.Dialog.conditionalshow(UnknownSource)
...
The print screen dialog fails to come up.
Can you tell us what you changed in the java code? Did you forget something? or do we need to make a change to accommodate something in your code?
Impact:
Many of our customer rely on your product to run our product. When they get automatic updates of your product and it causes ours to fail, we get calls.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
It would be interesting to see if a simple java applet that when selected File/Print pops up a Windows Print dialog fails.
I am not a developer and cannot provide access to code.
One of our developers says that 1.6 does not display this behavior.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Print dialog should pop up in the foreground and no exceptions should be displayed in the java console.
ACTUAL -
Print dialog fails to appear and exceptions are displayed in the java console.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
java.lang.NullPointerException
at java.awt.Component$NativeInLightFixer.install(Unknown Source)
at java.awt.Component$NativeInLightFixer.<init>(Unknown Source)
at java.awt.Component.addNotify(Unknown Source)
at java.awt.Container.addNotify(Unknown Source)
at java.awt.Window.addNotify(Unknown Source)
at java.awt.Dialog.addNotify(Unknown Source)
at sun.awt.windows.WPrintDialog.addNotify(Unknown Source)
at java.awt.Dialog.conditionalShow(Unknown Source)
at java.awt.Dialog.show(Unknown Source)
at sun.awt.windows.WPrinterJob.displayNativeDialog(Unknown Source)
at sun.awt.windows.WPrinterJob.printDialog(Unknown Source)
at com.ibm.eNetwork.beans.HOD.PrintScreen.?B(Unknown Source)
at com.ibm.eNetwork.beans.HOD.PrintScreen.?B(Unknown Source)
at com.ibm.eNetwork.beans.HOD.PrintScreen.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Use 1.5.0_09 and below or 1.6
Release Regression From : 5.0u9
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.