Oracle10g DB services startup sequence

Hi:
I have installed 10g on WinXP. All is well but I would like to start the Oracle services manually and I need to do it in the appropriate sequence, I only know about the SQLnet listener and the actual database. what is iSQLplus?
There are three other services and if I look in taskManager I see two java processes running as well. Http listener perhaps?
I have not installed iAs. Anybody has a script to start Oracle 10g on Windows?
Thanks in advance,
Jose

Hi,
As you have already sequence for 9.3 on specified page, i think sequence of service start will be remain the same.
even at the time of installation you can check the service box and it will automatically start all services in correct order
Thanks
Focusthread Hyperion Trainer
[http://focusthread.com/training]

Similar Messages

  • Oracle 11gr2 Cluster startup Sequences

    Hi,
    What is the Sequences of starting Oracle RAC 11gr2 services?

    Hi,
    The Oracle 11gR2 clusterware startup sequence starting by Oracle High Availability Services Daemon ohasd
    see this link for more details :)
    http://www.oracle-home.ro/Oracle_Database/RAC/11gR2-Clusterware-Startup-Sequence.html
    Or
    From Metalink ID 1053147.1: 11gR2 Clusterware and Grid Home

  • WES Startup sequence events

    Hi All,
    I'm going to try my best to explain my situation.  I have a Windows Embedded Standard 7 deployment released right now which boots up and runs fine.  I just want to tweak the startup sequence of events, if possible.
    We've written all the software that runs at startup from the services to the explorer shell replacement.
    I have 2 videos for you to watch.
    1) Explorer embedded start up for our device (Admin access only):
    http://youtu.be/Ge4otXvOUvY
    As you can see, I have to halt the auto login and enter the Admin user and password manually to login to the Admin account where explorer runs.  What I want you to take notice here after I begin login, is the full screen black-to-blue background with
    the typical Windows loading spinner running (This is Windows loading, not any of my software).  This spinner and background stays on the screen until Explorer is loaded and is ready to be displayed to the user.  There is no time where the user thinks
    something isn't happening.
    2) Normal embedded start up for our device:
    http://youtu.be/4nL0uuXuqYo
    As you can see, upon starting up, and our standard user automatic login, Winlogon displays a full screen black-to-blue background with the typical loading spinner running.  After some time, this fades out and displays the users desktop background color
    of red.  At this moment in time our explorer shell replacement is still loading and is not yet visible to the user, so the user keeps seeing the red screen for some time while it loads, then without warning our explorer shell replacement is loaded and
    is displayed on screen to notify the user the system is starting/doing something.
    So my question is: Is there some events that our explorer shell replacement can hook onto and also trigger and event to Winlogon when the application knows its loaded and visible and the full screen loading spinner will fade out and you'll immediately see
    our explorer shell replacement INSTEAD of now where it's a red background for some time?
    I've found an article explaining a little about how you can change the sequence of applications that run found
    here but I haven't given it a try yet.  I wanted to get community feedback first.
    Let me know if you need any more clarifications on this.
    Thanks.

    You can enable wallpaper with a custom shell. There was a post some time ago on the forum and it is in Chapter 7 of my book:
    Copy the wallpaper image file to a convenient folder in the file system. Example c:\users\test\Documents\myimage.bmp.
    Use Reg.exe to set up the registry:
    REG ADD "HKCU\Control Panel\Desktop" /v Wallpaper /d C:\users\test\Documents\myimage.bmp
    Finally call user32.dll:
    rundll32 user32.dll,UpdatePerUserSystemParameters
    You make the call to user32.dll on startup each and every time.
    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

  • Is this possible in TIDAL , Change the Lotus Domino Server (LotusDominoData) service Startup Type from 'Automatic' to 'Manual

    1) Shutdown the Domino server (Lotus Domino Server (LotusDominoData) service)
    2) Change the Lotus Domino Server (LotusDominoData) service Startup Type from 'Automatic' to 'Manual'
    3) Reboot the server
    4) Defragment the drive (D:\ or F:\)
    5) Change the Lotus Domino Server (LotusDominoData) service Startup type from 'Manual' to 'Automatic'
    6) Reboot the server
    Any help would be appreciated.

    Binu - are you wanting to automate this process with TES?
    There is a windows cmd command "net stop" and "net start" you can use to stop and start a service.
    You will need to work with your windows admin or look online for a command line way to change the service to manual and to start the defrag.
    There is a shutdown command that can be run from cmd. It has a switch to force the reboot.
    You might also check out scripting with WMI.
    Hope this helps,
    Michelle

  • Correct startup sequence with external display/keyboard/mouse etc

    Most laptop vendors have docking stations or other devices that enable you to use the laptop with the lid closed in conjunction with an external display/keyboard/mouse etc.
    Since no such beast exists for the MBP, what is the correct startup sequence for the MBP to do the same thing? Do you plug some parts in first before/after initial power on then others later or what?
    Also, the resolution on my external display is much greater than what the MBP provides with its monitor. Will I be limited to comparable resolution on the external monitor or can/will the video card sense and use (to its limits of course) the potential resolution of the external display??
    Thanks

    Never mind. Found the answer:
    http://docs.info.apple.com/article.html?artnum=86286

  • JMS5024: JMS service startup failed.

    I have created a hellowworld.jsp. I deployed the project using server Sun Java Application Server Edition 8.1 and Type exploded. The deploy was successful. When I try to start the sun Java Application Server Edition 8.1, I am receiving a JMS5024: JMS service startup failed SEVERE error. Any help would be appreciated. The error is below:
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21
    recursive call into SystemOutandErrhandler
    java.lang.RuntimeException: recursivecall
         at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189)
         at java.io.PrintStream.write(PrintStream.java:260)
         at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
         at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)
         at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
         at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146)
         at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
         at java.io.Writer.write(Writer.java:126)
         at java.util.logging.StreamHandler.publish(StreamHandler.java:191)
         at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:87)
         at java.util.logging.Logger.log(Logger.java:424)
         at java.util.logging.Logger.doLog(Logger.java:446)
         at java.util.logging.Logger.log(Logger.java:469)
         at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198)
         at java.io.PrintStream.write(PrintStream.java:260)
         at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
         at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
         at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
         at java.util.logging.StreamHandler.flush(StreamHandler.java:224)
         at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88)
         at java.util.logging.Logger.log(Logger.java:424)
         at java.util.logging.Logger.doLog(Logger.java:446)
         at java.util.logging.Logger.log(Logger.java:469)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:285)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
    SEVERE: JMS5024: JMS service startup failed.
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFa
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices
    SEVERE: UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
         at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
         at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.lang.NullPointerException
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
         at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getJavaConfigBean(ServerBeansFactory.java:184)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:102)
         ... 5 more
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.ja
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
    WARNING: Feb 21, 2005 11:34:38 AM com.sun.enterprise.server.ss.ASLazyKernel stopLifecycle
    SEVERE: Exception while stoppping Lifecycle.
    java.lang.NullPointerException
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)

    Hi
    successful. When I try to start the sun Java
    Application Server Edition 8.1, I am receiving a
    JMS5024: JMS service startup failed SEVERE error. Any
    help would be appreciated. The error is below:Could you share your MQ broker log file [$AS_INSTALL_DIR/domains/domain1/imq/instances/imqbroker/log/log.txt]? Does this error occur after you had installed the jsp app? Was the earlier shutdown a clean shutdown? Could you check and see if there are any jms processes around[ ps -efa | grep
    imqbrokerd] ?
    >
    WARNING: Feb 21, 2005 11:34:38 AM
    com.sun.enterprise.server.ss.ASLazyKernel
    startASSocketServices
    SEVERE: UnknownException during startup. Disable
    quick startup by setting system property
    com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleExceptionIs AS startup successful if you disable application server lazy startup using the above system property?
    --Siva.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Calling CoCreateInstance during OS and service startup

    I have created 2 COM  services ServiceA and SerivceB. ( OS Windows 7)
    ServiceA: Automatic startup
    ServiceB: Manual Startup
    During OS start-up, Calling CoCreateInstance of ServiceB from ServiceA->Run() is delayed almost 100 seconds.
    This issue only occurs during OS startup. below link says similar issue. But not applicable to Windows 7.
     http://support.microsoft.com/kb/258943
    Similar to http://stackoverflow.com/questions/3398105/calling-cocreateinstance-during-service-startup
    Thanks, Renjith V R

    It seems there is a solution in the second thread on stackoverflow.
    I need reason. Not solution. I already have a solution of adding dependency. Also below link says service db is locked during service startup. Then the startup of second service should be failed. But  my service is started successfully
    but it takes more than 1.5 mins.
    https://technet.microsoft.com/en-us/library/aa998749(v=exchg.65).aspx
    Thanks, Renjith V R

  • AS startup - JMS service startup failed

    After sucessful instalation of AS7 on sparc Solaris 8, I've got error during startup.
    [10/Jul/2003:16:42:12] INFO ( 1145): CORE1116: Sun ONE Application Server 7.0.0_01
    [10/Jul/2003:16:42:13] INFO ( 1146): CORE3016: daemon is running as super-user
    [10/Jul/2003:16:42:18] INFO ( 1146): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_01] from [Sun Microsystems Inc.]
    [10/Jul/2003:16:42:56] INFO ( 1146): JMS5035: Timed out after 30000 milliseconds while trying to verify if the JMS service startup succeeded.
    [10/Jul/2003:16:42:56] INFO ( 1146): JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server1. Please refer to the JMS provider documentation for the exact location of this log file.
    [10/Jul/2003:16:42:56] SEVERE ( 1146): JMS5024: JMS service startup failed.
    [10/Jul/2003:16:42:56] SEVERE ( 1146): CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:247)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
    at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
    Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:231)
    ... 2 more
    Caused by: javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:145)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
    at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
    at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:733)
    at com.iplanet.ias.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:284)
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:224)
    ... 2 more
    [10/Jul/2003:16:42:56] SEVERE ( 1146): CORE3186: Failed to set configuration

    This seems to be the same problem as one described in: http://swforum.sun.com/jive/thread.jsp?forum=68&thread=20049
    Double check JMS port assignments - port might already be in use by some other process and should be changed.
    Hope this helps...

  • Deployment order of MDBs vs EJBs in WL startup sequence

              This is a problem that follows on from my last posting.
              To recap, we have multiple WL servers not clustered, one acts as the JMS server that
              all of them use as their MDB jndi-provider-url so when a message (on a JMS topic)
              is published to the main server, all the WL servers receive it.
              The main WL server acting as the JMS server is started up first, then the others.
              The following problem can occur.
              A message can arrive at the main server while another server is booting up. The MDBs
              on this booting server can deploy it's MDBs before it's EJBs. Because this server
              is subscribing using the JMS server on the main server, the message is delivered
              and the onMessage() method is called. But this method may have to do lookups on EJBs
              that have not been deployed yet.
              So the question is, is it possible to ensure that all the EJBs deploy before the
              MDBs in a WL startup sequence? Does it require two separate JAR files to control
              the order, or can you control the order within a JAR file or have you simply no control
              over the order at all?
              Regs,
              Paul
              

    That's correct.
              "Paul Hammond" <[email protected]> wrote in message
              news:[email protected]...
              >
              > In my response to my own question I have seen in the WL docs that JMS
              servers are
              > deployed before EJB components, but within EJB components you can specify
              a deployment
              > order so presumably there by having separate JARs, one with EJBs, one with
              MDBs,
              > you can ensure your MDBs are deployed last?
              >
              > Paul
              >
              >
              >
              >
              > "Paul Hammond" <[email protected]> wrote:
              > >
              > >This is a problem that follows on from my last posting.
              > >
              > >To recap, we have multiple WL servers not clustered, one acts as the JMS
              > >server that
              > >all of them use as their MDB jndi-provider-url so when a message (on a
              JMS
              > >topic)
              > >is published to the main server, all the WL servers receive it.
              > >
              > >The main WL server acting as the JMS server is started up first, then the
              > >others.
              > >
              > >The following problem can occur.
              > >
              > >A message can arrive at the main server while another server is booting
              > >up. The MDBs
              > >on this booting server can deploy it's MDBs before it's EJBs. Because
              this
              > >server
              > >is subscribing using the JMS server on the main server, the message is
              delivered
              > >and the onMessage() method is called. But this method may have to do
              lookups
              > >on EJBs
              > >that have not been deployed yet.
              > >
              > >So the question is, is it possible to ensure that all the EJBs deploy
              before
              > >the
              > >MDBs in a WL startup sequence? Does it require two separate JAR files to
              > >control
              > >the order, or can you control the order within a JAR file or have you
              simply
              > >no control
              > >over the order at all?
              > >
              > >Regs,
              > >
              > >Paul
              > >
              >
              

  • Can't use MS keyboard to change startup sequence

    I'm using a MS Ergonomic Natural Keyboard 4000 with my Mac Pro (10.6.1); I can't select alternate sequences during the startup (Option to choose the startup device, or Cmd-Shift-Option-Delete to automatically select a FW external drive).
    One place told me that third-party devices weren't recognized early enough in the startup sequence to change the startup drive, this is sort of what MS also told me, they said I needed to make sure the USB keyboard option (or something similarly named) was activated in the BIOS…(do Macs even have BIOS?)
    Anyway if someone knows of a workaround (other than changing the startup drive in the System Preferences) that would be great.

    That ability is reserved for Macs that don't already have a built-in optical drive.
    I bet you probably looked at some of the guides online telling you to edit a plist file that supposedly unlocks the ability to create a bootable USB drive on a Mac that has a SuperDrive. But that's all it does. It doesn't change anything else about the process of Boot Camp Assistant creating the partition and requiring installation be done with the SuperDrive. All that modification does is literally "un-gray" a checkbox.
    Is it annoying that the SuperDrive must be used? No doubt, especially since this restriction was in not in place for older Macs. This is something that Apple would have to address via an SMC or other update, but the odds of that happening are less than those of you winning the Power Ball. It's a restriction you'll have to live with, unless you want to "upgrade" to a Retina display model.

  • JMS service startup failed

    Folks,
    I am having problem starting the application server after trying to add the following JVM options
    -DproxyHost=<my_host>.<my_domain> -DproxyPort=80
    OK, it didn't work, so I decided to remove the above options and back to where it was. Since then, I am unable to start the server. Below is the error log:
    [10/Nov/2004:18:12:00] INFO ( 1110): CORE1116: Sun ONE Application Server 7.0.0_03c
    [10/Nov/2004:18:12:00] INFO ( 1111): CORE3016: daemon is running as super-user
    [10/Nov/2004:18:12:03] INFO ( 1111): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_04] from [Sun Microsystems Inc.]
    [10/Nov/2004:18:12:05] SEVERE ( 1111): JMS5024: JMS service startup failed.
    [10/Nov/2004:18:12:05] SEVERE ( 1111): CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: congo.abc.com.au: congo.abc.com.au
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:247)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
    at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
    Caused by: java.net.UnknownHostException: congo.abc.com.au: congo.abc.com.au
    at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
    at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:148)
    ... 2 more
    [10/Nov/2004:18:12:05] SEVERE ( 1111): CORE3186: Failed to set configuration
    I have tried the followings: change the JMS port, increase time out, increase memory heaps AND nothing work.
    Appreciate any help.
    VQ

    Check for lock file blocking JMS service startup in /var/opt/imq/instances/domain1_server1
    I found it was causing me problems after rebooting without stopping the app server.
    Cheers,
    Ed

  • Possible to replay first time startup sequence?..

    Does anyone know if it is possible to replay the Imac startup sequence? If so, how?
    I tried searching and could not find any info on it.

    Is this what you are looking for?
    Mac Start Up Sound
    I note you have an Intel iMac. If the above is not what you are looking for, suggest that you re-post over in the Intel-based iMac Forums
    This area is for G5 iMac issues. Unknown if the Intels have a slightly different start up sound.

  • 11g Startup sequence (for Linux installs)

    What are the typical startup sequences folks are using for starting WLS > SOA Server?
    Our 11g install is shaky at best. It has stabilized somewhat since I've gotten away from an apparently buggy jdk (1.6.0_18 I believe it was) and I'm now on 1.6.0_27.
    I've created nohup scripts to start WLS followed by the SOA managed server. Pretty much using the 'setDomainEnv.sh' for pre-setting the environment, but out of the box, I've found it is severely lacking.
    I've had to fight through missing class defs (too many to count) and still am plagued with a highly unstable environment... seems when our developer deploys anything new it crashes the SOA server...
    Our 10g OC4J install has been generally care free for the past couple of years (aside from an out-of-control DB Cursor leak in B2B that requires some attention every month or two), but I just can't seem to get 11g under control...
    Hoping I can build on others experiences with this... re-inventing the wheel is getting old... fast...

    I've had to fight through missing class defs (too many to count) and still am plagued with a highly unstable environment.I'm not sure exactly what issue you faced but 'setDomainEnv.sh' is not the only file which sets the classpath. Usually for a clustered production installation, node manager is used for better control. AdminServer has to be started first and then managed servers can be started in any sequence. You may like to refer -
    http://blogs.oracle.com/middleware/entry/startup_scripts_for_weblogic_and_soa_suite
    http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/toc.htm
    http://download.oracle.com/docs/cd/E17904_01/web.1111/e13740/toc.htm
    Regards,
    Anuj

  • Is there any guide lines how you can secure windows 7 gpo enable system services startup security settings?

    Is there any guide lines how you can secure windows 7 gpo enable system services startup security settings?
    For example like many do with Forefront Client Security Anti-Malware service, and there is lots of other service that you would like to have control over to get an secure and stable Windows 7.
    /SaiTech

    Hi, 
    Since there is no response from you, we considered that you have gotten what you want in previous post. 
    For further question, please don't hesitate to come back here and let's discuss again. 
    If you have any feedback on our support, please click here
    Kate Li
    TechNet Community Support

  • What's your startup sequence?

    Hi guys,
    Just a quick question, and maybe silly, but I wondered what sequence other people's MacBooks booted in? The reason I ask is because I'm sure one phase didn't occur originally for me. Here's my sequence:
    Press power - Superdrive makes it's strange whirring noise.
    Chime
    Blank grey screen for 10 seconds (does anyone else get this? I'm sure I never used to but can't remember when it started)
    Grey Apple logo and spinning gear
    Blue screens
    Login Window
    It's not really a problem, I just wondered if it was normal behaviour. I've made sure the correct startup disk is selected in system preferences so it shouldn't be struggling to find OS X. Although I do have boot camp installed whether that makes a difference...
    Thanks everyone!

    Hi Andrew,
    I had this problem when I changed HD, startup took about 2 minutes instead of 25 seconds.
    Here is how I solved:
    *Reset NVRAM:*
    Right after you turn on your Mac press Option-Command-P-R until you hear two beeps.
    *Reset the System Management Controller (SMC):*
    - If the computer is on, turn it off.
    - Disconnect the AC adapter and remove the computer's battery.
    - Press and hold the power button for 5 seconds and then release the button.
    - Reconnect the battery and AC Adapter.
    - Press the power button to restart the computer
    I suggest you to try these two methods, i'm sure your startup sequence will improve, mine went back to normal 25 seconds!
    Kim

Maybe you are looking for