6 Replies Latest reply on Apr 2, 2015 11:19 AM by Marco Gralike

    SQL developer stopped working, due to global proxy configuration

    109922d8-a40e-4698-b4c3-c7511ebdb738

      I couldn't use SQL developer anymore since yesterday. When I started the application, it shows a the loading screen, the main window appears and after a couple of seconds it crashes with a message saying "sqldeveloper64W has stopped working". Last week it was still working fine. I tried downloading and installing a new version, same result.

      SQL developer version: I had version 4.0.1 and also tried 4.0.3

      JDK version: the versions included with SQL developer, being 1.7.0_51 and 1.7.0_55, I also tried my own installed jdk 1.8.0_25 (this resulted in an extra message about java 8, but the same crash)

      OS: Windows 7 Enterprise

      I was not yet connected to an oracle version. I cleared my AppData\Roaming\sqldeveloper and AppData\Roaming\SQL Developer directories (hoping this would help).

      The Windows eventviewer has the following information:

      Faulting application name: sqldeveloper64W.exe, version: 0.0.0.0, time stamp: 0x520cfebd

      Faulting module name: WS2_32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ca25

      Exception code: 0xc0000409

      Fault offset: 0x000000000000382c

      Faulting process id: 0x440

      Faulting application start time: 0x01d06b8bb2b97bef

      Faulting application path: C:\Programs\sqldeveloper\sqldeveloper\bin\sqldeveloper64W.exe

      Faulting module path: C:\windows\system32\WS2_32.dll

      Report Id: f755bce3-d77e-11e4-ba16-fc15b4edecb8

      I tried getting the information suggested in http://www.thatjeffsmith.com/archive/2012/06/how-to-collect-debug-info-for-oracle-sql-developer/ When I start sqldeveloper\bin>sqldeveloper.exe, the command window displays only something like:

      LOAD TIME : 579

      When SQL developer crashes, I hit Ctrl+Break in the command window and get my commandprompt back (no extra information yet). I click "Close the program" in the message window and get the following information in my command window:

      C:\Programs\sqldeveloper-4.0.1\sqldeveloper\bin>2015-03-31 16:14:56

      Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode):

       

      "Thread-22" daemon prio=2 tid=0x000000000b4de800 nid=0x1544 runnable [0x00000000120ff000]

         java.lang.Thread.State: RUNNABLE

              at sun.net.dns.ResolverConfigurationImpl.notifyAddrChange0(Native Method)

              at sun.net.dns.ResolverConfigurationImpl$AddressChangeListener.run(ResolverConfigurationImpl.java:142)

       

      "Automatic check for updates" prio=2 tid=0x000000000b4d9800 nid=0x1198 runnable [0x00000000135ae000]

         java.lang.Thread.State: RUNNABLE

              at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)

              at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901)

              at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293)

              at java.net.InetAddress.getAllByName0(InetAddress.java:1246)

              at java.net.InetAddress.getAllByName0(InetAddress.java:1223)

              at java.net.InetAddress.getHostFromNameService(InetAddress.java:607)

              at java.net.InetAddress.getCanonicalHostName(InetAddress.java:560)

              at sun.security.krb5.PrincipalName.<init>(PrincipalName.java:386)

              at sun.security.krb5.ServiceName.<init>(ServiceName.java:39)

              at sun.security.jgss.krb5.Krb5NameElement.getInstance(Krb5NameElement.java:121)

              at sun.security.jgss.krb5.Krb5MechFactory.getNameElement(Krb5MechFactory.java:95)

              at sun.security.jgss.GSSManagerImpl.getNameElement(GSSManagerImpl.java:202)

              at sun.security.jgss.GSSNameImpl.getElement(GSSNameImpl.java:472)

              - locked <0x00000000f8932180> (a sun.security.jgss.GSSNameImpl)

              at sun.security.jgss.GSSNameImpl.init(GSSNameImpl.java:201)

              at sun.security.jgss.GSSNameImpl.<init>(GSSNameImpl.java:170)

              at sun.security.jgss.GSSNameImpl.<init>(GSSNameImpl.java:151)

              at sun.security.jgss.GSSManagerImpl.createName(GSSManagerImpl.java:127)

              at sun.net.www.protocol.http.spnego.NegotiatorImpl.init(NegotiatorImpl.java:97)

              at sun.net.www.protocol.http.spnego.NegotiatorImpl.<init>(NegotiatorImpl.java:117)

              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

              at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

              at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

              at sun.net.www.protocol.http.Negotiator.getNegotiator(Negotiator.java:63)

              at sun.net.www.protocol.http.NegotiateAuthentication.isSupported(NegotiateAuthentication.java:104)

              - locked <0x00000000f88f6268> (a java.lang.Class for sun.net.www.protocol.http.NegotiateAuthentication)

              at sun.net.www.protocol.http.AuthenticationHeader.parse(AuthenticationHeader.java:180)

              at sun.net.www.protocol.http.AuthenticationHeader.<init>(AuthenticationHeader.java:126)

              at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1375)

              - locked <0x00000000f8849490>

      The "Automatic check for updates" triggered me to look into my proxy configuration. I use Forefront TMG Client to configure the corporate proxy. It has an option "Enable Web browser automatic configuration" for also letting the TMG Client managing the web browser proxy options. (I had that option disabled, because Microsoft Outlook uses the web browser settings and couldn't cope with it, causing it to take about half an hour to send an email). When I enabled the setting, SQL developer doesn't crash anymore.

      I'm happy I got a working sql developer back, but I think it shouldn't crash on a "wrong" proxy configuration.