18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

"J"<br />

java.lang.UnsatisfiedLinkError:<br />

Cause<br />

When trying to start Java Workshop 2.0 (or some other Java applications) on Solaris<br />

2, the following error is displayed:<br />

java.lang.UnsatisfiedLinkError: setCursor<br />

at sun.awt.motif.MComponentPeer.initialize(Compiled Code)<br />

at sun.awt.motif.MTextAreaPeer.initialize(Compiled Code)<br />

at sun.awt.motif.MComponentPeer.(Compiled Code)<br />

at sun.awt.motif.MTextAreaPeer.(Compiled Code)<br />

at sun.awt.motif.MToolkit.createTextArea(Compiled Code)<br />

Action<br />

The LD_LIBRARY_PATH is probably set up to include a Java lib directory that<br />

doesn’t quite match the java bin command used. For example, on Solaris 2.6:<br />

LD_LIBRARY_PATH = /usr/openwin/lib results in Java Workshop runing<br />

properly. But setting: LD_LIBRARY_PATH = /usr/java/lib:/usr/openwin/lib<br />

results in the error being displayed, since Java Workshop uses its own version of JDK<br />

and the startup process picks up a mixture of versions.<br />

The answer is to not include /usr/java/lib in your LD_LIBRARY_PATH since it is<br />

needed only in rare circumstances, such as if you are using the Java Invocation API.<br />

Alphabetical Message Listing 93

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!