WebLogic 8.1 doesn't work on SunOS 5.8

Question

Hello,
I install WebLogic 8.1 on SunOS 5.8, start it.
Looks like it doesn't work.
It doesn't accept requests, doesn't create log file on startup.
Just running as process.
Do you have any suggestions?
We are BEA castomers and going to migrate from version 6.1 to 8.1.
Thanks.
Oleg.

Answer 1

Hello Wayne,
1) As test, to see if first instance really listening on that port.
I run same version of WL8 on same machine on same port
Usually second instance can't start.
But now second instance runs without complains.
It means that port is free and first instance doesn't listening any port.
After startup, first and second instances display same message:
'started as the administration server (without port number).
2)
$ java -version
java version "1.2.2"
Before startup, I set
JAVA_HOME="/export/home/bea/jdk141_02".
3)
echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
4)
WL output after startup:
$ ./startWebLogic.sh
CLASSPATH=/export/home/bea/jdk141_02/lib/tools.jar:/export/home/bea/weblogic81/server/lib/weblogic_sp.jar:/export/home/bea/weblogic81/server/lib/weblogic.jar:/export/home/bea/weblogic81/server/lib/ojdbc14.jar::/export/home/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/export/home/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/export/home/bea/jdk141_02/jre/lib/rt.jar:/export/home/bea/weblogic81/server/lib/webservices.jar:
PATH=/export/home/bea/weblogic81/server/bin:/export/home/bea/jdk141_02/jre/bin:/export/home/bea/jdk141_02/bin:/export/home/bea/weblogic81/server/bin:/export/home/bea/jdk141_02/jre/bin:/export/home/bea/jdk141_02/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
ServerName=admin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://<hostname>:<port>/console *
<May 22, 2003 11:15:31 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting
WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.1_02-ea-b01 from Sun
Microsystems Inc.>
<May 22, 2003 11:15:31 AM EDT> <Info> <Configuration Management> <BEA-150016>
<This server is being started as the administration server.>
<May 22, 2003 11:15:31 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 8.1 Thu Mar 20 23:06:05 PST 2003 246620
WebLogic XMLX Module 8.1 Thu Mar 20 23:06:05 PST 2003 246620 >
4)
startup script:
# set up WL_HOME, the root directory of your WebLogic installation
WL_HOME="/export/home/bea/weblogic81"
# Set JAVA_HOME to java virtual machine you want to run on server side.
JAVA_HOME="/export/home/bea/jdk141_02"
# set up common environment
. "${WL_HOME}/common/bin/commEnv.sh"
./setEnv.sh
# Set Production Mode. When this is set to true, the server starts up in
# production mode. When set to false, the server starts up in development
# mode. If it is not set, it will default to false.
PRODUCTION_MODE=""
# Set JAVA_VENDOR to java virtual machine you want to run on server side.
JAVA_VENDOR="Sun"
set USE_CURRENT_JAVA_HOME "$@"
. "${WL_HOME}/common/bin/commEnv.sh"
shift 1
# Set SERVER_NAME to the name of the server you wish to start up.
SERVER_NAME=admin
# Set WLS_USER equal to your system username and WLS_PW equal
# to your system password for no username and password prompt
# during server startup. Both are required to bypass the startup
# prompt.
WLS_USER=
WLS_PW=
# Set JAVA_VM to java virtual machine you want to run on server side.
# JAVA_VM=""
# Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
# are more than one, include quotes around them. For instance:
# JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
# Reset number of open file descriptors in the current process
# This function is defined in commEnv.sh
resetFd
# Start WebLogic server
CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
export CLASSPATH
# Start WebLogic server
echo CLASSPATH="${CLASSPATH}"
echo
echo PATH="${PATH}"
echo
echo ServerName="${SERVER_NAME}"
echo
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://<hostname>:<port>/console *"
echo "***************************************************"
"$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
-Dweblogic.management.username=${WLS_USER} -Dweblogic.management.password=${WLS_PW}
-Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy"
weblogic.Server
5)
config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<Domain
Name="MyDomain"
ConfigurationVersion="8.1.0.0"
>
<Server
Name="admin"
ListenPort="7001"
ConsoleInputEnabled="false"
JavaCompiler="javac"
SocketReaderTimeoutMaxMillis="10"
>
<SSL
Name="admin"
ListenPort="7002"
Enabled="true"
/>
</Server></Domain>
Thank you,
Oleg.
"Wayne W. Scott" <[email protected]> wrote:
Oleg:
I have your installation log file. Please send the weblogic start script
you run.
I run another instance of WL on same port and it runs without complains.
Usually second instance stops with "Requested shutdown ..." if startedon busy
port.Are you running 2 instances at the same time on the same port? What version
of WLS?
I asked you on 5/16/2003 to show me ...
===============
What do you get from the following commands:
$ java -version
$ which java
===============
I have not seen that. I will not do any more on this without that data.
I also want to see output from
$ echo $PATH
Thanks,
Wayne
Oleg wrote:
I installed WL using SSH (PutTY tool) - as only way to communicatewith Unix.
I am using only console mode. No any X-Windows emulators.
I followed to all console instructions and WL was installed successful.
I run examples, it runs, but doesn't receive request.
It echoes right PATH and CLASSPATH.
I don't see any message about reading config.xml, as usually was done.
I run another instance of WL on same port and it runs without complains.
Usually second instance stops with "Requested shutdown ..." if startedon busy
port.
Looks like WL doesn't read or can't find config.xml and doesn't throwexceptions.
Thank you.
Oleg.