Doubt in WLS 7.0 JMS Cluster Failover

I configured 2 JMS servers JMS1 and JMS2. I also configured 2 JMS file stores FS1 and FS2. JMS server JMS1 using FS1 and JMS2 using FS2. I also configured 1 distributed queue DQ for the cluster server. I also configured 1 local queue LQ1 in JMS1 and 1 local queue LQ2 in JMS2.
          When the JMS2 server failed, I migrate it to the migratable target JMS1. The file store FS2 and all transaction log files have been copied to the JMS1 server with the same path. I first migrated JTA service and then JMS service. The migration procedure worked and no problem. But the messages in the JMS2 did not get processed by the migratable target JMS1.
          What was wrong in my configuration? In my migration procedure? Or in my file store? Or anything? I knew I should use shared disk storage for file store. I just want to simulate the problem and try cluster failover.
          

          Chan Tong wrote:
          > Tom Barnes <[email protected]> wrote:
          >
          >>
          >>Chan Tong wrote:
          >>
          >>>I configured 2 JMS servers JMS1 and JMS2. I also configured 2 JMS file
          >>
          >>stores FS1 and FS2. JMS server JMS1 using FS1 and JMS2 using FS2. I
          >>also configured 1 distributed queue DQ for the cluster server. I also
          >>configured 1 local queue LQ1 in JMS1 and 1 local queue LQ2 in JMS2.
          >>
          >>>When the JMS2 server failed, I migrate it to the migratable target
          >>
          >>JMS1. The file store FS2 and all transaction log files have been copied
          >>
          >>
          >>>to the JMS1 server with the same path. I first migrated JTA service
          >>
          >>and then JMS service. The migration procedure worked and no problem.
          >>
          >>>But the messages in the JMS2 did not get processed by the migratable
          >>
          >>target JMS1.
          >>
          >>>What was wrong in my configuration? In my migration procedure? Or in
          >>
          >>my file store? Or anything? I knew I should use shared disk storage
          >>for file store. I just want to simulate the problem and try cluster
          >>failover.
          >>
          >>Need more information. What do you mean by "the messages in the JMS2
          >>
          >>did not get processed"? Do JMS2's message counts
          >>show up in console monitoring?
          >>
          >
          > After migrate JMS2 to JMS1, the messages in the JMS2 file store were not processed
          > by the JMS1. Could it be I manual copied the file store? Or I will need to use
          > shared file store that can be access from from both servers?
          Either way yes. The migrated JMS server still needs to be able to
          find its store. Another way to do this is to use a JDBC store - as
          long as the remote database is highly available and your
          applications can tolerate the likely JMS performance reduction.
          

