"Ignore Sessions During Shutdown" and "Graceful Shutdown Sequence"

Hi
I have J2EE application consisting of WEB and EJB layers deployed on WL 8.1
I start the Graceful Shutdown Sequence with Ignore Sessions During Shutdown option set. sessionDestroyed() method of registered HttpSessionListener is fired but at this moment JNDI tree is already empty, EJB module undeployed and the listener is not able to get to application's EJBs.
In the documentation (http://e-docs.bea.com/wls/docs81/adminguide/overview_lifecycle.html#1045901) Ignore Sessions During Shutdown option is explained as follows:
"If you enable this option WebLogic Server will drop all HTTP sessions immediately, rather than waiting for them to complete or timeout."
What does "drop" mean here? Is this some exception to Graceful Shutdown Sequence and the following excerpt from the documentation? : "During a graceful shutdown, subsystems complete in-flight work and suspend themselves in a specific sequence and in a synchronized fashion, so that back-end subsystems like JDBC connection pools are available when front-end subsystems are suspending themselves."
Regards

Hi,
You can use tcodes
SMQR --> To register a queue
SMQS --> To register a destination in Queue Schedular
SMQ1 --> OutBound Queue Details
SMQ2 --> Inbound Queue Details
SXMB_ADMIN --> Manage Queue to register,deregister and activate the queue.
Check the link for more details : http://help.sap.com/saphelp_nw04/helpdata/en/59/d9fa40ee14f26fe10000000a1550b0/frameset.htm
For step details for server start/stop you can search on google for more details. And for an idea check the section Managing the SAP Start-Up Service via the SAP MMC Snap-In in the link https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3e3fad90-0201-0010-2f91-c8907db40bfe
Thanks!
Edited by: sudhir tiwari on Nov 12, 2008 12:00 PM

Similar Messages

  • Random Shutdown and Previous shutdown cause: -x2

    Hi,
    I had twice "random shutdown" for now. My MacBook is about 4 month old and It happend with about 3 weeks between them.
    I tried stress testing it with 'yes >/dev/null' heating it up and cooling it down several times but I could not reproduce the Problem. However, looking at older system.log files, I found the "Previous shutdown cause: -82" lines in there. My question: Some MBs seem to report -72, others -82 as the shutdown cause known as random shutdown but what actually is the difference? Is it possible to guess the time it will take to get it repaired depending on the shutdown cause (which obviously describe two different conditions)?
    Thanks a lot in advance and sorry for my somewhat clumsy english;-)
    Peter

    I don't know where you are in Austria, but I took my RSD macbook to mcshark in Vienna, and they repaired it, replaced the case, and returned it to me in one day. That was last Friday and it's been working great since. They knew all about the heat sink problem, didn't even ask for my user name or password, left my hard drive completely intact - they were absolutely super.
    If you are anywhere near Vienna, call McShark and make an appointment - they'll repair it quickly for sure.

  • Graceful Shutdown of a Content Engine (CE510, CE565)

    May I come back to y.lo's message from January this year. He asked for a shutdown or halt command for CEs.
    There is a possibility to shutdown the NM-CE-BP (network module) with the service-module command form the IOS. There must be something similar in ACNS! In the manuals there is quite often a referenc to "orderly shutdown" or "gracefully shutdown", but I couldn't find the appropriate command anywhere near these references.
    Thanks.

    Its not exactly graceful but I've always done a reload with the console plugged in, then when the BIOS messages come up for accessing the flash (before the disk scan), I power it off. The theory is the disks have been cleanly shutdown and the linux subsystem will flushed the filesystems and the content engine isn't actually running. If there is a command I'd like to know it as well.
    regards
    Mark

  • Please Help with Shutdown and Next Steps

    Hello,
    In the process of trying to back the Lacie External Hard drive which has 50 + gigs of valuable information, the computer locked up and it had to be shutdown. The power was turned off and turned back on. I purchased Disk Warrior and was able to regain access to all of my files. I then went to backup the disk. Itunes was open with nothing playing and mydesktop went blank. Everything on the computer was acting funny. I could not close itunes (it kept coming back) nor would things open. I also can not shut down the computer and the external drive is still connected so Im afraid it may do irreparable damage if I shut it down hard. Mac even identified that it needed to shutdown and said (Shutdown in 60 seconds, counted down and nothing happened). Can someone please advise me on my best course of action to try and cleanly shutdown the computer and reboot (Hopefully, it will remount the desktop). I am fairly new to Mac's so I would appreciate any help I can get. thanks.
    Scott

    Hi Scott, not a warm fuzzy feeling I'm sure. So you were backing up your mac and POOFF!!! Everything from there was all screwed up....Did I get that right? The first thing I would do is insert the install disc and restart the computer..If you have to shut it down by holding the power button...do it. Restart and hold the "C" key down after you hear the tone and release it when you see the Apple logo. Choose your language and when the install screen comes up choose "Utilities>disk utilities"....Repair Disc and then repair permissions. Close and quit installer.
    The data on your computer should have been untouched by the back-up operation. It is just copying your Macintosh HD to the Lacie. What program were you using??? In the future you can open the activity monitor located Applications>Utilities>Activity Monitor and select Active processes ---if it opens in your dock but not on your desktop, click the dock icon---this will show you what is working at the time and if its not responding. ---Just because its not responding doesn't mean its locked up. But from here you could have chosen the iTunes that would not quit and forced it to quit...same with any program running--BE CAREFUL WHAT YOU SHUT DOWN--if you don't know what it is leave it alone or get on the web and find out.
    There are many more things that could be the problem but try these first and get back I'll try to get ya going...
    Good luck, glynn

  • A UPS model that works with Mac Native software to do a graceful shutdown and automatic restart during a power failure.

    I've tried 3 UPS's (2 APC and one TripLite) that state they are OSX compatible, however, they do not fully respond to the native osx setting in (system Preferences/ Energy Saver/ UPS/Start up automatically after a power failure). This is what happens:
    During a power outage, the OS does a graceful shutdown, but does not reboot when power is restored. 
    Apparently, the UPS is not notified to turn off during the shut down process. The power (on-Off-On) cycle is required by the mac to restart.
    Trip lite tech support says they have software that works with Windows and linux to do this, but not mac.
    I've tried two older APC UPS's, One Smart UPS1500 and a Back-UPS 1500 with the same result on two different servers and one iMac.
    At this point I'm looking for a make and model of a UPS that does work. If anyone can verify a make and model that actually does this, I'd greatly appreciate it.
    Its a simple test, just pull the plug on your UPS, wait for the system to shut down, and then plug the UPS back in. The system should reboot.

    Many of the CyberPower UPS units are compatible. Checkout the home solutions on this page: http://www.cyberpowersystems.com/products/ups-systems.html

  • Systemd - kdm - xfce session: shutdown and reboot disappears randomly

    I use systemd and kdm as login manager; my desktop is XFCE.
    Immediately after login, if I click the logout button applet in the xfce panel, I can access all the options (shutdown, reboot, etc).
    But sometimes, after a while during the session, the shutdown and reboot option simply disappear - only logout works. If I log out to KDM and then again log in, they reappear.
    Does anyone have a clue about this?

    Just FYI the wikis were updated:
    Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
    https://wiki.archlinux.org/index.php/Sl … vironments
    SLiM is also ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must not use --with-ck-launch from your .xinitrc or slim.conf login_cmd.
    https://wiki.archlinux.org/index.php/Xfce#Manually

  • WLAN Controller and Location appliance graceful shutdown?

    Does anyone know if there is a supported graceful shutdown method/command for the
    4400 series WLAN Controller and 2700 Location Appliances?
    This weekend our server room will be undergoing maintenance and will experience a total power outage for a 4 hour period.  It is our intent to manually bring all equipment down (hopefully in a graceful manner) and then back up once the maintenance is completed.  As a result does anyone know if special precaution is needed to shutdown these 2 appliances, or can we simply bring down these devices hard which is the case with most other Cisco equipment?
    Thanks in advance

    Hi Mark,
    Channel 1, 6, and 11 are just about as non-overlapping as 1, 7, and 13. There's an insignificant amount of overlap, so it's just as plausible of a solution, even in Europe. I honestly don't know why you wouldn't use the extra channels to eliminate the minor overlap - every bit helps.
    The "channel blanket" or "virtual cell" WLAN design philosophy is rapidly spreading. Cisco maintains that it's a standards violation and I've heard no talk of them purchasing the not-to-be-named company or of them adopting the same design philosophy. I sincerely hope that they do one of the two soon, however, because it's very good design that's difficult for Cisco to compete against.

  • ILOM feature "Graceful Shutdown and Power Off"

    Hi,
    We are using Sunblade 6250/6270s, with a stripped down SLES linux installed. We would want to be able use the ILOM feature "Graceful Shutdown and Power Off", but have failed doing this so far. What is required from the configuration and/or operating system to support this power off alternative? I have searched but not found any information on this topic.
    Thanks,
    Harri

    The ILOM "Graceful Shutdown and Power Off" equal you press power button.
    The SLES GUI (init 5) it will popup a window to let you confirm your action when you press the power button.
    In the command line interface (init 3) when you press the power button your system Graceful Shutdown and Power Offed.

  • Node and domain shutdown after windows session logout

    Hello
    I made this script to launch all services and start ifs server at the startup of the computer :
    @echo off
    REM +++++++ Infra_START +++++++++
    set ORACLE_SID=iasdb
    set ORACLE_HOME=C:\Infrastructure
    set PATH=%ORACLE_HOME%\bin;%PATH%
    net start OracleInfrastructureTNSListener
    net start OracleServiceIASDB
    oidmon start
    ping 127.0.0.1 -n 10 -w 1000 > null
    oidctl connect=iasdb server=oidldapd instance=1 start
    ping 127.0.0.1 -n 10 -w 1000 > null
    REM +++++++ IFS_START +++++++
    set ORACLE_SID=database
    set ORACLE_HOME=C:\Files
    set PATH=%ORACLE_HOME%\bin;%PATH%
    call %ORACLE_HOME%\dcm\bin\dcmctl start -ct ohs -v
    call %ORACLE_HOME%\dcm\bin\dcmctl start -co OC4J_iFS_files -v
    call %ORACLE_HOME%\bin\webcachectl start
    call %ORACLE_HOME%\ifs\files\bin\ifsctl start
    REM +++++++ Infra_START +++++++++
    set ORACLE_SID=iasdb
    set ORACLE_HOME=C:\Infrastructure
    set PATH=%ORACLE_HOME%\bin;%PATH%
    net start OracleInfrastructureEMWebsite
    it works correctly. When user is logged on the server, there is no problem but when the user is logged out the node and domain shutdown.
    I'm using Ifs (Oracle Collaboration Suite 9.0.3) on Windows 2000 Pro
    Can you help me to solve my problem ?
    (sorry for my english)

    See this thread:
    Its a limitation of Java on Windows - but there are some workarounds.
    Re: Please read if considering iFS for production.

  • Elgato video to USB has become unreliable after shutdowns and restarts

    I have Yosemite 10.10 on an early 2009 iMac, and an Elgato Video capture device with latest software (1.1.5)
    The messages "Device could not be initialized" and also "Please connect your Elgato Video capture hardware to any USB 2.0 port" come up after I have had a shutdown and restart.
    For 2 or 3 years i have operated this system with no trouble, but as the iMac software became upgraded, and also the Elgato S/W upgraded, the problem has come up, so now I am reluctant to shut down.  However, there are times it must be, such as when the power company shuts service down for maintenance - happens a lot lately.  I have tried different ports, and done the unplug and replug routine, but it takes dozens or even hundreds of attempts until one time it works.  then i have to be sure not to "quit" after a recording session, or the problem comes up all over again. Also I tried using a USB hub, with no success.  Also, I have tried to reset of the USB bus routine (Command-Option-P and R keys during startup) with no success.

    Get rid of CleanMyMac and DivX. Add much more RAM. You don't have nearly enough for all that you are trying to load.

  • Mac Pro crashing on shutdown (and some other things)

    The following behavior began about 4 or 5 days ago...
    Mac Pro crashes/freezes every time I shutdown (or Restart).  Some process seems to be not quitting on shutdown - the screen goes blue and I get the spinning beachball. It'll just hang like that indefinitely.  To get it to shut down, I have to hold the power button for several seconds.  After starting up again, the machine *mostly* runs fine, but there are some apps/services that either just don't do anything, or causes the Mac to hang, or get into a funk state. These other things that seem to destabilize it include:
    Apple menu > About this Mac: nothing happens (no dialog)
    iTunes: dock icon just bounces, iTunes never launches
    System Prefs > Accounts > Login items: System Prefs hangs. Force quit allows Prefs to open again.
    Some apps/services also cause things to hang:
    Activity Monitor: quitting some processes causes Actvity Monitor to freeze
    Clicking SOHO Notes (tab alonmg the edge of the monitor) results in spinning beachball
    Rolling over Linotype FontExplorer in the Dock causes the Dock to freeze, FontExporer never opens
    There are probably other things that would make it hang, I have not gone looking for them all
    System details:
    Mac Pro 4,1 .66 ghz, 8 GB RAM
    Mac OSX 10.6.8
    Dual monitors, two internal hard drives (internal; drive A, internal drive B), multiple external FW hard drives attached
    I have already done the following:
    Disk Utility: Verified and Repaired Disk Permissions
    Disk Utility: Verified Disk, Repaired Disk - this found errors, and suggested reformat/reinstall
    I have already booted off internal drive B and ran Disk Utility, then restarted and booted off internal drive A again.  No difference.
    I have Time Machine backups on an external 1 TB FW drive.
    Late last night, I restarted, inserted my original Snow Leopard DVD, launched the MacOSX installer. Recovered a prior system by choosing Utilities > Restore System From Backup, selected a Time Machine backup a few days old (a day or two prior to the problem begining) on the external 1 TB FW drive, and initiated the restore.  The estimated restore time was about 5 hours, so I went to bed and let it run.  Got up early, and checked: it said the Restore operation was successful.  I was relieved.  But the same conditions continued - launching or rolling over the items listed above cause the same freeze/crash/hangs.  Hangs on shutdown, only way to kill things is the power button.  So now I'm disappointed.
    I do have multiple backups of my data files across the external hard drives, but this is a large machine with a lot of stuff on it, and I'd really like to recover things wholesale, rather than having to reconstruct accounts and other things.  Before I go to bed tonight, I'm going to take another shot at recovering the system from a Time Machine backup - this time, I'll pick a backup that's from a full week before the problems started (the idea being that maybe the backup I picked last time was not far enough back from whatever incident caused all this).
    If the week-old Time Machine backup works, great. But if not...any suggestions?
    Additional data points...
    Nothing new was installed or updated (as far as I know, and I generally pay attention) in the days prior to the problem.
    The last thing I recall doing on the computer before the problem began, was burning a DVD (using Toast) - something I do all the time. After that operation, I tried to shut down, and it froze.
    The primary internal hard drive partition (internal drive A) seems to be the only one that's having trouble: if I reboot off of internal drive B, the problems do NOT occur - no hang on quit, etc.
    That suggests it's not a hardware problem (logic board, etc.) but is something about the System on drive A.
    It *could* be bad sectors on drive A - but I have some questions about that...
    When I did the full system recovery via the MacOS installer (pulling the old system from Time machine), does the destination drive get reformatted? I don't recall being asked the usual partition/formatting questions.
    When the installer does a system restore, does it do any integrity checking on the target drive, or does it just blindly lay down bits?
    Does this "freeze on shutdown" (and related behaviors) sound familiar?
    Any tips/suggestions to fix this?
    Thanks in advance.

    More info and a question...
    Did another full restore (from a Time machine backup on an external drive) last night - picked a backup from from 10 days ago, long before things became problematic.  Still having the same issues.
    So, I'm thinking the next thing to try is a low-level reformat of the internal drive(s) and then restore again.  I have a couple questions about the finer points of that...
    I'm following the instructions in this KB document: Mac OS X 10.6: Recovering your entire system.
    Inserting my original Snow Leopard DVD, launching the MacOS installer, restarting, in the installer choosing Restore System from Backup.  It appears that there is no re-formatting of the target drive in this case - it just over-writes.
    My questions...
    The contents of the target drive are going to get wiped and overwritten anyway. Do I have anything to lose/to risk by reformatting FIRST (using Disk Utility), then booting off the install DVD and restoring then?
    My 1 TB internal drive is partitioned into the primary 750 GB partition (which is the problematic one) and a secondary 250 GB partition (which boots and runs fine).  The secondary partition has some data I would prefer not to lose.  I assume that if want to do a full reformat of the internal drive, that means the whole drive - both partitions - will be wiped (that is, I cant reformat just one partition on a single physical drive without reformatting the second partition).  Correct?
    I suppose I can back up the data that resides on the second partition to an additional external drive (I have extras) if needed - not a huge deal.
    Do my new partition sizes need to exactly match the sizes of the original partitions?  Neither is completely full, but I want to make sure that I will be able to restore the system and contents of the primary partition even if the new partition size is not bit-by-bit the exact same size as the old partition (I assume the new partition size just needs to be large enough to hold the backup - correct?).
    So....I'm looking at the following sequence:
    Back up the data I want off the secondary partition to an external drive
    Boot off the Snow Leopard install DVD
    Run Disk Utility and reformat (fully erase) the internall 1 TB drive
    Partition that 1 TB internal drive to (more or less) the two previous (about) 750 GB + 250 GB partitions
    Restore a recent Time Machine backup (from an external FW drive) to partition #1
    Reasonable plan?  Anything I'm missing here?  Any other steps I should take?
    Thanks for any help.

  • XFCE - Shutdown and Reboot buttons greyed-out (SOLVED)

    This issue cropped up for me a couple of weeks ago.  Just sat down to try and find a solution.  Followed several suggestions from several posts to no avail.
    Finally discovered that the syntax for achieving this in "/etc/sudoers" has evidently changed.
    This is what I got from the XFCE site: http://forum.xfce.org/viewtopic.php?pid=21331 and is very similar to what's in the Arch Wiki, https://wiki.archlinux.org/index.php/Al … o_Shutdown. So I had been using the following line in /etc/sudoers and it had been working:
    %users mylaptopname=NOPASSWD: /usr/lib/xfce4/xfsm-shutdown-helper
    At some point in an XFCE upgrade the path to "xfsm-shutdown-helper" changed to "/usr/lib/xfce4/session/xfsm-shutdown-helper"
    I changed the path to "xfsm-shutdown-helper" but that didn't solve the problem.
    Finally I tried this in /etc/sudoers:
    %users  ALL=(ALL)       NOPASSWD: /sbin/shutdown -h now,/sbin/reboot
    And all the usual options in the shutdown menu re-appeared.
    Hope this helps someone.
    (Edited to show the link to the the XFCE forums and the Wiki.)
    Last edited by whatshisname (2011-11-25 16:09:31)

    Replying to my own post because of what I've discovered since I first posted this.
    Most importantly, the fix which I thought had fixed this problem didn't really work.  I was snookered into thinking it had.  But I've found another solution which appears to be working now, thus this post.
    Here's what I've found.
    I had no login/display manager on my laptop.  I was auto-logging into my desktop with this setting in /etc/inittab:
    x:5:once:/bin/su myusername -l -c '/usr/bin/startx >/dev/null 2>&1'
    The snooker alluded to above was this:  If I booted to a command line and issued "startx" to start XFCE, I would have the shutdown and reboot buttons available on the logout dialog.
    But if I booted directly into the desktop, I didn't.  It's taken me a while to figure out that this is what was going on.
    Even though my old setup had worked for the almost 2 years I've been using Arch and XFCE, some upgrade somewhere in  recent months prevented it from working any longer.
    My final fix was to install a login manager, in my case, lxdm.  And set it to auto log me into my desktop.
    I now have the expected reboot and logout menus.
    Hope this helps someone.  This has been a bear to figure out.

  • Different ways to shutdown and startup instance in 10g

    I have just installed 10g on my win2003 server. There seems to be 3 different ways to shutdown / startup an instance in 10g.
    1. via SQLPLUS (how its always been) with shutdown and startup commands
    2. via the new OEM Web interface
    3. Start / Stop the NT Service for the instance
    questions:
    - Did I miss anything other methods?
    - how come OEM ask for O/S login as well as DB login, when shutdown or startup? but via SQLPLUS I only have to login using as DBA? different level of security?
    - When shutdown via either SQLPLUS or OEM, the NT service is still shown as "started"? so does this mean that the NT service is more than the oracle instance???
    Thanks
    Clo

    how come OEM ask for O/S login as well as DB loginWith SQL*Plus, you are already logged into the Operating System. There is a OS session in progress. With OEM web interface, it has to first start a OS session and then connect to Oracle using Oracle credentials supplied to actually shutdown the DB.
    the NT service is still shown as "started"? The difference between NT service started or not started (given that the database was already shutdown) will be:
    When NT service is started but the DB is shutdown, your users will get this error message:
    Enter user-name: scott
    Enter password:
    ERROR:
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    Enter user-name:When NT service is stopped, your users will get this error message:
    Enter user-name: scott
    Enter password:
    ERROR:
    ORA-12560: TNS:protocol adapter error
    Enter user-name:The NT service needs to be running for you to be able to do a STARTUP or SHUTDOWN on the database. You will NOT be able to STARTUP if the NT service was not running (STARTUP will not start your NT service automatically).

  • None exist error  code after a graceful shutdown

    I'd like to return a none zero exit code after a normal graceful shutdown.
    My end task is to be able to send a restart event to a number of machines running my application that will gracefully shutdown and inform the shell script that started it that it wants to be restarted.
    One option would be System.exit with a shutdown hook that monitors the current threads, and does not end until the other threads have also exited, but I would have to inform this hook of threads that should be allowed to finish naturally. But that seams a little [t]icky.
    I guess I could write to a file, and then close down naturally. But this leaves files drifting about. I'm not overly keen on that either.
    Any other suggestions? Thanks, Mike

    The "worker" thread should
    not be interupted, and told to exit, just left to
    exit under there own steam. (when they have finished
    the current job). What is the "worker" thread ? Is it what I meant with "watcher" thread ? Is that what you said or what I said ?
    And, I assumed we are talking about a server-like application, that is one running indefinitely, as opposed to one that would perform a specific task and then terminate. Am I correct ?
    The initalization of this new type of
    shutdown/restart is currently undefined, but will
    likely that the application start listening on a
    socket connection. I'm sorry, I don't understand that at all.
    I want this to ease deployment,
    currently when I deploy a new version I type "ant
    deploy", then VNC on to each of the computer
    (currently just 3, but likely to be more soon) and
    manually restart. What I want is to just type "ant
    deploy" it sends a signal to the running copies, and
    they restart themselfs. (I'm a lazy brsatard).You know this quote by Larry Wall (?) about the three most important characteristics of a programmer, don't you ?
    >
    and thus the exit code is already defined.Not so with what I would consider a "graceful
    shutdown". Then the application would shut down as
    all the threads have completed.It depends on whether having "all threads completed" is a normal part of the application's flow. If I assumed correctly we were talking about a server-like app, then it's not. Ergo the command to terminate has to be issued at some point. The question is how that gets done. For instance, if you send a CTRL-C from the shell, your application shuts down with an error code != 0.
    A graceful shutdown needs to be initiated somewhere. How do you plan to do it ?

  • How to shutdown and start agent in ODI 11g in Linux Environment

    Hi Experts,
    Pls any one can help me on "How to shutdown and start agent in ODI 11g in Linux Environment" and where can I find Agent.sh and Agentshutdown.sh files location in ODI 11g and parallely how can I find Odiparameter.sh file location
    Thanks in Advance
    Regards
    Phani

    Phani ,
    Go to your <ODI_11g_HOME>/oracledi/agent/bin
    and you will find agent.sh , agent_<standalone_agent>.sh and odiparams.sh and other agent files.
    Step 1. Update your odiparams.sh
    Step 2. Create the Physical and Logical Agent int your Topology using the same port_number and name provide while creating the Stand alone agent during installation ( or) create accordingly the agent in Topology with name and port number as required and make the modification in agent_<stand_alone>.sh file
    Step 3. After doing so start your agent_<stand_alone>.sh
    Step 4. Repeat the process 2-3 for any number of stand alone agent created on different ports and steps 1 to 3 for different Work repository
    Thanks
    Dev

Maybe you are looking for