Datacentre L2 cluster extension

I have two datacentres, where each has the following setup. The servers connects to two 450x switches which connects to two 650x switches. This is a two-tier design since the 6506 forms the core layer of the network. I have clustered servers in the two DCs that needs a L2 LAN extension over CWDMs. Many design guides shows that i have to extend the L2 over the core since i don't have a dedicated access layer and distribution Layer. However i don't want to do this since it will lead to STP issues at the core. What would happen if instead of implementing a collapsed core, i implement a collapsed distribution layer such that the 450x switches forms the access & distribution which would connect to the 650x over L3 links. With this i would have the L2 VLAN extension over the four 450x switches in the two datacentres. I know the ultimate solution is to invest in a 3 tier design but i need this to work and to work perfectly.Kindly shed some light into this design.
In addition i have redundant L3 connections between the two datacentres connected over the 650x core switches, With this, how do you deal with the datacentre subnet that will be learnt and advertised from two different sources?

Look into using EoMPLS or L2TPv3 ... allowing you to establish L2 connectivity over a routed network.
-Brad

Similar Messages

  • Cluster Extensions

    Hi All,
    Is there any good documentation on setting up Extended RAC with ASM using Host Mirroring. Need the steps.
    Looking for 11g.
    Regards

    Have gone through the docs you all sent;
    We intend to use 11gR2. If we use ASM as mirroring instead of any CLVM.
    The Main issues bugging me ;
    How the mirroring is getting done by ASM ; sync the 2 SAN Boxes accross the Cluster.
    My architecture proposed is a 3 Node RAC. 2 Nodes with one san on one-site and 1 Node with another SAN on second-site.
    How to design the failover groups. How each site is presented to the other node.
    Then the Network architecture;
    Is it achievable in 11gR2 + ASM ?
    Popular methods are using a CLVM 3rd party tool like Veritas, Sun Cluster.
    Is there any document on implementation methodology.

  • Question on coherence

    When installing ODI 12.1.3, using the Infratructure for the Enterprise features, it installs Coherence product files. 
    Once you create the domain, it automatically includes the Coherence Cluster Extensions and you can't appear to deselect this as it also deselects a lot of the other options - JRF, Enterprise Manager, ODI Agent.
    Later on during the configuration, it also expects a name for a coherence default cluster.
    Doesn't the use of Coherence incur additional licensing?  If so, is Is there any way to stop Coherence from running to prevent this?

    Hi goodboy626696,
    Ultimately, the configuration descriptor is located using the ClassLoader.getResource("session-cache-config.xml") API. It's up to the loader implementation to use a parent-first or child-first look-up strategy, but in either case you could remove that file from a web-app and place it in such a way that it's accessible and loadable by any ClassLoader.
    Having said that... if you change the "session-cache-config.xml", you would need to restart an application anyway, right? And if you change it in a way that affects all the applications, you would need to restart them all, right?
    Now, since I assume you have an automated build anyway and it refers to a common location for a descriptor, it's just a question of running that automated build before restarting the apps, so I'm not sure moving the descriptor buys you much.
    Regards,
    Gene

  • Maximum number of CCM user

    Hello,
    Does anybody can point me the link or webpage regarding to the maximum of users that I can configure in CCM?
    I'd like to follow datasheet like if my server is 7845 then I can have approximately 7500 users. But I'm not quite sure this is a proper estimation.
    Thank you very much.
    Chinnawoot

    The 7,500 figured mentioned for the 7845 refers more to the supported number of phones than users. This is a rough estimation and any large deployment should be planned using the appropriate capacity planning tools.
    CUCM uses a server clustering design with the typical maximum number of phones per cluster being 30,000 although Cisco have deployed "mega-clusters" for some customers that exceed this number. Clusters can also be linked together and newer versions of CUCM support cross-cluster extension mobility so the limits are fairly elastic.
    The best place to understand CUCM is at the SRND design guide.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/callpros.html
    I am sure that if you have a requirement for 5 million users your local Cisco office would love to talk to you .

  • When will BRE [Backup restartable Extensions] be available in Ontap Cluster mode ?

    Hi Folks, When will BRE [Backup restartable Extensions] be available in Ontap Cluster mode. With 7-mode there is no issue, we can suspend and restart backup from the checkpoint, however with Ontap cluster mode version 8.3 I am currently running, this is not possible [I guess all versions]. If the Job is suspended in cluster mode, session ID is lost and new session  ID is generated when the backup is resumed, in other words data backup starts from begining. Is this something will be available in Onap 8.4 cluster mode ? Thanks,
    -Ashwin 

    Hi, Yeah, you are right - 8.3RC1 is older than 8.3P1.
     8.3 Releases:
     8.3RC1 ----> old release [I already tested - dump restart does not work]
     8.3RC2
     8.3
     8.3P1 -----> Customer already is on higher update and it still dosent work
     8.3P2
     8.3.1RC1 ---> Latest release
    My confusion has only increased now as far as when this BUG is fixed Or if at all fixed?
    http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1472 According to this BUG, this is already fixed in all versions of 8.3. I am currently running 8.3RC1 Simulator and suspending a Job is causing NDMP session ID to end. In 7-mode: When we suspend a Job from Backup Software, NDMP session ID is not lost and when you run Backup status command, it shows -> State : RESTARTABLEThe key word is 'RESTARTABLE' which dosent seem to work in cluster mode.
    The NDMP Backup Restart Extension (BRE) interface is a proprietary extension defined in class 0x2050
    According to NDMP.org:
    NDMP_BRE_RESTART_BACKUP:
    This request is used by the backup application (DMA) to instruct the Data Server to restart a previous backup operation at a specific point in the backup stream.  Request arguments include a handle to a previously created backup context, the restart point specified as an absolute offset within the backup stream, and a file history entry corresponding to the restart point.The backup restart mechanism requires that the Data Server generate file history information and that the Data Server implementation of file history generate fh_info values as absolute byte offsets within the backup stream. The backup application determines restart points by accessing the Tape Server NDMP_MOVER_GET_STATE bytes_moved value at appropriate ‘checkpoints’ during the original backup operation. A checkpoint represents a known good point in the backup operation. BRE extensions are bydefault disabled, I enabled by setting it 'true' yet its not working. CMODE83RC1::*> ndmp extensions show
      (vserver services ndmp extensions show)Is Extension 0x2050 Enabled: true Thanks,
    -Ashwin

  • Windows Server 2012 - Hyper-V - iSCSI SAN - All Hyper-V Guests stops responding and extensive disk read/write

    We have a problem with one of our deployments of Windows Server 2012 Hyper-V with a 2 node cluster connected to a iSCSI SAN.
    Our setup:
    Hosts - Both run Windows Server 2012 Standard and are clustered.
    HP ProLiant G7, 24 GB RAM, 2 teamed NIC dedicated to Virtual Machines and Management, 2 teamed NIC dedicated to iSCSI storage. - This is the primary host and normaly all VMs run on this host.
    HP ProLiant G5, 20 GB RAM, 1 NIC dedicated to Virtual Machines and Management, 2 teamed NIC dedicated to iSCSI storage. - This is the secondary host that and is intended to be used in case of failure of the primary host.
    We have no antivirus on the hosts and the scheduled ShadowCopy (previous version of files) is switched of.
    iSCSI SAN:
    QNAP NAS TS-869 Pro, 8 INTEL SSDSA2CW160G3 160 GB i a RAID 5 with a Host Spare. 2 Teamed NIC.
    Switch:
    DLINK DGS-1210-16 - Both the network cards of the Hosts that are dedicated to the Storage and the Storage itself are connected to the same switch and nothing else is connected to this switch.
    Virtual Machines:
    3 Windows Server 2012 Standard - 1 DC, 1 FileServer, 1 Application Server.
    1 Windows Server 2008 Standard Exchange Server.
    All VMs are using dynamic disks (as recommended by Microsoft).
    Updates
    We have applied the most resent updates to the Hosts, WMs and iSCSI SAN about 3 weeks ago with no change in our problem and we continually update the setup.
    Normal operation
    Normally this setup works just fine and we see no real difference in speed in startup, file copy and processing speed in LoB applications of this setup compared to a single host with 2 10000 RPM Disks. Normal network speed is 10-200 Mbit, but occasionally
    we see speeds up to 400 Mbit/s of combined read/write for instance during file repair
    Our Problem
    Our problem is that for some reason all of the VMs stops responding or responds very slowly and you can for instance not send CTRL-ALT-DEL to a VM in the Hyper-V console, or for instance start task manager when already logged in.
    Symptoms (i.e. this happens, or does not happen, at the same time)
    I we look at resource monitor on the host then we see that there is often an extensive read from a VHDX of one of the VMs (40-60 Mbyte/s) and a combined write speed to many files in \HarddiskVolume5\System Volume Information\{<someguid and no file extension>}.
    See iamge below.
    The combined network speed to the iSCSI SAN is about 500-600 Mbit/s.
    When this happens it is usually during and after a VSS ShadowCopy backup, but has also happens during hours where no backup should be running (i.e. during daytime when the backup has finished hours ago according to the log files). There is however
    not that extensive writes to the backup file that is created on an external hard drive and this does not seem to happen during all backups (we have manually checked a few times, but it is hard to say since this error does not seem leave any traces in event
    viewer).
    We cannot find any indication that the VMs themself detect any problem and we see no increase of errors (for example storage related errors) in the eventlog inside the VMs.
    The QNAP uses about 50% processing Power on all cores.
    We see no dropped packets on the switch.
    (I have split the image to save horizontal space).
    Unable to recreate the problem / find definitive trigger
    We have not succeeded in recreating the problem manually by, for instance, running chkdsk or defrag in VM and Hosts, copy and remove large files to VMs, running CPU and Disk intensive operations inside a VM (for instance scan and repair a database file).
    Questions
    Why does all VMs stop responding and why is there such intensive Read/Writes to the iSCSI SAN?
    Could it be anything in our setup that cannot handle all the read/write requests? For instance the iSCSI SAN, the hosts, etc?
    What can we do about this? Should we use MultiPath IO instead of NIC teaming to the SAN, limit bandwith to the SAN, etc?

    Hi,
    > All VMs are using dynamic disks (as recommended by Microsoft).
    If this is a testing environment, it’s okay, but if this a production environment, it’s not recommended. Fixed VHDs are recommended for production instead of dynamically expanding or differencing VHDs.
    Hyper-V: Dynamic virtual hard disks are not recommended for virtual machines that run server workloads in a production environment
    http://technet.microsoft.com/en-us/library/ee941151(v=WS.10).aspx
    > This is the primary host and normaly all VMs run on this host.
    According to your posting, we know that you have Cluster Shared Volumes in the Hyper-V cluster, but why not distribute your VMs into two Hyper-V hosts.
    Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster
    http://technet.microsoft.com/en-us/library/jj612868.aspx
    > 2 teamed NIC dedicated to iSCSI storage.
    Use Microsoft MultiPath IO (MPIO) to manage multiple paths to iSCSI storage. Microsoft does not support teaming on network adapters that are used to connect to iSCSI-based storage devices. (At least it’s not supported until Windows Server 2008 R2. Although
    Windows Server 2012 has built-in network teaming feature, I don’t article which declare that Windows Server 2012 network teaming support iSCSI connection)
    Understanding Requirements for Failover Clusters
    http://technet.microsoft.com/en-us/library/cc771404.aspx
    > I have seen using MPIO suggests using different subnets, is this a requirement for using MPIO
    > or is this just a way to make sure that you do not run out of IP adressess?
    What I found is: if it is possible, isolate the iSCSI and data networks that reside on the same switch infrastructure through the use of VLANs and separate subnets. Redundant network paths from the server to the storage system via MPIO will maximize availability
    and performance. Of course you can set these two NICs in separate subnets, but I don’t think it is necessary.
    > Why should it be better to not have dedicated wireing for iSCSI and Management?
    It is recommended that the iSCSI SAN network be separated (logically or physically) from the data network workloads. This ‘best practice’ network configuration optimizes performance and reliability.
    Check that and modify cluster configuration, monitor it and give us feedback for further troubleshooting.
    For more information please refer to following MS articles:
    Volume Shadow Copy Service
    http://technet.microsoft.com/en-us/library/ee923636(WS.10).aspx
    Support for Multipath I/O (MPIO)
    http://technet.microsoft.com/en-us/library/cc770294.aspx
    Deployments and Tests in an iSCSI SAN
    http://technet.microsoft.com/en-US/library/bb649502(v=SQL.90).aspx
    Hope this helps!
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Lawrence
    TechNet Community Support

  • Error System Copy on cluster using R3load

    Hi currently we are doing a system copy on Cluster using R3load
    Source System win2003 SP2 32bit, MSSQl2000 SP4 32 bit
    Target System  win 2003 Sp2 64bit, MSSQL2005 SP2 X64 Server
    We have successfully installed MSSQL2005 Sp2 64 bit
    We have successfully installed Central Instance
    When we are trying to install the database Instance using R3load dump
    We are getting the fallowing error
    ERROR 2008-09-07 20:55:14
    MDB-05053  Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
    Please help me out to resolve this issue
    Thanx
    Jarish
    Entire log
    INFO 2008-09-07 20:26:00
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/keydb.xml to: q0w9e9r8t7.1.xml.
    INFO 2008-09-07 20:26:00
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/keydb.xml to: q0w9e9r8t7.1.xml.
    INFO 2008-09-07 20:26:00
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\q0w9e9r8t7.1.xml.
    INFO 2008-09-07 20:26:01
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/keydb.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/keydb.1.xml.
    INFO 2008-09-07 20:26:01
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/keydb.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/keydb.1.xml.
    INFO 2008-09-07 20:26:01
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\keydb.1.xml.
    INFO 2008-09-07 20:26:01
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\change.log.
    INFO 2008-09-07 20:26:01
    Output of change user /install is written to the logfile change.log.
    WARNING 2008-09-07 20:26:01
    Execution of the command "change user /install" finished with return code 1. Output:
    Install mode does not apply to a Terminal server configured for remote administration.
    INFO 2008-09-07 20:26:01
    File not found: [C:/DOCUME1/ADMINI1.SBA/LOCALS~1/Temp/2/sapinst_exe.1064.1220804594/msvcp71.dll].
    INFO 2008-09-07 20:26:01
    File not found: [C:/DOCUME1/ADMINI1.SBA/LOCALS~1/Temp/2/sapinst_exe.1064.1220804594/msvcr71.dll].
    INFO 2008-09-07 20:26:01
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'SBA\Administrator' on host '.'.
    INFO 2008-09-07 20:26:01
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\summary.html.
    PHASE 2008-09-07 20:26:01
    Prepare the installation program.
    INFO 2008-09-07 20:26:03
    Installation start: Sunday, 07 September 2008, 20:26:00; installation directory: C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB; product to be installed: SAP R3E 4.7 Extension Set 2 SR1> ABAP System> MS SQL Server> Non-Unicode> Database Instance Installation
    INFO 2008-09-07 20:26:38
    Host operation t_HostInfo_SHARED processed successfully.
    INFO 2008-09-07 20:28:26
    The 'saploc' share exists in directory 'S:/usr/sap'. Choosing drive S: as the SAP system drive.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssversions.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssversions.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mssversions.xml.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/db_all.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/db_all.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\db_all.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/db_di_clust.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/db_di_clust.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\db_di_clust.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/db_std_checks.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/db_std_checks.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\db_std_checks.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_get_defpath.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_get_defpath.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_get_defpath.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_get_r3db_config.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_get_r3db_config.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_get_r3db_config.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_init_jc.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_init_jc.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_init_jc.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_r3db_gconf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_r3db_gconf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_r3db_gconf.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_r3db_lconf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_r3db_lconf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_r3db_lconf.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_r3srv_conf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_r3srv_conf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_r3srv_conf.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_schema_cnv.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_schema_cnv.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_schema_cnv.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_sps_droptmp.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_sps_droptmp.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_sps_droptmp.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_users_sid_drop.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_users_sid_drop.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_users_sid_drop.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_users_sid_drop_objs.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/mss_users_sid_drop_objs.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mss_users_sid_drop_objs.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/srvchk.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/srvchk.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\srvchk.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/usrabap.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/usrabap.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\usrabap.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/usrstd.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL/usrstd.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\usrstd.sql.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/db_all.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/db_all.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/db_std_checks.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/db_std_checks.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/mss_r3db_gconf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/mss_r3db_gconf.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/usrabap.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/usrabap.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/usrstd.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:29:17
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/SQL9/usrstd.sql to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO[E] 2008-09-07 20:30:00
    Account group="ORA_PRD_DBA" does not exist.
    INFO[E] 2008-09-07 20:30:00
    Account group="ORA_PRD_OPER" does not exist.
    INFO[E] 2008-09-07 20:30:00
    Account group="SBA\dbprdctl" does not exist.
    INFO 2008-09-07 20:48:16
    Copying file E:/Export_PRD/DB/MSS/DBSIZE.XML to: DBSIZE.XML.
    INFO 2008-09-07 20:48:16
    Copying file E:/Export_PRD/DB/MSS/DBSIZE.XML to: DBSIZE.XML.
    INFO 2008-09-07 20:48:16
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\DBSIZE.XML.
    INFO 2008-09-07 20:50:58
    Package table created
    INFO 2008-09-07 20:50:58
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssprocs620.dat to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:50:58
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssprocs620.dat to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:50:58
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mssprocs620.dat.
    INFO 2008-09-07 20:50:58
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssprocs620BW.dat to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:50:58
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssprocs620BW.dat to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:50:58
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mssprocs620BW.dat.
    INFO 2008-09-07 20:50:58
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssprocs640.dat to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:50:58
    Copying file E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08/IM_WINDOWS_X86_64/SAPINST/NT/COMMON/MSS/mssprocs640.dat to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB.
    INFO 2008-09-07 20:50:58
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mssprocs640.dat.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/summary.html to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/summary.1.html.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/summary.html to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/summary.1.html.
    INFO 2008-09-07 20:53:12
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\summary.1.html.
    PHASE 2008-09-07 20:53:12
    SAP Web Application Server
    PHASE 2008-09-07 20:53:12
    Request common parameters of SAP system
    PHASE 2008-09-07 20:53:12
    Collecting information on database configuration
    PHASE 2008-09-07 20:53:12
    Collecting information on database configuration
    PHASE 2008-09-07 20:53:12
    Create accounts
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.1.xml.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.1.xml.
    INFO 2008-09-07 20:53:12
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\product.1.xml.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.2.xml.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/product.2.xml.
    INFO 2008-09-07 20:53:12
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\product.2.xml.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/mssversions.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/mssversions.1.xml.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/mssversions.xml to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/mssversions.1.xml.
    INFO 2008-09-07 20:53:12
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\mssversions.1.xml.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/DBSIZE.XML to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/DBSIZE.1.XML.
    INFO 2008-09-07 20:53:12
    Copying file C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/DBSIZE.XML to: C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/DBSIZE.1.XML.
    INFO 2008-09-07 20:53:12
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\DBSIZE.1.XML.
    WARNING 2008-09-07 20:53:25
    Existing account SAPMssXPUser has the primary group None, not Administrators. Changing primary group.
    PHASE 2008-09-07 20:53:25
    Preparing OS account for MCOD installation
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    PHASE 2008-09-07 20:53:25
    Request operating system user information
    INFO 2008-09-07 20:53:26
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-2140900914-1967063802-3263448767-500' on host 'QASECC1'.
    INFO 2008-09-07 20:53:26
    Successfully added privileges 'SeServiceLogonRight SeNetworkLogonRight SeDenyInteractiveLogonRight SeDenyRemoteInteractiveLogonRight' to account 'SBA\SAPServicePRD' on host 'QASECC1'.
    INFO 2008-09-07 20:53:26
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'SBA\prdadm' on host 'QASECC1'.
    INFO 2008-09-07 20:53:26
    All 'tNT_RegistryEntries' table rows evaluated.
    PHASE 2008-09-07 20:53:27
    Preparing DBMS-specific environment variables
    INFO 2008-09-07 20:53:27
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:27
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:27
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:27
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:28
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:28
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:28
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:28
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:28
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:28
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:28
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:28
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:29
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:29
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:29
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:29
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    INFO 2008-09-07 20:53:29
    Switched to user: prdadm.
    INFO 2008-09-07 20:53:29
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    PHASE 2008-09-07 20:53:29
    Adapt file system
    PHASE 2008-09-07 20:53:29
    Prepare check/adapt SAP instance file system
    INFO 2008-09-07 20:53:30
    File system node S:\usr\sap exists.
    INFO 2008-09-07 20:53:30
    All file system node operations of table t_SAPComponent_Filesystem_Action_SHARED processed successfully.
    INFO 2008-09-07 20:53:30
    File system node S:\usr\sap/PRD exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node S:\usr\sap/tmp exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/tmp exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/EPS exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/EPS/in exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/EPS/out exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/EPS/log exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/bin exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/buffer exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/cofiles exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/data exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/etc exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/log exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    File system node
    DEVECC64\sapmnt\trans/sapnames exists already. Nothing to do.
    INFO 2008-09-07 20:53:30
    All file system node operations of table t_SAPComponent_Filesystem_Action_SHARED processed successfully.
    INFO 2008-09-07 20:53:30
    All file system node operations of table t_SAPComponent_Filesystem_Action_SHARED processed successfully.
    INFO 2008-09-07 20:53:31
    All NT shares while processing the table 'tNT_SHARE' created successfully.
    PHASE 2008-09-07 20:53:31
    Extract archives
    INFO 2008-09-07 20:53:31
    All file system node operations of table t_SAPComponent_Archives_FORMS_SHARED processed successfully.
    PHASE 2008-09-07 20:53:31
    Extract SAP System kernel archives
    INFO 2008-09-07 20:53:32
    Copying file S:/usr/sap/PRD/SYS/exe/run/rfcexec.sec to: /rfcexec.sec.
    INFO 2008-09-07 20:53:32
    Copying file S:/usr/sap/PRD/SYS/exe/run/rfcexec.sec to: /rfcexec.sec.
    INFO 2008-09-07 20:53:32
    Creating file C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB\SAPMMC.SAR.log.
    INFO 2008-09-07 20:53:33
    C:/DOCUME1/ADMINI1.SBA/LOCALS~1/Temp/2/sapinst_exe.1064.1220804594\sapcar.exe -xvgf E:/4.7_200Ext/51033746_15_Inst_Master/Installation_Master_6.20_6.40_05_08\IM_WINDOWS_X86_64/SAPINST/NT/AMD64/MMC/SAPMMC.SAR, -R C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB succeeded. (See output in './SAPMMC.SAR.log'.)
    INFO 2008-09-07 20:53:33
    While copying node C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/sapmmc.dll to C:/WINDOWS/system32/sapmmc.dll, source is not newer than the target. Nothing to do.
    INFO 2008-09-07 20:53:33
    While copying node C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/sapmmcada.dll to C:/WINDOWS/system32/sapmmcada.dll, source is not newer than the target. Nothing to do.
    INFO 2008-09-07 20:53:33
    While copying node C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/sapmmcdb6.dll to C:/WINDOWS/system32/sapmmcdb6.dll, source is not newer than the target. Nothing to do.
    INFO 2008-09-07 20:53:33
    While copying node C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/sapmmcinf.dll to C:/WINDOWS/system32/sapmmcinf.dll, source is not newer than the target. Nothing to do.
    INFO 2008-09-07 20:53:33
    While copying node C:/Program Files/sapinst_instdir/R3E47X2/SYSTEM/ABAP/MSS/NUC/DB/sapmmcms.dll to C:/WINDOWS/system32/sapmmcms.dll, source is not newer than the target. Nothing to do.
    INFO 2008-09-07 20:53:33
    All file system node operations of table t_SAPComponent_Archives_Copy_SHARED processed successfully.
    INFO 2008-09-07 20:53:33
    Removing file S:\usr\sap\PRD\SYS\exe\run\strdbs.cmd.
    INFO 2008-09-07 20:53:33
    Creating file S:\usr\sap\PRD\SYS\exe\run\strdbs.cmd.
    INFO 2008-09-07 20:53:34
    All 'tNT_RegistryEntries' table rows evaluated.
    INFO 2008-09-07 20:53:34
    All NT registry entries from the tNT_RegistryEntries table created or updated successfully.
    PHASE 2008-09-07 20:53:34
    Creating service ports
    PHASE 2008-09-07 20:53:35
    Generate instance profiles
    PHASE 2008-09-07 20:53:35
    Create versions of default profile, instance profile and start profile
    INFO 2008-09-07 20:53:35
    All file system node operations of table t_SAPComponent_Profiles_FORMS_SHARED processed successfully.
    PHASE 2008-09-07 20:53:35
    Preparing DBMS-specific profile parameters
    INFO 2008-09-07 20:53:35
    Adapt operation t_SAPComponent_Profiles_SHARED processed successfully.
    PHASE 2008-09-07 20:53:35
    Setting up database server
    ERROR 2008-09-07 20:53:36
    MDB-05053  Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
    ERROR 2008-09-07 20:55:14
    MDB-05053  Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

    Hi,
    I think some of the Microsoft runtime DLLs are missing, which you can observe in the above pasted log :-
    INFO 2008-09-07 20:26:01
    File not found: C:/DOCUME1/ADMINI1.SBA/LOCALS~1/Temp/2/sapinst_exe.1064.1220804594/msvcp71.dll.
    INFO 2008-09-07 20:26:01
    File not found: C:/DOCUME1/ADMINI1.SBA/LOCALS~1/Temp/2/sapinst_exe.1064.1220804594/msvcr71.dll.
    Do have a look at snote Note 684106 - Microsoft runtime DLLs to drill more in to the issue.
    Rgds
    Radhakrishna D S

  • Can a BO XI R2 Cluster Span Two Subnets?

    We were able to setup a BO XI R2 two server cluster using two servers on the same subnet.
        Server A at IP address -.-.---.45
        Server B at IP address -.-.---.46
    Schedule reports and ad hoc queries through the web servers (on both machines) operated without issue. [The two servers share a Sybase database and a NetApp file system.]
    We then attempted to setup a BO XI R2 two server cluster, but with the two servers in different data centers and on different subnets. [Everything else is the same ... shared Sybase database, shared NetApp file system.] The two servers are able to ping each other without any trouble. Unfortunately, the reports we schedule only seem to run on the server where they were introduced. [Reports introduced on Server A only run on Server A - even if Server B goes down. And, vise versa.]
    We are wondering if there is some communications between the two servers that requires the servers to be on the same subnet.
    Edited by: Wesley Conner on Jun 19, 2009 2:45 AM

    We have had customers and employees successfully configure clustered CMS's across subnets, we have also had plenty of issues (especially if the subnets are geographically seperated by WAN links).
    You may want to open a case with support as some extensive tracing and analysis may be required. If no filtering is occurring and the link has enough bandwidth then it should work. CMS communication to the CMS DB is rather extensive so weithout enough bandwidth I'd expect all kinds of issues. I'm not sure how much would be enough but to be safe I'd say at least the same pipe of the server NIC(s)
    Regards,
    Tim

  • Error reading Web application occurs when starting one server in the cluster

    Hi All,
              I have configured two cluster servers in the win 2000. Admin server also win
              2000. One cluster server joins the cluster while other gives following error
              and starts. But it seems that it does not join to the cluster view because
              prevoius server only serves the requests. I have attached the log also.
              <> <101062> <[HTTP synergyserver] Error reading Web application
              "D:\bea\wlserver6.0\.\config\bd2kadmindomain\applications\.wl_temp_do_not_de
              lete_synergyserver\wl_local_comp12863.war">
              java.net.UnknownHostException: java.sun.com
              at java.net.InetAddress.getAllByName0(InetAddress.java:571)
              at java.net.InetAddress.getAllByName0(InetAddress.java:540)
              at java.net.InetAddress.getAllByName(InetAddress.java:533)
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:159)
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:221)
              at weblogic.net.http.HttpClient.<init>(HttpClient.java:85)
              at
              weblogic.net.http.HttpURLConnection.getHttpClient(HttpURLConnection.java:109
              at
              weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:30
              1)
              at java.net.URL.openStream(URL.java:798)
              at
              weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultRead
              erFactory.java:149)
              at
              weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
              Entity(DefaultEntityHandler.java:775)
              at
              weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
              Subset(DefaultEntityHandler.java:570)
              at
              weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner
              .java:1131)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocum
              entScanner.java:2177)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScan
              ner.java:2133)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatc
              h(XMLDocumentScanner.java:882)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
              nner.java:380)
              at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
              at
              weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
              va:123)
              at
              weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:1
              78)
              at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:446)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:404)
              at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
              at weblogic.j2ee.Application.addComponent(Application.java:133)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:327)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:143)
              at
              weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
              76)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:562)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              48)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:285)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
              at $Proxy40.addWebDeployment(Unknown Source)
              at
              weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
              t(WebServerMBean_CachingStub.java:1012)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:313)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              Target.java:277)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              eploymentTarget.java:232)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              entTarget.java:192)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:562)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              48)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:285)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
              at $Proxy0.updateDeployments(Unknown Source)
              at
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              ServerMBean_CachingStub.java:2299)
              at
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              icationManager.java:240)
              at
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              r.java:122)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:562)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              48)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:285)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
              at $Proxy9.start(Unknown Source)
              at
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              ApplicationManagerMBean_CachingStub.java:435)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1033)
              at weblogic.management.Admin.finish(Admin.java:493)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
              at weblogic.Server.main(Server.java:35)
              Each cluster servers domain names are different i.e. not "mydomain". The
              file its complaining is in the specified directory and it has proper
              priviledges.
              If anyone has an idea please respond.
              Thanks
              Nalika
              [synergyserver.log]
              

    You're getting that probably because the WL instance was not shut down properly.
    If that's the case, you'll need to remove an ldap lock file (with a .lok extension) in the directory of ldap files (under the server dir) .

  • Hyper-V host server upgrade from Server 2008 R2 Enterprise SP1 to Server 2012 R2 Datacentre

    We are about to upgrade our Hyper-V host servers from Server 2008R2 Enterprise SP1 to Server 2012 R2 Datacentre to take advantage of the latest Hyper-V features.
    This only concerns the host servers and not the guest VMs running on the hosts (they will be upgraded next year).
    This is what is running on our host servers:
    Host 1
    File,print & issuing CA server
    Exchange 2010
    SharePoint 2010
    Quickbooks server
    Domain controller 1
    Offline CRL CA
    Host 2
    SQL 2008
    Forefront TMG 2010
    Domain Controller 2
    Windows 7 client
    With this is mind, I have drafted a rough action plan as follows:
    Create a list of all file locations for VM memory, snapshots, virtual memory and Hyper-V config files
    Document all existing system settings
    Gather server information, download drivers, RAID controller and other boot drivers & firmware updates (in case the in-place upgrade fails)
    Test all software media
    Copy all VMs onto external data storage (NAS drive)
    As part of the upgrade process we will redistribute some hard drive space i.e.
    expand them to their new sizes and verify the data integrity of copied VMs by powering up each VM in a test environment
    Wipe and adjust the sizes of the host partitions to accommodate the expanded VMs
    Perform an in-place upgrade to Server 2012 R2 Datacenter
    Check EV, services etc
    Change the default locations for VM memory, snapshots, virtual memory and Hyper-V config files
    Upgrade Anti-virus and other system software
    Test the system
    Are there any glaring omissions? Does anyone have any tips they can give me?

    Hi Marco,
    always do a fresh Installation of your hyper-V Hosts, you could end up doing a lot of Troubleshooting with Drivers,Addons etc.. new Installation ist way faster.
    Depending if you have a Cluster or Standalone Servers there are different ways to do it.
    When you have installed your 2012 R2 Hyper-V Server you just can Import the VMs from the new Location.
    As far as i know VMs with snapshots are not supported, so you have to remove them before doing that move and commit the changes to the vhd files, the VM need to be offline on 2008R2 to do that.
    You do not Need to Export the VMs on 2008R2, just copy it, normaly you should have all Files of a VM in one Folder.
    A working Backup is always your friend on such Tasks.
    When the VMs are running on Hyper-V 2012R2 do not forget to Update the Integration Services.
    Make Sure your Servers Hardware are still supported with 2012R2, see Server Catalog and Support Matrix of the Vendor.
    And last one, where possible and supported convert the VHDs to VHDx Disks, after testing the first boot of the VM.
    Udo

  • WebLogic 5.1 sp6 .. session in cluster not working properly

    It seems like there is a problem in Weblogic 5.1 with sessions in a
              clustered environment. The problem is immediately visible with sp3 but
              also appears in different form with sp6 . I discovered the problem is
              actually with session while testing the cluster with a Session servlet
              given with the Weblogic 5.1 kit.
              I regiestered the servlet as servlet/session.
              The environment is briefly as follows:
              Solaris 2.6
              Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
              machine with two multihome addreses like home1:7001 and home2:7001
              Cluster properties in mycluster/weblogic.properties are set as,
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.persistence=true
              weblogic.httpd.session.persistentStoreType=replicated
              and also started with required cluster properties in startup.
              iPlanet 4.0 webserver - obj.conf has entries like
              WebLogicCluster="home1:7001,home2:7001"
              All requests are made as http://<host>/servlet/session
              sp3 ) After both members are booted up, the first call to session
              servlet from any new browser session throws a NullException in server,
              but subsequent calls work fine. Single server works fine.
              After looking at sp6 release notes it appeared to me that it was a known
              problem with cluster.
              sp6 ) After both members are booted up, all calls to session servlet do
              not complete and eventually it times out. Other servlets work fine.
              It only works if we do these steps,
              - one of the member is booted up and then session servlet is called and
              response comes back.
              - second member is booted up and it works well if session servlet is
              called. Subsequent requests to both members work fine.
              Another strange behaviour:
              While running a snoop servlet in cluster subsequent requests show,
              Requested url :
              either http://<host>/servlet/snoop
              or http://<host>:7001/servlet/snoop alternatively
              which is strange.
              

    You are not using the same service pack on both the servers. let try do that and see how it goes.
              1. Also, if you are doing testing why do you so many threads.
              2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
              - Prasad
              Sutanu Ghosh wrote:
              > Here are the thread dumps from both members of the cluster. I took the dumps
              > about 5 times in 10 secs interval. It will be helpful for us if you can give
              > some insight about this problem.
              > Also about the snoop servlet, can you explain why the requested url is
              > different (one with weblogic port another without it) in every alternate
              > requests ?
              > thanks
              >
              > Prasad Peddada wrote:
              >
              > > Sutanu Ghosh wrote:
              > >
              > > > It seems like there is a problem in Weblogic 5.1 with sessions in a
              > > > clustered environment. The problem is immediately visible with sp3 but
              > > > also appears in different form with sp6 . I discovered the problem is
              > > > actually with session while testing the cluster with a Session servlet
              > > > given with the Weblogic 5.1 kit.
              > > > I regiestered the servlet as servlet/session.
              > > >
              > > > The environment is briefly as follows:
              > > > Solaris 2.6
              > > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
              > > > machine with two multihome addreses like home1:7001 and home2:7001
              > > > Cluster properties in mycluster/weblogic.properties are set as,
              > > > weblogic.httpd.clustering.enable=true
              > > > weblogic.httpd.session.enable=true
              > > > weblogic.httpd.session.persistence=true
              > > > weblogic.httpd.session.persistentStoreType=replicated
              > > > and also started with required cluster properties in startup.
              > > >
              > > > iPlanet 4.0 webserver - obj.conf has entries like
              > > > WebLogicCluster="home1:7001,home2:7001"
              > > >
              > > > All requests are made as http://<host>/servlet/session
              > > >
              > > > sp3 ) After both members are booted up, the first call to session
              > > > servlet from any new browser session throws a NullException in server,
              > > > but subsequent calls work fine. Single server works fine.
              > > > After looking at sp6 release notes it appeared to me that it was a known
              > > > problem with cluster.
              > > >
              > > > sp6 ) After both members are booted up, all calls to session servlet do
              > > > not complete and eventually it times out. Other servlets work fine.
              > > > It only works if we do these steps,
              > >
              > > Take thread dumps in intervals of 10 seconds and post them again.
              > >
              > > > - one of the member is booted up and then session servlet is called and
              > > > response comes back.
              > > > - second member is booted up and it works well if session servlet is
              > > > called. Subsequent requests to both members work fine.
              > > >
              > > > Another strange behaviour:
              > > > While running a snoop servlet in cluster subsequent requests show,
              > > > Requested url :
              > > > either http://<host>/servlet/snoop
              > > > or http://<host>:7001/servlet/snoop alternatively
              > > > which is strange.
              >
              > ------------------------------------------------------------------------
              > SIGQUIT
              > A SIGQUIT has been received. Do you want to:
              > [ 0 ] continue program
              > [ 1 ] check & print one deadlock
              > [ 2 ] check & print all deadlocks
              > [ 3 ] dump thread stacks
              > [ 4 ] dump lock registry
              > [ 5 ] heap inspection
              > [ 6 ] terminate program
              > Type number corresponding to selected action: Found 0 deadlock
              >
              > Full thread dump:
              > "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
              >
              > [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
              > [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
              > [3] java.lang.Thread.run(Thread.java:479)
              > -------------------
              > "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
              > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
              > [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
              > [4] java.net.ServerSocket.accept(ServerSocket.java:224)
              > [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
              > [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
              > [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
              > -------------------
              > "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
              > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
              > [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
              > [4] java.net.ServerSocket.accept(ServerSocket.java:223)
              > [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
              > -------------------
              > "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
              > [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
              > [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
              > [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
              > [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
              > [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
              > [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
              > [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
              > [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
              > [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
              > [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
              > [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
              > [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
              > [9] weblogic.jndi.Environment.getContext(Environment.java:122)
              > [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
              > [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
              > [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
              > [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
              > [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
              > [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
              > [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
              > [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
              > [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
              > [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
              > [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              > [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
              > [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
              > [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
              > [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              > [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
              > [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
              > [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.ke

  • Cisco ise 1.2 install certificates for ise cluster question

    hello all i have an ise cluster of 4 devices. 1 primary admin/secondary monitor, 1 secondary admin/primary admin and 2 policy nodes
    i need to install public CA certs on them. can I generate 1 CSR on one of the nodes, that includes a SAN with the DNS names of all the nodes?
    Therefore get only 1 cert from the CA, and export and import the same cert into all the other nodes?
    or do i have to generate 1 CSR for each node and purchase 4 certs? Wild card certs is not an option. tHANKS,

    ISE allows you to install a certificate with multiple Subject Alternative Name (SAN) fields. A browser reaching the ISE using any of the listed SAN names will accept the certificate without any error as long as it trusts the CA that signed the certificate.
    The CSR for such a certificate cannot be generated from the ISE GUI. http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-software/113675-ise-binds-multi-names-00.html
    Cisco ISE checks for a matching subject name as follows:
    1. Cisco ISE looks at the subject alternative name (SAN) extension of the certificate. If the SAN contains one or more DNS names, then one of the DNS names must match the FQDN of the Cisco ISE node. If a wildcard certificate is used, then the wildcard domain name must match the domain in the Cisco ISE node's FQDN.
    2. If there are no DNS names in the SAN, or if the SAN is missing entirely, then the Common Name (CN) in the Subject field of the certificate or the wildcard domain in the Subject field of the certificate must match the FQDN of the node.
    3. If no match is found, the certificate is rejected.
    Regards,
    Jatin Katyal
    *Do rate helpful posts*

  • SOA 11.1.1.5 two Node Cluster BAM not starting on the second Machine

    Hi,
    I have installed Oracle SOA 11.1.1.5 in a 2 Node Cluster. Both SOA Managed Servers are coming up fine. BAM Managed Server installed on the primary HOST also comes up fine. But my second BAM Managed Server is not starting. I don't see anything in the logs and on the Console the status is showing as Starting but it never starts. I can access the BAM Console for the one installed on the primary HOST but when giving the URL for the second HOST it doesn't come up as the I don't see an option the server is running.
    I have 2 machines for this cluster setup
    On machine one with IP Address: *192.168.2.2* all below servers come-up fine
    Admin
    BAM1
    SOA1
    On machine two with IP Address: *192.168.3.3* have the below servers and only the SOA is coming up fine BAM not starting
    BAM2 not starting
    SOA2 coming up fine also
    After giving user/password this is what I see in the terminal window and it never moves looks like getting stuck:
    <Mar 8, 2012 12:31:40 PM EST> <Info> <Security> <BEA-090065> <Getting boot ident
    ity from user.>
    Enter username to boot WebLogic server:weblogic
    Enter password to boot WebLogic server:
    <Mar 8, 2012 12:32:58 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
    c Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STARTING>
    <Mar 8, 2012 12:33:01 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
    lf-tuning thread pool>
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
    le C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BA
    M2.log will be rotated. Reopen the log file if tailing has stopped. This can hap
    pen on some platforms like Windows.>
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
    le has been rotated to C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\
    servers\BAM2\logs\BAM2.log00001. Log messages will continue to be logged in C:\o
    racle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BAM2.log.
    >
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <Log Management> <BEA-170019> <The server
    log file C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\
    logs\BAM2.log is opened. All server side log events will be written to this file
    .>
    <Mar 8, 2012 12:33:09 PM EST> <Notice> <Security> <BEA-090082> <Security initial
    izing using security realm myrealm.>
    <Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STANDBY>
    <Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STARTING>
    <Mar 8, 2012 12:33:26 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
    package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.
    model, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, reference
    d from: C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tm
    p\_WL_user\usermessagingserver\wehyzl]. Make sure the referenced optional packag
    e has been deployed as a library.>
    <Mar 8, 2012 12:33:28 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRe
    ceiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.ja
    r), the value for the activation config property 'connectionFactoryJNDIName' wil
    l be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFacto
    ry';>
    <Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-012035> <The Remote interface
    method: 'public abstract void oracle.ucs.userprefs.DefaultFactStore.setBusiness
    FactValue(java.lang.String,java.lang.String,java.lang.Object) throws oracle.ucs.
    userprefs.UserPrefsException' in EJB 'UserPrefsDefaultFactStore' contains a para
    meter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Use
    rPrefsDefaultFactStore' has call-by-reference set to false, this parameter is no
    t Serializable and hence will be passed by reference. A parameter can be passed
    using call-by-value only if the parameter type is Serializable.>
    <Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageDi
    spatcherBean(Application: usermessagingserver, EJBComponent: sdpmessagingclient-
    ejb-parlayx.jar), the value for the activation config property 'connectionFactor
    yJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueC
    onnectionFactory';>
    <Mar 8, 2012 12:33:37 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapt
    er is calling BootstrapContext.createTimer() and allocating a Timer Thread that
    is not managed by WebLogic Server. This may adversely impact the performance/ope
    ration of WebLogic Server.>
    <Mar 8, 2012 12:33:37 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB DriverDis
    patcherBean(Application: usermessagingdriver-email, EJBComponent: sdpmessagingdr
    iver-dispatcher-ejb.jar), the value for the activation config property 'connecti
    onFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDP
    M/QueueConnectionFactory';>
    <Mar 8, 2012 12:33:43 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-adc-ejb.jar/META-INF/ejb-jar.xml. A version attribut
    e 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.>
    <Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-ems-ejb.jar/META-INF/ejb-jar.xml. A version attribut
    e 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.>
    <Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-eventengine-ejb.jar/META-INF/ejb-jar.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.>
    <Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-reportcache-ejb.jar/META-INF/ejb-jar.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.>
    <Mar 8, 2012 12:33:52 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-
    26024> <Registration of driver Email-Driver did not complete; will retry periodi
    cally until messaging server responds.>This is what I see in the diagnostic log
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> And this is what I see in the log
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048125> <BEA-149059> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014021> <The EJB 'BamAdcServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-adc-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014022> <******** oracle.bam.adc.ejb.BamAdcServerRemote is bound with JNDI name:BamAdcServerBean#oracle.bam.adc.ejb.BamAdcServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-adc-ejb_jarBamAdcServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149060> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149059> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> Any help is appreciated.
    Thanks

    Hi,
    I have installed Oracle SOA 11.1.1.5 in a 2 Node Cluster. Both SOA Managed Servers are coming up fine. BAM Managed Server installed on the primary HOST also comes up fine. But my second BAM Managed Server is not starting. I don't see anything in the logs and on the Console the status is showing as Starting but it never starts. I can access the BAM Console for the one installed on the primary HOST but when giving the URL for the second HOST it doesn't come up as the I don't see an option the server is running.
    I have 2 machines for this cluster setup
    On machine one with IP Address: *192.168.2.2* all below servers come-up fine
    Admin
    BAM1
    SOA1
    On machine two with IP Address: *192.168.3.3* have the below servers and only the SOA is coming up fine BAM not starting
    BAM2 not starting
    SOA2 coming up fine also
    After giving user/password this is what I see in the terminal window and it never moves looks like getting stuck:
    <Mar 8, 2012 12:31:40 PM EST> <Info> <Security> <BEA-090065> <Getting boot ident
    ity from user.>
    Enter username to boot WebLogic server:weblogic
    Enter password to boot WebLogic server:
    <Mar 8, 2012 12:32:58 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
    c Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STARTING>
    <Mar 8, 2012 12:33:01 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
    lf-tuning thread pool>
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
    le C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BA
    M2.log will be rotated. Reopen the log file if tailing has stopped. This can hap
    pen on some platforms like Windows.>
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
    le has been rotated to C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\
    servers\BAM2\logs\BAM2.log00001. Log messages will continue to be logged in C:\o
    racle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BAM2.log.
    >
    <Mar 8, 2012 12:33:01 PM EST> <Notice> <Log Management> <BEA-170019> <The server
    log file C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\
    logs\BAM2.log is opened. All server side log events will be written to this file
    .>
    <Mar 8, 2012 12:33:09 PM EST> <Notice> <Security> <BEA-090082> <Security initial
    izing using security realm myrealm.>
    <Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STANDBY>
    <Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STARTING>
    <Mar 8, 2012 12:33:26 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
    package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.
    model, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, reference
    d from: C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tm
    p\_WL_user\usermessagingserver\wehyzl]. Make sure the referenced optional packag
    e has been deployed as a library.>
    <Mar 8, 2012 12:33:28 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRe
    ceiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.ja
    r), the value for the activation config property 'connectionFactoryJNDIName' wil
    l be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFacto
    ry';>
    <Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-012035> <The Remote interface
    method: 'public abstract void oracle.ucs.userprefs.DefaultFactStore.setBusiness
    FactValue(java.lang.String,java.lang.String,java.lang.Object) throws oracle.ucs.
    userprefs.UserPrefsException' in EJB 'UserPrefsDefaultFactStore' contains a para
    meter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Use
    rPrefsDefaultFactStore' has call-by-reference set to false, this parameter is no
    t Serializable and hence will be passed by reference. A parameter can be passed
    using call-by-value only if the parameter type is Serializable.>
    <Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageDi
    spatcherBean(Application: usermessagingserver, EJBComponent: sdpmessagingclient-
    ejb-parlayx.jar), the value for the activation config property 'connectionFactor
    yJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueC
    onnectionFactory';>
    <Mar 8, 2012 12:33:37 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapt
    er is calling BootstrapContext.createTimer() and allocating a Timer Thread that
    is not managed by WebLogic Server. This may adversely impact the performance/ope
    ration of WebLogic Server.>
    <Mar 8, 2012 12:33:37 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB DriverDis
    patcherBean(Application: usermessagingdriver-email, EJBComponent: sdpmessagingdr
    iver-dispatcher-ejb.jar), the value for the activation config property 'connecti
    onFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDP
    M/QueueConnectionFactory';>
    <Mar 8, 2012 12:33:43 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-adc-ejb.jar/META-INF/ejb-jar.xml. A version attribut
    e 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.>
    <Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-ems-ejb.jar/META-INF/ejb-jar.xml. A version attribut
    e 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.>
    <Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-eventengine-ejb.jar/META-INF/ejb-jar.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.>
    <Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
    ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
    iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
    am_11.1.1\ert5kb\oracle-bam-reportcache-ejb.jar/META-INF/ejb-jar.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.>
    <Mar 8, 2012 12:33:52 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-
    26024> <Registration of driver Email-Driver did not complete; will retry periodi
    cally until messaging server responds.>This is what I see in the diagnostic log
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> And this is what I see in the log
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048125> <BEA-149059> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014021> <The EJB 'BamAdcServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-adc-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014022> <******** oracle.bam.adc.ejb.BamAdcServerRemote is bound with JNDI name:BamAdcServerBean#oracle.bam.adc.ejb.BamAdcServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-adc-ejb_jarBamAdcServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149060> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149059> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> Any help is appreciated.
    Thanks

  • Problem starting managed server in Cluster

    Hi,
    I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
    The WebLogic Server encountered a critical failure
    Reason: Assertion violated
    Exception in thread "main" java.lang.NoClassDefFoundError
    at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
    at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
    at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
    at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
    at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
    at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
    at weblogic.Server.main(Server.java:67)
    Could you pl tell the reason of this error?
    Thanks in advance
    Hi,
    Can anybody help?
    Edited by: user10680571 on Dec 4, 2008 4:42 AM

    Thanks David.
    During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
    <04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    Thanks for your help.....

  • WL Cluster with NES Proxy

    We are evaluating the Cluster features of WebLogic and got a eval
              license for the Cluster Support.
              I am running a default cluster (mycluster) using the default Multicast
              address (237.0.0.1) and am seeing
              some strange behaviour/errors.
              Would appreciate some asistance in this matter.
              Our Environment
              I created directory in a shared file system to host the cluster.
              (h:\kkanth\weblogic)
              Created the mycluster directory and other directories as recommended in
              the Administrator's guide.
              I have two WL Servers (asera190 and asera162) with permanent IP
              addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
              I'm using a NES proxy on asera190 with the plugin for WL specified in
              obj.conf alongwith the other parameters.
              I'm able to have both the servers join to cluster mycluster and the WL
              Admin Console does display a tree that depicts the cluster as well as
              servers in it (server61 and server70). The individual server directories
              are being created in h:\kkanth\weblogic\mycluster directory with the
              appropriate access.log and weblogic.log files.
              When a browser attempts to access a URL such as
              http://asera190/weblogic/snoop it does return the proper response, but
              all requests are processed by asera162 which is listed first in the
              obj.conf. Opening multiple sessions does not cause the requests to be
              sent to asera190 which is the second server in the cluster. When
              asera162 is shutdown and removed from the cluster, I hoped that
              subsequent requests would go to asera190. However , depending on the
              origin of the request, different errors were thrown. If I try to access
              http://asera190/weblogic/snoop from a browser on asera190, I get an
              error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
              from asera162 cause "Failure at line 706 of file proxy.cpp".
              I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
              directory as well as the obj.conf file in the ....\config\ directory of
              asera190.
              We are running NES 3.5.1 and have setup proxy35.dll appropriately.
              weblogic.properties
              # THE WEBLOGIC PROPERTIES FILE
              # This file, which conforms to the java.util.Properties file
              # definition, configures your WebLogic products. You cannot run
              # WebLogic Server without setting required configuration properties in
              this
              # file. Required properties are marked and appear first in the file.
              # Details on each entry and important information about configuration
              # and security are documented on our website. Please go to:
              # http://www.weblogic.com/docs45/admindocs/properties.html
              # for full instructions on how to edit this file.
              # You do not need to include properties in this file unless you want to
              # change the default, embedded property. Some properties on the
              # T3AdminProps page are not listed here because the default property
              # is being used. You can change the default by adding the property and
              # its value to this file.
              # You cannot set weblogic.system.home in this file, since the WebLogic
              Server
              # must know where home is in order to retrieve this file. You can
              # change WebLogic home on the command line when you start the
              # WebLogic Server.
              # CLUSTER USERS: Note that the (shared) per-cluster properties file
              should
              # contain most all of the properties in this file. The only properties
              # that potentially belong in a per-server properties file for a server
              # running in a cluster are the registration (startup class) of pinned
              # RMI objects, and a few tuning properties that may be different for
              # servers in the cluster, depending upon hardware and memory. If you use
              # a per-server properties file, please REMOVE all properties except
              those
              # that are specifically required in the per-server properties file. You
              # can find specific notes on clusters by searching through this file for
              # "CLUSTER USERS".
              # The way this file is organized:
              # Core properties (includes REQUIRED and RECOMMENDED)
              # Core system properties
              # Core security-related properties
              # Core security-related properties for SSL
              # Core HTTPD administrative properties
              # Optional properties
              # Administrator properties
              # System properties
              # System startup files
              # System shutdown files
              # Security-related properties for Workspaces
              # Jolt for WebLogic properties
              # WebLogic Enterprise Connectivity properties
              # WebLogic File properties
              # WebLogic JMS demo properties
              # WebLogic RMI demo properties
              # WebLogic EJB demo properties
              # WebLogic ZAC demo properties
              # HTTPD administrative properties
              # WebLogic JDBC driver properties
              # WebLogic JDBC connection pool management
              # WebLogic demo connection pool
              # WebLogic HTTP Servlet properties
              # Proxy servlet registration
              # Classpath servlet registration
              # File servlet registration
              # ServerSideInclude servlet registration
              # PageCompileServlet (used by JHTML)
              # JSPServlet (used by JSP)
              # ServletServlet registration
              # Servlet reload properties
              # Servlet ACLs
              # WebLogic JHTML properties
              # User-written and demo servlet registrations
              # CORE PROPERTIES
              # You should set these before you start the WebLogic Server the first
              time.
              # If you need more instructions on individual properties in this
              # section, check the same section in the Optional Properties, where
              # we've left the long explanations. Or, better yet, go to our
              # website and read all about properties, at:
              # http://www.weblogic.com/docs45/admindocs/properties.html
              # CORE SYSTEM PROPERTIES
              # TCP/IP port number at which the WebLogic Server listens for
              connections
              weblogic.system.listenPort=7001
              # CORE SECURITY-RELATED PROPERTIES
              # Read important information about security at:
              # http://www.weblogic.com/docs45/admindocs/properties.html
              # REQUIRED: The system password MUST be set in order to start the
              # WebLogic Server. This password is case-sensitive, at least 8
              characters.
              # The username for the privileged user is ALWAYS "system".
              # This username and password also includes httpd access (see
              # HTTPD properties below).
              weblogic.password.system=kaykayka
              # RECOMMEND Set to 'everyone' if HTTPD is enabled
              weblogic.allow.execute.weblogic.servlet=everyone
              # Set individual ACLs to restrict access to HTTP-related resources,
              # such as the Administration servlets.
              # To make your own servlets generally available, follow this
              # pattern (provide a weblogic.allow.execute) for your packages and
              # set ACLs as appropriate.
              # CORE SECURITY-RELATED PROPERTIES FOR SSL
              # Read important information about SSL at:
              # http://www.weblogic.com/docs45/classdocs/API_secure.html
              # Enable SSL
              # (default if property not defined is false)
              weblogic.security.ssl.enable=true
              # SSL listen port
              weblogic.system.SSLListenPort=7002
              # Servlets for SSL
              # Authentication servlet for creating tokens for applets
              weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
              # Limits number of unclaimed stored tokens
              weblogic.security.certificateCacheSize=3
              # Capture CA root of client servlet
              weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
              # Certificates for SSL
              # Name of acceptable CA roots
              # For client authentication change value to a valid .pem file
              #weblogic.security.clientRootCA=SecureServerCA.pem
              # Server certificates for SSL
              weblogic.security.certificate.server=democert.pem
              weblogic.security.key.server=demokey.pem
              weblogic.security.certificate.authority=ca.pem
              # registration for certificate generator servlet
              weblogic.httpd.register.Certificate=utils.certificate
              weblogic.allow.execute.weblogic.servlet.Certificate=system
              # CORE HTTPD ADMINISTRATIVE PROPERTIES
              # True permits the HTTPD to run (default)
              # Uncomment this property to disable HTTPD
              #weblogic.httpd.enable=false
              # If authentication is required, add username/password for each user
              # who will be included in an ACL, as in this commented-out example:
              #weblogic.password.peter=#8gjsL4*
              # OPTIONAL PROPERTIES
              # These properties affect the behavior of the WebLogic Server.
              # You only need to set these properties if you want
              # to change the default setting, which is the property shown.
              # ADMINISTRATOR PROPERTIES
              # Administrator properties are optional information properties,
              # particularly useful for clusters.
              #weblogic.administrator.location=3355 California Drive, West Hampshire,
              CA 94104
              #weblogic.administrator.name=Joe Administrator
              #weblogic.administrator.phone=1 415 555 1234
              # SYSTEM PROPERTIES
              # System properties in this section are set to system defaults
              # Performance pack. The shared library must be accessible from your
              # PATH (NT) or from your shared library path (UNIX; the name of the
              # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
              weblogic.system.nativeIO.enable=true
              # Outputs logging information to the console as well as to the log file
              weblogic.system.enableConsole=true
              # Sets the directory or URL for the WebLogic Admin help pages
              # The help pages are shipped in the "docs/adminhelp" directory, in the
              # default document root in public_html
              weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
              # If you prefer to access the most recent help pages, you can do so
              online
              # by commenting out the previous property and uncommenting this one:
              #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
              # Properties for tuning the server's performance
              # Number of WebLogic Server execute threads.
              weblogic.system.executeThreadCount=15
              # Other optional system properties
              # Limits size of weblogic.log (in K) and versions old log
              weblogic.system.maxLogFileSize=1024
              # Adjust minimum length of password
              weblogic.system.minPasswordLen=8
              # UNIX only: If running on port 80 on UNIX, enable the setUID program
              #weblogic.system.enableSetUID=false
              # UNIX only: Unprivileged user to setUID to after starting up
              # WebLogic Server on port 80
              #weblogic.system.nonPrivUser=nobody
              # CLUSTER-SPECIFIC PROPERTIES
              # Cluster-specific properties in this section are set to system
              defaults.
              # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
              # in the per-cluster properties file ONLY.
              # Time-to-live (number of hops) for the cluster's multicast messages
              # (default 1, range 1-255).
              #weblogic.cluster.multicastTTL=1
              # Sets the load-balancing algorithm to be used between
              # replicated services if none is specified. If not specified,
              # round-robin is used.
              #weblogic.cluster.defaultLoadAlgorithm=round-robin
              # SERVER-SPECIFIC CLUSTER PROPERTIES
              # Cluster-related properties in this section are set to system defaults.
              # CLUSTER USERS: Note that these server-specific cluster-related
              properties
              # should be set in the per-server properties file ONLY.
              # Sets the weight of the individual server for the weight-based
              load-balancing.
              # Range is 0 - 100.
              # Larger numbers increase the amount of traffic routed to this server.
              #weblogic.system.weight=100
              # SYSTEM STARTUP FILES - Examples
              # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
              # objects should be registered in the per-server properties file.
              # All other startup classes should be registered in the per-cluster
              # properties file.
              # For more info on writing and using startup file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs45/classdocs/API_t3.html
              # Register a startup class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.startupClass.[virtual_name]=[full_pathname]
              # Add arguments for the startup class
              #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/StartupQuery.java
              #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
              #weblogic.system.startupArgs.doquery=\
              # query=select * from emp,\
              # db=jdbc:weblogic:pool:demoPool
              # Other system startup files for use with VisiBroker
              # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
              # You must have installed Visigenic 2.5 for use with
              # the WebLogic Server before you uncomment these properties
              #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
              #weblogic.system.startupArgs.dovisi=\
              # clientName=T3Client Manager,\
              # connName=T3Connection Manager
              # SYSTEM SHUTDOWN FILES - Examples
              # For more info on writing and using shutdown file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs45/classdocs/API_t3.html
              # Register a shutdown class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
              # Add arguments for the shutdown class
              #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/ShutdownTest.java
              #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
              #weblogic.system.shutdownArgs.ShutdownTest=\
              # outfile=c:/temp/shutdown.log
              # SECURITY-RELATED PROPERTIES FOR WORKSPACES
              # For backward compatibility, the following entries disable Access
              # Control on Workspaces
              weblogic.allow.read.weblogic.workspace=everyone
              weblogic.allow.write.weblogic.workspace=everyone
              # JOLT FOR WEBLOGIC PROPERTIES
              # These properties configure a BEA Jolt connection pool for use with
              # the simpapp and bankapp examples, and register a servlet for use with
              # with the simpapp example. The default server address provided here
              # points to a public TUXEDO server that is hosted by BEA for use with
              # this example.
              # Servlet registration for simpapp example:
              #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
              # Pool creation and cleanup
              # note this example is set up to work with the public
              # demo TUXEDO server available from BEA's website:
              #weblogic.system.startupClass.demojoltpoolStart=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
              #weblogic.system.startupArgs.demojoltpoolStart=\
              # poolname=demojoltpool,\
              # appaddrlist=//beademo1.beasys.com:8000,\
              # failoverlist=//beademo1.beasys.com:8000,\
              # minpoolsize=1,\
              # maxpoolsize=3
              #weblogic.system.shutdownClass.demojoltpoolStop=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
              #weblogic.system.shutdownArgs.demojoltpoolStop=\
              # poolname=demojoltpool
              # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
              # The registrations enable a BEA IIOP connection pool and
              # register servlets for use with the simpapp and university examples.
              # Configure for your environment and uncomment to use.
              # Uncommenting these properties requires WebLogic Enterprise
              Connectivity
              # and an operating WebLogic Enterprise Server.
              # Servlet registration for simpapp servlet example
              #weblogic.httpd.register.SimpappServlet=\
              # examples.wlec.servlets.simpapp.SimpappServlet
              #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
              # Servlet registration for simpapp EJB example
              # (You'll need to add the wlec_ejb_simpapp.jar to the
              # weblogic.ejb.deploy property in this file.)
              #weblogic.httpd.register.ejbSimpappServlet=\
              # examples.wlec.ejb.simpapp.ejbSimpappServlet
              #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
              # Pool creation and cleanup for the simpapp example
              #weblogic.CORBA.connectionPool.simplepool=\
              # appaddrlist=//wlehost:2468,\
              # failoverlist=//wlehost:2468,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # domainname=simpapp
              # Servlet registration for university Servlet example:
              #weblogic.httpd.register.UniversityServlet=\
              # examples.wlec.servlets.university.UniversityServlet
              #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
              # Pool creation and cleanup for the University example:
              #weblogic.CORBA.connectionPool.Univpool=\
              # appaddrlist=//wlehost:2498,\
              # failoverlist=//wlehost:2498,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # apppassword=wlepassword,\
              # domainname=university
              # WEBLOGIC FILE PROPERTIES
              # Maps a volume name to a path, for client file read/write
              #weblogic.io.fileSystem.[volumeName]=[fullPathName]
              # WEBLOGIC JMS DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL JMS deployment should be done in the
              # per-cluster properties file ONLY.
              # You set up a JDBC connection pool if you want persistent messages
              # (including durable subscriptions). To use JMS and EJBs in the same
              # transaction, both must use the same JDBC connection pool. Uncomment
              # the following property to use the default JDBC connection pool
              # 'demo', which is defined in the Demo connection pool section of this
              file.
              #weblogic.jms.connectionPool=demoPool
              # The JMS Webshare example demonstrates how the ClientID for a
              # durable subscriber is configured in the connection factory:
              #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
              #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
              #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
              #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
              # The JMS trader example shows how to use JMS with an EJB. In addition
              # to uncommenting the following properties, you must also set up and
              # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
              # try out this JMS example:
              #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
              #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
              #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
              #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
              # Registers the underlying servlet
              #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
              # These properties are used with the ServerReceive JMS example,
              # which demonstrates how to establish a JMS message consumer
              # in a startup class:
              #weblogic.system.startupClass.serverReceive=\
              # examples.jms.startup.ServerReceive
              #weblogic.system.startupArgs.serverReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              # These properties are used with the PoolReceive JMS example,
              # which demonstrates how to establish a pool of JMS message consumers
              # in a startup class:
              #weblogic.system.startupClass.poolReceive=\
              # examples.jms.startup.PoolReceive
              #weblogic.system.startupArgs.poolReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              # WEBLOGIC RMI DEMO PROPERTIES
              # CLUSTER USERS: Note that pinned RMI objects should be registered
              # in the per-server properties file ONLY. All other RMI startup
              # classes should be registered in the per-cluster properties file.
              # Remote classes registered at startup after the pattern:
              #weblogic.system.startupClass.[virtualName]=[fullPackageName]
              # These examples can be compiled to see RMI in action. Uncomment to use:
              #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
              #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
              # WEBLOGIC EJB DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL EJB deployment should be done in the
              # per-cluster properties file ONLY.
              # See WebLogic Demo Connection Pool below for a connection pool
              # to use with these examples.
              # Deploys EJBeans. Uncomment the appropriate lines below and
              # modify DBMS-related info and paths to match your particular
              installation:
              #weblogic.ejb.deploy=\
              # d:/weblogic/myserver/cluster_ejb.jar, \
              # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
              # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
              # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
              # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
              # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
              # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
              # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
              # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
              # d:/weblogic/myserver/ejb_subclass.jar, \
              # d:/weblogic/myserver/jolt_ejb_bankapp.jar
              # Servlets used by the EJB basic examples beanManaged and
              # containerManaged. Uncomment to use:
              #weblogic.httpd.register.beanManaged=\
              # examples.ejb.basic.beanManaged.Servlet
              #weblogic.httpd.register.containerManaged=\
              # examples.ejb.basic.containerManaged.Servlet
              # Add a list of users (set the password with
              weblogic.password.[username]=XXX)
              # to set an ACL for this servlet:
              #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
              #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
              #weblogic.password.user1=user1Password
              #weblogic.password.user2=user2Password
              # WEBLOGIC ZAC DEMO PROPERTIES
              # These registrations enable the ZAC Publish Wizard.
              weblogic.zac.enable=true
              # Set the publish root for a WebLogic Server. Edit and
              # uncomment to use
              #weblogic.zac.publishRoot=d:/weblogic/zac
              # Set an ACL for each package you publish. The [name] is
              # the "Package name" you assign in the ZAC Publish Wizard.
              # Publish a package, edit this property, and uncomment to use.
              #weblogic.allow.read.weblogic.zac.[name]=[user list]
              #weblogic.allow.write.weblogic.zac.[name]=system
              # HTTPD ADMINISTRATIVE PROPERTIES
              # Enables logging of HTTPD info in common log format and
              # sets the log file name (default is "access.log" in "myserver")
              weblogic.httpd.enableLogFile=true
              weblogic.httpd.logFileName=access.log
              # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
              weblogic.httpd.enableEvents=false
              # Enables HTTP sessions
              weblogic.httpd.session.enable=true
              # Sets an optional cookie name. The default name is "WebLogicSession".
              # Prior to version 4.0, the default was "TengahSession". To make
              # this backward compatible with cookies generated from previous
              # installations, you should set this property to "TengahSession".
              # Uncomment this line and set this to any string of your choice,
              # or comment out this property to use the default.
              #weblogic.httpd.session.cookie.name=WebLogicSession
              # MIME types
              weblogic.httpd.mimeType.text/html=html,htm
              weblogic.httpd.mimeType.image/gif=gif
              weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
              weblogic.httpd.mimeType.application/pdf=pdf
              weblogic.httpd.mimeType.application/zip=zip
              weblogic.httpd.mimeType.application/x-java-vm=class
              weblogic.httpd.mimeType.application/x-java-archive=jar
              weblogic.httpd.mimeType.application/x-java-serialized-object=ser
              weblogic.httpd.mimeType.application/octet-stream=exe
              # In seconds, the keep-alive for HTTP and HTTPS requests
              weblogic.httpd.http.keepAliveSecs=60
              weblogic.httpd.https.keepAliveSecs=120
              # WEBLOGIC JDBC DRIVER PROPERTIES
              # Enables JDBC driver logging and sets the file name for the log
              # The weblogic.jdbc.logFile is placed in the per-server
              # directory (default is "myserver")
              weblogic.jdbc.enableLogFile=false
              weblogic.jdbc.logFileName=jdbc.log
              # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
              # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
              # in the per-cluster properties file ONLY.
              # For creating JDBC connection pools. This example shows a connection
              # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and
              "jill"
              # to use 4 JDBC connections (with a potential for up to 10 connections,
              # incremented by two at a time, with a delay of 1 second between each
              # attempt to connect to the database), to an Oracle database server
              called
              # "DEMO." If more than 4 connections are opened, after 15 minutes,
              unused
              # connections are dropped from the pool until only 4 connections remain
              open.
              # Every 10 minutes, any unused connections in the pool are tested and
              # refreshed if they are not viable.
              #weblogic.jdbc.connectionPool.oraclePool=\
              # url=jdbc:weblogic:oracle,\
              # driver=weblogic.jdbc.oci.Driver,\
              # loginDelaySecs=1,\
              # initialCapacity=4,\
              # maxCapacity=10,\
              # capacityIncrement=2,\
              # allowShrinking=true,\
              # shrinkPeriodMins=15,\
              # refreshMinutes=10,\
              # testTable=dual,\
              # props=user=SCOTT;password=tiger;server=DEMO
              # Get more details on each argument for this property in the
              # Administrators Guide on setting properties at:
              # http://www.weblogic.com/docs45/admindocs/properties.html
              # Set up ACLs for this connection pool with the following:
              #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
              # guest,joe,jill
              #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
              # joe,jill
              #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
              # joe,jill
              # This property is an ACL that specifies the users who can
              # create dynamic connection pools

    Try the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
              Init fn="load-types" mime-types="mime.types"
              Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
              Init fn="wl-init"
              Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
              \"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
              <Object name="tg" ppath="*/weblogic/*">
              Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
              </Object>
              <Object name="default">
              NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
              NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
              NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
              NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
              PathCheck fn="nt-uri-clean"
              PathCheck fn="check-acl" acl="default"
              PathCheck fn="find-pathinfo"
              PathCheck fn="find-index" index-names="index.html,home.html"
              ObjectType fn="type-by-extension"
              ObjectType fn="force-type" type="text/plain"
              Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
              Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
              Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
              Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
              AddLog fn="flex-log" name="access"
              </Object>
              <Object ppath="/usr/suitespot/docs/.perf">
              Service fn="service-dump"
              </Object>
              <Object name="cgi">
              ObjectType fn="force-type" type="magnus-internal/cgi"
              Service fn="send-cgi"
              </Object>
              Hope this helps
              Krishna Kanth wrote:
              > We are evaluating the Cluster features of WebLogic and got a eval
              > license for the Cluster Support.
              > I am running a default cluster (mycluster) using the default Multicast
              > address (237.0.0.1) and am seeing
              > some strange behaviour/errors.
              > Would appreciate some asistance in this matter.
              >
              > Our Environment
              > ----------------
              >
              > I created directory in a shared file system to host the cluster.
              > (h:\kkanth\weblogic)
              > Created the mycluster directory and other directories as recommended in
              > the Administrator's guide.
              >
              > I have two WL Servers (asera190 and asera162) with permanent IP
              > addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
              > I'm using a NES proxy on asera190 with the plugin for WL specified in
              > obj.conf alongwith the other parameters.
              >
              > I'm able to have both the servers join to cluster mycluster and the WL
              > Admin Console does display a tree that depicts the cluster as well as
              > servers in it (server61 and server70). The individual server directories
              > are being created in h:\kkanth\weblogic\mycluster directory with the
              > appropriate access.log and weblogic.log files.
              >
              > When a browser attempts to access a URL such as
              >
              > http://asera190/weblogic/snoop it does return the proper response, but
              > all requests are processed by asera162 which is listed first in the
              > obj.conf. Opening multiple sessions does not cause the requests to be
              > sent to asera190 which is the second server in the cluster. When
              > asera162 is shutdown and removed from the cluster, I hoped that
              > subsequent requests would go to asera190. However , depending on the
              > origin of the request, different errors were thrown. If I try to access
              > http://asera190/weblogic/snoop from a browser on asera190, I get an
              > error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
              > from asera162 cause "Failure at line 706 of file proxy.cpp".
              >
              > I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
              > directory as well as the obj.conf file in the ....\config\ directory of
              > asera190.
              >
              > We are running NES 3.5.1 and have setup proxy35.dll appropriately.
              >
              > weblogic.properties
              > *********
              > # THE WEBLOGIC PROPERTIES FILE
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # This file, which conforms to the java.util.Properties file
              > # definition, configures your WebLogic products. You cannot run
              > # WebLogic Server without setting required configuration properties in
              > this
              > # file. Required properties are marked and appear first in the file.
              > #
              > # Details on each entry and important information about configuration
              > # and security are documented on our website. Please go to:
              > #
              > # http://www.weblogic.com/docs45/admindocs/properties.html
              > #
              > # for full instructions on how to edit this file.
              > #
              > # You do not need to include properties in this file unless you want to
              > # change the default, embedded property. Some properties on the
              > # T3AdminProps page are not listed here because the default property
              > # is being used. You can change the default by adding the property and
              > # its value to this file.
              > #
              > # You cannot set weblogic.system.home in this file, since the WebLogic
              > Server
              > # must know where home is in order to retrieve this file. You can
              > # change WebLogic home on the command line when you start the
              > # WebLogic Server.
              > #
              > # CLUSTER USERS: Note that the (shared) per-cluster properties file
              > should
              > # contain most all of the properties in this file. The only properties
              > # that potentially belong in a per-server properties file for a server
              > # running in a cluster are the registration (startup class) of pinned
              > # RMI objects, and a few tuning properties that may be different for
              > # servers in the cluster, depending upon hardware and memory. If you use
              >
              > # a per-server properties file, please REMOVE all properties except
              > those
              > # that are specifically required in the per-server properties file. You
              > # can find specific notes on clusters by searching through this file for
              >
              > # "CLUSTER USERS".
              > #
              > # -------------------------------------------------
              > # The way this file is organized:
              > # Core properties (includes REQUIRED and RECOMMENDED)
              > # Core system properties
              > # Core security-related properties
              > # Core security-related properties for SSL
              > # Core HTTPD administrative properties
              > #
              > # Optional properties
              > # Administrator properties
              > # System properties
              > # System startup files
              > # System shutdown files
              > # Security-related properties for Workspaces
              > # Jolt for WebLogic properties
              > # WebLogic Enterprise Connectivity properties
              > # WebLogic File properties
              > # WebLogic JMS demo properties
              > # WebLogic RMI demo properties
              > # WebLogic EJB demo properties
              > # WebLogic ZAC demo properties
              > # HTTPD administrative properties
              > # WebLogic JDBC driver properties
              > # WebLogic JDBC connection pool management
              > # WebLogic demo connection pool
              > # WebLogic HTTP Servlet properties
              > # Proxy servlet registration
              > # Classpath servlet registration
              > # File servlet registration
              > # ServerSideInclude servlet registration
              > # PageCompileServlet (used by JHTML)
              > # JSPServlet (used by JSP)
              > # ServletServlet registration
              > # Servlet reload properties
              > # Servlet ACLs
              > # WebLogic JHTML properties
              > # User-written and demo servlet registrations
              > # -------------------------------------------------
              >
              > #################################################################
              > # CORE PROPERTIES
              > # -------------------------------------------------
              > # You should set these before you start the WebLogic Server the first
              > time.
              > # If you need more instructions on individual properties in this
              > # section, check the same section in the Optional Properties, where
              > # we've left the long explanations. Or, better yet, go to our
              > # website and read all about properties, at:
              > # http://www.weblogic.com/docs45/admindocs/properties.html
              > #################################################################
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # CORE SYSTEM PROPERTIES
              > # -------------------------------------------------
              > # TCP/IP port number at which the WebLogic Server listens for
              > connections
              > weblogic.system.listenPort=7001
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # CORE SECURITY-RELATED PROPERTIES
              > # -------------------------------------------------
              > # Read important information about security at:
              > #
              > # http://www.weblogic.com/docs45/admindocs/properties.html
              > #
              > # REQUIRED: The system password MUST be set in order to start the
              > # WebLogic Server. This password is case-sensitive, at least 8
              > characters.
              > # The username for the privileged user is ALWAYS "system".
              > # This username and password also includes httpd access (see
              > # HTTPD properties below).
              > weblogic.password.system=kaykayka
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # RECOMMEND Set to 'everyone' if HTTPD is enabled
              > weblogic.allow.execute.weblogic.servlet=everyone
              > # Set individual ACLs to restrict access to HTTP-related resources,
              > # such as the Administration servlets.
              > # To make your own servlets generally available, follow this
              > # pattern (provide a weblogic.allow.execute) for your packages and
              > # set ACLs as appropriate.
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # CORE SECURITY-RELATED PROPERTIES FOR SSL
              > # ------------------------------------------------
              > # Read important information about SSL at:
              > #
              > # http://www.weblogic.com/docs45/classdocs/API_secure.html
              > #
              > # Enable SSL
              > # (default if property not defined is false)
              > weblogic.security.ssl.enable=true
              > #
              > # SSL listen port
              > weblogic.system.SSLListenPort=7002
              >
              > # Servlets for SSL
              > # ------------------------------------------------
              > # Authentication servlet for creating tokens for applets
              > weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
              >
              > # Limits number of unclaimed stored tokens
              > weblogic.security.certificateCacheSize=3
              > # Capture CA root of client servlet
              > weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
              >
              > # Certificates for SSL
              > # ------------------------------------------------
              > # Name of acceptable CA roots
              > # For client authentication change value to a valid .pem file
              > #weblogic.security.clientRootCA=SecureServerCA.pem
              > #
              > # Server certificates for SSL
              > # ------------------------------------------------
              > weblogic.security.certificate.server=democert.pem
              > weblogic.security.key.server=demokey.pem
              > weblogic.security.certificate.authority=ca.pem
              >
              > # registration for certificate generator servlet
              > weblogic.httpd.register.Certificate=utils.certificate
              > weblogic.allow.execute.weblogic.servlet.Certificate=system
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # CORE HTTPD ADMINISTRATIVE PROPERTIES
              > # ------------------------------------------------
              > # True permits the HTTPD to run (default)
              > # Uncomment this property to disable HTTPD
              > #weblogic.httpd.enable=false
              > #
              > # If authentication is required, add username/password for each user
              > # who will be included in an ACL, as in this commented-out example:
              > #weblogic.password.peter=#8gjsL4*
              >
              > #################################################################
              > # OPTIONAL PROPERTIES
              > # ------------------------------------------------
              > # These properties affect the behavior of the WebLogic Server.
              > # You only need to set these properties if you want
              > # to change the default setting, which is the property shown.
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # ADMINISTRATOR PROPERTIES
              > # ------------------------------------------------
              > # Administrator properties are optional information properties,
              > # particularly useful for clusters.
              > #weblogic.administrator.location=3355 California Drive, West Hampshire,
              > CA 94104
              > #weblogic.administrator.name=Joe Administrator
              > #weblogic.administrator.phone=1 415 555 1234
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # SYSTEM PROPERTIES
              > # ------------------------------------------------
              > # System properties in this section are set to system defaults
              >
              > # Performance pack. The shared library must be accessible from your
              > # PATH (NT) or from your shared library path (UNIX; the name of the
              > # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
              > weblogic.system.nativeIO.enable=true
              >
              > # Outputs logging information to the console as well as to the log file
              > weblogic.system.enableConsole=true
              >
              > # Sets the directory or URL for the WebLogic Admin help pages
              > # The help pages are shipped in the "docs/adminhelp" directory, in the
              > # default document root in public_html
              > weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
              >
              > # If you prefer to access the most recent help pages, you can do so
              > online
              > # by commenting out the previous property and uncommenting this one:
              > #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
              >
              > # Properties for tuning the server's performance
              > # ------------------------------------------------
              > # Number of WebLogic Server execute threads.
              > weblogic.system.executeThreadCount=15
              >
              > # Other optional system properties
              > # ------------------------------------------------
              > # Limits size of weblogic.log (in K) and versions old log
              > weblogic.system.maxLogFileSize=1024
              >
              > # Adjust minimum length of password
              > weblogic.system.minPasswordLen=8
              >
              > # UNIX only: If running on port 80 on UNIX, enable the setUID program
              > #weblogic.system.enableSetUID=false
              >
              > # UNIX only: Unprivileged user to setUID to after starting up
              > # WebLogic Server on port 80
              > #weblogic.system.nonPrivUser=nobody
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # CLUSTER-SPECIFIC PROPERTIES
              > # ------------------------------------------------
              > # Cluster-specific properties in this section are set to system
              > defaults.
              > # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
              >
              > # in the per-cluster properties file ONLY.
              > #
              > # Time-to-live (number of hops) for the cluster's multicast messages
              > # (default 1, range 1-255).
              > #weblogic.cluster.multicastTTL=1
              > #
              > # Sets the load-balancing algorithm to be used between
              > # replicated services if none is specified. If not specified,
              > # round-robin is used.
              > #weblogic.cluster.defaultLoadAlgorithm=round-robin
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # SERVER-SPECIFIC CLUSTER PROPERTIES
              > # ------------------------------------------------
              > # Cluster-related properties in this section are set to system defaults.
              >
              > # CLUSTER USERS: Note that these server-specific cluster-related
              > properties
              > # should be set in the per-server properties file ONLY.
              > #
              > # Sets the weight of the individual server for the weight-based
              > load-balancing.
              > # Range is 0 - 100.
              > # Larger numbers increase the amount of traffic routed to this server.
              > #weblogic.system.weight=100
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # SYSTEM STARTUP FILES - Examples
              > # ------------------------------------------------
              > # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
              > # objects should be registered in the per-server properties file.
              > # All other startup classes should be registered in the per-cluster
              > # properties file.
              > #
              > # For more info on writing and using startup file, see the
              > # Developers Guide "Writing a WebLogic Client application," at
              > # http://www.weblogic.com/docs45/classdocs/API_t3.html
              > #
              > # Register a startup class by giving it a virtual name and
              > # supplying its full pathname.
              > #weblogic.system.startupClass.[virtual_name]=[full_pathname]
              > #
              > # Add arguments for the startup class
              > #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
              > #
              > # This example shows the entry for examples/t3client/StartupQuery.java
              > #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
              > #weblogic.system.startupArgs.doquery=\
              > # query=select * from emp,\
              > # db=jdbc:weblogic:pool:demoPool
              > #
              > # Other system startup files for use with VisiBroker
              > # ------------------------------------------------
              > # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
              > # You must have installed Visigenic 2.5 for use with
              > # the WebLogic Server before you uncomment these properties
              > #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
              >
              > #weblogic.system.startupArgs.dovisi=\
              > # clientName=T3Client Manager,\
              > # connName=T3Connection Manager
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # SYSTEM SHUTDOWN FILES - Examples
              > # ------------------------------------------------
              > # For more info on writing and using shutdown file, see the
              > # Developers Guide "Writing a WebLogic Client application," at
              > # http://www.weblogic.com/docs45/classdocs/API_t3.html
              > #
              > # Register a shutdown class by giving it a virtual name and
              > # supplying its full pathname.
              > #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
              > #
              > # Add arguments for the shutdown class
              > #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
              > #
              > # This example shows the entry for examples/t3client/ShutdownTest.java
              > #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
              >
              > #weblogic.system.shutdownArgs.ShutdownTest=\
              > # outfile=c:/temp/shutdown.log
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # SECURITY-RELATED PROPERTIES FOR WORKSPACES
              > # ------------------------------------------------
              > # For backward compatibility, the following entries disable Access
              > # Control on Workspaces
              > weblogic.allow.read.weblogic.workspace=everyone
              > weblogic.allow.write.weblogic.workspace=everyone
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # JOLT FOR WEBLOGIC PROPERTIES
              > # ------------------------------------------------
              > # These properties configure a BEA Jolt connection pool for use with
              > # the simpapp and bankapp examples, and register a servlet for use with
              > # with the simpapp example. The default server address provided here
              > # points to a public TUXEDO server that is hosted by BEA for use with
              > # this example.
              > #
              > # Servlet registration for simpapp example:
              > # ------------------------------------------------
              > #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
              >
              > #
              > # Pool creation and cleanup
              > # note this example is set up to work with the public
              > # demo TUXEDO server available from BEA's website:
              > # ------------------------------------------------
              > #weblogic.system.startupClass.demojoltpoolStart=\
              > # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
              > #weblogic.system.startupArgs.demojoltpoolStart=\
              > # poolname=demojoltpool,\
              > # appaddrlist=//beademo1.beasys.com:8000,\
              > # failoverlist=//beademo1.beasys.com:8000,\
              > # minpoolsize=1,\
              > # maxpoolsize=3
              > #
              > #weblogic.system.shutdownClass.demojoltpoolStop=\
              > # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
              > #weblogic.system.shutdownArgs.demojoltpoolStop=\
              > # poolname=demojoltpool
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
              > # ------------------------------------------------
              > # The registrations enable a BEA IIOP connection pool and
              > # register servlets for use with the simpapp and university examples.
              > # Configure for your environment and uncomment to use.
              > # Uncommenting these properties requires WebLogic Enterprise
              > Connectivity
              > # and an operating WebLogic Enterprise Server.
              > #
              > # Servlet registration for simpapp servlet example
              > # ------------------------------------------------
              > #weblogic.httpd.register.SimpappServlet=\
              > # examples.wlec.servlets.simpapp.SimpappServlet
              > #
              > #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
              > #
              > # Servlet registration for simpapp EJB example
              > # (You'll need to add the wlec_ejb_simpapp.jar to the
              > # weblogic.ejb.deploy property in this file.)
              > # --------------------------------------------
              > #weblogic.httpd.register.ejbSimpappServlet=\
              > # examples.wlec.ejb.simpapp.ejbSimpappServlet
              > #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
              > #
              > # Pool creation and cleanup for the simpapp example
              > # -------------------------------------------------
              > #weblogic.CORBA.connectionPool.simplepool=\
              > # appaddrlist=//wlehost:2468,\
              > # failoverlist=//wlehost:2468,\
              > # minpoolsize=2,\
              > # maxpoolsize=3,\
              > # username=wleuser,\
              > # userrole=developer,\
              > # domainname=simpapp
              > #
              > # Servlet registration for university Servlet example:
              > # ---------------------------------------------------
              > #weblogic.httpd.register.UniversityServlet=\
              > # examples.wlec.servlets.university.UniversityServlet
              > #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
              > #
              > # Pool creation and cleanup for the University example:
              > # ----------------------------------------------------
              > #weblogic.CORBA.connectionPool.Univpool=\
              > # appaddrlist=//wlehost:2498,\
              > # failoverlist=//wlehost:2498,\
              > # minpoolsize=2,\
              > # maxpoolsize=3,\
              > # username=wleuser,\
              > # userrole=developer,\
              > # apppassword=wlepassword,\
              > # domainname=university
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # WEBLOGIC FILE PROPERTIES
              > # ------------------------------------------------
              > # Maps a volume name to a path, for client file read/write
              > #weblogic.io.fileSystem.[volumeName]=[fullPathName]
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # WEBLOGIC JMS DEMO PROPERTIES
              > # -------------------------------------------------
              > # CLUSTER USERS: Note that ALL JMS deployment should be done in the
              > # per-cluster properties file ONLY.
              > #
              > # You set up a JDBC connection pool if you want persistent messages
              > # (including durable subscriptions). To use JMS and EJBs in the same
              > # transaction, both must use the same JDBC connection pool. Uncomment
              > # the following property to use the default JDBC connection pool
              > # 'demo', which is defined in the Demo connection pool section of this
              > file.
              > #
              > #weblogic.jms.connectionPool=demoPool
              > #
              > # The JMS Webshare example demonstrates how the ClientID for a
              > # durable subscriber is configured in the connection factory:
              > #
              > #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
              > #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
              >
              > #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
              > #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
              > #
              > # The JMS trader example shows how to use JMS with an EJB. In addition
              > # to uncommenting the following properties, you must also set up and
              > # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
              > # try out this JMS example:
              > #
              > #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
              > #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
              > #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
              > #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
              > #
              > # Registers the underlying servlet
              > #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
              > #
              > # These properties are used with the ServerReceive JMS example,
              > # which demonstrates how to establish a JMS message consumer
              > # in a startup class:
              > #
              > #weblogic.system.startupClass.serverReceive=\
              > # examples.jms.startup.ServerReceive
              > #weblogic.system.startupArgs.serverReceive=\
              > # connectionFactory=javax.jms.TopicConnectionFactory,\
              > # topic=javax.jms.exampleTopic
              > #
              > # These properties are used with the PoolReceive JMS example,
              > # which demonstrates how to establish a pool of JMS message consumers
              > # in a startup class:
              > #weblogic.system.startupClass.poolReceive=\
              > # examples.jms.startup.PoolReceive
              > #weblogic.system.startupArgs.poolReceive=\
              > # connectionFactory=javax.jms.TopicConnectionFactory,\
              > # topic=javax.jms.exampleTopic
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # WEBLOGIC RMI DEMO PROPERTIES
              > # ------------------------------------------------
              > # CLUSTER USERS: Note that pinned RMI objects should be registered
              > # in the per-server properties file ONLY. All other RMI startup
              > # classes should be registered in the per-cluster properties file.
              > #
              > # Remote classes registered at startup after the pattern:
              > #weblogic.system.startupClass.[virtualName]=[fullPackageName]
              > #
              > # These examples can be compiled to see RMI in action. Uncomment to use:
              >
              > #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
              >
              > #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # WEBLOGIC EJB DEMO PROPERTIES
              > # -------------------------------------------------
              > # CLUSTER USERS: Note that ALL EJB deployment should be done in the
              > # per-cluster properties file ONLY.
              > #
              > # See WebLogic Demo Connection Pool below for a connection pool
              > # to use with these examples.
              > #
              > # Deploys EJBeans. Uncomment the appropriate lines below and
              > # modify DBMS-related info and paths to match your particular
              > installation:
              > #weblogic.ejb.deploy=\
              > # d:/weblogic/myserver/cluster_ejb.jar, \
              > # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
              > # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
              > # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
              > # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
              > # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
              > # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
              >
              > # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
              > # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
              > # d:/weblogic/myserver/ejb_subclass.jar, \
              > # d:/weblogic/myserver/jolt_ejb_bankapp.jar
              > #
              > # Servlets used by the EJB basic examples beanManaged and
              > # containerManaged. Uncomment to use:
              > #weblogic.httpd.register.beanManaged=\
              > # examples.ejb.basic.beanManaged.Servlet
              > #weblogic.httpd.register.containerManaged=\
              > # examples.ejb.basic.containerManaged.Servlet
              > #
              > # Add a list of users (set the password with
              > weblogic.password.[username]=XXX)
              > # to set an ACL for this servlet:
              > #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
              > #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
              >
              > #weblogic.password.user1=user1Password
              > #weblogic.password.user2=user2Password
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # WEBLOGIC ZAC DEMO PROPERTIES
              > # -------------------------------------------------
              > # These registrations enable the ZAC Publish Wizard.
              > #
              > weblogic.zac.enable=true
              > #
              > # Set the publish root for a WebLogic Server. Edit and
              > # uncomment to use
              > #
              > #weblogic.zac.publishRoot=d:/weblogic/zac
              > #
              > # Set an ACL for each package you publish. The [name] is
              > # the "Package name" you assign in the ZAC Publish Wizard.
              > # Publish a package, edit this property, and uncomment to use.
              > #weblogic.allow.read.weblogic.zac.[name]=[user list]
              > #weblogic.allow.write.weblogic.zac.[name]=system
              >
              > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
              > # HTTPD ADMINISTRATIVE PROPERTIES
              > # ------------------------------------------------
              > # Enables logging of HTTPD info in common log format and
              > # sets the log file name (default is "access.log" in "myserver")
              > weblogic.httpd.enableLogFile=true
              > weblogic.httpd.logFileName=access.log
              >
              > # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
              > weblogic.httpd.enableEvents=false
              >
              > # Enables HTTP sessions
              > weblogic.httpd.session.enable=true
              >
              > # Sets an optional cookie name. The default name is "WebLogicSession".
              > # Prior to version 4.0, the default was "TengahSession". To make
              > # this backward compatible with cookies generated from previous
              > # installations, you should set this property to "TengahSession".
              > # Uncomment t

Maybe you are looking for