3 Replies Latest reply on Mar 5, 2014 3:01 PM by Arpod

    4.0 (Debug mode) - swarm of WindowManagerImpl warnings on every keypress in package editor or worksheet

    Arpod

      I'm not sure if it's worth reporting at all, but after enabling debug configuration (via sqldeveloper-debug.conf), every keypress in package editor or worksheet results in 24 identical warnings written to log:

       

      LevelSourceMessage
      WARNINGorg.netbeans.core.windows.WindowManagerImplProblem in some module which uses Window System: Window System API is required to be called from AWT thread only, see http://core.netbeans.org/proposals/threading/ - org.netbeans.core.windows.WindowManagerImpl.warnIfNotInEDT(WindowManagerImpl.java:1755)

       

      This doesn't seem critical, but doesn't seem okay either, and it obscures other useful info found in logs.

       

      Also, for future reference - should suspicious errors/warnings found in debug/normal mode be reported here, in the forums? Because SQLDeveloper also throws "SEVERE oracle.ide.extension.hash    Unexpected runtime exception while delivering HashStructureHookEventUnexpected runtime exception while delivering HashStructureHookEvent" error in the log every time on startup, but extensions seem to work fine...

        • 1. Re: 4.0 (Debug mode) - swarm of WindowManagerImpl warnings on every keypress in package editor or worksheet
          Arpod

          Looking at it further, when these warnings appear for the first time, additional "EDT Violations" error is thrown:

           

          Call to Swing component not from the EDT Thread - in violation of Swing's single threaded policy.

          javax.swing.JTree[,0,0,263x374,alignmentX=0.0,alignmentY=0.0,border=,flags=285213032,maximumSize=,minimumSize=,preferredSize=,editable=false,invokesStopCellEditing=false,largeModel=false,rootVisible=true,rowHeight=17,scrollsOnExpand=true,showsRootHandles=false,toggleClickCount=2,visibleRowCount=20]

          at javax.swing.JComponent.repaint(JComponent.java:4793)

          at java.awt.Component.repaint(Component.java:3286)

          at javax.swing.JTree.treeDidChange(JTree.java:2933)

          at javax.swing.plaf.basic.BasicTreeUI.updateSize(BasicTreeUI.java:1848)

          at javax.swing.plaf.basic.BasicTreeUI.setModel(BasicTreeUI.java:413)

          at javax.swing.plaf.basic.BasicTreeUI$Handler.propertyChange(BasicTreeUI.java:3417)

          at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)

          at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)

          at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)

          at java.awt.Component.firePropertyChange(Component.java:8382)

          at javax.swing.JTree.setModel(JTree.java:879)

          at oracle.dbtools.raptor.plsql.structure.OutlinePanel.setModel(OutlinePanel.java:240)

          at oracle.dbtools.raptor.plsql.structure.OutlinePanel.stateChanged(OutlinePanel.java:289)

          at oracle.dbtools.raptor.plsql.BackgroundParser.parse(BackgroundParser.java:208)

          at oracle.dbtools.raptor.plsql.BackgroundParser$1.construct(BackgroundParser.java:154)

          at oracle.dbtools.raptor.utils.NamedSwingWorker$2.run(NamedSwingWorker.java:115)

          at java.lang.Thread.run(Thread.java:744)

          • 2. Re: 4.0 (Debug mode) - swarm of WindowManagerImpl warnings on every keypress in package editor or worksheet
            thatJeffSmith-Oracle

            Thanks for the report.

             

            Any particular reason you're running in debug mode?

            • 3. Re: 4.0 (Debug mode) - swarm of WindowManagerImpl warnings on every keypress in package editor or worksheet
              Arpod

              Jeff Smith SQLDev PM wrote:

               

              Any particular reason you're running in debug mode?

              Well, 4.0.1 still has a handful of bugs (ctrl+c/v hangs, most notably, and also seemingly illogical completion insight at times), and looking in the log to try and see the cause right away and report it is more productive then trying to reproduce the same behavior after a restart. That, and I'm also curious to get a glimpse of what's happening "behind the scenes".