Exception in thread "AWT-EventQueue-0" java.lang.UnsatisfiedLinkError: glGenList

OpenGL Development JOGL Development
#1

Hi folks,

I’m really stuck with this one. I just downloaded and installed jogl-1_0_0-windows-i586.zip, and now my app (which has been running nicely for months) is falling over with the stack trace shown below. I saw something about a mismatched jogl.dll and jogl.jar, but mine are in the correct place, correct path and classpath, and same filedate. Anyone have any neat ideas please?

Thanks!

Exception in thread “AWT-EventQueue-0” java.lang.UnsatisfiedLinkError: glGenLists
at com.sun.opengl.impl.GLImpl.glGenLists(Native Method)
at javax.media.opengl.DebugGL.glGenLists(DebugGL.java:2058)
at TessTest$TessRenderer.init(TessTest.java:139)
at com.sun.opengl.impl.GLDrawableHelper.init(GLDrawableHelper.java:71)
at javax.media.opengl.GLCanvas$InitAction.run(GLCanvas.java:242)
at com.sun.opengl.impl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:123)
at javax.media.opengl.GLCanvas.maybeDoSingleThreadedWorkaround(GLCanvas.java:236)
at javax.media.opengl.GLCanvas.display(GLCanvas.java:127)
at javax.media.opengl.GLCanvas.paint(GLCanvas.java:139)
at sun.awt.RepaintArea.paintComponent(RepaintArea.java:248)
at sun.awt.RepaintArea.paint(RepaintArea.java:224)
at sun.awt.windows.WComponentPeer.handleEvent(WComponentPeer.java:254)
at java.awt.Component.dispatchEventImpl(Component.java:4031)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

#2

do you have all the dlls in the right place? jogl.dll and jogl_awt.dll ?

#3

Double check to make sure you didn’t drop a jogl.jar or jogl.dll anywhere in your JRE or elsewhere on your CLASSPATH or PATH. -verbose:class will show you where the JOGL classes are coming from.

At the point the exception is thrown, you can use a utility like the SysInternals ProcessExplorer to see what DLLs have been loaded by the java process. That should indicate to you where the JOGL native code is coming from.

#4

You are a genius. I found a ZIPPED copy of jogl.jar further down the path. Removed, and we’re now looking good. Thank you so much, I don’t think I’d have found that without your suggestion of using the process explorer.

Tim