PeopleSoft Weblogic Server - Startup Problems

PeopleSoft Weblogic server in Solaris behaves strangely at times. The webserver will be taken down using StopPIA.sh and when you try starting the webserver with startPIA.sh, you will not be able to get to the sign on page.

If you look at the weblogic log file, PIA_weblogic.log, you can find the following exception being logged

####<Apr 23, 2010 2:40:18 PM EST> <Info> <Socket> <server> <PIA> <ListenThread.Default> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>

####<Apr 23, 2010 2:40:18 PM EST> <Emergency> <WebLogicServer> <server> <PIA> <ListenThread.Default> <<WLS Kernel>> <> <BEA-000351> <Unable to create a server socket on Channel Default for port: 8200. java.net.BindException: Address already in use Perhaps another process is using port 8200.>

==> Here the server is just not starting up, because there is already a process that is using the port 8200. If we find the process and kill it, we should be able to bring the server back.

####<Apr 23, 2010 2:40:18 PM EST> <Emergency> <WebLogicServer> <server> <PIA> <SSLListenThread.Default> <<WLS Kernel>> <> <BEA-000351> <Unable to create a server socket on Channel Default for port: 8250. java.net.BindException: Address already in use Perhaps another process is using port 8250.>

####<Apr 23, 2010 2:40:18 PM EST> <Emergency> <Security> <server> <PIA> <main> <<WLS Kernel>> <> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>

####<Apr 23, 2010 2:40:18 PM EST> <Emergency> <WebLogicServer> <server> <PIA> <main> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>

If you attempt to make another shut down at this stage, (though you wouldn't), you will get this message

Failed to connect to t3://<server>:8200: Destination unreachable; nested exception is:

 java.net.SocketTimeoutException: Read timed out; No available router to destination

So, the objective for us would be to start the server and get into the PeopleSoft environment back. To find which process is currently using the port 8200, I used the following shell script:

#!/bin/ksh

#

# find the process that makes the weblogic server preoccupied

#

line='-------------------------------------------------------------------------'

pids=`/usr/bin/ps -ef | sed 1d | awk '{print $2}'`

# Prompt users or use 1st cmdline argument

if [ $# -eq 0 ]; then

         read answer?"For which port do you need the PID:  "

else

         answer=$1

fi

# Check all pids for this port, then list that process

for f in $pids

do

         /usr/proc/bin/pfiles $f 2>/dev/null | /usr/xpg4/bin/grep -q "port: $answer"

         if [ $? -eq 0 ] ; then

                 echo "$line\nPort: $answer is being used by PID: \c"

                 /usr/bin/ps -o pid -o args -p $f | sed 1d

         fi

done

exit 0

When this script is triggered with the port number specified, this script would list all the PIDs that are busy with the port to which the current server is trying to attach itself.

When all these processes are killed, try the StartPIA.sh again, and the server would be up and running.

####<Apr 23, 2010 2:49:32 PM EST> <Notice> <WebLogicServer> <server> <PIA> <main> <<WLS Kernel>> <> <BEA-000329> <Started WebLogic Admin Server "PIA" for domain "Domain" running in Production Mode>

####<Apr 23, 2010 2:49:32 PM EST> <Notice> <WebLogicServer> <server> <PIA> <ListenThread.Default> <<WLS Kernel>> <> <BEA-000355> <Thread "ListenThread.Default" listening on port 8200, ip address *.*>