JMS Server is not Migrating to other Managed Server using Databse Leasing

Hi,
WLS 10.3 on Linux Itanium.
I Tried JMS Server migration but its not working.
Below is the Configuration Details :-
1. Cluster with three managed servers( MS1,MS2,MS3 )
2.JMS Server is targeted on MS1(migratable)
3.created Persistant store as JDBC store for JMS Server and targeted it to MS1(migratable)
4.Environment -> Cluster->Migration Tab
-Migration Basis :- Database
-DataSource For Automatic Migration -> DS1
     -Auto Migration Table Name:(ACTIVE)          
5.Created a table ACTIVE as per schema given in WL_HOME/server/db/dbname/leasing.ddl (I am using Oracle database at backend and Database is running and accessible)
6.Created Jms module (say module1)
-target module1 to Cluster.
7.Create Subdeployment(say "sub1") and target to JmsServer
8.Create Queue.and select subdeployment as "sub1" which was created above.
9.I am using default JMSXAconnectionfactory
10.Environment -> Migratable Targets->Select MS1(Migratable)->Migration tab
-Service Migration Policy->Auto Migration Exactly Once Service
               -Constrained Cadidate Servers :-
               Selected all the servers in that cluster
but when I check the Current Server for JMS Server (It should be MS1) which is not displayed. The field in the table is blank.
(Environment->Messaging->JMS Server->here i checked the Current Server for JMS Server )
with the above setting I did it successfully on windows platform. I am able to see Current Server as MS1.and when I shutdown MS1 it changes to either MS2 or MS3
but when I am doing it on Winodows I am explicitly creating connection factory and targeting it to cluster.but on linux platform I am not creating any connection factory(default JMS XA Connection Factory is used)
I have tried a lot to find why its not working but didnt get any idea why so happened?
Required your help
Thanks in Advance ........

I managed to start my managedserver.The issue was with startmanagedserver command.I modified it to my need.