Similar Messages

  • JMS cluster and happen JMS Queue Exception javax.naming.NameAlreadyBoundExc

    Hi,
    Sorry I not sure how to setup JMS cluster in WLS 10.3.2. We have two manager server in two machine. And will join into one cluster. After configure the JMS module & JMS server. We found it only can work in one server. And will faill in another server. And reply the error message as below :
    Any one can help to tell me why one server success. And other is fail !
    javax.naming.NameAlreadyBoundException: JMS_Queue_misdel_a is already bound; rem
    aining name ''
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
    at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:140)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
    at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.jav
    ==> config for JMS
    <jms-server>
    <name>JMS_Server_cim_a</name>
    <target>ebowls05</target>
    <persistent-store xsi:nil="true"></persistent-store>
    <hosting-temporary-destinations>true</hosting-temporary-destinations>
    <temporary-template-resource xsi:nil="true"></temporary-template-resource>
    <temporary-template-name xsi:nil="true"></temporary-template-name>
    <message-buffer-size>-1</message-buffer-size>
    <expiration-scan-interval>30</expiration-scan-interval>
    </jms-server>
    <jms-server>
    <name>JMS_Server_cim_b</name>
    <target>ebowls06</target>
    <persistent-store xsi:nil="true"></persistent-store>
    <hosting-temporary-destinations>true</hosting-temporary-destinations>
    <temporary-template-resource xsi:nil="true"></temporary-template-resource>
    <temporary-template-name xsi:nil="true"></temporary-template-name>
    <message-buffer-size>-1</message-buffer-size>
    <expiration-scan-interval>30</expiration-scan-interval>
    </jms-server>
    <migratable-target>
    <name>ebowls06 (migratable)</name>
    <notes>This is a system generated default migratable target for a server. Do
    not delete manually.</notes>
    <user-preferred-server>ebowls06</user-preferred-server>
    <cluster>ebouatCluster</cluster>
    </migratable-target>
    <migratable-target>
    <name>ebowls05 (migratable)</name>
    <notes>This is a system generated default migratable target for a server. Do
    not delete manually.</notes>
    <user-preferred-server>ebowls05</user-preferred-server>
    <cluster>ebouatCluster</cluster>
    </migratable-target>
    <jms-system-resource>
    <name>JMS_ConnFactory_cim</name>
    <target>ebouatCluster</target>
    <descriptor-file-name>jms/JMS_ConnFactory_cim/JMS_ConnFactory_cim-jms.xml</d
    escriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>JMS_Queue_promis</name>
    <target>ebouatCluster</target>
    <sub-deployment>
    <name>JMS_Queue_promis@JMS_Server_cim_a</name>
    <target>JMS_Server_cim_a</target>
    </sub-deployment>
    <sub-deployment>
    <name>JMS_Queue_promis@JMS_Server_cim_b</name>
    <target>JMS_Server_cim_b</target>
    </sub-deployment>
    <descriptor-file-name>jms/JMS_Queue_promis/JMS_Queue_promis-jms.xml</descrip
    tor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>JMS_Template_cim</name>
    <target>ebouatCluster</target>
    <descriptor-file-name>jms/JMS_Template_cim/JMS_Template_cim-jms.xml</descrip
    tor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>JMS_Queue_misdel_a</name>
    <target>ebouatCluster</target>
    <sub-deployment>
    <name>JMS_Queue_misdel_a@JMS_Server_cim_a</name>
    <target>JMS_Server_cim_a</target>
    </sub-deployment>
    <sub-deployment>
    <name>JMS_Queue_misdel_a@JMS_Server_cim_b</name>
    <target>JMS_Server_cim_b</target>
    </sub-deployment>
    <descriptor-file-name>jms/JMS_Queue_misdel_a/JMS_Queue_misdel_a-jms.xml</des
    criptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>JMS_Queue_misdel_b</name>
    <target>ebouatCluster</target>
    <sub-deployment>
    <name>JMS_Queue_misdel_b@JMS_Server_cim_a</name>
    <target>JMS_Server_cim_a</target>
    </sub-deployment>
    <sub-deployment>
    <name>JMS_Queue_misdel_b@JMS_Server_cim_b</name>
    <target>JMS_Server_cim_b</target>
    </sub-deployment>
    <descriptor-file-name>jms/JMS_Queue_misdel_b/JMS_Queue_misdel_b-jms.xml</des
    criptor-file-name>
    </jms-system-resource>

    1 - JMS clustering is an advanced concept, and, in most cases, uses "distributed queues". In case you haven't already, I highly recommend reading the JMS chapter of the new book "Professional Oracle WebLogic" as well as the related chapters in the JMS Programmer's Guide in the edocs.
    2 - The basic problem below is that you have two different queues that have matching JNDI names, but are in the same cluster.
    3 - The config snippet supplied below does not include the queue configuration. Queue configuration is embedded within the referenced module files.
    4 - Please ensure that you follow configuration best practices, as per: http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG

  • SAP ECC 6.0 SR3 Cluster failover not working in AIX with DB2 UDB V9.1 FP6

    Hi Gurus,
    We have installed the SAP ECC 6.0 SR3 High Availability  with DB2 UDB V9.1 FP6 in AIX cluster environment.
    After installation we are doing the cluster fail test.
    Node A
    Application Server
    Mount Points:
    /sapmnt/<SID>
    /usr/sap/<SID>
    /usr/sap/trans
    Node B
    Database Server
    Mount Points:
    /db2//<SID>
    The procedure followed to do the cluster failover:
    We have down the cluster on Node A and all the resources of the Node A has been moved to Node B.
    On Node B when we issued a command to start the SAP. It says u201Cno start profiles foundu201D
    WE have down the cluster on Node B and  moved the Resource from Node B to Node A .  There the db2 User IDu2019s are not available. We have crated the user Idu2019s manually on Node A. however it did not work.
    Please suggest the procedure to start the sap in cluster failover.
    Best Regards
    Sija

    Hi Sija,
    Can i have detailed scenario in your cluster configuration.
    Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
    Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
    Regards
    Nick Loy

  • Using Connection Pooling in a WLS 5.1.x - Cluster

    Hi,
              We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
              possible to use CP in such a cluster at all ? The problem is, connections
              will be opened and never been closed. How can I configure a cluster for CP?
              I have a WLS-Cluster with 2 instances and my webApp uses connection pooling.
              By the way I get a connection on Instance 1, Instance 2 gets a connection
              also, but never releases it.
              In my opinion, the reference to the connection in the partner-instance will
              be lost.
              How do I have to configure my cluster to work well with that stuff ?
              Thank a lot,
              Markus.
              

    Clustering with connection pools works fine in WLS 5.1. If connections are
              not being release, you have bugs in your code.
              When a connection is retrieved from a pool on one instance, a corresponding
              connection is NOT retrieved on another instance.
              Mike
              "M. Hammer" <[email protected]> wrote in message
              news:[email protected]..
              > Hi,
              >
              > We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
              > possible to use CP in such a cluster at all ? The problem is, connections
              > will be opened and never been closed. How can I configure a cluster for
              CP?
              >
              > I have a WLS-Cluster with 2 instances and my webApp uses connection
              pooling.
              > By the way I get a connection on Instance 1, Instance 2 gets a connection
              > also, but never releases it.
              > In my opinion, the reference to the connection in the partner-instance
              will
              > be lost.
              > How do I have to configure my cluster to work well with that stuff ?
              >
              > Thank a lot,
              >
              > Markus.
              >
              >
              >
              

  • Does WLS 9.0 jms ra support JCA 1.5?

    WLS 9.0 installation incudes jms-xa-adp.rar, jms-notran-adp.rar, jms-local-adp.rar. But all support only JCA 1.0 version if you look at their resource adapter descriptors. The release note says that WLS 9.0 supports JCA 1.5, does not say anything about JMS RA.
    Does WLS 9.0 JMS RAR support JCA 1.5? If so, where can I
    get these rars?
    Thank you in advance
    Charles

    desuported? Can you post a source for this?
    9.0.4 is not certified with JDK 1.5 and will not be. AS 10.1.3 is the first release that is (as far as I know).

  • Re: SocketException WLS 6.1 JMS

     

    Google newsgroup search helps out here:
              http://groups.google.com/groups?q=SocketException+WLS+6.1+JMS&ie=UTF-8&hl=en&btnG=Google+Search
              SImmie Kastner wrote:
              > I am trying to bring up this thread on the weblogic site and nothing shows up. Could you possibly send it to me? Thanks --SImmie
              

  • RDP Services do not accept connection after cluster failover

    Hi guys,
    i am having weird behaviour on my Windows Server 2012 R2. 
    server 1
    - 10.100.1.201
    server 2   - 10.100.1.203
    VIP - 10.100.1.202
    when i perform remote desktop session to server 1 and server 2 after both servers are being rebooted, they are working perfectly fine. during the remote desktop session, i perform a cluster node failover switching node to server 2. immediately i perform
    the task, my server 1 connection will hang and not able to login anymore.
    strangely, when i am connection from the same server zone and perform remote desktop, they work perfectly fine and will not disconnect me from neither of the server 1 and 2. 
    i am suspecting the network routing mess up during the cluster failover, but from the route print, there are identical and has no problem with it.
    any one here has the same problem i experience?
    zhiyuan

    Hi,
    sorry if i lose you ... here is the story
    node 1 - 10.100.1.201
    node 2 - 10.100.1.203
    vip - 10.100.1.202
    when both server restarted, i can remote to both servers, no problem.
    1. RDP to both node 1 and 2 together on their physical IP. Connected successfully. 
    2. checked the Active node on node 1. Perform fail over from node 1 to 2, node 1 RDP session loss connection immediately. checked on node 2, cluster node active on node 2. no errors.
    3. perform node 2 to node 1 fail over. Node 2 RDP session loss connection immediately, node 1 session came back. checked cluster node active on node 1. no errors.
    4. in order to have both can continue to rdp, perform restart on node 2 (the node cannot reconnect), after reboot, rdp back to normal. 
    5. firewall team confirm connection has reach server, server not responding to rdp apparently. 

  • How to manually create a standby db with SAN for hardware cluster failover

    Hi all,
    The primary db(oracle 9i r2, Sun Solaris) puts its datafile, redo logs, control files in SAN while the pfile, listener and tnsnames files are in its local hardisk. I need to create a standby db(not for dataguard) for hardware cluster failover, where if the primary db fails the hardware cluster will failover to standby db(mounting the datafile, redologs, control files in
    SAN to a mount point automatically and start the db services). But I don't know how to create the standby db, I would install the db software first then should I copy the pfile(created from primary db), listener and tnsnames files to standby db? What are the correct steps to do it? Any advice is greatly appreciated.

    Thanks ackermsb for the reponse. I think I have confused of setting standby db and creating a HA. What I trying to achieve is creating a HA with vendor clusterware and oracle e.g. Sun Cluster HA for Oracle.
    The steps involved in preparing the primary and standby oracle are:
    Oracle application files – These files include Oracle binaries, configuration files, and parameter files. Need to installed separately in two servers locally.
    The Database-related files – These files include the control file, redo logs, and data files are placed in a Cluster File System.
    What I don't how to do it is, after installing the oracle binary in standby server, should I create the listener, tnsnames and pfile or copy them from the primary db?
    Thanks in advance.

  • Veritas Cluster failover for oracle

    Hi,
    I'm performing veritas cluster failover for 2 oracle servers which is not working in one way. I've 2 solaris boxes where veritas cluster is configured for failover. In Box1 I'm running 10g and Box2 9.2 when I failover from Box1 to Box2 is working but the other way is not working I'm using 10g listerner for both the services.
    Any help would be appreicated.
    Thanks,

    Hi,
    I'm performing veritas cluster failover for 2 oracle servers which is not working in one way. I've 2 solaris boxes where veritas cluster is configured for failover. In Box1 I'm running 10g and Box2 9.2 when I failover from Box1 to Box2 is working but the other way is not working I'm using 10g listerner for both the services.
    Any help would be appreicated.
    Thanks,

  • X86-64 GNU/LINUX cluster failover alert

    Hi..
    I would like to know how to set the email alert so that I can receive email when the gnu/linux cluster failover to another node. Please Help
    Thanks in advance ...

    Check the documentation of the clusterware product you are using. It will explain how to run commands on failover.

  • Weblogic JMS Cluster

    Hi,
              I have a 6.1 cluster that has a JMS server A and a JMS Server B
              deployed and running on each of the managed nodes. As destination I
              created a topic with the same name for each JMS Server. The connection
              factories I deployed to the cluster only.
              My problem is, when I start the second managed server, I get the
              following error:
              <Error> <Cluster> <Conflict start: You tried to bind an object under
              the name
              com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
              have bound
              from 169.59.5.26 is non clusterable and you have tried to bind more
              than once
              from two or more servers. Such objects can only deployed from one
              server.>
              When I understand correctly, this happens because the JNDI tree gets
              distributed to all nodes of the cluster, so there would be two object
              with the same name. How do I solve this situation? Do I have the
              specify different names for topics in different JMSServer running in a
              cluster? How would the load balancing work?
              Please help. Thanks in advance
              Juerg
              

    Tom,
              Thanks for your help so far, I installed the patch and got things
              working. However I still have some open points where you might be able
              to help.
              Let's assume I don't have these smart forwarders and I have four
              topics per JMSServer deployed to two managed nodes. Connection
              factories deployed to the cluster. When I connect N publishers
              through the cluster, messages from one publisher end up in the
              appropriate topic on nodeA, messages from another publisher end up in
              the appropriate topic on nodeB. Now when I connect a durable
              subscriber via the cluster I only get messages from topics from one of
              the managed nodes, right? (This is exactly what I am seeing in my
              tests) Connecting durable subscribers to each managed node is not
              possible because of JNDI (throws exception like
              InstanceAlreadyExists). How would I connect a subscriber so that it
              subscribes to the right topics on the right node ( one the works with
              the previously described publisher)?
              All this leads me to the conclusion, that without the forwarders, a
              JMS cluster with Weblogic 6.1 is not so powerful, it basically does
              just load balacing.
              Is this correct or am I missing something important here?
              Thanks a lot and have a nice weekend
              Juerg
              Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
              > Juerg Staub wrote:
              > > Tom,
              > >
              > > Thanks a lot. Bascially I did everything right, just need the patch.
              > >
              > > In the other hand I'd like to know what the benefits of the smart
              > > forwarders would be. When I understand correctly, every message would
              > > be forwarded to the appropriate topic in the different JMS servers.
              > > What would that bring in the case of a failure(one node of a cluster
              > > goes down)? As far as I can see, I still would need to 're-establish'
              > > the connection factory, topic session, topic and publisher in order to
              > > publish messages again?
              > >
              >
              > Yep. I think we are on the same page:
              >
              > The "smart-forwarders" would do what the 7.0 distributed topic
              > forwarders do for you. They would forward messages bound to
              > a particular physical topic to all instances of the topic.
              > This can be implemented via a durable subscription on a
              > member topic by each remote member topic's host.
              > MDBs could be used to service the durable subscription,
              > as they already have the reconnect logic built in.
              > (Durable subscriptions are used if you wish to guard against
              > lost messages). The forwarders
              > need to change a property on the message to indicate
              > that the message is already forwarded, and forward
              > only messages that have'nt been forwarded (to prevent
              > endless loops!).
              >
              >
              > > Thanks
              > >
              > > Juerg
              > >
              > > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
              > >
              > >>I suggest you read the "emulating 7.0 distributed destinations"
              > >>section of the JMS performance white-paper available on dev2dev.bea.com.
              > >>You will need to apply the referenced enhancement patch on top of SP3 to
              > >>disable JNDI replication (or update to 6.1SP4).
              > >>
              > >>If you need to create a true distributed topic, you will also need to
              > >>write your own "smart-forwarders" to forward messages
              > >>between the different physical instances of the topic. Or simply
              > >>use WL JMS 7.0 (the upgrade from 6.1 is straight-forward).
              > >>
              > >>Tom
              > >>
              > >>Juerg Staub wrote:
              > >>
              > >>>Hi,
              > >>>
              > >>>I have a 6.1 cluster that has a JMS server A and a JMS Server B
              > >>>deployed and running on each of the managed nodes. As destination I
              > >>>created a topic with the same name for each JMS Server. The connection
              > >>>factories I deployed to the cluster only.
              > >>>
              > >>>My problem is, when I start the second managed server, I get the
              > >>>following error:
              > >>>
              > >>><Error> <Cluster> <Conflict start: You tried to bind an object under
              > >>>the name
              > >>>com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
              > >>>have bound
              > >>>from 169.59.5.26 is non clusterable and you have tried to bind more
              > >>>than once
              > >>>from two or more servers. Such objects can only deployed from one
              > >>>server.>
              > >>>
              > >>>
              > >>>When I understand correctly, this happens because the JNDI tree gets
              > >>>distributed to all nodes of the cluster, so there would be two object
              > >>>with the same name. How do I solve this situation? Do I have the
              > >>>specify different names for topics in different JMSServer running in a
              > >>>cluster? How would the load balancing work?
              > >>>
              > >>>
              > >>>Please help. Thanks in advance
              > >>>
              > >>>Juerg
              > >>
              

  • Different behaviour in JMS Cluster automatic failover

    Hi,
              I am problem in JMS clustering, now let me explain the scenario.
              I have 2 managed servers participating in the weblogic cluster, now since JMS is a singleton service what i did is i have created 2 JMS servers and targeted them to Managedservers 1 and 2 respectively.I have also created a Distributed Destination and deploy they with the deployment "wizard" ("autodeploy") to all the member of the cluster.
              Now in my case I created two different type of client
              Asynchronous and synchronous .
              The first one register himself as MessageListener and also as ExceptionListener. When I bring down the managed server in which the client is connect the call back method onException is called.
              The second client instead register himself as ExceptionListener but not as MessageListener. It call in different thread the receive method on the destination.
              In this case if i I bring down the managed server in which the client is connect the call back method onException is NOT called, instead i receive the JMSException on all the call "receive".
              I expected that the behaviour was the same of the firts client.
              Thanks in advance.
              dani

    Its not clear from your description what you're trying to do, as typical apps use a single module, including those that use distributed destinations, and typical apps do not use the convention of specifying a module name in their JNDI name. (The "!" syntax makes me suspect that you're not using JNDI to lookup destinations, rather you're using the rarely recommended JMS session "createQueue()" call.).
    Never-the-less, I suspect the problem is simply that your using a distributed queue and haven't realized that queue browsers and consumers pin themselves to a single queue member. To ensure full coverage of a distributed queue, the best practice is to use a WebLogic MDB: WebLogic MDBs automatically ensure that each queue member has consumers.
    By the way, if you are using a distributed queues, then the best practice config is as follows for each homogeneous set of JMS servers:
    -- Configure a custom WL store per server, target to the server's default migratable target.
    -- Configure a JMS server per server, target to the server's default migratable target, set the store for the JMS server to be the same as the custom store.
    -- Configure a single JMS module, target to the cluster.
    -- Configure a single subdeployment for the module that references each JMS server (and nothing else).
    -- Configure one or more distributed queues for the module. Never use default targeting -- instead use advanced subdeployment targeting to target each distributed queue to the single subdeployment you defined earlier.
    -- Configure one or more custom connection factories in the module, use default targeting.
    I recommend that you read through the JMS admin and programmer's guides in the edocs if you haven't done so already. You might find that the JMS chapter of the new book "Professional Oracle WebLogic" is helpful.
    Tom
    Edited by: TomB on Nov 4, 2009 10:12 AM

  • JMS queue| failover test question

    HI gurus,
    We are planning a failover test to migrate from prod to contingency environment.
    What happens to transactions that may be sitting in the JMS queue when the prod jvms are stopped? Is there a way to migrate them to the cont jvms?We are using jdbc stores and the supporting tables for both prod and cont will exist in the oracle DB, but with different names. Since the CONT jvms will be using different tables for the JMS queues, is there a way to migrate those queued transactions from prod to the CONT side?
    Details of environment
    1) OS for App Server
    Linux x86-64.
    Linux va2xpre03.gdsososos.com 2.6.18-128.1.6.el5 #1 SMP Tue Mar 24 12:05:57 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
    2) App Server type and version
    WLS 10.3.0
    JDK version
    jrockit_160_11
    3)
    Clustered and it is a Prod environment.
    Details:
    UI cluster has 5 servers. There are 4 jvms in each server. Altogether there are 20 jvms in UI cluster
    Recon cluster has 3 servers. There are 4 jvms in each server. Altogether there are 12 jvms in Recon cluster
    regards,
    Thiago Leoncio Guimaraes

    A common practice for handling this type of fail-over is to ensure that the main environment's domain name, server names, store, transaction logs (default store), and JMS configuration all all the same in the contigency environment (basically, differences, if any, are confined to things like URLs and Data Source configuration of DB location). Recovery is accomplished in the fail-over environment by copying over each server's default file store, as well as its JDBC store backing tables, prior to booting the fail-over servers.
    Transaction logs don't need to be copied over if you don't use XA (JTA) in your applications...

  • WLS 7.0 SP2 Cluster deployment problems

    I am having problems deploying our application to a weblogic cluster. Environment is
    windows 2000/XP and weblogic 7.0 SP2.
    Here's a simplified version of the cluster.
    I have 2 managed servers that are part of the cluster.I have defined the managed server
    configuration in the admin server's config.xml as below.
    <Server Cluster="myCluster" ExpectedToRun="false" ListenPort="7771"
    Machine="machine1" Name="Server1" ServerVersion="7.0.2.0"
    WeblogicPluginEnabled="false" XMLEntityCache="XMLCacheMBean_Server1">
    <COM Name="Server1"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="Server1"/>
    <JTAMigratableTarget Cluster="myCluster" Name="Server1" UserPreferred
    er="Server1"/>
    <JTARecoveryService Name="Server1"/>
    <KernelDebug Name="Server1"/>
    <Log Name="Server1"/>
    <SSL Enabled="false" ListenPort="7772" Name="Server1"/>
    <ServerDebug Name="Server1"/>
    <ServerStart Name="Server1"/>
    <WebServer Name="Server1"/>
    </Server>
    <Server Cluster="myCluster" ExpectedToRun="false" ListenPort="7771"
    Machine="machine2" Name="Server2" ServerVersion="7.0.2.0"
    WeblogicPluginEnabled="false" XMLEntityCache="XMLCacheMBean_Server2">
    <COM Name="Server2"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="Server2"/>
    <JTAMigratableTarget Cluster="myCluster" Name="Server2" UserPreferred
    er="Server2"/>
    <JTARecoveryService Name="Server2"/>
    <KernelDebug Name="Server2"/>
    <Log Name="Server2"/>
    <SSL Enabled="false" ListenPort="7772" Name="Server2"/>
    <ServerDebug Name="Server2"/>
    <ServerStart Name="Server2"/>
    <WebServer Name="Server2"/>
    </Server>
    <Server AcceptBacklog="50" HelpPageURL="c:/public/as"
    InstrumentStackTraceEnabled="true"
    JDBCLogFileName="myserver\jdbc.log" JDBCLoggingEnabled="false"
    ListenPort="7770" LogRemoteExceptionsEnabled="true"
    LoginTimeout="1000" Machine="MyMachine" Name="myserver"
    NativeIOEnabled="false" ReverseDNSAllowed="false"
    ServerVersion="7.0.2.0" StdoutDebugEnabled="true"
    StdoutEnabled="true" StdoutSeverityLevel="32"
    SystemPassword="{3DES}2LwBLCayHcc="
    ThreadPoolPercentSocketReaders="99" TunnelingClientPingSecs="45"
    TunnelingClientTimeoutSecs="40" TunnelingEnabled="false"
    WorkspaceShowUserKeysOnly="false"
    XMLEntityCache="XMLCacheMBean_myserver" XMLRegistry="company XMLRegist
    <COM Name="myserver"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="myserver"/>
    <JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="
    rver"/>
    <JTARecoveryService Name="myserver"/>
    <KernelDebug Name="myserver"/>
    <Log FileMinSize="4096" FileName="myserver\company.log"
    FileTimeSpan="24" Name="myserver"
    NumberOfFilesLimited="true" RotationType="bySize"/>
    <SSL ListenPort="7775" Name="myserver"/>
    <ServerDebug Name="myserver"/>
    <ServerStart Name="myserver"/>
    <WebServer DefaultWebApp="go" LogFileName="myserver\access.log"
    LoggingEnabled="true" Name="myserver" Targets="myserver"/>
    </Server>
    <ShutdownClass ClassName="company.appserver.weblogic.companyStartup"
    DeploymentOrder="600" Name="companyShutdown2"
    Targets="myCluster,Server1,Server2,myserver"/>
    <ShutdownClass
    ClassName="company.appserver.weblogic.WLTaskManagerInit"
    DeploymentOrder="675" Name="TaskManagerShutdown" Targets="Server2"/>
    <StartupClass ClassName="company.appserver.weblogic.ContextHandler"
    DeploymentOrder="105" FailureIsFatal="true"
    Name="ContextHandlerStartup1" Targets="myserver"/>
    <XMLEntityCache Name="XMLCacheMBean"/>
    <XMLEntityCache Name="XMLCacheMBean_Server1"/>
    <XMLEntityCache Name="XMLCacheMBean_Server2"/>
    <XMLEntityCache Name="XMLCacheMBean_myserver"/>
    <XMLRegistry
    DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactory
    Name="company XMLRegistry"
    SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl" Transf
    rFactory="org.apache.xalan.processor.TransformerFactoryImpl"/>
    /Domain>
    The managed server config.xml looks like below.
    $ cat config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!--Last updated on: Fri Nov 12 15:46:28 CET 2004, If your domain is active, ple
    ase do not edit the config.xml file. Any changes made to that file while the dom
    ain is active will not have any effect on the domain's configuration and are lik
    ely to be lost. If your domain is inactive, you may edit this file with an XML e
    ditor. If you do so, please refer to the BEA Weblogic Server Configuration Refer
    ence documentation available from http://edocs.bea.com/wls/docs70/config_xml.
    In general, we recommend that changes to your configuration file be made through
    the Administration Console.-->
    <Domain ConfigurationVersion="7.0.2.0" Name="company">
    <Application Deployed="true" Name="AGENTMANAGER"
    Path=".\deployments\activity" TwoPhase="false">
    <EJBComponent DeploymentOrder="20" Name="AGENTMANAGER"
    Targets="Server2" URI="AGENTMANAGER.jar"/>
    </Application>
    <Application Deployed="true" Name="MDBERT1"
    Path=".\deployments\service" TwoPhase="false">
    <EJBComponent DeploymentOrder="46" Name="MDBERT1"
    Targets="Server2" URI="MDBERT1.jar"/>
    </Application>
    <Application Deployed="true" Name="TM" Path=".\deployments\service" TwoPhase
    ="false">
    <EJBComponent DeploymentOrder="15" Name="TM.jar"
    Targets="Server2" URI="TM.jar"/>
    </Application>
    </Application>
    <Application Deployed="true" Name="go" Path=".\applications"
    StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="go" Targets="Server2" URI="go"/>
    </Application>
    <Application Deployed="true" Name="im" Path=".\applications"
    StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="im" Targets="Server2" URI="im"/>
    </Application>
    <Application Deployed="true" Name="pmcl" Path=".\applications"
    StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="pmcl" Targets="Server2" URI="pmcl"/>
    </Application>
    <ApplicationManager Name="company"/>
    <CachingRealm ACLCacheEnable="true" ACLCacheSize="2000"
    ACLCacheTTLNegative="60" ACLCacheTTLPositive="60"
    AuthenticationCacheEnable="false" AuthenticationCacheSize="211"
    AuthenticationCacheTTLNegative="10"
    AuthenticationCacheTTLPositive="60" BasicRealm="companyRealm"
    CacheCaseSensitive="true" GroupCacheEnable="true"
    GroupCacheSize="100" GroupCacheTTLNegative="60"
    GroupCacheTTLPositive="60" GroupMembershipCacheTTL="17700"
    Name="companyCacheRealm" PermissionCacheEnable="true"
    PermissionCacheSize="211" PermissionCacheTTLNegative="10"
    PermissionCacheTTLPositive="60" UserCacheEnable="true"
    UserCacheSize="2000" UserCacheTTLNegative="60" UserCacheTTLPositive="60"
    />
    <CustomRealm Name="companyRealm" Password="{3DES}2LwBLCayHcc=" RealmClassName
    ="company.appserver.weblogic.WLRealmStub"/>
    <EmbeddedLDAP
    Credential="{3DES}VW4H4+7OUny8Er78dGhHbIqbB6w7l9btTnLbz4Cu1jE=" Name="Cy
    gent"/>
    <FileRealm Name="myFileRealm"/>
    <JDBCConnectionPool CapacityIncrement="2"
    DriverName="weblogic.jdbc.oci.Driver" InitialCapacity="5"
    MaxCapacity="100" Name="Geneva0"
    PreparedStatementCacheSize="100"
    Properties="user=admin;password=;server=LSUP1"
    Targets="Server2" URL="jdbc:weblogic:oracle"/>
    <JDBCConnectionPool CapacityIncrement="2"
    DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="5"
    MaxCapacity="100" Name="JMSDBConnectionPool"
    PreparedStatementCacheSize="100"
    Properties="user=admin;password=gent;url=jdbc:oracle:thin:@x.x.x.179:1521:SUP1;dll=ocijdbc8;dataSourceName=ejbPool;protocol=thin"
    Targets="Server2" URL="jdbc:oracle:thin:@x.x.x.x:1521:LSUP1"/>
    <JDBCConnectionPool CapacityIncrement="2"
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="5" MaxCapacity="100" Name="ejbPool"
    PreparedStatementCacheSize="100"
    Properties="user=company_admin;url=jdbc:oracle:thin:@10.28.138.179:1521:P
    MCLSUP1;password=company;dll=ocijdbc8;dataSourceName=ejbPool;protocol=thin"
    SupportsLocalTransaction="true" Targets="Server2,Server2" URL="jdbc:orac
    le:thin:@x.x.x.x:1521:LSUP1"/>
    <JDBCDataSource JNDIName="geneva.jdbc.GenevaNonTrans0"
    Name="GenevaNonTrans0" PoolName="Geneva0" Targets="Server2"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="true"
    JNDIName="geneva.jdbc.Geneva0" Name="Geneva0" PoolName="Geneva0" Targets
    ="Server2"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="false"
    JNDIName="authJtsDataSource" Name="authJtsDataSource"
    PoolName="ejbPool" Targets="Server2"/>
    <JMSConnectionFactory DefaultRedeliveryDelay="5000"
    DefaultTimeToDeliver="3000" JNDIName="company.ctm.QCFactory"
    Name="CTMQCFactory" Targets="Server2"
    UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
    <JMSConnectionFactory DefaultRedeliveryDelay="5000"
    DefaultTimeToDeliver="3000" JNDIName="company.im.QCFactory"
    Name="QCFactory" Targets="Server2"/>
    <JMSConnectionFactory DefaultRedeliveryDelay="5000"
    DefaultTimeToDeliver="3000" JNDIName="company.im.TCFactory"
    Name="TCFactory" Targets="Server2"/>
    <JMSJDBCStore ConnectionPool="JMSDBConnectionPool"
    Name="companyCTMJDBCStore" PrefixName="CTM"/>
    <JMSJDBCStore ConnectionPool="JMSDBConnectionPool"
    Name="companyJMSJDBCStore" PrefixName="IM"/>
    <JMSServer Name="CIM JMSServer-0" Store="companyJMSJDBCStore" Targets="Server
    2">
    <JMSQueue JNDIName="javax.jms.inRequestQueue" Name="inRequestQueue"/>
    <JMSQueue JNDIName="javax.jms.inResponseQueue" Name="inResponseQueue"/>
    <JMSQueue JNDIName="javax.jms.logQueue" Name="logQueue"/>
    <JMSQueue JNDIName="javax.jms.outRequestQueue" Name="outRequestQueue"/>
    <JMSQueue JNDIName="javax.jms.outResponseQueue" Name="outResponseQueue"/
    >
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="company.service.mg.impl.InboundMsgListener"
    Name="InboundRequestSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.inRequestQueue"
    MessagesMaximum="10" Name="InboundRequestSessionPool" Selector="
    TRUE"/>
    </JMSSessionPool>
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="company.service.mg.impl.InboundMsgListener"
    Name="InboundResponseSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.inResponseQueue"
    MessagesMaximum="10"
    Name="InboundResponseConnectionConsumer" Selector="TRUE"/>
    </JMSSessionPool>
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="pmcl.company.service.mg.impl.PmclOutboundMsgListener"
    Name="OutboundRequestSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.outRequestQueue"
    MessagesMaximum="10"
    Name="OutboundRequestConnectionPool" Selector="TRUE"/>
    </JMSSessionPool>
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="pmcl.company.service.mg.impl.PmclOutboundMsgListener"
    Name="OutboundResponseSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.outResponseQueue"
    MessagesMaximum="10"
    Name="OutboundResponseConnectionConsumer" Selector="TRUE"/>
    </JMSSessionPool>
    <JMSTopic JNDIName="javax.jms.CreateOfferTopic" Name="createOfferTopic"/
    >
    <JMSTopic JNDIName="javax.jms.CreateProductTopic" Name="createProductTop
    ic"/>
    </JMSServer>
    <JMSServer Name="JMSServer-0">
    <JMSQueue JNDIName="javax.jms.logQueue" Name="logQueue"/>
    </JMSServer>
    <JMSServer DeploymentOrder="1" Name="Task Manager Server-1"
    Store="companyCTMJDBCStore" Targets="Server2">
    <JMSQueue ErrorDestination="ERT1 Queue" JNDIName="activate_task"
    Name="AT1 Queue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="complete_process_flow" Name="CPF1 Queue" RedeliveryL
    imit="5"/>
    <JMSQueue ErrorDestination="ERT1 Queue" JNDIName="complete_task"
    Name="CT1 Queue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="error_task" Name="ERT1 Queue" RedeliveryLimit="1"/>
    <JMSQueue ErrorDestination="ERT1 Queue" JNDIName="escalate_task"
    Name="ET1 Queue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="recover_process_flow" Name="RPF1 Queue" RedeliveryLi
    mit="5"/>
    <JMSQueue JNDIName="terminate_process_flow" Name="TPF1 Queue" Redelivery
    Limit="5"/>
    <JMSQueue ErrorDestination="ERT1 Queue"
    JNDIName="terminate_task" Name="TT1 Queue" RedeliveryLimit="5"/>
    </JMSServer>
    <JTA Name="company" TimeoutSeconds="3600"/>
    <Log FileName="./logs/company.log" Name="company"/>
    <Machine Name="MyMachine">
    <NodeManager Name="MyMachine"/>
    </Machine>
    <PasswordPolicy MinimumPasswordLength="8" Name="mypasswordpolicy"/>
    <Realm CachingRealm="companyCacheRealm" FileRealm="myFileRealm" Name="myRealm
    "/>
    <SNMPAgent Name="company"/>
    <Security CompatibilityMode="true" Name="company"
    PasswordPolicy="mypasswordpolicy" Realm="myRealm" RealmSetup="true"/>
    <SecurityConfiguration Credential="{3DES}Osb3tCLDbyc="
    CredentialGenerated="false" Name="company"/>
    <Server HelpPageURL="c:/public/as" InstrumentStackTraceEnabled="true"
    JDBCLogFileName="Server2\jdbc.log" JDBCLoggingEnabled="false"
    ListenPort="7771" LogRemoteExceptionsEnabled="true"
    LoginTimeout="1000" Machine="MyMachine" Name="Server2"
    NativeIOEnabled="true" ReverseDNSAllowed="false"
    ServerVersion="7.0.2.0" StdoutDebugEnabled="true"
    StdoutEnabled="true" StdoutSeverityLevel="32"
    SystemPassword="{3DES}2LwBLCayHcc="
    ThreadPoolPercentSocketReaders="99" TunnelingClientPingSecs="45"
    TunnelingClientTimeoutSecs="40" TunnelingEnabled="false"
    WorkspaceShowUserKeysOnly="false"
    XMLEntityCache="XMLCacheMBean_Server2" XMLRegistry="company XMLRegistry">
    <COM Name="Server2"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="Server2"/>
    <JTAMigratableTarget Cluster="myCluster" Name="Server2" UserPreferredSer
    ver="Server2"/>
    <JTARecoveryService Name="Server2"/>
    <KernelDebug Name="Server2"/>
    <Log FileMinSize="4096" FileName="Server2\company.log"
    FileTimeSpan="24" Name="Server2"
    NumberOfFilesLimited="true" RotationType="bySize"/>
    <SSL ListenPort="7772" Name="Server2"/>
    <ServerDebug Name="Server2"/>
    <ServerStart Name="Server2"/>
    <WebServer DefaultWebApp="go" LogFileName="Server2\access.log"
    LoggingEnabled="true" Name="Server2" Targets="Server2"/>
    </Server>
    <ShutdownClass ClassName="company.appserver.weblogic.companyStartup"
    DeploymentOrder="200" Name="companyShutdown2" Targets="Server2"/>
    <ShutdownClass
    ClassName="company.appserver.weblogic.WLTaskManagerInit"
    DeploymentOrder="175" Name="TaskManagerShutdown" Targets="Server2"/>
    <StartupClass ClassName="company.appserver.weblogic.ContextHandler"
    DeploymentOrder="105" FailureIsFatal="true"
    Name="ContextHandlerStartup1" Targets="Server2"/>
    <StartupClass ClassName="company.appserver.weblogic.companyStartup"
    DeploymentOrder="100" FailureIsFatal="true"
    Name="companyStartup1" Targets="Server2,Server2"/>
    <StartupClass
    ClassName="company.appserver.weblogic.WLTaskManagerInit"
    DeploymentOrder="125" FailureIsFatal="true"
    Name="TaskManagerStartup" Targets="Server2"/>
    <XMLEntityCache Name="XMLCacheMBean"/>
    <XMLEntityCache Name="XMLCacheMBean_Server2"/>
    <XMLRegistry
    DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImp
    l"
    Name="company XMLRegistry"
    SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl" Transform
    erFactory="org.apache.xalan.processor.TransformerFactoryImpl"/>
    </Domain>
    I start the admin server first followed by one of the managed servers. The admin server
    starts fine. When I start the managed server 1, it is not deploying the application on the
    managed server and I am getting the following exception on the managed server.
    Setting custom initial context factory<Nov 25, 2004 11:54:44 PM CET> <Notice> <Management> <141053> <Application Polle
    r not started for production server.>
    <Nov 25, 2004 11:54:45 PM CET> <Notice> <Management> <141030> <Starting discover
    y of Managed Server... This feature is on by default, you may turn this off by p
    assing -Dweblogic.management.discover=false>
    <Nov 25, 2004 11:54:45 PM CET> <Notice> <WebLogicServer> <000354> <Thread "Liste
    nThread.Default" listening on port 7770>
    <Nov 25, 2004 11:55:06 PM CET> <Warning> <RJVM> <000519> <Unable to connect to a
    remote server on address x.x.x.x and port 7771 with protocol t3. The Exce
    ption is java.net.ConnectException: Connection refused: connect>
    <Nov 25, 2004 11:55:06 PM CET> <Warning> <Management> <141028> <Unable to locate
    Managed server Server2 on listen address x.x.x.223 listen port 7771. Ignore
    this message if the Managed server was shutdown intentionally. The Managed serv
    er will connect to the Admin server when it is re-started.>
    <Nov 25, 2004 11:55:08 PM CET> <Warning> <RJVM> <000519> <Unable to connect to a
    remote server on address x.x.x.222 and port 7771 with protocol t3. The Exce
    ption is java.net.ConnectException: Connection refused: connect>
    <Nov 25, 2004 11:55:08 PM CET> <Warning> <Management> <141028> <Unable to locate
    Managed server Server1 on listen address x.x.x.222 listen port 7771. Ignore
    this message if the Managed server was shutdown intentionally. The Managed serv
    er will connect to the Admin server when it is re-started.>
    <Nov 25, 2004 11:55:08 PM CET> <Notice> <WebLogicServer> <000329> <Started WebLo
    gic Admin Server "myserver" for domain "company" running in Production Mode>
    <Nov 25, 2004 11:55:09 PM CET> <Notice> <WebLogicServer> <000365> <Server state
    changed to RUNNING>
    <Nov 25, 2004 11:55:09 PM CET> <Notice> <WebLogicServer> <000360> <Server starte
    d in RUNNING mode>
    <Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
    server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
    ing;Ljava.lang.String;)
    javax.management.InstanceNotFoundException: company:Name=Server1,Type=Migratable
    Target
    javax.management.InstanceNotFoundException: company:Name=Server1,Type=MigratableT
    arget
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:144)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:268)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
    meImpl.java:288)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:821)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    >
    <Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
    server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
    ing;Ljava.lang.String;)
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=Migratable
    Target
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=MigratableT
    arget
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:144)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:268)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
    meImpl.java:288)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:821)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    >
    <Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
    server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
    ing;Ljava.lang.String;)
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=Migratable
    Target
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=MigratableT
    arget
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:144)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:268)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
    meImpl.java:288)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:821)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    >
    Can somebody help me find out why this problem is occuring..?

    I am having problems deploying our application to a weblogic cluster. Environment is
    windows 2000/XP and weblogic 7.0 SP2.
    Here's a simplified version of the cluster.
    I have 2 managed servers that are part of the cluster.I have defined the managed server
    configuration in the admin server's config.xml as below.
    <Server Cluster="myCluster" ExpectedToRun="false" ListenPort="7771"
    Machine="machine1" Name="Server1" ServerVersion="7.0.2.0"
    WeblogicPluginEnabled="false" XMLEntityCache="XMLCacheMBean_Server1">
    <COM Name="Server1"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="Server1"/>
    <JTAMigratableTarget Cluster="myCluster" Name="Server1" UserPreferred
    er="Server1"/>
    <JTARecoveryService Name="Server1"/>
    <KernelDebug Name="Server1"/>
    <Log Name="Server1"/>
    <SSL Enabled="false" ListenPort="7772" Name="Server1"/>
    <ServerDebug Name="Server1"/>
    <ServerStart Name="Server1"/>
    <WebServer Name="Server1"/>
    </Server>
    <Server Cluster="myCluster" ExpectedToRun="false" ListenPort="7771"
    Machine="machine2" Name="Server2" ServerVersion="7.0.2.0"
    WeblogicPluginEnabled="false" XMLEntityCache="XMLCacheMBean_Server2">
    <COM Name="Server2"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="Server2"/>
    <JTAMigratableTarget Cluster="myCluster" Name="Server2" UserPreferred
    er="Server2"/>
    <JTARecoveryService Name="Server2"/>
    <KernelDebug Name="Server2"/>
    <Log Name="Server2"/>
    <SSL Enabled="false" ListenPort="7772" Name="Server2"/>
    <ServerDebug Name="Server2"/>
    <ServerStart Name="Server2"/>
    <WebServer Name="Server2"/>
    </Server>
    <Server AcceptBacklog="50" HelpPageURL="c:/public/as"
    InstrumentStackTraceEnabled="true"
    JDBCLogFileName="myserver\jdbc.log" JDBCLoggingEnabled="false"
    ListenPort="7770" LogRemoteExceptionsEnabled="true"
    LoginTimeout="1000" Machine="MyMachine" Name="myserver"
    NativeIOEnabled="false" ReverseDNSAllowed="false"
    ServerVersion="7.0.2.0" StdoutDebugEnabled="true"
    StdoutEnabled="true" StdoutSeverityLevel="32"
    SystemPassword="{3DES}2LwBLCayHcc="
    ThreadPoolPercentSocketReaders="99" TunnelingClientPingSecs="45"
    TunnelingClientTimeoutSecs="40" TunnelingEnabled="false"
    WorkspaceShowUserKeysOnly="false"
    XMLEntityCache="XMLCacheMBean_myserver" XMLRegistry="company XMLRegist
    <COM Name="myserver"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="myserver"/>
    <JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="
    rver"/>
    <JTARecoveryService Name="myserver"/>
    <KernelDebug Name="myserver"/>
    <Log FileMinSize="4096" FileName="myserver\company.log"
    FileTimeSpan="24" Name="myserver"
    NumberOfFilesLimited="true" RotationType="bySize"/>
    <SSL ListenPort="7775" Name="myserver"/>
    <ServerDebug Name="myserver"/>
    <ServerStart Name="myserver"/>
    <WebServer DefaultWebApp="go" LogFileName="myserver\access.log"
    LoggingEnabled="true" Name="myserver" Targets="myserver"/>
    </Server>
    <ShutdownClass ClassName="company.appserver.weblogic.companyStartup"
    DeploymentOrder="600" Name="companyShutdown2"
    Targets="myCluster,Server1,Server2,myserver"/>
    <ShutdownClass
    ClassName="company.appserver.weblogic.WLTaskManagerInit"
    DeploymentOrder="675" Name="TaskManagerShutdown" Targets="Server2"/>
    <StartupClass ClassName="company.appserver.weblogic.ContextHandler"
    DeploymentOrder="105" FailureIsFatal="true"
    Name="ContextHandlerStartup1" Targets="myserver"/>
    <XMLEntityCache Name="XMLCacheMBean"/>
    <XMLEntityCache Name="XMLCacheMBean_Server1"/>
    <XMLEntityCache Name="XMLCacheMBean_Server2"/>
    <XMLEntityCache Name="XMLCacheMBean_myserver"/>
    <XMLRegistry
    DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactory
    Name="company XMLRegistry"
    SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl" Transf
    rFactory="org.apache.xalan.processor.TransformerFactoryImpl"/>
    /Domain>
    The managed server config.xml looks like below.
    $ cat config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!--Last updated on: Fri Nov 12 15:46:28 CET 2004, If your domain is active, ple
    ase do not edit the config.xml file. Any changes made to that file while the dom
    ain is active will not have any effect on the domain's configuration and are lik
    ely to be lost. If your domain is inactive, you may edit this file with an XML e
    ditor. If you do so, please refer to the BEA Weblogic Server Configuration Refer
    ence documentation available from http://edocs.bea.com/wls/docs70/config_xml.
    In general, we recommend that changes to your configuration file be made through
    the Administration Console.-->
    <Domain ConfigurationVersion="7.0.2.0" Name="company">
    <Application Deployed="true" Name="AGENTMANAGER"
    Path=".\deployments\activity" TwoPhase="false">
    <EJBComponent DeploymentOrder="20" Name="AGENTMANAGER"
    Targets="Server2" URI="AGENTMANAGER.jar"/>
    </Application>
    <Application Deployed="true" Name="MDBERT1"
    Path=".\deployments\service" TwoPhase="false">
    <EJBComponent DeploymentOrder="46" Name="MDBERT1"
    Targets="Server2" URI="MDBERT1.jar"/>
    </Application>
    <Application Deployed="true" Name="TM" Path=".\deployments\service" TwoPhase
    ="false">
    <EJBComponent DeploymentOrder="15" Name="TM.jar"
    Targets="Server2" URI="TM.jar"/>
    </Application>
    </Application>
    <Application Deployed="true" Name="go" Path=".\applications"
    StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="go" Targets="Server2" URI="go"/>
    </Application>
    <Application Deployed="true" Name="im" Path=".\applications"
    StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="im" Targets="Server2" URI="im"/>
    </Application>
    <Application Deployed="true" Name="pmcl" Path=".\applications"
    StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="pmcl" Targets="Server2" URI="pmcl"/>
    </Application>
    <ApplicationManager Name="company"/>
    <CachingRealm ACLCacheEnable="true" ACLCacheSize="2000"
    ACLCacheTTLNegative="60" ACLCacheTTLPositive="60"
    AuthenticationCacheEnable="false" AuthenticationCacheSize="211"
    AuthenticationCacheTTLNegative="10"
    AuthenticationCacheTTLPositive="60" BasicRealm="companyRealm"
    CacheCaseSensitive="true" GroupCacheEnable="true"
    GroupCacheSize="100" GroupCacheTTLNegative="60"
    GroupCacheTTLPositive="60" GroupMembershipCacheTTL="17700"
    Name="companyCacheRealm" PermissionCacheEnable="true"
    PermissionCacheSize="211" PermissionCacheTTLNegative="10"
    PermissionCacheTTLPositive="60" UserCacheEnable="true"
    UserCacheSize="2000" UserCacheTTLNegative="60" UserCacheTTLPositive="60"
    />
    <CustomRealm Name="companyRealm" Password="{3DES}2LwBLCayHcc=" RealmClassName
    ="company.appserver.weblogic.WLRealmStub"/>
    <EmbeddedLDAP
    Credential="{3DES}VW4H4+7OUny8Er78dGhHbIqbB6w7l9btTnLbz4Cu1jE=" Name="Cy
    gent"/>
    <FileRealm Name="myFileRealm"/>
    <JDBCConnectionPool CapacityIncrement="2"
    DriverName="weblogic.jdbc.oci.Driver" InitialCapacity="5"
    MaxCapacity="100" Name="Geneva0"
    PreparedStatementCacheSize="100"
    Properties="user=admin;password=;server=LSUP1"
    Targets="Server2" URL="jdbc:weblogic:oracle"/>
    <JDBCConnectionPool CapacityIncrement="2"
    DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="5"
    MaxCapacity="100" Name="JMSDBConnectionPool"
    PreparedStatementCacheSize="100"
    Properties="user=admin;password=gent;url=jdbc:oracle:thin:@x.x.x.179:1521:SUP1;dll=ocijdbc8;dataSourceName=ejbPool;protocol=thin"
    Targets="Server2" URL="jdbc:oracle:thin:@x.x.x.x:1521:LSUP1"/>
    <JDBCConnectionPool CapacityIncrement="2"
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="5" MaxCapacity="100" Name="ejbPool"
    PreparedStatementCacheSize="100"
    Properties="user=company_admin;url=jdbc:oracle:thin:@10.28.138.179:1521:P
    MCLSUP1;password=company;dll=ocijdbc8;dataSourceName=ejbPool;protocol=thin"
    SupportsLocalTransaction="true" Targets="Server2,Server2" URL="jdbc:orac
    le:thin:@x.x.x.x:1521:LSUP1"/>
    <JDBCDataSource JNDIName="geneva.jdbc.GenevaNonTrans0"
    Name="GenevaNonTrans0" PoolName="Geneva0" Targets="Server2"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="true"
    JNDIName="geneva.jdbc.Geneva0" Name="Geneva0" PoolName="Geneva0" Targets
    ="Server2"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="false"
    JNDIName="authJtsDataSource" Name="authJtsDataSource"
    PoolName="ejbPool" Targets="Server2"/>
    <JMSConnectionFactory DefaultRedeliveryDelay="5000"
    DefaultTimeToDeliver="3000" JNDIName="company.ctm.QCFactory"
    Name="CTMQCFactory" Targets="Server2"
    UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
    <JMSConnectionFactory DefaultRedeliveryDelay="5000"
    DefaultTimeToDeliver="3000" JNDIName="company.im.QCFactory"
    Name="QCFactory" Targets="Server2"/>
    <JMSConnectionFactory DefaultRedeliveryDelay="5000"
    DefaultTimeToDeliver="3000" JNDIName="company.im.TCFactory"
    Name="TCFactory" Targets="Server2"/>
    <JMSJDBCStore ConnectionPool="JMSDBConnectionPool"
    Name="companyCTMJDBCStore" PrefixName="CTM"/>
    <JMSJDBCStore ConnectionPool="JMSDBConnectionPool"
    Name="companyJMSJDBCStore" PrefixName="IM"/>
    <JMSServer Name="CIM JMSServer-0" Store="companyJMSJDBCStore" Targets="Server
    2">
    <JMSQueue JNDIName="javax.jms.inRequestQueue" Name="inRequestQueue"/>
    <JMSQueue JNDIName="javax.jms.inResponseQueue" Name="inResponseQueue"/>
    <JMSQueue JNDIName="javax.jms.logQueue" Name="logQueue"/>
    <JMSQueue JNDIName="javax.jms.outRequestQueue" Name="outRequestQueue"/>
    <JMSQueue JNDIName="javax.jms.outResponseQueue" Name="outResponseQueue"/
    >
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="company.service.mg.impl.InboundMsgListener"
    Name="InboundRequestSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.inRequestQueue"
    MessagesMaximum="10" Name="InboundRequestSessionPool" Selector="
    TRUE"/>
    </JMSSessionPool>
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="company.service.mg.impl.InboundMsgListener"
    Name="InboundResponseSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.inResponseQueue"
    MessagesMaximum="10"
    Name="InboundResponseConnectionConsumer" Selector="TRUE"/>
    </JMSSessionPool>
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="pmcl.company.service.mg.impl.PmclOutboundMsgListener"
    Name="OutboundRequestSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.outRequestQueue"
    MessagesMaximum="10"
    Name="OutboundRequestConnectionPool" Selector="TRUE"/>
    </JMSSessionPool>
    <JMSSessionPool ConnectionFactory="company.im.QCFactory"
    ListenerClass="pmcl.company.service.mg.impl.PmclOutboundMsgListener"
    Name="OutboundResponseSessionPool" SessionsMaximum="5">
    <JMSConnectionConsumer
    Destination="javax.jms.outResponseQueue"
    MessagesMaximum="10"
    Name="OutboundResponseConnectionConsumer" Selector="TRUE"/>
    </JMSSessionPool>
    <JMSTopic JNDIName="javax.jms.CreateOfferTopic" Name="createOfferTopic"/
    >
    <JMSTopic JNDIName="javax.jms.CreateProductTopic" Name="createProductTop
    ic"/>
    </JMSServer>
    <JMSServer Name="JMSServer-0">
    <JMSQueue JNDIName="javax.jms.logQueue" Name="logQueue"/>
    </JMSServer>
    <JMSServer DeploymentOrder="1" Name="Task Manager Server-1"
    Store="companyCTMJDBCStore" Targets="Server2">
    <JMSQueue ErrorDestination="ERT1 Queue" JNDIName="activate_task"
    Name="AT1 Queue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="complete_process_flow" Name="CPF1 Queue" RedeliveryL
    imit="5"/>
    <JMSQueue ErrorDestination="ERT1 Queue" JNDIName="complete_task"
    Name="CT1 Queue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="error_task" Name="ERT1 Queue" RedeliveryLimit="1"/>
    <JMSQueue ErrorDestination="ERT1 Queue" JNDIName="escalate_task"
    Name="ET1 Queue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="recover_process_flow" Name="RPF1 Queue" RedeliveryLi
    mit="5"/>
    <JMSQueue JNDIName="terminate_process_flow" Name="TPF1 Queue" Redelivery
    Limit="5"/>
    <JMSQueue ErrorDestination="ERT1 Queue"
    JNDIName="terminate_task" Name="TT1 Queue" RedeliveryLimit="5"/>
    </JMSServer>
    <JTA Name="company" TimeoutSeconds="3600"/>
    <Log FileName="./logs/company.log" Name="company"/>
    <Machine Name="MyMachine">
    <NodeManager Name="MyMachine"/>
    </Machine>
    <PasswordPolicy MinimumPasswordLength="8" Name="mypasswordpolicy"/>
    <Realm CachingRealm="companyCacheRealm" FileRealm="myFileRealm" Name="myRealm
    "/>
    <SNMPAgent Name="company"/>
    <Security CompatibilityMode="true" Name="company"
    PasswordPolicy="mypasswordpolicy" Realm="myRealm" RealmSetup="true"/>
    <SecurityConfiguration Credential="{3DES}Osb3tCLDbyc="
    CredentialGenerated="false" Name="company"/>
    <Server HelpPageURL="c:/public/as" InstrumentStackTraceEnabled="true"
    JDBCLogFileName="Server2\jdbc.log" JDBCLoggingEnabled="false"
    ListenPort="7771" LogRemoteExceptionsEnabled="true"
    LoginTimeout="1000" Machine="MyMachine" Name="Server2"
    NativeIOEnabled="true" ReverseDNSAllowed="false"
    ServerVersion="7.0.2.0" StdoutDebugEnabled="true"
    StdoutEnabled="true" StdoutSeverityLevel="32"
    SystemPassword="{3DES}2LwBLCayHcc="
    ThreadPoolPercentSocketReaders="99" TunnelingClientPingSecs="45"
    TunnelingClientTimeoutSecs="40" TunnelingEnabled="false"
    WorkspaceShowUserKeysOnly="false"
    XMLEntityCache="XMLCacheMBean_Server2" XMLRegistry="company XMLRegistry">
    <COM Name="Server2"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="Server2"/>
    <JTAMigratableTarget Cluster="myCluster" Name="Server2" UserPreferredSer
    ver="Server2"/>
    <JTARecoveryService Name="Server2"/>
    <KernelDebug Name="Server2"/>
    <Log FileMinSize="4096" FileName="Server2\company.log"
    FileTimeSpan="24" Name="Server2"
    NumberOfFilesLimited="true" RotationType="bySize"/>
    <SSL ListenPort="7772" Name="Server2"/>
    <ServerDebug Name="Server2"/>
    <ServerStart Name="Server2"/>
    <WebServer DefaultWebApp="go" LogFileName="Server2\access.log"
    LoggingEnabled="true" Name="Server2" Targets="Server2"/>
    </Server>
    <ShutdownClass ClassName="company.appserver.weblogic.companyStartup"
    DeploymentOrder="200" Name="companyShutdown2" Targets="Server2"/>
    <ShutdownClass
    ClassName="company.appserver.weblogic.WLTaskManagerInit"
    DeploymentOrder="175" Name="TaskManagerShutdown" Targets="Server2"/>
    <StartupClass ClassName="company.appserver.weblogic.ContextHandler"
    DeploymentOrder="105" FailureIsFatal="true"
    Name="ContextHandlerStartup1" Targets="Server2"/>
    <StartupClass ClassName="company.appserver.weblogic.companyStartup"
    DeploymentOrder="100" FailureIsFatal="true"
    Name="companyStartup1" Targets="Server2,Server2"/>
    <StartupClass
    ClassName="company.appserver.weblogic.WLTaskManagerInit"
    DeploymentOrder="125" FailureIsFatal="true"
    Name="TaskManagerStartup" Targets="Server2"/>
    <XMLEntityCache Name="XMLCacheMBean"/>
    <XMLEntityCache Name="XMLCacheMBean_Server2"/>
    <XMLRegistry
    DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImp
    l"
    Name="company XMLRegistry"
    SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl" Transform
    erFactory="org.apache.xalan.processor.TransformerFactoryImpl"/>
    </Domain>
    I start the admin server first followed by one of the managed servers. The admin server
    starts fine. When I start the managed server 1, it is not deploying the application on the
    managed server and I am getting the following exception on the managed server.
    Setting custom initial context factory<Nov 25, 2004 11:54:44 PM CET> <Notice> <Management> <141053> <Application Polle
    r not started for production server.>
    <Nov 25, 2004 11:54:45 PM CET> <Notice> <Management> <141030> <Starting discover
    y of Managed Server... This feature is on by default, you may turn this off by p
    assing -Dweblogic.management.discover=false>
    <Nov 25, 2004 11:54:45 PM CET> <Notice> <WebLogicServer> <000354> <Thread "Liste
    nThread.Default" listening on port 7770>
    <Nov 25, 2004 11:55:06 PM CET> <Warning> <RJVM> <000519> <Unable to connect to a
    remote server on address x.x.x.x and port 7771 with protocol t3. The Exce
    ption is java.net.ConnectException: Connection refused: connect>
    <Nov 25, 2004 11:55:06 PM CET> <Warning> <Management> <141028> <Unable to locate
    Managed server Server2 on listen address x.x.x.223 listen port 7771. Ignore
    this message if the Managed server was shutdown intentionally. The Managed serv
    er will connect to the Admin server when it is re-started.>
    <Nov 25, 2004 11:55:08 PM CET> <Warning> <RJVM> <000519> <Unable to connect to a
    remote server on address x.x.x.222 and port 7771 with protocol t3. The Exce
    ption is java.net.ConnectException: Connection refused: connect>
    <Nov 25, 2004 11:55:08 PM CET> <Warning> <Management> <141028> <Unable to locate
    Managed server Server1 on listen address x.x.x.222 listen port 7771. Ignore
    this message if the Managed server was shutdown intentionally. The Managed serv
    er will connect to the Admin server when it is re-started.>
    <Nov 25, 2004 11:55:08 PM CET> <Notice> <WebLogicServer> <000329> <Started WebLo
    gic Admin Server "myserver" for domain "company" running in Production Mode>
    <Nov 25, 2004 11:55:09 PM CET> <Notice> <WebLogicServer> <000365> <Server state
    changed to RUNNING>
    <Nov 25, 2004 11:55:09 PM CET> <Notice> <WebLogicServer> <000360> <Server starte
    d in RUNNING mode>
    <Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
    server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
    ing;Ljava.lang.String;)
    javax.management.InstanceNotFoundException: company:Name=Server1,Type=Migratable
    Target
    javax.management.InstanceNotFoundException: company:Name=Server1,Type=MigratableT
    arget
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:144)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:268)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
    meImpl.java:288)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:821)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    >
    <Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
    server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
    ing;Ljava.lang.String;)
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=Migratable
    Target
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=MigratableT
    arget
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:144)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:268)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
    meImpl.java:288)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:821)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    >
    <Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
    server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
    ing;Ljava.lang.String;)
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=Migratable
    Target
    javax.management.InstanceNotFoundException: company:Name=Server2,Type=MigratableT
    arget
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:144)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
    a:268)
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
    meImpl.java:288)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:821)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    >
    Can somebody help me find out why this problem is occuring..?

  • Question on sql cluster failover behaviour

    Hi Experts,
    I have a doubt on SQL Cluster.
    In SQL cluster, If we MOVE the group or failover the group to another node what happens to the user connections(say 100 conn's) and ongoing open transactions during failover?
    Will all connections gets disconnected and open transactions gets rollbacked or the connections and txns will be moved to other node?
    Could anyone shed some insight on this?
    Thank you.

    All connections get disconnected an ongoing transactions have to be rolled back. Its like restarting the service, just on the other node.
    Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

Maybe you are looking for

  • Problem with group messaging?

    A couple of days ago I started receiving only some of the texts that the people in the group message were sending. I receive some messages, but not others. Sometimes the ones that I hadn't received are received hours after the messages were sent. Ple

  • Group Mail Management on Wiki

    We have a Wiki setup for one of our groups. It so happens this is also a mail group and we have enabled mail on the Wiki/Blog page. Mail that comes in for the group (for example: "[email protected]") gets posted on the mail for the Wiki. This is actu

  • Photoshop crashing, Lightroom not opening, help to fix please?

    I paid for and downloaded Creative cloud last week, and have installed Photoshop, Lightroom and Bridge. When I went to use these programs I found that Bridge works, Lightroom won't even open, and Photoshop tends to crash after 3-5seconds upon opening

  • XML Flight Finder Sample - Again

    Oracle XSQL Servlet Page Processor 1.0.0.0 (Production) XSQL-007: Cannot acquire a database connection to process page. Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=135290880)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4)))) i stil

  • Azure AD in MSDN Subscription

    I have an issue with an imported AD into an MSDN account not being able to be used for things, for example, like the source for VS Online users or subscription co-admins. I *assume* this is because when the Azure account was provisioned, it wasn't ti