The error message received was:
Enter password to boot WebLogic server:*********
Starting WebLogic Server ....
<May 15, 2002 1:13:37 PM PDT> <Notice> <Management> <Loading configuration file
\config\mydomain\config.xml ...>
log file: C:\bea\wlserver6.0\.\config\mydomain\logs\weblogic.log
<May 15, 2002 1:13:39 PM PDT> <Info> <Logging> <Only log messages of severity "E
rror" or worse will be displayed in this window. This can be changed at Admin Console>
mydomain> Servers> myserver> Logging> General> Stdout severity threshold>
<May 15, 2002 1:13:48 PM PDT> <Notice> <WebLogicServer> <WebLogic Server started
>
<May 15, 2002 1:13:51 PM PDT> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<May 15, 2002 1:13:51 PM PDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<May 15, 2002 1:13:51 PM PDT> <Error> <Performance Pack> <Unable to load performance
pack, using Java I/O.
java.lang.UnsatisfiedLinkError: no wlntio in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at weblogic.socket.NTSocketMuxer.<init>(NTSocketMuxer.java:173)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.socket.SocketMuxer.makeTheMuxer(SocketMuxer.java:126)
at weblogic.socket.SocketMuxer.getMuxer(SocketMuxer.java:83)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:224)
>
What exact version of windows are you running?
Regards,
Michael
Janet Carmichael wrote:
--
Michael Young
Developer Relations Engineer
BEA Support
Thanks for your reply. We use Windows NT.
Janet
make sure you have wlntio.dll in the \bea\wlserver6.0\bin directory. Also make sure
you have this directory in your system path, or verify in your weblogic.log file
that this directory is included in your java.library.path.
If you are missing the file wlntio.dll then your installation has been corrupted in
some way - you should probably reinstall.
FWIW, in the end, if you are not stress testing or in production this error is not
critical - the server will still run using java sockets instead of native sockets,
but performance will probably be lower than with native sockets.