This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I get the following exception when running the mobile app in debug mode: java.lang.NullPointerException at sun.swing.table.DefaultTableCellHeaderRenderer.getColumnSortOrder(DefaultTableCellHeaderRenderer.java:104) at com.sun.java.swing.plaf.windows.WindowsTableHeaderUI$XPDefaultRenderer.getTableCellRendererComponent(WindowsTableHeaderUI.java:108) at org.openide.explorer.view.TableSheetCell.getTableCellRendererComponent(TableSheetCell.java:280) at org.openide.explorer.view.TreeTableView$SortingHeaderRenderer.getTableCellRendererComponent(TreeTableView.java:1581) at javax.swing.plaf.basic.BasicTableHeaderUI.getHeaderRenderer(BasicTableHeaderUI.java:663) at javax.swing.plaf.basic.BasicTableHeaderUI.getHeaderHeight(BasicTableHeaderUI.java:698) at javax.swing.plaf.basic.BasicTableHeaderUI.createHeaderSize(BasicTableHeaderUI.java:727) at javax.swing.plaf.basic.BasicTableHeaderUI.getPreferredSize(BasicTableHeaderUI.java:758) at javax.swing.JComponent.getPreferredSize(JComponent.java:1632) at org.openide.explorer.view.TreeTable$TreeTableHeader.getPreferredSize(TreeTable.java:869) at javax.swing.ViewportLayout.preferredLayoutSize(ViewportLayout.java:78) at java.awt.Container.preferredSize(Container.java:1616) at java.awt.Container.getPreferredSize(Container.java:1601) at javax.swing.JComponent.getPreferredSize(JComponent.java:1634) at javax.swing.ScrollPaneLayout.preferredLayoutSize(ScrollPaneLayout.java:507) at java.awt.Container.preferredSize(Container.java:1616) at java.awt.Container.getPreferredSize(Container.java:1601) at javax.swing.JComponent.getPreferredSize(JComponent.java:1634) at java.awt.BorderLayout.preferredLayoutSize(BorderLayout.java:702) at java.awt.Container.preferredSize(Container.java:1616) at java.awt.Container.getPreferredSize(Container.java:1601) at javax.swing.JComponent.getPreferredSize(JComponent.java:1634) at javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:769) at java.awt.Container.layout(Container.java:1432) at java.awt.Container.doLayout(Container.java:1421) at java.awt.Container.validateTree(Container.java:1519) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validate(Container.java:1491) at org.netbeans.core.windows.view.ui.DesktopImpl$LayeredLayout.layoutContainer(DesktopImpl.java:431) at java.awt.Container.layout(Container.java:1432) at java.awt.Container.doLayout(Container.java:1421) at java.awt.Container.validateTree(Container.java:1519) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validateTree(Container.java:1526) at java.awt.Container.validate(Container.java:1491) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:635) [catch] at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:127) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121) It would seem to be a problem with the screen components of the debugger output. The app never gets reach a debug point before this occurs (it doesn't even get to the "Launch" point for the app), only the emulator.
If there is anything I can provide further then let me know.
Yes, there are some questions that might to help us to reproduce it in our enviroment... Is there any report in output window? Any message from Vista? This problem usually happens when the Vista block the new socket connection of the debugger. However there should be an feedback. I'll try to reproduce in Vista enviroment. Is there anything special what I should do to be able to reproduce it? Can I just debug helloWorld project to get into this state (at least in your enviroment)? What Vista distribution are you using? What build of NetBeans IDE? What JDK? thank you.
from reporter's email: I'm using JDK 1.6.0_05 with Vista Business. For Netbeans, any of Beta1, Beta2 plus daily builds 20071021, 20071023 that I've tried result in the same problem. (my log file is attached) A very simple helloworld does reproduce the issue. I have thought it might be the windows firewall or something but I've turned that off and the issue still arises
OK, I've copied over my workspace from Vista to my XP laptop and debugging is working perfectly on the same build (200710231200). So I guess that shows its a Vista issue. But the question is how do we fix it? Windows firewall is off, Windows Defender isn't running, but could perhaps Zayit.exe still be being blocked or something similar??
reassigning to Window System for evaluation
Reporter, can you reproduce when debugging simple J2SE project? It seems error is triggered from TreeTableView and it's used in J2SE debugger as well. Ideally, write down exact steps of how to reproduce on Vista from the scratch, thanks. Stando, didn't you see something similar already?
it seem to be the same as #119569 i guess it's jdk1.6 u5 issue but i haven't any related jdk bug and don't know how to reproduce this one
Normally I would be tracing down the root cause of this issue (since it's mobility related) however i don't have access to Vista. it seems a good idea to first determine if this issues also arises under vista on j2se. it may be worth it to try under vista using a different emulator.
i'm not sure mobility code is at fault here. it's just an NPE from treetableview's ui.
i see it's thrown from DefaultTableCellHeaderRenderer.java:104 however from what the reporter said it seems that the debugging session doesn't start properly, so the exception may be a result of failed jdwp connection rather than the root cause of the problem, i may be reaching out a bit :)
the debugging session does start it would seem, but it cannot show any of the local variable values etc, the mobile app however, still runs fine.
*** This issue has been marked as a duplicate of 119569 ***