We want essbase to start during server boot via init.d as the essbase user.

We want essbase to start during server boot via init.d as the essbase user.
Do we have any documents for this.
Opereating System : Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opteron Architecture)
Version : 11.1.1.1.00
Regards,
Mink
http://newhyperion-blog.blogspot.com/

We want essbase to start during server boot via init.d as the essbase user.
Do we have any documents for this.
Opereating System : Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opteron Architecture)
Version : 11.1.1.1.00
Regards,
Mink
http://newhyperion-blog.blogspot.com/

Similar Messages

  • Grid on a standalone server Cluster daemons not starting during server boot

    Hi!I have installed Oracle Grid on a standalone server and setup Oracle db 11.2.0.2 on Oracle Linux 6.2 64 bit server.When I reoot the server and run crs_stat -t,several daemons havent started thus the ASM and db instances are also down as below
    Name Type Target State Host
    ora.DATA.dg ora....up.type OFFLINE OFFLINE
    ora.FRADG.dg ora....up.type OFFLINE OFFLINE
    ora....ER.lsnr ora....er.type ONLINE ONLINE amldb01dc
    ora.amldb.db ora....se.type OFFLINE OFFLINE
    ora.asm ora.asm.type OFFLINE OFFLINE
    ora.cssd ora.cssd.type ONLINE OFFLINE
    ora.diskmon ora....on.type ONLINE OFFLINE
    ora.evmd ora.evm.type ONLINE ONLINE amldb01dc
    ora.ons ora.ons.type OFFLINE OFFLINE
    I am forced to manually start the daemons via command crsctl start resource -all then I manually start the ASM and db instances.
    Yet when I run the commands
    crsctl config has
    CRS-4622: Oracle High Availability Services autostart is enabled.
    crsctl check has
    CRS-4638: Oracle High Availability Services is online.
    Thus I would assume the daemons would start automatically during boot.
    How can I resolve this?

    crstcl check crs seems not to be applicable to single instance but for RAC,since I have a single instance db,the output of the command is as below
    crsctl check crs
    Parse error:
    'crs' is an invalid argument
    Brief usage:
    crsctl check has
    Check status of OHAS.
    There is no crsd.log in path /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/crsd.The output of crs_stat -t is already posted in initial post and output of entire alert log is as below
    2012-07-03 16:18:35.975
    [client(8182)]CRS-2101:The OLR was formatted using version 3.
    2012-07-03 16:18:36.471
    [client(8218)]CRS-1001:The OCR was formatted using version 3.
    [client(8293)]CRS-10001:CRS-6021: No msg for has:crs-6021 [l][unlimited]
    [client(8294)]CRS-10001:CRS-6021: No msg for has:crs-6021 [n][65536]
    2012-07-03 16:18:42.528
    [ohasd(8291)]CRS-2112:The OLR service started on node amldb01dc.
    2012-07-03 16:18:42.538
    [ohasd(8291)]CRS-1301:Oracle High Availability Service started on node amldb01dc.
    2012-07-03 16:18:51.271
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(8465)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:1:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-03 16:18:52.299
    [evmd(8479)]CRS-1401:EVMD started on node amldb01dc.
    [client(8520)]CRS-10001:03-Jul-12 16:18 ACFS-9459: ADVM/ACFS is not supported on this OS version: 'error: file /etc/SuSE-release: No such file or directory
    [client(8889)]CRS-10001:03-Jul-12 16:19 ACFS-9459: ADVM/ACFS is not supported on this OS version: 'error: file /etc/SuSE-release: No such file or directory
    2012-07-03 16:19:22.600
    [cssd(9014)]CRS-1713:CSSD daemon is started in local-only mode
    2012-07-03 16:19:31.128
    [cssd(9014)]CRS-1601:CSSD Reconfiguration complete. Active nodes are amldb01dc .
    [client(10038)]CRS-10001:03-Jul-12 16:25 ACFS-9459: ADVM/ACFS is not supported on this OS version: 'error: file /etc/SuSE-release: No such file or directory
    2012-07-03 16:34:13.791
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(8465)]CRS-5010:Update of configuration file "/u01/app/oracle/product/11.2.0/dbhome_1/srvm/admin/oratab.bak.amldb01dc" failed: details at "(:CLSN00011:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-03 16:37:39.674
    [ohasd(8291)]CRS-2765:Resource 'ora.DATA.dg' has failed on server 'amldb01dc'.
    2012-07-03 16:37:43.636
    [ohasd(8291)]CRS-2767:Resource state recovery not attempted for 'ora.asm' as its target state is OFFLINE
    2012-07-03 16:38:06.905
    [cssd(9014)]CRS-1603:CSSD on node amldb01dc shutdown by user.
    2012-07-03 16:38:07.006
    [cssd(9014)]CRS-1660:The CSS daemon shutdown has completed
    2012-07-03 16:38:10.118
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(8465)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-03 16:42:09.578
    [ohasd(4827)]CRS-2112:The OLR service started on node amldb01dc.
    2012-07-03 16:42:09.649
    [ohasd(4827)]CRS-1301:Oracle High Availability Service started on node amldb01dc.
    2012-07-03 16:42:10.437
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:2:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-03 16:42:10.667
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-03 16:42:40.463
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5818:Aborted command 'check for resource: ora.DATA.dg amldb01dc 1' for resource 'ora.DATA.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-03 16:42:40.464
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5818:Aborted command 'check for resource: ora.FRADG.dg amldb01dc 1' for resource 'ora.FRADG.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-03 16:42:54.641
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5046)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:4:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-03 16:42:55.675
    [evmd(5060)]CRS-1401:EVMD started on node amldb01dc.
    2012-07-03 16:54:35.840
    [cssd(5256)]CRS-1713:CSSD daemon is started in local-only mode
    2012-07-03 16:54:44.396
    [cssd(5256)]CRS-1601:CSSD Reconfiguration complete. Active nodes are amldb01dc .
    2012-07-03 16:54:56.832
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5046)]CRS-5010:Update of configuration file "/u01/app/oracle/product/11.2.0/dbhome_1/srvm/admin/oratab.bak.amldb01dc" failed: details at "(:CLSN00011:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:03:53.530
    [ohasd(4827)]CRS-2767:Resource state recovery not attempted for 'ora.asm' as its target state is OFFLINE
    2012-07-04 10:04:02.701
    [cssd(5256)]CRS-1603:CSSD on node amldb01dc shutdown by user.
    2012-07-04 10:04:02.809
    [cssd(5256)]CRS-1660:The CSS daemon shutdown has completed
    2012-07-04 10:04:03.008
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5046)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:07:48.492
    [ohasd(4698)]CRS-2112:The OLR service started on node amldb01dc.
    2012-07-04 10:07:48.534
    [ohasd(4698)]CRS-1301:Oracle High Availability Service started on node amldb01dc.
    2012-07-04 10:07:49.059
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4946)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:1:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:07:49.192
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4946)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:08:19.085
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4946)]CRS-5818:Aborted command 'check for resource: ora.DATA.dg amldb01dc 1' for resource 'ora.DATA.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:08:19.093
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4946)]CRS-5818:Aborted command 'check for resource: ora.FRADG.dg amldb01dc 1' for resource 'ora.FRADG.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:08:33.278
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5053)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:4:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:08:34.319
    [evmd(5069)]CRS-1401:EVMD started on node amldb01dc.
    2012-07-04 10:27:13.716
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5053)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:30:57.260
    [ohasd(4619)]CRS-2112:The OLR service started on node amldb01dc.
    2012-07-04 10:30:57.280
    [ohasd(4619)]CRS-1301:Oracle High Availability Service started on node amldb01dc.
    2012-07-04 10:30:57.660
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:1:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:30:57.784
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:31:27.685
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5818:Aborted command 'check for resource: ora.FRADG.dg amldb01dc 1' for resource 'ora.FRADG.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:31:27.685
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4992)]CRS-5818:Aborted command 'check for resource: ora.DATA.dg amldb01dc 1' for resource 'ora.DATA.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:31:41.868
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5168)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:4:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:31:42.916
    [evmd(5184)]CRS-1401:EVMD started on node amldb01dc.
    2012-07-04 10:39:17.166
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5168)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:43:01.219
    [ohasd(4575)]CRS-2112:The OLR service started on node amldb01dc.
    2012-07-04 10:43:01.240
    [ohasd(4575)]CRS-1301:Oracle High Availability Service started on node amldb01dc.
    2012-07-04 10:43:01.643
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4971)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:1:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:43:01.781
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4971)]CRS-5016:Process "/u01/app/oracle/product/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2012-07-04 10:43:31.680
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4971)]CRS-5818:Aborted command 'check for resource: ora.FRADG.dg amldb01dc 1' for resource 'ora.FRADG.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:43:31.680
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(4971)]CRS-5818:Aborted command 'check for resource: ora.DATA.dg amldb01dc 1' for resource 'ora.DATA.dg'. Details at (:CRSAGF00113:) {0:0:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:43:45.864
    [u01/app/oracle/product/11.2.0/grid/bin/oraagent.bin(5120)]CRS-5815:Agent '/u01/app/oracle/product/11.2.0/grid/bin/oraagent_grid' could not find any base type entry points for type 'ora.daemon.type'. Details at (:CRSAGF00108:) {0:4:2} in /u01/app/oracle/product/11.2.0/grid/log/amldb01dc/agent/ohasd/oraagent_grid/oraagent_grid.log.
    2012-07-04 10:43:46.915
    [evmd(5136)]CRS-1401:EVMD started on node amldb01dc.

  • How do I prevent Firefox from automatically starting when I boot-up my Mac in the morning?

    Whenever I boot up my Mac in the morning Firefox automatically starts and displays my home page. I would only like to see the desk top with no applications running. I am running OSX 10.4.11 on my laptop.
    == Started possibly a few weeks ago.

    Hmm.. Okay I've done a bit more digging and tried the following two things before the last restart.. Not sure which one actually worked but give these a shot (one at a time) and let us know which is the ''actual'' solution! :)
    1. Open Safari -> Preferences -> General
    - change "Default Web Browser" to Safari
    - Close all applications
    - Relaunch Safari and change default browser back to Firefox.
    2. Remove the check from "Reopen windows when logging in" in the logout dialog and logout of the computer..
    I suspect step 2 is actually the proper solution, but I did both so, hopefully one of them works for everyone else!

  • Starting managed server's via NodeManager from command line.

    In WLS 70 weblogic.Admin utility has been enhanced to start/stop/kill
    managed servers via NodeManager.
    Here's the syntax
    java weblogic.Admin -url {admin server url} -username {admin user}
    -password {admin password} START {managed server instance name for e.g. S1}
    Pls make sure that the admin server & Nodemanager have started prior to
    executing the above command.
    Similary you can issue "SHUTDOWN S1" command which will shutdown the
    managed server.
    See weblogic.Admin for more info. With this interface you don't need to
    go to admin console to remotely start/stop managed servers.
    Hope it helps
    Kumar

    Solved: attention must be paid to the casing of the attribute name. The first character of the attribute name must be uppercase.
    So the property must be set as following:
    set JAVA_OPTIONS=-Dweblogic.ssl.ServerPrivateKeyPassPhrase=<the_password> %JAVA_OPTIONS%
    Edited by: javawarrior2003 on 24-nov-2011 18.19
    Edited by: javawarrior2003 on 24-nov-2011 18.20

  • Can't start messaging server - get "Load Environment Failed" in the administration server

    The messaging server can't restart, and when I use the
    admininstration server to verify setting I get the following message:
    <P>
    load environment failed
    <P>
    The file /etc/netscape.mail.conf is probably corrupted or missing.
    Try to regenerate it out of a backup.

    We also use a boot.properties in ${domain.home}, which may only be for Admin server, but worth checking anyway. Also, I often receive the boot.properties message you're seeing when there's other problems upstream, and I've found the message to be quite misleading at times. For example, if I have a problem with an LDAPAuthenticator or any other security mechanism I'll often see the boot.properties message eventhough the problem has nothing to do with that file.

  • Just want to get started. I am unable to move beyond the voice over welcome screen.  Any advice would be welcome.

    I just want to get started with my new out of the box MacAir.  I canot move beyond the voice over welcome screen.  It seems to be stuck.  What do I need to do to advance out of it? 

    Bt seem to have got their act together. After six days! All of a sudden it works. What a surprise, shame their help desk would not admit anything was wrong.

  • Login problem in that the radius server is not configured. And the local user does not authenticate

    When trying to login, the message appears "No radius server configured" and the local user does not authenticate. How do I access without rebooting the Switch 6500 with CatOS.

    Hi PK.
    Thanks for your Attention. You know how to insert a line configuration via SNMP RW  "set radius server 10.112.15.21 auth-port 1645 primary"?
    I believe this way or can I work around the problem.

  • Can't start weblogic server using Ant

    Hello,
    I can't start the WL Portal after installation.
    On a Windows 2000 Server SP2 : - I installed WebLogic Server 6.1 SP2 with the examples
    - I installed WebLogic Portal 4.0 SP2 (giving the same password as during the WL
    Server installation) -I installed EBCC 4.0 SP2 .
    I updated the license with UpdateLicense.cmd
    Now If I run - run the default WL server, both from the menu and as a service -
    enter the WL server console (on port 7001) - run the EBCC .
    When I try to start the WL Portal, from the program menu I am able to start the
    WP server properly , But I I try to start it from an ant wlrun then I get the error
    an IllegalAccessError (with the same password I gave during installation and I use
    to enter the server console): The WebLogic Server did not start up properly. Exception
    raised: java.lang.IllegalAccessError: try to access method weblogic/management/internal/Helper.preloadMBeanInfos()V
    from class weblogic/management/Admin at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35) Reason: Fatal initialization exception
    Any idea ?

    Hi VG,
    thank u a lot for ur answer. But there are no files at the Admin Server boot.properties path.
    and at the BI Server boot.properties path there is no security folder. Do u have any idea why i cant found anything at this directions ? Also I tried again the command "./startWeblogic.sh " and get a new error message which I post below. I am rlly worry about this. Is there maybe a way to reset the OBIEE and undo all changes ?
    <Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Oct 30, 2013 10:00:48 AM CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
    ^C<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    <Oct 30, 2013 10:39:50 AM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    <Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

  • Can't start weblogic Server -The server will force shutdown now

    Hello Community  ; ) , I hope i post this on the right topic if not pls advise me.
    I'm working as a trainee by a company which wants to establish OIBEE.
    I'm really new to this topic and hope i can get some help with my problems . Cause i stuck in many ways .
    I installed Oracle OBIEE 11g and the latest Patch 11.1.1.7.1.
    After changing the Oracle Logo in Oracle Home I restarted the Services, using Oracle WebLogic Server Administration Console.But it cant restart and stuck!
    So i stopped all manual using commands like "./stopWebLogic.sh ". As I wanted to start it again i get some error messages. Can somebody advise me how to handle this problem ? I would be very grateful.
    <Oct 29, 2013 12:09:31 PM CET> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in /app/oracle/product/OBIEE11.1.1.7/oracle_common/atgpf/modules/oracle.applcore.model_11.1.1/oracle.applcore.model.stub.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Oct 29, 2013 12:09:32 PM CET> <Warning> <Security> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
    <Oct 29, 2013 12:09:35 PM CET> <Warning> <Connector> <BEA-190155> <Compliance checking/validation of the resource adapter /app/oracle/product/OBIEE11.1.1.7/user_projects/domains/bifoundation_domain/servers/AdminServer/tmp/_WL_user/ESSAPP/z68zjr/stub-ess-ra.rar resulted in the following warnings:
    The ra.xml <resourceadapter-class> class 'oracle.as.scheduler.adapter.ra.RAImpl' should implement java.io.Serializable but does not.>
    <Oct 29, 2013 12:24:25 PM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    <Oct 29, 2013 12:24:25 PM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    <Oct 29, 2013 12:24:25 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

    Hi VG,
    thank u a lot for ur answer. But there are no files at the Admin Server boot.properties path.
    and at the BI Server boot.properties path there is no security folder. Do u have any idea why i cant found anything at this directions ? Also I tried again the command "./startWeblogic.sh " and get a new error message which I post below. I am rlly worry about this. Is there maybe a way to reset the OBIEE and undo all changes ?
    <Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Oct 30, 2013 10:00:48 AM CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
    ^C<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    <Oct 30, 2013 10:39:50 AM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    <Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

  • Unable to start SOA server through Node Manager

    Hi All,
    I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
    I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
    Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
    Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
    I am getting an error while trying to start soa server with nmStart() command, below is the error message...
    "Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
    I executed the dumpStack() command, and i am getting the output as "No stack trace available"
    If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
    I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
    I followed some of the blogs like...
    http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
    http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
    Experts, please give your advice.
    Many Thanks,
    N

    Hi Narsing,
    I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
    Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
    As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
    Regards,
    Neeraj Sehgal
    Hi Neeraj,
    I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
    I have made sure the property StartScriptEnabled= true.
    I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
    If i see the log messages in the nodemanager.log, this is the below message...
    <Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
    <Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    The log message in the soa_server1.out file is as below...
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
    <Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
    Many Thanks.

  • [solved] Large number of services enabled during first boot

    I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
    To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
    Any ideas as to what might be causing this?
    Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
    Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
    Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
    Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
    Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
    getty.target.wants:
    * [email protected]
    multi-user.target.wants:
    * [email protected]
    * iptables.service
    * remote-fs.target
    * sshd.service
    sysinit.target.wants:
    (none)
    Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
    default.target.wants:
    * systemd-readahead-collect.service
    * systemd-readahead-replay.service
    multi-user.target.wants:
    * dhcpcd.service * krb5-kpropd.service
    * fstrim.service * nscd.service
    * ftpd.service * rsyncd.service
    * gpm.service * systemd-journal-upload.service
    * ip6tables.service * systemd-networkd.service
    * krb5-kadmind.service * systemd-resolved.service
    * krb5-kdc.service
    sockets.target.wants:
    * krb5-kpropd.socket * systemd-journal-remote.socket
    * rlogin.socket * talk.socket
    * rsh.socket * telnet.socket
    * rsyncd.socket * uuidd.socket
    * sshd.socket
    sysinit.target.wants:
    * dm-event.service
    * systemd-timesyncd.service
    system-update.target.wants:
    * systemd-readahead-drop.service
    Explicitly installed packages:
    dhcpcd iputils procps-ng systemd-sysvcompat
    diffutils linux-grsec psmisc tar
    dnsutils logrotate reflector vim-systemd
    file mlocate rsync wget
    gradm mtr s-nail which
    grub openssh screen whois
    inetutils pacman
    Last edited by tazmanian (2014-09-10 23:11:42)

    +1.
    Here is the ports these services are listening:
    $ ss -tpl
    State      Recv-Q Send-Q                                                                                                       Local Address:Port                                                                                                           Peer Address:Port   
    LISTEN     0      128                                                                                                                      *:llmnr                                                                                                                     *:*       
    LISTEN     0      128                                                                                                                      *:ssh                                                                                                                       *:*       
    LISTEN     0      128                                                                                                                     :::llmnr                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::19532                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::tell                                                                                                                     :::*       
    LISTEN     0      128                                                                                                                     :::ssh                                                                                                                      :::*       
    LISTEN     0      128                                                                                                                     :::telnet                                                                                                                   :::*       
    LISTEN     0      128                                                                                                                     :::login                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::shell                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::rsync                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::git                                                                                                                      :::*

  • Sun Application Server -  Trouble starting default server

    Hi everyone.
    I am new to J2EE and am currently trying to get the Sun Appliation Server to run, but am having difficulties.
    I have installed version 1.4 of J2EE SDK.
    Running Windows XP SP2.
    When I run the program Start Default Server, it hangs for ages on the message "Starting Domain1, please wait" and finally after about a minute or so gives me an error message stating:
    "Timeout waiting for domain domain1 to go to starting state.
    CLI156 Could not start the domain domain1."
    I have been told that it is very common to get problems with the port you choose for the JMS to be the same as somehting else on your PC. I have experimented with different port numbers (all of which not in current use - as indiated by netstat -a in the cmd window).
    If anyone knows anything else I could try that would be great and much appreciated.
    Cheers
    Phill
    Below is a listing of my server.log file...
    Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
    [#|2004-11-22T21:11:05.125+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
    [#|2004-11-22T21:11:07.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
    [#|2004-11-22T21:11:08.140+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2004-11-22T21:11:14.484+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
    [#|2004-11-22T21:11:14.500+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
    [#|2004-11-22T21:11:14.546+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2004-11-22T21:11:20.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
    [#|2004-11-22T21:11:23.687+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
    [#|2004-11-22T21:11:24.453+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
    [#|2004-11-22T21:11:25.515+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
    [#|2004-11-22T21:11:26.671+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2004-11-22T21:11:27.859+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2004-11-22T21:11:27.859+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2004-11-22T21:11:27.968+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
    [#|2004-11-22T21:11:28.312+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
    [#|2004-11-22T21:11:28.656+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
    [#|2004-11-22T21:11:28.656+0000|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2004-11-22T21:11:28.656+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
    [#|2004-11-22T21:11:28.671+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
    [#|2004-11-22T21:11:28.671+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
    [#|2004-11-22T21:11:28.796+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
    [#|2004-11-22T21:11:33.031+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
    [#|2004-11-22T21:11:34.796+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
    [#|2004-11-22T21:11:34.828+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
    [#|2004-11-22T21:11:34.984+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
    [#|2004-11-22T21:11:34.984+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
    [#|2004-11-22T21:11:35.015+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
    [#|2004-11-22T21:11:35.015+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
    [#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
    [#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]
    [#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
    [#|2004-11-22T21:12:36.578+0000|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7678]. - cause: java.net.ConnectException: Connection refused: connect
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7678]. - cause: java.net.ConnectException: Connection refused: connect
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
         at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
         at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
         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:734)
         at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
         ... 7 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
         at java.net.Socket.connect(Socket.java:452)
         at java.net.Socket.connect(Socket.java:402)
         at java.net.Socket.<init>(Socket.java:309)
         at java.net.Socket.<init>(Socket.java:124)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
         ... 25 more
    |#]
    [#|2004-11-22T21:12:36.578+0000|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
    [#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
    [#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
    [#|2004-11-22T21:12:36.593+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
    [#|2004-11-22T21:12:36.593+0000|SEVERE|sun-appserver-pe8.0.0_01|org.apache.tomcat.util.net.PoolTcpEndpoint|_ThreadID=10;|Caught exception trying to unlock accept on 8080 java.net.ConnectException: Connection refused: connect|#]
    [#|2004-11-22T21:12:36.671+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
    [#|2004-11-22T21:12:36.687+0000|SEVERE|sun-appserver-pe8.0.0_01|org.apache.tomcat.util.net.PoolTcpEndpoint|_ThreadID=10;|Caught exception trying to unlock accept on 1043 java.net.ConnectException: Connection refused: connect|#]
    [#|2004-11-22T21:12:36.765+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
    [#|2004-11-22T21:12:36.781+0000|SEVERE|sun-appserver-pe8.0.0_01|org.apache.tomcat.util.net.PoolTcpEndpoint|_ThreadID=10;|Caught exception trying to unlock accept on 4848 java.net.ConnectException: Connection refused: connect|#]
    [#|2004-11-22T21:12:36.953+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
    [#|2004-11-22T21:12:36.953+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2004/11/22 21:12:36]|#]
    [#|2004-11-22T21:12:36.953+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
    [#|2004-11-22T21:12:36.953+0000|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7678]. - cause: java.net.ConnectException: Connection refused: connect
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    |#]
    [#|2004-11-22T21:12:36.984+0000|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]

    OK, here is the contents of log.txt from the imqbroker\log directory...
    Tell me if you have a hard time decifering which date of this log corresponds to the date of the first log and I will clear both files and recreate it.
    Thanks very much for your help, I am sure we will crack it!
    Thanks again
    Phill
    # 1101144571937 Do not modify this line
    [22/Nov/2004:17:29:31 GMT] [B1002]: An existing property file for imqbroker was not found, no stored properties will be loaded
    [22/Nov/2004:17:29:31 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [22/Nov/2004:17:29:32 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:17:29:32 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:17:29:32 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:17:29:32 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:17:29:32 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:17:29:32 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
    [22/Nov/2004:17:29:32 GMT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
    [22/Nov/2004:17:29:32 GMT] [B1060]: Loading persistent data...
    [22/Nov/2004:17:29:32 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
    [22/Nov/2004:17:29:33 GMT] [B1136]: Processing stored transactions
    [22/Nov/2004:17:29:33 GMT] [B1013]: Auto Creation of Queues is Enabled
    [22/Nov/2004:17:29:33 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    [22/Nov/2004:17:29:33 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    [22/Nov/2004:17:29:33 GMT] [B1039]: Broker "imqbroker@mono:7676" ready.
    [22/Nov/2004:17:40:21 GMT] [B1047]: Shutting down broker...
    [22/Nov/2004:17:40:21 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:17:40:21 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:17:40:21 GMT] [B1077]: Broadcast good-bye to all connections ...
    [22/Nov/2004:17:40:21 GMT] [B1078]: Flushing good-bye messages ...
    [22/Nov/2004:17:40:21 GMT] [B1063]: Done
    [22/Nov/2004:17:40:21 GMT] [B1048]: Shutdown of broker complete.
    jre
    [22/Nov/2004:17:32:07 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:17:32:07 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:17:32:07 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:17:32:07 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:17:32:07 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:17:32:07 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
    [22/Nov/2004:17:32:07 GMT] ERROR Could not start the Broker's portmapper service on port 7676.
    This port is already in use by another application -- possibly another
    instance of the Broker. Please quit that other application, or use a
    different port number for this instance of the Broker.
    [22/Nov/2004:17:42:31 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [22/Nov/2004:17:42:31 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:17:42:31 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:17:42:31 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:17:42:31 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:17:42:31 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:17:42:31 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
    [22/Nov/2004:17:42:31 GMT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
    [22/Nov/2004:17:42:31 GMT] [B1060]: Loading persistent data...
    [22/Nov/2004:17:42:31 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
    [22/Nov/2004:17:42:32 GMT] [B1136]: Processing stored transactions
    [22/Nov/2004:17:42:32 GMT] [B1013]: Auto Creation of Queues is Enabled
    [22/Nov/2004:17:42:32 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    [22/Nov/2004:17:42:32 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    [22/Nov/2004:17:42:32 GMT] [B1039]: Broker "imqbroker@mono:7676" ready.
    [22/Nov/2004:19:26:20 GMT] [B1047]: Shutting down broker...
    [22/Nov/2004:19:26:20 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:19:26:20 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:19:26:20 GMT] [B1077]: Broadcast good-bye to all connections ...
    [22/Nov/2004:19:26:20 GMT] [B1078]: Flushing good-bye messages ...
    [22/Nov/2004:19:26:20 GMT] [B1063]: Done
    [22/Nov/2004:19:26:20 GMT] [B1048]: Shutdown of broker complete.
    jre
    [22/Nov/2004:19:12:30 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:19:12:30 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:19:12:30 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:19:12:30 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:19:12:30 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:19:12:30 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
    [22/Nov/2004:19:12:30 GMT] ERROR Could not start the Broker's portmapper service on port 7676.
    This port is already in use by another application -- possibly another
    instance of the Broker. Please quit that other application, or use a
    different port number for this instance of the Broker.
    [22/Nov/2004:19:15:43 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [22/Nov/2004:19:15:43 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:19:15:43 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:19:15:43 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:19:15:43 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:19:15:43 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:19:15:43 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
    [22/Nov/2004:19:15:43 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
    [22/Nov/2004:19:15:43 GMT] [B1060]: Loading persistent data...
    [22/Nov/2004:19:15:43 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
    [22/Nov/2004:19:15:43 GMT] [B1136]: Processing stored transactions
    [22/Nov/2004:19:15:43 GMT] [B1013]: Auto Creation of Queues is Enabled
    [22/Nov/2004:19:15:44 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    [22/Nov/2004:19:15:44 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    [22/Nov/2004:19:15:44 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.
    [22/Nov/2004:19:26:21 GMT] [B1047]: Shutting down broker...
    [22/Nov/2004:19:26:21 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:19:26:21 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:19:26:21 GMT] [B1077]: Broadcast good-bye to all connections ...
    [22/Nov/2004:19:26:21 GMT] [B1078]: Flushing good-bye messages ...
    [22/Nov/2004:19:26:21 GMT] [B1063]: Done
    [22/Nov/2004:19:26:21 GMT] [B1048]: Shutdown of broker complete.
    jre
    [22/Nov/2004:19:20:56 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:19:20:56 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:19:20:56 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:19:20:56 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:19:20:56 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:19:20:56 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
    [22/Nov/2004:19:20:56 GMT] ERROR Could not start the Broker's portmapper service on port 7678.
    This port is already in use by another application -- possibly another
    instance of the Broker. Please quit that other application, or use a
    different port number for this instance of the Broker.
    [22/Nov/2004:19:21:14 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [22/Nov/2004:19:21:14 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:19:21:15 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:19:21:15 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:19:21:15 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:19:21:15 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:19:21:15 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
    [22/Nov/2004:19:21:15 GMT] ERROR Could not start the Broker's portmapper service on port 7678.
    This port is already in use by another application -- possibly another
    instance of the Broker. Please quit that other application, or use a
    different port number for this instance of the Broker.
    [22/Nov/2004:21:11:12 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [22/Nov/2004:21:11:12 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:21:11:13 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:21:11:13 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:21:11:13 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:21:11:13 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:21:11:13 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
    [22/Nov/2004:21:11:13 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
    [22/Nov/2004:21:11:13 GMT] [B1060]: Loading persistent data...
    [22/Nov/2004:21:11:13 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
    [22/Nov/2004:21:11:14 GMT] [B1136]: Processing stored transactions
    [22/Nov/2004:21:11:14 GMT] [B1013]: Auto Creation of Queues is Enabled
    [22/Nov/2004:21:11:14 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    [22/Nov/2004:21:11:14 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    [22/Nov/2004:21:11:14 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.
    [22/Nov/2004:21:24:10 GMT] [B1047]: Shutting down broker...
    [22/Nov/2004:21:24:10 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:21:24:10 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:21:24:10 GMT] [B1077]: Broadcast good-bye to all connections ...
    [22/Nov/2004:21:24:10 GMT] [B1078]: Flushing good-bye messages ...
    [22/Nov/2004:21:24:11 GMT] [B1063]: Done
    [22/Nov/2004:21:24:11 GMT] [B1048]: Shutdown of broker complete.
    [22/Nov/2004:23:47:09 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [22/Nov/2004:23:47:09 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [22/Nov/2004:23:47:09 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [22/Nov/2004:23:47:09 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [22/Nov/2004:23:47:09 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [22/Nov/2004:23:47:09 GMT] Java Heap Size: max=194432k, current=16256k
    [22/Nov/2004:23:47:09 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
    [22/Nov/2004:23:47:10 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
    [22/Nov/2004:23:47:10 GMT] [B1060]: Loading persistent data...
    [22/Nov/2004:23:47:10 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
    [22/Nov/2004:23:47:10 GMT] [B1136]: Processing stored transactions
    [22/Nov/2004:23:47:10 GMT] [B1013]: Auto Creation of Queues is Enabled
    [22/Nov/2004:23:47:10 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    [22/Nov/2004:23:47:11 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    [22/Nov/2004:23:47:11 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.
    [22/Nov/2004:23:56:18 GMT] [B1047]: Shutting down broker...
    [22/Nov/2004:23:56:18 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:23:56:18 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
    [22/Nov/2004:23:56:18 GMT] [B1077]: Broadcast good-bye to all connections ...
    [22/Nov/2004:23:56:18 GMT] [B1078]: Flushing good-bye messages ...
    [22/Nov/2004:23:56:18 GMT] [B1063]: Done
    [22/Nov/2004:23:56:18 GMT] [B1048]: Shutdown of broker complete.
    [23/Nov/2004:00:19:36 GMT]
    ================================================================================
    Sun Java(tm) System Message Queue
    Sun Microsystems, Inc.
    Version: 3.5 SP1 (Build 48-G)
    Compile: Thu 01/29/2004
    Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
    [23/Nov/2004:00:19:36 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
    [23/Nov/2004:00:19:36 GMT] IMQ_HOME=C:\Sun\AppServer\imq
    [23/Nov/2004:00:19:36 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
    [23/Nov/2004:00:19:36 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
    [23/Nov/2004:00:19:36 GMT] Java Heap Size: max=194432k, current=16256k
    [23/Nov/2004:00:19:36 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
    [23/Nov/2004:00:19:36 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
    [23/Nov/2004:00:19:36 GMT] [B1060]: Loading persistent data...
    [23/Nov/2004:00:19:36 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
    [23/Nov/2004:00:19:37 GMT] [B1136]: Processing stored transactions
    [23/Nov/2004:00:19:37 GMT] [B1013]: Auto Creation of Queues is Enabled
    [23/Nov/2004:00:19:37 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    [23/Nov/2004:00:19:37 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    [23/Nov/2004:00:19:37 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.

  • Issues starting weblogic server

    I get the following error in my Jdeveloper console whenever I try starting the webLogic server.
    <AnnotatedLogger> <logWithThrowable> JAXB marshaller creation fails due to underlying error "javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespacePrefixMapper" must be an instance of type com.sun.xml.bind.marshaller.NamespacePrefixMapper, not oracle.wsm.resmgmt.ResourceMarshaller$ResourceNamespacePrefixMapper".
    javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespacePrefixMapper" must be an instance of type com.sun.xml.bind.marshaller.NamespacePrefixMapper, not oracle.wsm.resmgmt.ResourceMarshaller$ResourceNamespacePrefixMapper
         at com.sun.xml.bind.v2.runtime.MarshallerImpl.setProperty(MarshallerImpl.java:502)
         at oracle.wsm.resmgmt.ResourceMarshaller$1.run(ResourceMarshaller.java:297)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.wsm.resmgmt.ResourceMarshaller.<init>(ResourceMarshaller.java:285)
         at oracle.wsm.resmgmt.ResourceMarshaller.<init>(ResourceMarshaller.java:263)
         at oracle.wsm.policymanager.accessor.BeanAccessor.buildIndexes(BeanAccessor.java:477)
         at oracle.wsm.policymanager.accessor.BeanAccessor.updateCache(BeanAccessor.java:1647)
         at oracle.wsm.policymanager.accessor.BeanAccessor.fetchDocuments(BeanAccessor.java:989)
         at oracle.wsm.policymanager.accessor.BeanAccessor.access$400(BeanAccessor.java:133)
         at oracle.wsm.policymanager.accessor.BeanAccessor$MissingDocsFetcherTask.run(BeanAccessor.java:208)
         at oracle.wsm.common.scheduler.TimerManagerWrapper$TimerListenerImpl.timerExpired(TimerManagerWrapper.java:57)
         at weblogic.timers.internal.commonj.ListenerWrap.timerExpired(ListenerWrap.java:37)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    <WsmMessageLogger> <logSevere> Failed to retrieve requested documents due to underlying error "javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespac

    go to the below loacation and remove the system folder and try to start weblogic server it will ask to set the login credentials and port number,
    C:\Users\###\AppData\Roaming\JDeveloper
    let us know how it goes...

  • Node Manager unable to start managed Server. SSL Handshake problem

    I am getting the following Error:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for server wecarebeadev via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'wecarebeadev' to NodeManager at host: 'localhost:5555' with exception Write Channel Closed, possible SSL handshaking or trust failure. Please ensure that the NodeManager is active on the target machine].]
    I have Weblogic Server 7.0 SP1 with Admin and Managed Server running on the same physical machine as Windows Services.
    SSL port has been setup properly for Managed Server. Host Name Verification Ignored is checked for MS.

    Hi Ajay,
    This happens when the SSL communication between the admin and the node
    manager fails. The SSL configuration of the admin server or the node
    manager is the problem.
    cheers,
    gaurav.
    On 30 Jun 2003 12:19:49 -0700, Ajay Kulkarni <[email protected]> wrote:
    I am getting the following Error:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for server wecarebeadev via the Node Manager - reason:
    [CommandInvoker: Failed to send command: 'online to server 'wecarebeadev'
    to NodeManager at host: 'localhost:5555' with exception Write Channel
    Closed, possible SSL handshaking or trust failure. Please ensure that the
    NodeManager is active on the target machine].]
    I have Weblogic Server 7.0 SP1 with Admin and Managed Server running on
    the same physical machine as Windows Services.
    SSL port has been setup properly for Managed Server. Host Name
    Verification Ignored is checked for MS.
    Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

  • HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

    hi all, i am trying to start a managed server using nodeManager, but i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for
    server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
    send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
    to negotiate an acceptable set of security parameters.. Please ensure that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try to start
    the managed server via adminserver console, i got the exception mentioned in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver, and
    nodemanager is supposed to run at localhost:5555 (and indeed it does, because
    ihave started it successfully).
    thanx in advance and regards marco

    Marco.
    Sorry, this is not a solution to your problem but i am trying to solve the same
    problem for a week now.
    I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
    same error. I know that the default certificate installed provides a hostname
    verification of weblogic.com. I turned the hostname verification off, i put in
    the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
    error when starting the managed server. I went ahead and created my own certificate
    for machine called mallik, created my own passphrase, created a new keystore,
    made the admin server view the keystore, used the same certificate for both the
    admin server and the node manager. It still fails with the same error. I went
    ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
    totally confused now what needs to be done.
    My nodeManger.hosts looks like this:
    mallik 10.100.10.130
    managedServer1 10.100.10.130
    managedServer2 10.100.10.13
    Below is the startNodeManager.cmd.
    @echo off
    @rem *************************************************************************
    @rem This script can be used to start the WebLogic NodeManager
    @rem
    @rem This script sets the following variables before starting the NodeManager:
    @rem
    @rem WL_HOME - The root directory of your WebLogic installation.
    @rem NODEMGR_HOME - The home directory for this NodeManager instance.
    @rem JAVA_HOME - Location of the version of Java used to start WebLogic
    @rem Server. This variable must point to the root directory of
    @rem a JDK installation and will be set for you by the
    @rem          installer. See the WebLogic platform support page
    @rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
    list of
    @rem supported JVMs on Windows NT.
    @rem PATH - Adds the JDK and WebLogic directories to the system path.
    @rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
    @rem JAVA_OPTIONS - Java command-line options for running the server. (These
    @rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    @rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    @rem -client, etc.)
    @rem MEM_ARGS - The variable to override the standard memory arguments
    @rem passed to java
    @rem
    @rem *************************************************************************
    SETLOCAL
    set WL_HOME=C:\bea7.0\weblogic700
    set NODEMGR_HOME=%WL_HOME%\common\nodemanager
    set JAVA_HOME=C:\bea7.0\jdk131_06
    Call %WL_HOME%\common\bin\commEnv.cmd
    @rem If NODEMGR_HOME does not exist, create it
    :checkNodeManagerHome
    if exist %NODEMGR_HOME% goto checkJava
    echo.
    echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
    mkdir %NODEMGR_HOME%
    @rem Check that java is where we expect it to be
    :checkJava
    if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
    echo The JDK wasn't found in directory %JAVA_HOME%.
    echo Please edit this script so that the JAVA_HOME
    echo variable points to the location of your JDK.
    goto finish
    :runNodeManager
    if not "%JAVA_VM%" == "" goto noResetJavaVM
    rem set JAVA_VM=-hotspot
    set JAVA_VM=%COMM_VM%
    :noResetJavaVM
    if not "%MEM_ARGS%" == "" goto noResetMemArgs
    set MEM_ARGS=-Xms32m -Xmx200m
    :noResetMemArgs
    @echo on
    set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    cd %NODEMGR_HOME%
    #"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
    "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
    "%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
    "-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
    "-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
    "-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
    goto finish
    :finish
    ENDLOCAL
    I would appreciate if anybody can help me.
    Mallik.
    "Marco" <[email protected]> wrote:
    >
    hi all, i am trying to start a managed server using nodeManager, but
    i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for
    server managedServer via the Node Manager - reason: [CommandInvoker:
    Failed to
    send command: 'online to server 'managedServer' to NodeManager at host:
    'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
    was unable
    to negotiate an acceptable set of security parameters.. Please ensure
    that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
    at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
    -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost
    and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try
    to start
    the managed server via adminserver console, i got the exception mentioned
    in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver,
    and
    nodemanager is supposed to run at localhost:5555 (and indeed it does,
    because
    ihave started it successfully).
    thanx in advance and regards marco

Maybe you are looking for