Automating Weblogic Startup/Shutdown on Linux
hello and hope you fine
im using weblogic 10.3 with oracle db 11g on CentoOS 5.5
everything is working fine
but my problem is that i want to startup/shutdown weblogic on system start/shutdown
i defined weblogic as service ( i tried all levels) and it works but the problem is
when the system is booting it start weblogic but it stops continue system boot!
i also tries put the start weblogic on the .bash_profile
the system boot but when im trying to login it stops because the same problem
(weblogic startup and prevent contitnue the loginin )
i also tried to add startWeblogic in /etc/rc.d/rc.local
and the same problem when weblogic start system cant continue booting
i also tried using nohup
also the same problem
so how can i start/shutdown weblogic ?
and thanks for help
Edited by: user13113692 on Aug 2, 2010 3:22 AM
thank you for your replay
but its the same
when server is booting
the weblogic start and goes to the running state
it stops continue the other services and
the server boot could not continue
here is some of my script
#!/bin/sh
WEBLOGIC_HOME=/root/Oracle/Middleware/user_projects/domains/mydomain/
# source function library
. /etc/rc.d/init.d/functions
case "$1" in
start)
echo "Starting weblogic..."
cd $WEBLOGIC_HOME
su root $WEBLOGIC_HOME/bin/startWebLogic.sh &
stop)
echo "Stopping weblogic..."
cd $WEBLOGIC_HOME
su root $WEBLOGIC_HOME/bin/stopWebLogic.sh &
i also tried something like this to grape all the output to a log file
but the problem here is that the weblogic give me a exception about the paths
case "$1" in
start)
echo "Starting weblogic..."
cd $WEBLOGIC_HOME
su root $WEBLOGIC_HOME/bin/startWebLogic.sh ALL > ${WEBLOGIC_HOME}/logz/start.log 2>&1 &
stop)
echo "Stopping weblogic..."
cd $WEBLOGIC_HOME
su root $WEBLOGIC_HOME/bin/stopWebLogic.sh ALL >${WEBLOGIC_HOME}/logz/stops.log 2>&1 &
i also tried this with the standalone weblogic and its the same
any help will be appreciated
Similar Messages
-
Automated Oracle Startup & Shutdown
I am trying to get make my Oracle database shutdown and startup
automatically at boot, but am having a hard time getting this to
work properly. I have created a file in /etc/rc.d/init.d called
dbora:
case "$1" in
'start')
su - oracle -c $ORACLE_BASE/admin/bin/dbstart.sh &
'stop')
su - oracle -c $ORACLE_BASE/admin/bin/dbshut.sh &
esac
I also created the following links in EVERY (out of frustration)
/etc/rc.d/rc#.d directory:
lrwxrwxrwx 1 root root 22 Jul 1 10:12 S99dbora -
/etc/rc.d/init.d/dboralrwxrwxrwx 1 root root 22 Jul 1 10:12 K30dbora -
/etc/rc.d/init.d/dboraThe problem does not really appear to be linked to the actual
database shutdown or startup, but rather with LINUX. I have
replaced the contents of dbstart.sh & dbshut.sh with a simple
echo redirect to file to prove this out. Specifically, here is
what is happening:
* Running "dbora start" or "dbora stop" manually always works.
* Neither "dbora start" or "dbora stop" work when booting or
switching runlevels, although the message STARTING DBORA does
scroll past the console.
I have several people look at this here and no one can figure
out why this isn't working. Can you assist?
nullPeter,
Normally the problem here is that the environment is not set, or
is not being set correctly OR that things that Oracle needs to be
available have already been killed (lower run level) or have not
been started (higher run level).
Check that the environment is OK when the dbora script is run and
check that your scripts are called in the right order of things
when moving between run levels.
Regards,
Mark
Pete Petersen (guest) wrote:
: I am trying to get make my Oracle database shutdown and startup
: automatically at boot, but am having a hard time getting this
to
: work properly. I have created a file in /etc/rc.d/init.d called
: dbora:
: case "$1" in
: 'start')
: su - oracle -c $ORACLE_BASE/admin/bin/dbstart.sh &
: 'stop')
: su - oracle -c $ORACLE_BASE/admin/bin/dbshut.sh &
: esac
: I also created the following links in EVERY (out of
frustration)
: /etc/rc.d/rc#.d directory:
: lrwxrwxrwx 1 root root 22 Jul 1 10:12 S99dbora
: > /etc/rc.d/init.d/dbora
: lrwxrwxrwx 1 root root 22 Jul 1 10:12 K30dbora
: > /etc/rc.d/init.d/dbora
: The problem does not really appear to be linked to the actual
: database shutdown or startup, but rather with LINUX. I have
: replaced the contents of dbstart.sh & dbshut.sh with a simple
: echo redirect to file to prove this out. Specifically, here is
: what is happening:
: * Running "dbora start" or "dbora stop" manually always works.
: * Neither "dbora start" or "dbora stop" work when booting or
: switching runlevels, although the message STARTING DBORA does
: scroll past the console.
: I have several people look at this here and no one can figure
: out why this isn't working. Can you assist?
null -
How to customize oracle to manually startup/shutdown in Linux ?
Hello Friends,
I am having Oracle 10g XE installed on Ubuntu 7.10..It is working fine..
I want to make it custom startup and shutdown..(As of now it is starting up when gutsy boots) as it is not required Oracle to run each time...Please suggest the way to do it.
Thanks in AdvanceHi,
For Ubuntu, there has an alternative utility for editing runlevels that can be used just like chkconfig on RedHat.
To install:
# sudo apt-get install sysv-rc-conf
Then,
# sysv-rc-conf oracle-xe off
Cheers
Terry -
Automating Oracle Startup/Shutdown
I have been unable to start up Oracle automatically after
rebooting the system. I am able to start it as the root user and
executing /etc/init.d/oracle8i script but for some reason it
won't do it automatically. I have done the ln -
s /etc/init.d/oracle8i /etc/rc3.d/S99oracle8i and thought it
would work but it hasn't. Any ideas?Try to use /etc/oratab file
-
Is there startup/shutdown-like capability for EAR deployment/undeployment ?
We have our application bundled in an EAR. We have the need
to do some things as the application is deployed and undeployed.
Is there the capability for having some class do something
on these events, much like the startup and shutdown classes?
Note our application is not the only app on the server, so we
can't necessarily commandeer the weblogic startup/shutdown classes.
This is with WLS7SP2, but we are looking to move to WLS8.1.
Thanks!Jay Schmidgall wrote:
We have our application bundled in an EAR. We have the need
to do some things as the application is deployed and undeployed.
Is there the capability for having some class do something
on these events, much like the startup and shutdown classes?
Note our application is not the only app on the server, so we
can't necessarily commandeer the weblogic startup/shutdown classes.
This is with WLS7SP2, but we are looking to move to WLS8.1.Yes, in 8.1 you can do this. See the javadocs for
weblogic.application.ApplicationLifecycleListener. We use it
successfully so I can report that it does indeed work!
Robert -
Startup/Shutdown script for OBIEE 11g on Linux
Hi all,
as a follow-up to [url http://forums.oracle.com/forums/thread.jspa?messageID=4546010]an earlier thread by some fine gentleman, I have improved the original startup/shutdown script for Linux a bit, making sure that all processes are handled correctly. The script has been tested and works fine on CentOS 5.5 with Oracle BI 11.1.1.3.0 in a clustered configuration. Instructions:
Manual start/stop:
> service obiee start
> service obiee stop
> service obiee status
Automatic start/stop during boot sequence:
> chkconfig --add obiee
> chkconfig obiee on
Note that in order for the procedure to go through smoothly, you need to provide the admin credentials (username/password, defaulting to weblogic/weblogic) in three different places:
1. In configuration file <FMW_HOME>/user_projects/domains/<domain name>/servers/AdminServer/security/boot.properties for the administration server;
2. In script <FMW_HOME>/user_projects/domains/<domain name>/bin/startManagedWebLogic.sh (variables WLS_USER and WLS_PW) for the managed server;
3. In the startup script itself (variables BIEE_USER and BIEE_PASSWD) for shutting down the managed server.
Complete logs are available in /var/log/obiee-start (-stop).log files.
Please comment as necessary,
Chris
#!/bin/bash
# File: /etc/init.d/obiee
# Purpose: Start and stop Oracle Business Intelligence 11g components.
# chkconfig: 2345 99 10
# description: Manage OBIEE service.
# These values must be adapted to your environment.
ORACLE_OWNR=oracle # Local Unix user running OBIEE
ORACLE_FMW=/home/oracle/biee # Deployment root directory
BIEE_USER=<username> # BIEE administrator name
BIEE_PASSWD=<password> # BIEE administrator password
BIEE_DOMAIN=<domain name> # Domain name
BIEE_INSTANCE=instance1 # Instance name
BIEE_SERVER=bi_server1 # Server name
BIEE_MANAGER_URL=<hostname>:7001 # Admin server URL (hostname:port)
# These should require no change.
WL_PATH=$ORACLE_FMW/wlserver_10.3/server/bin
BIEE_PATH=$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/bin
ORACLE_INSTANCE=$ORACLE_FMW/instances/$BIEE_INSTANCE
export ORACLE_INSTANCE
START_LOG=/var/log/obiee-start.log
STOP_LOG=/var/log/obiee-stop.log
SUBSYS=obiee
start() {
echo "********************************************************************************"
echo "Starting Admin Server on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$BIEE_PATH/startWebLogic.sh" &
wait_for "Server started in RUNNING mode"
echo "********************************************************************************"
echo "Starting Node Manager on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$WL_PATH/startNodeManager.sh" &
wait_for "socket listener started on port"
echo "********************************************************************************"
echo "Starting Managed Server $BIEE_SERVER on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$BIEE_PATH/startManagedWebLogic.sh $BIEE_SERVER http://$BIEE_MANAGER_URL" &
wait_for "Server started in RUNNING mode"
echo "********************************************************************************"
echo "Starting BI components on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl startall"
echo "********************************************************************************"
echo "OBIEE start sequence completed on $(date)"
echo "********************************************************************************"
stop() {
echo "********************************************************************************"
echo "Stopping BI components on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl stopall"
echo "********************************************************************************"
echo "Stopping Managed Server $BIEE_SERVER on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$BIEE_PATH/stopManagedWebLogic.sh $BIEE_SERVER t3://$BIEE_MANAGER_URL $BIEE_USER $BIEE_PASSWD"
echo "********************************************************************************"
echo "Stopping Node Manager on $(date)"
echo "********************************************************************************"
pkill -TERM -u $ORACLE_OWNR -f "weblogic\\.NodeManager"
echo "********************************************************************************"
echo "Stopping Admin Server on $(date)"
echo "********************************************************************************"
su $ORACLE_OWNR -c "$BIEE_PATH/stopWebLogic.sh"
echo "********************************************************************************"
echo "OBIEE stop sequence completed on $(date)"
echo "********************************************************************************"
wait_for() {
res=0
while [[ ! $res -gt 0 ]]
do
res=$(tail -5 "$START_LOG" | fgrep -c "$1")
sleep 5
done
case "$1" in
start)
echo "********************************************************************************"
echo "Starting Oracle Business Intelligence on $(date)"
echo "Logs are sent to $START_LOG"
echo "********************************************************************************"
start &> $START_LOG &
touch /var/lock/subsys/$SUBSYS
stop)
echo "********************************************************************************"
echo "Stopping Oracle Business Intelligence on $(date)"
echo "Logs are sent to $STOP_LOG"
echo "********************************************************************************"
stop &> $STOP_LOG
rm -f /var/lock/subsys/$SUBSYS
status)
echo "********************************************************************************"
echo "Oracle BIEE components status...."
echo "********************************************************************************"
su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl status"
restart)
$0 stop
$0 start
echo "Usage: $(basename $0) start|stop|restart|status"
exit 1
esac
exit 0You can use WLST to start/stop BI Services and it works on both Linux and Windows.
Following link has the sample -
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10541/admin_api.htm#CDEFAHDD -
Startsap & stopsap on Linux startup & shutdown
Hy everyone!
I have a simple question: does anyone use startsap/stopsap scripts on Linux startup/shutdown run levels? I mean, when Linux starts up (init 5 run level) it must start SAP using startsap and stopsap on init 0 as well.
It seems to be no problem at all to do that but once that is not set up by default on Linux systems (not in mine for sure) I have decided to ask for a second opinion.
Thanx in advance for any help.
PauloEric,
my goal is a little bit different that that: I'm looking for a way to quick shutdown or startup SAP system with the mininum possible effort during an emergency situation.
Let me explain the situation: we are constantly affected by power down issues, especially in summer time. When such situations occur, we have to quickly shut down as many servers as possible before the power turns completely off (by nobreak).
We are currently working on power infrastructure to avoid those "downs" issues, but until we have fully reached that, we need to get some safe systems shutdowns (at least for production servers).
So I was considering to include at least the stopsap script in init 0 run level on Linux.
What do you think about that?
Thanx for your help until now. It's good to have someone to discuss something like that and exchange experiences/ideas.
Paulo -
WebLogic as daemon on Linux?
Can WL be started as a daemon in Linux?
If so, how?
Is this desirable?
I'm looking for the best way to automate WL on Linux.
Thanks,
Jamie Orchard-HaysJaime,
I would add a simple script in /etc/rc.d/init.d to run the
startWebLogic.sh script. Look at the existing scripts such as httpd,
inetd, etc. These are invoked as "script start|stop|restart". For
example, I copied the ldap file into a file named weblogic under the
/etc/rd.c/init.d directory. I then edited it to only support stop and
start operations. Under Linux-Mandrake 7.1, there exists a Startup
Services application under DrakConf. This application will see the
weblogic script in the init.d directory, and create symbolic links to it
in the rcn.d directories. The n refers to the startup level. Once this
happens you will be able to execute the script directly by typing
/etc/rc.d/init.d/weblogic start|stop, or at system shutdown, a file named
Knnweblogic will be run automatically with the stop command. Conversely,
when the system boots, there will be an Snnweblogic link in the rc5.d
directory. The nn in the link name is a number assigned to allow the
lower numbers to excute earlier. A copy of the weblogic script I made up
follows:
#!/bin/sh
# ldap This shell script takes care of starting and stopping
# the WebLogic application server
# chkconfig: - 70 40
[ -f /home/weblogic/weblogic/startWebLogic.sh ] || exit 0
RETVAL=0
# See how we were called.
case "$1" in
start)
# Start daemons.
echo -n "Starting WebLogic: "
su -l weblogic -c 'cd weblogic;./startWebLogic.sh >/dev/null &'
stop)
# Stop daemons.
echo -n "Shutting down WebLogic: "
su -l weblogic -c 'java weblogic.Admin http://localhost:7001 SHUTDOWN
system ******** >/dev/null ;exit 0'
esac
exit $RETVAL
I have commented out the password. You could probably write a script
readable by the user under which you run weblogic. I am simply su'ing as
user weblogic and having it run some commands. WebLogic requires that the
startWebLogic script be run from the install directory. Having the
weblogic script in init.d simply so something like "su -l weblogic -c
'mystartScript.sh' would probably take care of everything. You could also
make the stop path more robust by having another script immediately after
the su that would check to see when WebLogic actually stops before
exiting. Of course your could also just let killall handle shutdown.
Although I used the ldap script, the httpd would probably be just as good
as a model. The daemon used is a function provided in the Mandrake
Linux. I just haven't fooled with it, so I am executing the code the old
fashioned way. Hope this helps.
George.
Original Message <<<<<<<<<<<<<<<<<<On 9/27/00, 12:18:53 PM, "Jamie Orchard-Hays" <[email protected]>
wrote regarding WebLogic as daemon on Linux?:
Can WL be started as a daemon in Linux?
If so, how?
Is this desirable?
I'm looking for the best way to automate WL on Linux.
Thanks,
Jamie Orchard-Hays -
Automatics Startup database in linux server 2.1
Hi,
How can I setup a file that can startup oracle database (9.2.0.4) after the linux server reboot? Can anyone teach me step by step? ThanksThis will be help you:
DB startup & shutdown in 10g DB on Linux
Joel Pérez -
Installing WebLogic 6.1 on Linux?
I have a few rather basic questions regarding installing WebLogic 6.1 on
Linux.
1. What should I use as a home directory? I know that we use C:\BEA in the
Windows world. I've seen a number of people referring to /usr/local/bea.
Is there a general consensus as to where the home directory should be?
2. What user should run the WL server? Obviously, root is not the best
option. If I create a new account, say "weblogic", what rights/privileges
will the account need to run the server?
3. How can the server be setup to start WL server as a daemon at startup?
Does WL provide startup scripts that can be linked from the /etc/rc.d/rX.d
directories?
Thanks!
- GCHi.
the answer is...it depends.
1. Your home directory can be anywhere. If you are developing I suggest you
install in your user directory. If you are going to be running WLS constantly
in production then you may want a system directory such as the one you mention.
It's traditional to install apps in /usr/local, but I've seen customers install
it in other directories as well.
2. You should not run WLS as root for security reasons. If you are not binding
to a port number below 1025 then this is no problem. If you are then you need
to start WLS as root and configure it to switch to a non-priveliged user after
binding to the port.
3. see http://edocs.bea.com/wls/docs61/faq/server.html#291592. You probably
won't want to use this exact script, but take a look at the command line start
scripts for ideas on how to do this.
Hope this helps,
Michael
Geoffrey Corb wrote:
I have a few rather basic questions regarding installing WebLogic 6.1 on
Linux.
1. What should I use as a home directory? I know that we use C:\BEA in the
Windows world. I've seen a number of people referring to /usr/local/bea.
Is there a general consensus as to where the home directory should be?
2. What user should run the WL server? Obviously, root is not the best
option. If I create a new account, say "weblogic", what rights/privileges
will the account need to run the server?
3. How can the server be setup to start WL server as a daemon at startup?
Does WL provide startup scripts that can be linked from the /etc/rc.d/rX.d
directories?
Thanks!
- GC--
Michael Young
Developer Relations Engineer
BEA Support -
Slow startup/shutdown on WL
Hi,
We're having a performance issue starting/shutting down weblogic 8.1.1 on Solaris 8 on a Sunfire V240 with 4Gb of memory. it takes an average of 15-20 minutes to start the application using command line start.
Here is some background on the environment:
A. Start with java args :
-Xms1536m -Xmx1536m MaxPermSize=128m NewSize=256m MaxNewSize=256m SurvivorRation=8.
B. There is a cron job that starts/stops then imports at night. The shutdown is also slow, so after 2 minutes of attempted FORCESHUTDOWN, we do a 'kill -9' on the process. My guess is that there is still a transcation that needs to finish ( some are fairly large ), and so FORCESHUTDOWN doesnt complete in 2min.
C. There are multiple applications on the server, but even if we remove one of them ( the second ), startup/shutdown takes the same time to start. The second app depends on the first, so we havent removed the first one
D. There have been some database issues as well, running out of database connections. This is due to Connections not being closed, and we are correcting that issue right now, and is not complete.
E. Most of the time, the logs hang on the last statement below in the logs. However, I don't see any consistency in what follows the BEA-101133 message in the logs.
I apologize in advance for asking more than one item in a post, but I have multiple questions that I believe might be related to the slow startup:
1. Will running 'kill -9' on the process have an impact on the startup of WL, as it is trying to recover or restore connections or resources?
2. Once the database connection issues are cleared up ( working on them now), should startup time increase?
3. Any other suggestions to increase the startup time of WL?
####<Apr 26, 2008 6:44:13 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:13 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool
"ds.oem", out of which "10" are available and "0" are unavailable.>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.oem.>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.im for
Pool ds.im.>
####<Apr 26, 2008 6:44:18 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.nice for Pool ds.nice.>
####<Apr 26, 2008 6:44:18 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.core for Pool ds.core.>
####<Apr 26, 2008 6:44:18 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.oem for Pool ds.oem.>
####<Apr 26, 2008 6:44:19 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.wf for
Pool ds.wf.>
####<Apr 26, 2008 6:44:19 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory
"jms.ds.TopicConnectionFactory" is started.>
####<Apr 26, 2008 6:44:19 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040054> <JMSServer "JMServ". No persistent store
configured.>
####<Apr 26, 2008 6:44:20 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040321> <JMSServer "JMServ" is resuming.>
####<Apr 26, 2008 6:44:21 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040010> <JMSServer "JMServ" configured no session pools.>
####<Apr 26, 2008 6:44:22 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040109> <JMSServer "JMServ" is started.>
####<Apr 26, 2008 6:44:22 AM EST> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mysrv.>
tializing Web server mysrv.>First of all I apologize for the late response, and thank you for the replies.
Here is the WebLogic log file from startup. Note there is a lag of between 10:20 and 11:13. I'm not sure of the cause of this, and any hints or resolutions would be appreciated.
Looks like the slowness is occuring when initializing the web server. Both the Apache web server and Weblogic application server reside on the same machine, so it's not a firewall issue.
####<May 11, 2008 10:11:36 AM GMT> <Notice> <WebLogicServer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000327> <Starting WebLogic Admin Server "mysrv" for domain "jmssrv">
####<May 11, 2008 10:11:36 AM GMT> <Info> <WebLogicServer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mysrv" version:
WebLogic Temporary Patch for CR105892 05/29/2003 16:47:19
WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<May 11, 2008 10:11:36 AM GMT> <Info> <WebLogicServer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/oss/bea/license.bea>
####<May 11, 2008 10:11:36 AM GMT> <Info> <RJVM> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mysrv"
Listen Address *
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<May 11, 2008 10:11:37 AM GMT> <Debug> <RJVM> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mysrv"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<May 11, 2008 10:11:39 AM GMT> <Info> <XML> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<May 11, 2008 10:11:41 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<May 11, 2008 10:11:48 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<May 11, 2008 10:11:51 AM GMT> <Info> <Connector> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<May 11, 2008 10:11:56 AM GMT> <Info> <Connector> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<May 11, 2008 10:11:56 AM GMT> <Info> <IIOP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<May 11, 2008 10:11:57 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<May 11, 2008 10:11:58 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<May 11, 2008 10:12:00 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<May 11, 2008 10:12:00 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mysrv.>
####<May 11, 2008 10:12:01 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mysrv] Initialized>
####<May 11, 2008 10:12:01 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101135> <mysrv is the default Web server.>
####<May 11, 2008 10:12:02 AM GMT> <Info> <J2EE> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<May 11, 2008 10:12:04 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<May 11, 2008 10:12:05 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:06 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:07 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:10 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module console of application console is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module console of application console successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:02 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:04 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal2 of application wl_management_internal2 is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal2 of application wl_management_internal2 successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:09 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module console of application console is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module console of application console successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal2 of application wl_management_internal2 is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal2 of application wl_management_internal2 successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JTA> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101239> <HTTP log rotation is date based for the Web server: mysrv.>
####<May 11, 2008 10:19:17 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101243> <HTTP log rotation scheduled to begin at: Mon May 12 10:19:17 GMT 2008. Rotation taking place every: 1440 minutes for the Web server: mysrv.>
####<May 11, 2008 10:19:17 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mysrv] started>
####<May 11, 2008 10:19:17 AM GMT> <Info> <WebService> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<May 11, 2008 10:19:18 AM GMT> <Info> <WebService> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<May 11, 2008 10:19:18 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<May 11, 2008 10:19:18 AM GMT> <Notice> <SNMP Agent> <myservername> <mysrv> <SNMP Service Thread> <<WLS Kernel>> <> <000000> <The SNMP trap version is 1>
####<May 11, 2008 10:19:18 AM GMT> <Info> <SNMP Agent> <myservername> <mysrv> <SNMP Service Thread> <<WLS Kernel>> <> <000000> <SNMP agent is initializating ...>
####<May 11, 2008 10:19:18 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.core" will be tested every "30" seconds.>
####<May 11, 2008 10:19:19 AM GMT> <Info> <SNMP Agent> <myservername> <mysrv> <SNMP Service Thread> <<WLS Kernel>> <> <000000> <SNMP Agent Initialization Complete.
Sending generic coldStart trap ...>
####<May 11, 2008 10:19:24 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:25 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:26 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:26 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:27 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:27 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:27 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:28 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:33 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.core", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.core.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.wf" will be tested every "30" seconds.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.wf" created.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.wf".>
####<May 11, 2008 10:19:34 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "1" resources for pool "ds.wf", out of which "1" are available and "0" are unavailable.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.wf.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.nice" will be tested every "30" seconds.>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:37 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:37 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:39 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:39 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:45 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:45 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:46 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:46 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:47 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:47 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:47 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.nice", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:19:48 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.nice.>
####<May 11, 2008 10:19:48 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.oem" will be tested every "30" seconds.>
####<May 11, 2008 10:19:52 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:52 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:54 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:54 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:54 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:56 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:56 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:56 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:57 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:57 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:00 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:20:00 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:01 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.oem", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.oem.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.im" will be tested every "30" seconds.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:02 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:02 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:09 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:13 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:14 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:14 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:16 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:16 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:17 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.im", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:20:17 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.im.>
####<May 11, 2008 10:20:18 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <>
<BEA-001121> <Created TX Data Source named ds.nice for Pool ds.nice.>
####<May 11, 2008 10:20:19 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.wf for Pool ds.wf.>
####<May 11, 2008 10:20:19 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <B -
How to automate database startup/shutdown in RHEL4
Dear All
I have Oracle 10gR2 database on RHEL4.
If i want to automate database startup/shutdown with OS startup/shutdown,
Then where i need to update about dbstart.sh & dbshut.sh
I have already made entry in /etc/oratab as Y for database SID.
I am using Bourn Shell.
ThanksYou can refer to my post in my Blog
[Automatically StartUp and Shutdown an Oracle Database in Linux OS|http://kamranagayev.wordpress.com/2008/12/22/automatically-startup-and-shutdown-database-in-linux-os/]
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com
[Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/] -
Automate startup/shutdown thru script on windows
WIndows 2003
oracle 9.2.0.7
I am new to oracle on windows.
Is there way to automated startup/shutdown database thru script on windows?
I want to schedule this task at perticuler time.
ThanksYou have to come up with your own script to shutdown.
There's a sample here
[Start / Shut Oracle with a Click (Windows Script) |http://it.toolbox.com/wiki/index.php/Start_/_Shut_Oracle_with_a_Click_(Windows_Script)]
Edited by: yingkuan on Oct 9, 2008 5:05 PM -
Unix startup/shutdown of Livecache
Hi all,
I would like to know how one can startup/shutdown Live cache from the operating system without have to run a RFC to a function module. Is it possible to simply run dbmcli and issue db_offline/db_online? Please assist.
Thanks,
Frank Magliozzi
[email protected]Frank,
if you want to set up HA for liveCache, SAP note 952783 provides all the info, such as the various options available for HA.
This note points to further notes, which has info on shutdown/restart of liveCache in a HA environment, for e.g.:
Note 319835 : Availability of liveCache on Microsoft Cluster.
For all supported UNIX platforms, the operating system partners offer cluster agents for liveCache. Also, hot standby for liveCache has been implemented for:
- IBM (SVC, ESS, DS8000)
- EMC (Symmetrix)
Contact your hardware partner if you are interested in these options.
For Linux, the product LifeKeeper by Steeleye (<http://www.steeleye.com>), among others, supports liveCache.
Thanks,
Ashwath -
Is several entries of startup / shutdown possible?
hi
does Weblogic 8.1 really support several startup classes in weblogic-application.xml?
i have a few <startup> sections, but it seems that only the first one is executed
(same for shutdown section) - i shuffled them around to make sure it's the case.
however in the docs it says: "<startup>Zero or more. Used to register user-defined
startup classes."
out of the structure below, only StartupClass1 and ShutdownClass2 are executed.
any idea why?
<!DOCTYPE weblogic-application PUBLIC '-//BEA Systems, Inc.//DTD WebLogic Application
8.1.0//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd'>
<weblogic-application>
<startup>
<startup-class>
StartupClass1
</startup-class>
<startup-uri>
ejb-r1-1.jar
</startup-uri>
</startup>
<startup>
<startup-class>
StartupClass2
</startup-class>
<startup-uri>
ejb-r1-1.jar
</startup-uri>
</startup>
<startup>
<startup-class>
StartupClass3
</startup-class>
<startup-uri>
ejb-r1-1.jar
</startup-uri>
</startup>
<shutdown>
<shutdown-class>
ShutdownClass2
</shutdown-class>
<shutdown-uri>
ejb-r1-1.jar
</shutdown-uri>
</shutdown>
<shutdown>
<shutdown-class>
ShutdownClass1
</shutdown-class>
<shutdown-uri>
ejb-r1-1.jar
</shutdown-uri>
</shutdown>
<shutdown>
<shutdown-class>
ShutdownClass3
</shutdown-class>
<shutdown-uri>
ejb-r1-1.jar
</shutdown-uri>
</shutdown>
</weblogic-application>
thanks
andreiYes, this is unfortunately a known bug. It's fixed in 8.1SP2.
Until then, you'll have to email [email protected] and ask for a patch for
CR110084
-- Rob
Andrei Rusakou wrote:
hi
does Weblogic 8.1 really support several startup classes in weblogic-application.xml?
i have a few <startup> sections, but it seems that only the first one is executed
(same for shutdown section) - i shuffled them around to make sure it's the case.
however in the docs it says: "<startup>Zero or more. Used to register user-defined
startup classes."
out of the structure below, only StartupClass1 and ShutdownClass2 are executed.
any idea why?
<!DOCTYPE weblogic-application PUBLIC '-//BEA Systems, Inc.//DTD WebLogic Application
8.1.0//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd'>
<weblogic-application>
<startup>
<startup-class>
StartupClass1
</startup-class>
<startup-uri>
ejb-r1-1.jar
</startup-uri>
</startup>
<startup>
<startup-class>
StartupClass2
</startup-class>
<startup-uri>
ejb-r1-1.jar
</startup-uri>
</startup>
<startup>
<startup-class>
StartupClass3
</startup-class>
<startup-uri>
ejb-r1-1.jar
</startup-uri>
</startup>
<shutdown>
<shutdown-class>
ShutdownClass2
</shutdown-class>
<shutdown-uri>
ejb-r1-1.jar
</shutdown-uri>
</shutdown>
<shutdown>
<shutdown-class>
ShutdownClass1
</shutdown-class>
<shutdown-uri>
ejb-r1-1.jar
</shutdown-uri>
</shutdown>
<shutdown>
<shutdown-class>
ShutdownClass3
</shutdown-class>
<shutdown-uri>
ejb-r1-1.jar
</shutdown-uri>
</shutdown>
</weblogic-application>
thanks
andrei
Maybe you are looking for
-
I was prompted to upgrade Firefox yesterday to 4.0.1 and did so. Since then Firefox keeps freezing. I will be on a website or in a google search and it freezes and I am unable to quit firefox- can't even force quit so must reboot my computer. This ha
-
IS COMPUTER FIX, INC A 3rd party Independent Tech Support Provider FOR APPLE? THEY CHARGED AS 339.00 DOLLARS TO REMOTELY REPAIR OUR MACBOOK
-
Hi. A slight variation on an often asked question - but one I haven't found asked elsewhere on the forums: So, my old computer died and I don't have a backup of my iPhone contents. I'm trying to sync to a new instance of iTunes on my new laptop. I ha
-
Retrieving messages stuck in EVENT_QTAB and IP_QTAB?
All, While two Oracle B2Bs were exchanging messages, the network suddenly went down causing messages to be stuck in the AQs- EVENT_QTAB and IP_QTAB. As these are messages are orders, the clients do not wish to lose them. They want to know the followi
-
How do I fix error 4002 in iTunes
How do I ghet rid of the error message 4002 in iTunes?