Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem restarting WL5.1 after Service Pack installation

0 views
Skip to first unread message

Kin Ho

unread,
Aug 16, 2000, 3:00:00 AM8/16/00
to
HI,

I am using weblogic 5.1 with NT Server 4.0 and can
start the server fine (using the server
console)without any service pack. However, after I
follow the step by step instruction (copied below) to
install the service pack. (I tried sp3 and sp4
separately) but I cannot restart the server in either
case. Somehow, it is trying to look for a class and
did not find it.

Can you help me on that pls? Thank you.

The error is:

***************************************************************************
The WebLogic Server did not start up properly.
Exception raised: java.lang.ClassNotFoundException:
weblogic.t3.srvr.T3Srvr
java.lang.ClassNotFoundException:
weblogic.t3.srvr.T3Srvr
at
weblogic.boot.ServerClassLoader.findLocalClass(ServerClassLoader.java:322)
at
weblogic.boot.ServerClassLoader.loadClass(ServerClassLoader.java:102)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
weblogic.Server.startServerDynamically(Server.java:96)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
***************************************************************************

Installation I am following is
*************************************************************************

1)Read this document and the release notes.

2)Unzip the contents of the service pack into a
temporary directory, such as /temp.

3)Copy weblogic510sp3.jar and weblogic510sp3boot.jar
from /temp to a location where it can be referenced by
your WebLogic Server installation. If you have
installed WebLogic Server in its default location of
/weblogic, then an appropriate place to copy the .jar
file would be to the directory /weblogic/lib.
If you are running the installation from a drive that
is not writable, then you will need to copy the
service pack jar to a directory outside of the
installation, but whose path is accessible. The
directory of the weblogic.properties file that you are
using to start WebLogic Server is an alternative.
Also, if the server is running under Java 2, the jar
must be in a directory that has been made accessible
in the security policy file.

If you are using VisualAge, import both jars to your
workspace, first weblogic510sp3.jar and then
weblogic510sp3boot.jar.


Add the path ofweblogic510sp4boot.jar to the beginning
of the Java system classpath. Add the path of
weblogic510sp3.jar to the beginning of the WebLogic
classpath before you start the WebLogic Server:
$ java ...
-classpath
c:\weblogic\lib\weblogic510sp3boot.jar;
c:\java\lib\classes.zip;
c:\weblogic\classes\boot;
c:\weblogic\eval\cloudscape\lib\cloudscape.jar

-Dweblogic.class.path=c:\weblogic\lib\weblogic510sp3.jar;
c:\weblogic\classes;

c:\weblogic\license;c:\weblogic\lib\weblogicaux.jar;
c:\weblogic\myserver\serverclasses
... weblogic.Server
You can do this by editing the command line script
that you use to start the WebLogic Server, as
described in the Installation Guide, Setting up and
Starting WebLogic Server 5.1.


If you are running on NT and are using either the
Start Menu commands or running as an NT Service, you
need to use wlconfig.exe to set values for classpath,
weblogic.class.path and JAVA_HOME.
Save the current values of your configuration to a
file before making changes in case you need to revert
your changes:

C:\> wlconfig > config.txt
Include the weblogic510sp3boot.jar file at the start
of classpath (to be entered on one line):

C:\> wlconfig -classpath
c:\weblogic\lib\weblogic510sp3boot.jar;
c:\java\lib\classes.zip;
c:\weblogic\classes\boot;
c:\weblogic\eval\cloudscape\lib\cloudscape.jar
Include the weblogic510sp3.jar file at the start
ofweblogic.class.path (to be entered on one line):

C:\> wlconfig
-Dweblogic.class.path=c:\weblogic\lib\weblogic510sp4.jar;
c:\weblogic\license;c:\weblogic\classes;
c:\weblogic\myserver\serverclasses;
c:\weblogic\lib\weblogicaux.jar
Next, set JAVA_HOME to point to a JDK that you have
installed, as the JREs that were shipped with the
distribution do not support multi-byte character sets:


C:\> wlconfig -JAVA_HOME c:\java117

The file lib/persistence/WebLogic_RDBMS.jar will need
to be copied to your /weblogic/lib/persistence
directory if you are developing or deploying EJBs, and
are interested in resolving issues related to
WebLogic_RDBMS.jar.
To deploy the lib/persistence/WebLogic_RDBMS.jar, make
a copy of the original to a safe location and then
copy lib/persistence/WebLogic_RDBMS.jar from the
service pack to replace the original file that you
backed up in another location. For instance, if you
installed WebLogic in /weblogic, here are the sample
commands:

$ cp /weblogic/lib/persistence/WebLogic_RDBMS.jar
/weblogic/lib/persistence/WebLogic_RDBMS.jar.510
$ cd /tmp
$ jar xvf weblogic510sp4.zip
$ cp /tmp/lib/persistence/WebLogic_RDBMS.jar
/weblogic/lib/persistence/WebLogic_RDBMS.jar

Once you have made these changes and started the
Server, you can check that installation was successful
by checking the server version:
java weblogic.Admin t3://Host:Port VERSION
should return
WebLogic Build: 5


Wei Guan

unread,
Aug 16, 2000, 3:00:00 AM8/16/00
to
Post your startup script or output of wlconfig.

--
Cheers - Wei

Kin Ho <kinho...@yahoo.com> wrote in message
news:399a42f7$1...@newsgroups.bea.com...

0 new messages