Similar Messages

  • Messaging Bridge Migration to other Managed Server

              Hi
              I had encountered a difficulty when I deployed the Messaging Bridge using the
              Migratable Target. The Messaging Bridge stop function with no exception. I had
              double check that in my Managed Server (serverA) I had set the Migratable Target
              ServerA (Migratable) preferable to serverA itself. However if I deployed the
              Messaging Bridge to serverA directly it works perfectly. Can anyone share some
              ideas that I can setup the Bridge in order I can failover the Bridge from one
              Managed Server to another Managed Server manually without restart any Managed
              Servers?
              Thanks
              Stephen
              

    hi,
    this is file from - .../new-admin-server/config-store/server-farm.xml
    in the .../old-admin-server/config-store/server-farm.xml it was not glass it was "rama1" of course.
    i've edit this manually
    i can deploy, stop-start instance from new-admin-server
    <?xml version="1.0" encoding="UTF-8"?>
    <!--
    Copyright 2006 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    -->
    <server-farm>
    <admin-server>glass</admin-server>
    <node>
    <host>glass</host>
    <port>8989</port>
    <description>This is the Administration Server node</description>
    </node>
    <node>
    <host>kuku</host>
    <port>8989</port>
    </node>
    </server-farm>

  • Can not redirect to other page when using adfc-config.xml in standalone WL

    Hi all,
    I created a very simple fusion app, only have two jspx pages(view1 view2). I drag these two pages to adfc-config file and created a control flow(adfcView2) between these two pages.
    +<?xml version="1.0" encoding="UTF-8" ?>+
    +<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">+
    +<view id="view1">+
    +<page>/view1.jspx</page>+
    +</view>+
    +<view id="view2">+
    +<page>/view2.jspx</page>+
    +</view>+
    +<control-flow-rule>+
    +<from-activity-id>view1</from-activity-id>+
    +<control-flow-case>+
    +<from-outcome>adfcView2</from-outcome>+
    +<to-activity-id>view2</to-activity-id>+
    +</control-flow-case>+
    +</control-flow-rule>+
    +</adfc-config>+
    When I run the view1.jspx in the embeded WL, all go well, can navigate from view1 to view2.
    But when I created an ear and deployed this ear to a standalone WL, view1 can be displayed successfully, but when I clicked one commandbutton in view1, want to navigator to view2, the page can not be redirected to view2(still show view1.jspx). there is no any error msg in WL Console.
    Did I miss anything for deploying a taskflow app? If I change the view controller to faces-config.xml not adfc-config.xml, all work fine.
    Any info is appreciated.
    Edited by: harth on Oct 25, 2009 7:21 PM

    Hi Harth,
    I guess you are running the jspx page not view activity, check if your url contains .jspx page at the end. If so, run the url without .jspx page at end(which is view id name)
    Eg:
    Give http://<Host_Name>:<Port>/<ContextRoot>/faces/view1 instead of http://<Host_Name>:<Port>/<ContextRoot>/faces/view1.jspxSireesha
    Edited by: Sireesha Pinninti on Oct 25, 2009 8:00 PM

  • Lotus Notes documents migration into Solution Manager

    We have been using Lotus notes application for maintaining only documentation in our landscape. But now, the plan is to move all the documentation from Lotus notes to SAP Solution Manager and use it as a document management system from now....
    Could anyone please answer the following queries:
    1) Does LSX environment help/enhance the migration ?. If not, are there any tools/accelerators/functions/automatic methods for mas uploading?
    2) This documentation is not project specific documentation. Where do you think this must go in Solution Manager?
    In the custom area of BPR?. If yes, please do let me know the procedure for the same.
    3) Would it be possible to link the documents to functional domains/ business scenarios/ business processes in the BPR?
    4) Lotus notes provides access to all the versions (Draft/Approved/Reviewed) of a document. Would it be possible to have the same features even in Solution Manager?
    5) What all document types does Solution Manager recognize?.
    I think the Lotus notes documents can be converted to 'Word' format and then put in Solution Manager. Besides this, is there any other common format which is recognized by both the tools?
    6) Standard SAP Solution manager does not provide indexed search. So, in order to retrieve a document later what indexing nomenclature/guidelines do you recommend?
    Has anyone done/faced with this kind of requirement. The idea now is to use Solution manager as a document management system. The efforts/process/timelines information if already known would be of great help to start with for us....
    Could you also provide the trade offs b/n Solution Manager and SAP knowledge warehouse (KW)?
    Hoping for some replies ...

    we also had the same requirement to migration from LN to SolMan Documentation base but there is no such tool (yet?)
    What you can do you can migrate from any ARIS like platform to SolMan:
    http://en.sap.info/ids-scheer-announces-migration-program-to-aris-platform/4058
    You do have versioning in SolMan and you can upload any kind of document via SOLAR01
    regarding the indexing you can either use SAP SES or connect TREX, this is documented in the customizing (SPRO)
    TREX will also be the prerequisite to make use of KM in SolMan
    nesimi

  • Add a machine to Managed Server using silent mode script in wls12c (x64)

    Hi,
    I am Kanakaraju. I am new to this silent installation of weblogic server and domain creation. my requirement while creating domain with production mode is,
    I need to add followings to the domain.
    1. Data source
    2. JMSServer
    3. ConnectionFactory
    4. JMSModule
    5. Queue
    6. Machine which can be assigned to Managed Server.
    7. subdeployment
    I can add only first 3 (Data source, JMSManager, Connection factory), but can't add remaining.
    when i use "+create JMSQueue "PfPerformanceProfileQueue" as queue;+", it is throwing exception like JMSQueue is not found.
    Can anybody please help me creating the script to add these?
    Following is my Silent mode script
    read template from "C:\Oracle\Weblogic12\wlserver_12.1\common\templates\domains\wls.jar";
    set CreateStartMenu "false";
    set JavaHome "C:\bea10_3_3\jrockit_160_17_R28.0.0-679";
    set ServerStartMode "prod";
    find Server "AdminServer" as AdminServer;
    set AdminServer.ListenAddress "";
    set AdminServer.ListenPort "7003";
    set AdminServer.SSL.Enabled "true";
    set AdminServer.SSL.ListenPort "7002";
    //We can directly create a new managed server.
    create Server "ManagedServer_1" as ManagedServer_1;
    set ManagedServer_1.ListenAddress "";
    set ManagedServer_1.ListenPort "7001";
    set ManagedServer_1.SSL.Enabled "true";
    set ManagedServer_1.SSL.ListenPort "7002";
    //Create JDBC datasource and targeting it to cluster
    create JDBCConnectionPool "xxxxDSName" as xxxxxDSName;
    set MVestDSName.DriverName "oracle.jdbc.OracleDriver";
    set MVestDSName.URL "jdbc:oracle:thin:@(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)";
    set MVestDSName.Password "xxxxxxx";
    set MVestDSName.Properties "user=xxxxxxx_user";
    assign JDBCConnectionPool "*" to target "ManagedServer_1";
    //create JMS server
    create JMSServer "MVestJMSServer" as jmsserver;
    assign JMSServer "*" to target "ManagedServer_1";
    //create JMS queue, default subdeployment will be created and targeted. Not sure
    create JMSConnectionFactory "xxxxxConnectionFactory" as connectionFactory;
    set connectionFactory.JNDIName "jms/xxxxxConnectionFactory"; //JNDI name for Queue
    assign JMSConnectionFactory "*" to Target "ManagedServer_1"; //Target queue to JMS server
    //create JMS queue, default subdeployment will be created and targeted. Not sure
    //create JMSQueue "PfPerformanceProfileQueue" as queue;
    //set queue.JNDIName "jms/PfPerformanceProfileQueue"; //JNDI name for Queue
    //set queue.StoreEnabled "false";
    //set queue.JMSServer "JMSServer"; //Target queue to JMS server
    //use templates default weblogic user
    find User "weblogic" as u1;
    set u1.password "weblogic1";
    //create a new user
    create User "Admin" as u2;
    set u2.password "weblogic1";
    //assign User "Admin" to Group "Administators";
    write domain to "C:\Oracle\Weblogic12\user_projects\domains\silent-domain"; // The domain name will be "silent-domain"
    close template;
    Edited by: 998028 on 4 Apr, 2013 5:35 AM
    Edited by: 998028 on 9 Apr, 2013 6:28 AM

    Hi,
    I am Kanakaraju. I am new to this silent installation of weblogic server and domain creation. my requirement while creating domain with production mode is,
    I need to add followings to the domain.
    1. Data source
    2. JMSServer
    3. ConnectionFactory
    4. JMSModule
    5. Queue
    6. Machine which can be assigned to Managed Server.
    7. subdeployment
    I can add only first 3 (Data source, JMSManager, Connection factory), but can't add remaining.
    when i use "+create JMSQueue "PfPerformanceProfileQueue" as queue;+", it is throwing exception like JMSQueue is not found.
    Can anybody please help me creating the script to add these?
    Following is my Silent mode script
    read template from "C:\Oracle\Weblogic12\wlserver_12.1\common\templates\domains\wls.jar";
    set CreateStartMenu "false";
    set JavaHome "C:\bea10_3_3\jrockit_160_17_R28.0.0-679";
    set ServerStartMode "prod";
    find Server "AdminServer" as AdminServer;
    set AdminServer.ListenAddress "";
    set AdminServer.ListenPort "7003";
    set AdminServer.SSL.Enabled "true";
    set AdminServer.SSL.ListenPort "7002";
    //We can directly create a new managed server.
    create Server "ManagedServer_1" as ManagedServer_1;
    set ManagedServer_1.ListenAddress "";
    set ManagedServer_1.ListenPort "7001";
    set ManagedServer_1.SSL.Enabled "true";
    set ManagedServer_1.SSL.ListenPort "7002";
    //Create JDBC datasource and targeting it to cluster
    create JDBCConnectionPool "xxxxDSName" as xxxxxDSName;
    set MVestDSName.DriverName "oracle.jdbc.OracleDriver";
    set MVestDSName.URL "jdbc:oracle:thin:@(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)";
    set MVestDSName.Password "xxxxxxx";
    set MVestDSName.Properties "user=xxxxxxx_user";
    assign JDBCConnectionPool "*" to target "ManagedServer_1";
    //create JMS server
    create JMSServer "MVestJMSServer" as jmsserver;
    assign JMSServer "*" to target "ManagedServer_1";
    //create JMS queue, default subdeployment will be created and targeted. Not sure
    create JMSConnectionFactory "xxxxxConnectionFactory" as connectionFactory;
    set connectionFactory.JNDIName "jms/xxxxxConnectionFactory"; //JNDI name for Queue
    assign JMSConnectionFactory "*" to Target "ManagedServer_1"; //Target queue to JMS server
    //create JMS queue, default subdeployment will be created and targeted. Not sure
    //create JMSQueue "PfPerformanceProfileQueue" as queue;
    //set queue.JNDIName "jms/PfPerformanceProfileQueue"; //JNDI name for Queue
    //set queue.StoreEnabled "false";
    //set queue.JMSServer "JMSServer"; //Target queue to JMS server
    //use templates default weblogic user
    find User "weblogic" as u1;
    set u1.password "weblogic1";
    //create a new user
    create User "Admin" as u2;
    set u2.password "weblogic1";
    //assign User "Admin" to Group "Administators";
    write domain to "C:\Oracle\Weblogic12\user_projects\domains\silent-domain"; // The domain name will be "silent-domain"
    close template;
    Edited by: 998028 on 4 Apr, 2013 5:35 AM
    Edited by: 998028 on 9 Apr, 2013 6:28 AM

  • Foreign JMS Server Persistance\Retry in case Remote JMS Provider goes down

    Hi All
    I would need more clarity on this. How does the Foreign JMS Server behave in case the remote JMS provider goes down. Does it take the message from the Publishing Proxy Service and retries\persists the JMS Message till the remote provide is up?
    Please let us know. This would effect our design as retrial is very important here. Thanks

    If you want to provide guaranteed delivery with automatic retries when using remote JMS implementations, there are multiple ways to implement it:
    1. While reading from a foreign JMS destination
    Create a Foreign JMS server using transactional drivers (use XA in case of JMS). The messages remain on remote server JMS queue and OSB proxy polls the message directly on remote server. So if Remote Server is down OSB will not be able to read the message. Once remote server is up OSB will pick up the message (as long as foreign JMS server provides persistence and maintains the messages in the queue during a server restart). In case of error in OSB foreign queue can do retry if it provides a retry mechanism.
    2. While writing the message to a foreign JMS destination
    a. Use a foreign JMS server using transactional connection. Put the retry mechanism in OSB Business service which writes to the foreign JMS/MQ queue. In case of failure Business Service can retry based on configuration. If you want to provide guaranteed delivery then create a local JMS queue to store the messages. So when remote destination is down for a long time undelivered messages will be rolled back to the local queue. You can put retry mechanism on the local queue.
    b. Use a messaging bridge which will write the messages to the remote destination. You can configure retry delivery rules in messaging bridge so once busienss service writes the message to the bridge, a SAF agent will ensure the delivery to remote destination whenever it is up.

  • How retieve ste data records(I did not export) in Site manager

    corrupted my vista (files exist not lost) how retieve ste data records(I did not export) in Site manager for use in a new installation... was dw cs4 now dw cs6...

    Unless you previously exported all your site definition setting and saved them to a safe place (i.e. an external drive, local or remote site folder), you must manually recreate them in CS6 via  Site > Manage Sites > New...
    Nancy O.

  • Can anyone help me how to work with jms server in osb?

    Hi,
    I am new in osb. I have requirement in osb listeners.
    I want to put some data in to jms server using osb in one project and then consume that data using osb in diffrent projects.
    how to configure jms server to work above scenario?
    how to construct business and proxy sevices?
    jms protocal format?
    My requirement is topic in jms server
    Regards,
    Raju..

    Hi,
    The below link will help you to create simple JMS in weblogic
    https://blogs.oracle.com/soaproactive/entry/how_to_create_a_simple
    How to push message and consume message
    http://rangarb.wordpress.com/2012/04/18/working-with-jms-in-osb-11g/
    Another example of subscription of jms
    http://oraclesoaandoim.blogspot.co.uk/2012/04/oracle-service-11116-consume-jms.html
    Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.
    Thanks,
    Vijay

  • JMS topic-cache topic is not getting broadcasting in other managed servers

    Hi All,
    Please give me some idea in fixing the issue that im facing.
    I have created the JMS topic in my weblogic console server which has 2 managed servers.
    I have a feature in my application which is kept in a cache that will be used by my JMS topic. If my request hits managed 1 server im able to see the newly created feature.
    But the same feature is not working when i make the request hit managed 2 server.
    It means the JMS topic is not getting broadcasted properly in other managed server. I dont want to go for a server recycle which will resolve the issue.
    Please let me know if im not clear enough.
    Below is the description provided by my partner on the same issue in his words..
    "The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.
    The same problem is observed in Production as well. Let us know if there is anything wrong in the way the JMS Topic is created or any other configuration is missing, that is not allowing the proper functioning of the Topic."
    fyi...i have all my firewall enabled between the managed servers.And multicast property is also declared correctly only.

    Please let me know if im not clear enough.No. Please explain again.
    The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.Is it a distributed topic? Or does it mean a topic message doesnt get delivered to all subscribers?
    ram.

  • JMSHelper throws 'JMS server is not targetted' creating distributed queue

    I am trying to use the 8.1 weblogic.jms.extensions.JMSHelper to create a distributed queue. The target JMS servers are all migratable servers. When calling method createDistributedQueueAsync() I get a JMSException thrown compaining that the [first] JMS server is not targetted. Looking at the code provided in [http://forums.bea.com/bea/thread.jspa?messageID=200023386] which is based on the JMSHelper class source, the exception may be thrown because the target MBean is of class MigratableTargetMBean, whereas the JMSHelper is expecting class TargetMBean. Yet, the 9.0 documentation (which at least documents it) suggests that MigratableTargetMBean is derived from TargetMBean
              Does anyone have experience of this issue or its resolution, short of crafting the code by hand as per the above-referenced reply?

    Hi,
    Just to remember the configuration: 2 managed servers configured as cluster that should be deployed on 2 different machine.
    Following summary of the tests:
         - node manager + admin server + 1 managed server running on the first machine --> server failed to init with error "Server is not in the majority cluster partition"
         - node manager + admin server + 2 managed servers running on the one machine --> servers are running without errors
         - node manager + admin server + 1 managed server running on the first  machine / node manager runs on the second machine --> server on the first machine runs without errors without the famous error ' Server is not in the majority cluster partition'.
    Bottom line, seems that if the node manager is not running on the remote machine, the cluster is not in a stable state and so the single managed server failed to initialize.
    Is it according the documentation / expectations ?
    Thanks,
    Yaakov

  • Issues with JMS Server migration

    Hi All,
    I have issue with JMS server migration.
    I have configured clustred environment with 2 Managed server (MS1 & MS2) and with one JMS Server which is running on MS1 and configured for auto migration, when I start both my managed server once and access the application very functionality works fine and when I stop the MS1 the JMS server successfully geting migrated to MS2 and in this scenarion also my application works as expected and when I restart the MS1 and access the application all the functionalities related to MDBs are executed twice.
    However once we restart the MS1 we observe that in the monitor tab of MDB the connection status for both managed servers it show as connected.
    As a result there is a redundancy when the MDB is executed
    I am using Weblogic Server 10.3.0 & normal topics in the MDBs.
    Please let me know is this a bug or am I missing any configuration.

    Hi Suresh,
    There is a "Bug-10007947" in WLS 10.3.0 version which dose not displays the values properly on admin-console once the migration has taken place, however I am assuming that bug may fix your issue so try that out in your test environment. If that dose not work try out the below suggestions.
    Suggestion:
    - Try the same test on different versions of WLS lower as well as on higher versions compared to WLS 10.3.0 (i.e WLS 9.2.X and WLS 10.3.x) and check what are the result.
    - If in any other version your test runes properly, then you can create a simple test case and open a service request with Oracle asking for creating a BUG and let them do their job.
    Hope above information helped you.
    Regards,
    Ravish Mody

  • Migratable JMS server

    Hello!
    Weblogic 10.3.6
    I just trying to create JMS cluster.
    First i have two managed servers (MS1 and MS2) in the same domain (DOMAIN1) and in the same cluster (CLUSTER1). Cluster have not any additional settings related to migration options.
    Then i create file store "FS1" with target "MS1 (migratable)".
    Then i create one JMS server "JMSS1" with target "MS1 (migratable)" and with file store FS1.
    Then i create connection factory "CF1" with target CLUSTER1.
    Then i create distributed queue "Q1" with target CLUSTER1.
    May i hope with this configuration that Q1 will jump to MS2 in case of fail on MS1?

    Hi,
    Please follow the below steps for the automatic migration:
    1. First cluster needs to be configured for automatic server migration:
    Home->Cluster->configuration ->Migration -> Lock and Edit ->Choose Migratable machine for automatic server migration ->Data Source For AUtomatic Migration(Choose Datastore for automatic server migration) -> Click on Save
    2. Environment -> Migratable target -> click on the migratable target -> Click on Migration -> select the Constrained Candidate Servers -> select service migration policy as Automatic Migrate Failure Recovery services -> Save and activate changes
    3. Need to create a table called ACTIVE in the DB and the ddl script is located under($WL_SERVER/wl_server_10.3/server/db/oracle/920) query name:leasing.ddl
    4. Create a Non XA data source(While selecting the driver you should select the Non XA driver) and in the transaction tab of the data source uncheck the global transaction option. Also the data source should point to cluster.
    5. The data source created in the step 4 should be used in the JDBC Persistence store and also can be used in Cluster data source. The JDBC persistence store should be used in the JMS server and the JMS Server should be used in the JMS Queue.
    Regards
    Asutosh Kar

  • JNDI Names of JMS server's queue not replicating to cluster

              Am having some trouble configuring a JMS Server and Queues in a clustered development
              environment. It is a simple cluster of 2 servers (Server1 and Server2) both on
              a single machine.
              The "JobServer" JMS Server is targeted to "Server1 (migratable)". All the JNDI
              names for the Queues appear in the JNDI tree of Server1, but not in Server2.
              When the sending of a message is attempted on Server2, the following occurs:
              javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
              didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
              at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
              This may be a problem with the cluster configuration, but I haven't been able
              to see anything wrong with it.
              Any and all help will be appreciated.
              There is the Config.xml file:
              <?xml version="1.0" encoding="UTF-8"?>
              <Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
              <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
              ListenPort="7001" Name="myserver" NativeIOEnabled="true"
              ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              <SSL Enabled="false" HostnameVerificationIgnored="false"
              IdentityAndTrustLocations="KeyStores" ListenPort="7002" Name="myserver"/>
              <Log Name="myserver" NumberOfFilesLimited="true"/>
              </Server>
              <Security Name="mydomain"
              PasswordPolicy="wl_default_password_policy"
              Realm="wl_default_realm" RealmSetup="true">
              <weblogic.security.providers.authentication.DefaultAuthenticator
              Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authentication.DefaultIdentityAsserter
              ActiveTypes="AuthenticatedUser"
              Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authorization.DefaultRoleMapper
              Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authorization.DefaultAuthorizer
              Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
              <weblogic.security.providers.authorization.DefaultAdjudicator
              Name="Security:Name=myrealmDefaultAdjudicator"
              Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
              <weblogic.security.providers.credentials.DefaultCredentialMapper
              Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
              <weblogic.management.security.authentication.UserLockoutManager
              Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
              <weblogic.management.security.Realm
              Adjudicator="Security:Name=myrealmDefaultAdjudicator"
              Auditors="Security:Name=myrealmSTARSIIAuditor"
              AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
              Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
              CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
              DefaultRealm="true" DisplayName="myrealm"
              FullyDelegateAuthorization="true"
              Name="Security:Name=myrealm"
              RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
              <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
              ControlFlag="SUFFICIENT"
              Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
              <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
              ExemptUri="/common/,/images/,/warning.do,/login.do"
              Name="Security:Name=myrealmSTARSIIAuthorizer"
              PolicyDeploymentEnabled="false"
              Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
              <gov.fns.starsii.common.security.audit.STARSIIAuditor
              Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
              </Security>
              <EmbeddedLDAP
              Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI=" Name="mydomain"/>
              <SecurityConfiguration
              Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
              Name="mydomain" RealmBootStrapVersion="1"/>
              <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
              <FileRealm Name="wl_default_file_realm"/>
              <PasswordPolicy Name="wl_default_password_policy"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII BRSB Pool"
              Password="{3DES}9pslRpr051lR9/NEKdanag=="
              Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
              PoolName="STARSII Store Pool" Targets="MyCluster"/>
              <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
              PoolName="STARSII Store Pool" Targets="MyCluster"/>
              <!--StartupClass
              ClassName="gov.fns.starsii.common.common.PropertiesFileLoader"
              DeploymentOrder="250" Name="STARS II Properties Startup Class" Targets="myserver,MyCluster"/>
              <StartupClass
              ClassName="gov.fns.starsii.common.common.ReferenceValuesHelper"
              DeploymentOrder="500"
              Name="STARS II Reference Values Startup Class" Targets="myserver,MyCluster"/>
              <StartupClass
              ClassName="gov.fns.starsii.common.common.ReportCriteriaHelper"
              DeploymentOrder="750"
              Name="STARS II Reports Criteria Startup Class" Targets="myserver,MyCluster"/
              -->
              <MailSession JNDIName="mail/STARSIIMailSession"
              Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj" Targets="myserver"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII Store Pool"
              Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              Targets="MyCluster"
              TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="AffTest" Password=""
              Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
              <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
              PoolName="AffTest" Targets=""/>
              <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
              Name="Spy STARSII BRSB Pool"
              Password="{3DES}9pslRpr051lR9/NEKdanag=="
              Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII Store Pool 2"
              Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
              PoolName="STARSII Store Pool" Targets=""/>
              <JDBCConnectionPool
              DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              Name="STARSII Stars Pool"
              Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
              Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
              Targets="MyCluster"
              TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              <Machine Name="MachineA">
              <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
              </Machine>
              <Server Cluster="MyCluster" ExpectedToRun="false"
              ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
              ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
              Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              <ServerDebug Name="Server1"/>
              <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
              <KernelDebug Name="Server1"/>
              <Log Name="Server1"/>
              <ServerStart Name="Server1"
              OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
              Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              <WebServer Name="Server1"/>
              <COM Name="Server1"/>
              <IIOP Name="Server1"/>
              <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
              <JTARecoveryService Name="Server1"/>
              </Server>
              <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
              MulticastAddress="226.0.0.244" Name="MyCluster"/>
              <Server Cluster="MyCluster" ExpectedToRun="false"
              ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
              ListenPort="7002" Machine="MachineB" Name="Server2"
              ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              <ServerDebug Name="Server2"/>
              <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
              <KernelDebug Name="Server2"/>
              <Log Name="Server2"/>
              <ServerStart Name="Server2"
              Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              <WebServer Name="Server2"/>
              <COM Name="Server2"/>
              <IIOP Name="Server2"/>
              <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
              <JTARecoveryService Name="Server2"/>
              </Server>
              <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
              Notes="This is a system generated default migratable target for a server.
              Do not delete manually." UserPreferredServer="Server1"/>
              <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
              Notes="This is a system generated default migratable target for a server.
              Do not delete manually." UserPreferredServer="Server2"/>
              <Application Deployed="true" Name="STARSII"
              Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
              <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
              <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
              <EJBComponent Name="../commonSession" Targets="MyCluster" URI="../commonSession"/>
              <EJBComponent Name="../complianceMessage" Targets="MyCluster" URI="../complianceMessage"/>
              <EJBComponent Name="../complianceSession" Targets="MyCluster" URI="../complianceSession"/>
              <EJBComponent Name="../starsiiEntity" Targets="MyCluster" URI="../starsiiEntity"/>
              <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
              <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
              <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
              <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
              <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
              </Application>
              <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
              StagingMode="nostage" TwoPhase="true">
              <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
              </Application>
              <Application Name="activeportal"
              Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
              StagingMode="nostage" TwoPhase="true">
              <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
              </Application>
              <JTA Name="mydomain" TimeoutSeconds="300"/>
              <JMSServer Name="JobServer" Targets="Server1 (migratable)">
              <JMSQueue CreationTime="1072820642598"
              JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
              <JMSQueue CreationTime="1072820669345"
              JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
              <JMSQueue CreationTime="1088000795852"
              JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
              <JMSQueue CreationTime="1072820687125"
              JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
              <JMSQueue CreationTime="1072820687125"
              JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
              <JMSQueue CreationTime="1072820687225"
              JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
              <JMSQueue CreationTime="1072820687325"
              JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
              <JMSQueue CreationTime="1072820687425"
              JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
              <JMSQueue CreationTime="1072820687525"
              JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
              <JMSQueue CreationTime="1072820687625"
              JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
              <JMSQueue CreationTime="1072820687725"
              JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
              <JMSQueue CreationTime="1072820687825"
              JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
              <JMSQueue CreationTime="1072820687925"
              JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
              <JMSQueue CreationTime="1072820688025"
              JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
              <JMSQueue CreationTime="1072820688125"
              JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
              <JMSQueue CreationTime="1072820688225"
              JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
              <JMSQueue CreationTime="1072820688325"
              JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
              </JMSServer>
              <Machine Name="MachineB">
              <NodeManager DebugEnabled="true" Name="MachineB"/>
              </Machine>
              </Domain>
              

    Internally, many BEA developers and testers use various versions
              of XP with clustering on a daily basis. I don't know what
              is unique about your machine. I suggest raising the issue
              with customer support and/or posting to the clustering newsgroup...
              Andy Frank wrote:
              > It would seems that my OS and the MultiCast config are to blame. The MultiCast
              > test utility worked fine the Win2K machines I tried. Think I will take another
              > look at MS KB article 827536 and/or think about another dev OS.
              >
              > "Andy Frank" <[email protected]> wrote:
              >
              >>Tom,
              >>Thanks for this info.
              >>
              >>My servers don't look like they are running in different subnets (had
              >>a friend
              >>look this over and he concurs).
              >>
              >>My network admin says he hasn't blocked multicast traffic.
              >>
              >>I think the MultiCast test utility is telling me that I have some kind
              >>of multicast
              >>config problem. Output follows:
              >>
              >>------ Begin MultiCast test utility output: ------
              >>C:\bea\weblogic81\server\bin>java utils.MulticastTest -N server200 -A
              >>237.155.15
              >>5.1 -t 15
              >>***** WARNING ***** WARNING ***** WARNING *****
              >>Do NOT use the same multicast address as a running WLS cluster.
              >>
              >>
              >>Starting test. Hit any key to abort
              >>
              >>
              >>Using multicast address 237.155.155.1:7001
              >>Will send messages under the name server200 every 2 seconds
              >>Will print warning every 15 seconds if no messages are received
              >>
              >> I (server200) sent message num 1
              >> I (server200) sent message num 2
              >> I (server200) sent message num 3
              >> I (server200) sent message num 4
              >> I (server200) sent message num 5
              >> I (server200) sent message num 6
              >> I (server200) sent message num 7
              >>java.net.SocketTimeoutException: Receive timed out
              >> at java.net.PlainDatagramSocketImpl.receive(Native Method)
              >> at java.net.DatagramSocket.receive(DatagramSocket.java:680)
              >> at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
              >> I (server200) sent message num 8
              >> I (server200) sent message num 9
              >> I (server200) sent message num 10
              >> I (server200) sent message num 11
              >> I (server200) sent message num 12
              >>------ End MultiCast test utility output: ------
              >>
              >>No "Received message X from server200" messages. I think I need to look
              >>into
              >>configuring multicast communications on my OK (Windows XP Pro, ver 2002
              >>SP1).
              >>I did see MS KB article 827536 about "An IP multicast may not be sent
              >>correctly
              >
              >>from Windows XP or from Windows Server 2003" (I do have 2 network adapters),
              >
              >>but
              >>the resolution scared me some.
              >>
              >>Think I will try some things out on another OS and see what that gets
              >>me.
              >>
              >>Any other thoughts on this will be appreciated.
              >>
              >>
              >>Tom Barnes wrote:
              >>
              >>>I too suspect something is going wrong with clustering, I wonder
              >>>if the servers are running in different subnets (even though
              >>>they are on the same box) and/or your network admin has
              >>>blocked multicast traffic.
              >>>
              >>>The MultiCast test utility should help narrow things down:
              >>>
              >>>http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798
              >>>
              >>>Tom
              >>>
              >>>Andy Frank wrote:
              >>>
              >>>
              >>>>Am having some trouble configuring a JMS Server and Queues in a clustered
              >>>
              >>>development
              >>>
              >>>>environment. It is a simple cluster of 2 servers (Server1 and Server2)
              >>>
              >>>both on
              >>>
              >>>>a single machine.
              >>>>
              >>>>The "JobServer" JMS Server is targeted to "Server1 (migratable)".
              >>
              >>>All the JNDI
              >>>
              >>>>names for the Queues appear in the JNDI tree of Server1, but not in
              >>>
              >>>Server2.
              >>>
              >>>>When the sending of a message is attempted on Server2, the following
              >>>
              >>>occurs:
              >>>
              >>>>javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
              >>>>didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
              >>>> at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
              >>>>
              >>>>This may be a problem with the cluster configuration, but I haven't
              >>>
              >>>been able
              >>>
              >>>>to see anything wrong with it.
              >>>>
              >>>>Any and all help will be appreciated.
              >>>>
              >>>>There is the Config.xml file:
              >>>><?xml version="1.0" encoding="UTF-8"?>
              >>>><Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
              >>>> <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
              >>>> ListenPort="7001" Name="myserver" NativeIOEnabled="true"
              >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              >>>> <SSL Enabled="false" HostnameVerificationIgnored="false"
              >>>> IdentityAndTrustLocations="KeyStores" ListenPort="7002"
              >>>
              >>>Name="myserver"/>
              >>>
              >>>> <Log Name="myserver" NumberOfFilesLimited="true"/>
              >>>> </Server>
              >>>> <Security Name="mydomain"
              >>>> PasswordPolicy="wl_default_password_policy"
              >>>> Realm="wl_default_realm" RealmSetup="true">
              >>>> <weblogic.security.providers.authentication.DefaultAuthenticator
              >>>> Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
              >>>>
              >>>> <weblogic.security.providers.authentication.DefaultIdentityAsserter
              >>>> ActiveTypes="AuthenticatedUser"
              >>>> Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.security.providers.authorization.DefaultRoleMapper
              >>>> Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.security.providers.authorization.DefaultAuthorizer
              >>>> Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.security.providers.authorization.DefaultAdjudicator
              >>>> Name="Security:Name=myrealmDefaultAdjudicator"
              >>>> Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
              >>>> <weblogic.security.providers.credentials.DefaultCredentialMapper
              >>>> Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.management.security.authentication.UserLockoutManager
              >>>> Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
              >>>> <weblogic.management.security.Realm
              >>>> Adjudicator="Security:Name=myrealmDefaultAdjudicator"
              >>>> Auditors="Security:Name=myrealmSTARSIIAuditor"
              >>>> AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
              >>>> Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
              >>>> CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
              >>>> DefaultRealm="true" DisplayName="myrealm"
              >>>> FullyDelegateAuthorization="true"
              >>>> Name="Security:Name=myrealm"
              >>>> RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
              >>>>
              >>>> <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
              >>>> ControlFlag="SUFFICIENT"
              >>>> Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
              >>>> <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
              >>>> ExemptUri="/common/,/images/,/warning.do,/login.do"
              >>>> Name="Security:Name=myrealmSTARSIIAuthorizer"
              >>>> PolicyDeploymentEnabled="false"
              >>>> Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
              >>>> <gov.fns.starsii.common.security.audit.STARSIIAuditor
              >>>> Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
              >>>> </Security>
              >>>> <EmbeddedLDAP
              >>>> Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI="
              >>>
              >>>Name="mydomain"/>
              >>>
              >>>> <SecurityConfiguration
              >>>> Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
              >>>> Name="mydomain" RealmBootStrapVersion="1"/>
              >>>> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
              >>>> <FileRealm Name="wl_default_file_realm"/>
              >>>> <PasswordPolicy Name="wl_default_password_policy"/>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII BRSB Pool"
              >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
              >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>
              >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
              >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
              >>>> <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
              >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
              >>>> <!--StartupClass
              >>>> ClassName="gov.fns.starsii.common.common.PropertiesFileLoader"
              >>>> DeploymentOrder="250" Name="STARS II Properties Startup Class"
              >>>
              >>>Targets="myserver,MyCluster"/>
              >>>
              >>>> <StartupClass
              >>>> ClassName="gov.fns.starsii.common.common.ReferenceValuesHelper"
              >>>> DeploymentOrder="500"
              >>>> Name="STARS II Reference Values Startup Class" Targets="myserver,MyCluster"/>
              >>>> <StartupClass
              >>>> ClassName="gov.fns.starsii.common.common.ReportCriteriaHelper"
              >>>> DeploymentOrder="750"
              >>>> Name="STARS II Reports Criteria Startup Class" Targets="myserver,MyCluster"/
              >>>>-->
              >>>> <MailSession JNDIName="mail/STARSIIMailSession"
              >>>> Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj"
              >>>
              >>>Targets="myserver"/>
              >>>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII Store Pool"
              >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              >>>> Targets="MyCluster"
              >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="AffTest" Password=""
              >>>> Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
              >>>
              >>>> <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
              >>>> PoolName="AffTest" Targets=""/>
              >>>> <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
              >>>> Name="Spy STARSII BRSB Pool"
              >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
              >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
              >>>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII Store Pool 2"
              >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
              >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
              >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
              >>>
              >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>
              >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
              >>>> PoolName="STARSII Store Pool" Targets=""/>
              >>>> <JDBCConnectionPool
              >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
              >>>> Name="STARSII Stars Pool"
              >>>> Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
              >>>> Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
              >>>> Targets="MyCluster"
              >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
              >>>> <Machine Name="MachineA">
              >>>> <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
              >>>> </Machine>
              >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
              >>>> ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
              >>>> ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
              >>>> Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true"
              >>>
              >>>StdoutSeverityLevel="64">
              >>>
              >>>> <ServerDebug Name="Server1"/>
              >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
              >>>> <KernelDebug Name="Server1"/>
              >>>> <Log Name="Server1"/>
              >>>> <ServerStart Name="Server1"
              >>>> OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
              >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              >>>> <WebServer Name="Server1"/>
              >>>> <COM Name="Server1"/>
              >>>> <IIOP Name="Server1"/>
              >>>> <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
              >>>> <JTARecoveryService Name="Server1"/>
              >>>> </Server>
              >>>> <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
              >>>> MulticastAddress="226.0.0.244" Name="MyCluster"/>
              >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
              >>>> ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
              >>>> ListenPort="7002" Machine="MachineB" Name="Server2"
              >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
              >>>> <ServerDebug Name="Server2"/>
              >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
              >>>> <KernelDebug Name="Server2"/>
              >>>> <Log Name="Server2"/>
              >>>> <ServerStart Name="Server2"
              >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
              >>>> <WebServer Name="Server2"/>
              >>>> <COM Name="Server2"/>
              >>>> <IIOP Name="Server2"/>
              >>>> <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
              >>>> <JTARecoveryService Name="Server2"/>
              >>>> </Server>
              >>>> <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
              >>>> Notes="This is a system generated default migratable target
              >>>
              >>>for a server.
              >>>
              >>>>Do not delete manually." UserPreferredServer="Server1"/>
              >>>> <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
              >>>> Notes="This is a system generated default migratable target
              >>>
              >>>for a server.
              >>>
              >>>>Do not delete manually." UserPreferredServer="Server2"/>
              >>>> <Application Deployed="true" Name="STARSII"
              >>>> Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
              >>>> <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
              >>>> <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
              >>>> <EJBComponent Name="../commonSession" Targets="MyCluster"
              >>
              >>URI="../commonSession"/>
              >>
              >>>> <EJBComponent Name="../complianceMessage" Targets="MyCluster"
              >>>
              >>>URI="../complianceMessage"/>
              >>>
              >>>> <EJBComponent Name="../complianceSession" Targets="MyCluster"
              >>>
              >>>URI="../complianceSession"/>
              >>>
              >>>> <EJBComponent Name="../starsiiEntity" Targets="MyCluster"
              >>
              >>URI="../starsiiEntity"/>
              >>
              >>>> <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
              >>>> <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
              >>>> <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
              >>>> <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
              >>>> <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
              >>>> </Application>
              >>>> <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
              >>>> StagingMode="nostage" TwoPhase="true">
              >>>> <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
              >>>> </Application>
              >>>> <Application Name="activeportal"
              >>>> Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
              >>>> StagingMode="nostage" TwoPhase="true">
              >>>> <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
              >>>> </Application>
              >>>> <JTA Name="mydomain" TimeoutSeconds="300"/>
              >>>> <JMSServer Name="JobServer" Targets="Server1 (migratable)">
              >>>> <JMSQueue CreationTime="1072820642598"
              >>>> JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
              >>>> <JMSQueue CreationTime="1072820669345"
              >>>> JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
              >>>> <JMSQueue CreationTime="1088000795852"
              >>>> JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
              >>>> <JMSQueue CreationTime="1072820687125"
              >>>> JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
              >>>> <JMSQueue CreationTime="1072820687125"
              >>>> JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
              >>>> <JMSQueue CreationTime="1072820687225"
              >>>> JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
              >>>> <JMSQueue CreationTime="1072820687325"
              >>>> JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
              >>>> <JMSQueue CreationTime="1072820687425"
              >>>> JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
              >>>> <JMSQueue CreationTime="1072820687525"
              >>>> JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
              >>>> <JMSQueue CreationTime="1072820687625"
              >>>> JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
              >>>> <JMSQueue CreationTime="1072820687725"
              >>>> JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
              >>>> <JMSQueue CreationTime="1072820687825"
              >>>> JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
              >>>> <JMSQueue CreationTime="1072820687925"
              >>>> JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
              >>>> <JMSQueue CreationTime="1072820688025"
              >>>> JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
              >>>> <JMSQueue CreationTime="1072820688125"
              >>>> JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
              >>>> <JMSQueue CreationTime="1072820688225"
              >>>> JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
              >>>> <JMSQueue CreationTime="1072820688325"
              >>>> JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
              >>>> </JMSServer>
              >>>> <Machine Name="MachineB">
              >>>> <NodeManager DebugEnabled="true" Name="MachineB"/>
              >>>> </Machine>
              >>>></Domain>
              >>>
              >
              

  • Offline WLST changes JMS Server Target From a Migratable target

    I have a simple WL 9.2mp2 domain which has 2 managed servers, one JMS Server and two migratable targets (one for each managed server) and the JMS server is targeted to one of the migratable targets. When I read the domain into WLST offline, the JMS server's target is changed from the migratable target to the preferred server defined in the migratable target. Is this a bug in WLST? Am I missing some option on WLST that can fix this?
              I saw a similar posting for 8.1 and no resolution.
              Thanks in advance,
              Mark.

    Hi
              Please find my answers below:
              Q1:
              It depends how you configured the JMSSevers.
              If both the JMSServers are targeted to the same MigratableTarget, then you do the migration only once, that will move both of them to the new active server.
              If not, you have to perform the migration once for each MT.
              Q2:
              No, you dont have to start the Managed Server II, unless otherwise you wanted it to be readily available for the migration next time.
              Q3:
              You can just repeat the migration process by specifying the destination as Maganged Server-I this time. You dont need change the configuration for this, since the MT, shall already have the Candidate servers M1 and M2 and both JMSServers are targeted to MT.
              Q4:
              Yes, as long as the CF is targeted to the cluster, your connection is valid. But your destinations references will become invalid after migration, so you have to have some logic in the exception listeners to reconnect again.
              Hope this helps.

  • Weblogic Server 9.2 - JMS File Store not working as expected.

    Hi,
    I am facing a problem at the server startup possibly due to huge size of the JMS File Store created.
    My question is that our application receives messages via MDB (container managed),
    Even after successfully processing the message, the message which is logged in the File Store is not deleted.
    How can i make sure that a message which is successfully processed is not logged in the file store?
    (considering container managed transactions do not require acknowledgement-mode set in the descriptor, altough i have it specified)
    Find the the stack trace on the server log below:
    ####<Dec 10, 2008 11:45:30 AM CST> <Error> <JMS> <xlqwls01> <ACSServer1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tu
    ning)'> <<WLS Kernel>> <> <> <1228931130485> <BEA-040123> <Failed to start JMS Server "SDBJMSServer1" due to weblogic.jms.common.JMSException: web
    logic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery.
    weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:963)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
    at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:839)
    at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.store.PersistentStoreException: [Store:280020]There was an error while reading from the log file
    at weblogic.store.io.file.Heap.read(Heap.java:648)
    at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
    at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
    at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
    at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
    at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
    at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.io.IOException: Error reading from file, No such file or directory, errno=2
    at weblogic.store.io.file.direct.DirectIONative.read(Native Method)
    at weblogic.store.io.file.direct.DirectFileChannel.read(DirectFileChannel.java:133)
    at weblogic.store.io.file.StoreFile.read(StoreFile.java:281)
    at weblogic.store.io.file.Heap.read(Heap.java:646)
    at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
    at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
    at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
    at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
    at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
    at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Edited by: user5823244 on Dec 14, 2008 2:59 AM

    Hi,
    It seems there are two problems going on here:
    (1) Forceful shutdowns should not (must not) normally corrupt the file store. There may be a bug in WL, or it may be the admin is arbitrarily deleting some file store files while leaving others in place (not supported).
    (2) "Even after successfully processing the message, the message which is logged in the File Store is not deleted."
    This is a strong indicator that there's an application error and the message is not actually getting deleted. The file store size is proportional to the number of current messages (successfully processing/acknowledging/committing a received message frees space for new messages), and is not proportional to the number of successfully processed messages.
    I think it's likely that the application isn't actually successfully processing the message but is instead receiving a message somehow and is either:
    (A) throwing an exception from within an XA-or-non-XA-MDB or auto-ack-onMessage() and somehow forcing the message into a state where its not being redelivered for reprocessing
    (B) specifying a transacted session and failing to call session.commit()
    (C) specifying an XA transaction capable receive and failing to call commit
    (D) specifying a "client acknowledge" mode and failing to call acknowledge .
    For evidence, check the console statistics for the destination after "successfully processing" all sent messages: the value of "current" + "pending" should be zero once all processing completes, the value of "received (aka total)" should match the sent message count. If the "current" + "pending" value is non-zero, then this is an indication there are messages that were not successfully processed.
    Tom Barnes
    WebLogic Server Messaging Developer Team

Maybe you are looking for