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

Similar Messages

Migrating JMS - Server Crash

          I was looking up the documentation for JMS Migratable services and it looks like
          the migration is a process initiated manually rather than automatic in 8.1.
          Does this mean that if we have a server that was the target for a migratable service,
          the messages associated with that server are lost when it crashes (Unless i have
          a persistence store associated). Can i assume that the above is true?
          TIA
          Raj


Raj wrote:
          > I was looking up the documentation for JMS Migratable services and it looks like
          > the migration is a process initiated manually rather than automatic in 8.1.
          > Does this mean that if we have a server that was the target for a migratable service,
          > the messages associated with that server are lost when it crashes (Unless i have
          > a persistence store associated). Can i assume that the above is true?
          >
          Yes. This is the fundamental trade-off between using
          non-persistent and persistent messages. If you need
          higher availability, I suggest reading the JMS Performance
          Guide white-paper for ideas.
          FYI: One of my co-workers is working on a migration
          white-paper - it should show up on dev2dev sometime
          in the near future (no clue exactly when).
          Look for "white-papers" here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          > TIA
          > Raj
          >

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

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.

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.

MDBs failed to connect to remote JMS server

Hi,
          We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
          In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
          <weblogic-enterprise-bean>
               <ejb-name>MyBean</ejb-name>
               <message-driven-descriptor>
                    <destination-jndi-name>MyTopic</destination-jndi-name>
          <provider-url>t3://myhost:19009,myhost:19011</provider-url>
          <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
          di-name>
               </message-driven-descriptor>
          </weblogic-enterprise-bean>
          When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
          (t3://myhost:19009) but got the same result.
          When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
          I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
          Any help would be greatly appreciated.
          Thanks,
          Thao

I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?).                    I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
          >>> Could you elaborate on the known problem?
          9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
          >>> What else I can try?
          Beyond contacting customer support, I'm not sure.
          Tom

Best way to determine if JMS server is alive in a cluster

Can anyone give me an idea on the best way to find out if a JMS server
          in a cluster
          has failed so I can signal migration to another server in the cluster.
          Thanks Larry
          PS weblogic 7.0 sp1


Hallo Larry,
          you can go via JMX and retrieve the according RuntimeMBeans in order to
          check the health state of the
          JMSServer resp. the server hosting the JMSServer. If they are not available
          or failed you can trigger the
          migration. At least that's the way I'm doing it...
          try
          JMSServerMBean jmsServer = null;
          ServerMBean candidateServer = null;
          MigratableTargetMBean migratableTarget = null;
          * Retrieve all JMSServer defined for the current domain
          Set jmsServerSet = home.getMBeansByType("JMSServer", domainName);
          Object[] jmsServers = jmsServerSet.toArray();
          * Just the first one is picked assuming there is only one defined
          * within the active FHO domain
          if(jmsServers != null && jmsServers.length > 0)
          jmsServer = (JMSServerMBean) jmsServers[0];
          if(s_logger.isDebugEnabled())
          s_logger.debug("JMSServer: " + jmsServer.getName());
          * A JMSServer can only be associated with a single target,
          * thus pick again the first from the list.
          TargetMBean[] targets = jmsServer.getTargets();
          if(targets != null && targets.length > 0)
          boolean hostingServerRunning = false;
          boolean candidateServerRunning = false;
          * Check whether the JMSServer is really associated with
          * a migratable target. Otherwise the migration must be canceled
          * since it cannot be performed!
          if(targets[0] instanceof MigratableTargetMBean)
          migratableTarget = (MigratableTargetMBean) targets[0];
          * Retrieve all available candidates and select a running instance
          * if any. First check for constrained candidate servers, than for
          * all candidate servers
          ServerMBean[] candidates =
          migratableTarget.getConstrainedCandidateServers();
          if(candidates == null || candidates.length == 0)
          candidates = migratableTarget.getAllCandidateServers();
          if(candidates != null && candidates.length > 0)
          ServerMBean hostingServer = migratableTarget.getHostingServer();
          boolean gotHostingServer = false;
          boolean gotCandidateServer = false;
          boolean runningInstance = false;
          * Loop over all candidates as long as hosting server and candidate
          * server are visited and there running state has been determined
          for(int i=0; i< candidates.length; i++)
          ServerRuntimeMBean serverRuntime = null;
          * Retrieve the current state from the according runtime MBean
          * if available
          try
          serverRuntime = (ServerRuntimeMBean) home.getMBean(new
          WebLogicObjectName(candidates.getName(), "ServerRuntime", domainName,
          candidates[i].getName()));
          runningInstance =
          serverRuntime.getState().equalsIgnoreCase(ServerRuntimeMBean.RUNNING);
          catch(InstanceNotFoundException inf)
          * When a server instance is not available, an InstanceNotFoundException will
          be raised
          * by WLS, which can be ignored
          if(hostingServer != null && hostingServer.equals(candidates[i]))
          hostingServerRunning = runningInstance;
          gotHostingServer = true;
          else
          * A running candidate server will be prefered, thus only if no running
          * instance can be detected, another instance is selected
          if(!gotCandidateServer)
          candidateServerRunning = runningInstance;
          candidateServer = candidates[i];
          gotCandidateServer = runningInstance;
          if(gotCandidateServer && gotHostingServer)
          break;
          if(s_logger.isDebugEnabled())
          s_logger.debug("Migratable Target: " + migratableTarget.getName());
          s_logger.debug("Candidate Server: " + candidateServer.getName());
          else
          throw new Exception("JMSServer not deployed on a migratable target!");
          * Retrieve the migration service coordinator for the active domain assuming
          * there exists only one and invoke the migration later on
          MigratableServiceCoordinatorRuntimeMBean coordinator = null;
          Set coordinatorSet =
          home.getMBeansByType("MigratableServiceCoordinatorRuntime", domainName);
          Object[] coordinators = coordinatorSet.toArray();
          if(coordinators.length > 0)
          coordinator = (MigratableServiceCoordinatorRuntimeMBean) coordinators[0];
          if(enforceMigrationOnInstancesDown)
          coordinator.migrate(migratableTarget, candidateServer, hostingServerRunning,
          candidateServerRunning);
          else
          coordinator.migrate(migratableTarget, candidateServer);
          s_logger.info("Migration of JMSServer from node "
          + migratableTarget.getName()
          + " to node "
          + candidateServer.getName()
          + " has been started");
          else
          throw new Exception("MigrationServiceCoordinator cannot be retrieved");
          catch(Exception e)
          s_logger.error("Could not migrate JMSServer", e);
          Regards,
          CK
          "Larry Presswood" <[email protected]> schrieb im Newsbeitrag
          news:[email protected]...
          > Can anyone give me an idea on the best way to find out if a JMS server
          > in a cluster
          > has failed so I can signal migration to another server in the cluster.
          >
          > Thanks Larry
          >
          > PS weblogic 7.0 sp1
          >

JMS Server deployed to cluster of servers

Hey guys,
I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
I read the following passage in the weblogic documents:
Obtain a Clustered JMS Licence
In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
If i'm just building a model does this apply to me?
Thanks

continued reading to clarify. Problem solved, thanks for looking

Foreign JMS Server Limitation

Hi all,
          Iam facing a limitation with Foreign JMS server.
          We are tyring to migrate from Message Bridge to Foreign JMS server.
          Our current setup is
          We have 3 MQ queues which are bridged to one JMS destination(queue).The MDB is consuming messages from the weblogic queue.
          If we want to replace this setup with Foreign JMS server the MDB can connect to only one MQ queue.
          We want the MDB to consume messages from all the 3 queues.
          How can we acheive this ?
          Thanks,
          Rabbani

U should take my reply with a grain of salt because I'm pretty new at this stuff but I don't think it's within an MDBs design to listen to more than one queue/topic so therefore you'll have to create additional MDBs that either listen to each foreign queue individually and do whatever your single MDB is doing with the data now or create the n MDBS (where n = number of foreign queues currently bridgin to the one) that then publish to an intermediate topic which your existing MDB can listen to.
          Hope this helps, figure if I'm going to be pounding the boards with questions I should try to contribute where I can ;)
          And also, if you do setup the foreign JMS provider feel free to take a look at my topic and provide your experience if you think it will help :D

Foreign JMS server connection issue.

Hi All,
We are migrating a JMS application from websphere 6.1 to weblogic 10.3. The message queue resides in a TIBCO EMS server.
We are trying to configure the foreign JMS server through JMS Module in the admin console. We are getting the following error will deploying the application.
+<May 4, 2009 12:32:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TxnMessageSubscriber is unable to connect to the JMS destination: weblogic.bbmdb-txn.jms/system+
module-0-jms.xml. The Error was:
Can not get distribute destination information. The destination JNDI name is weblogic.bbmdb-txn.jms/systemmodule-0-jms.xml, the provider URL is null>
we have provided the connection URL in "JNDI Connection URL" column in the foreign server setup page.
Is there any other thing that need to be configured?

I m facing the same problem, we are using Weblogic Server 10.3.
We have defined a cluster on one Weblogic server and have created one managed server in the cluster machine and the other managed server in another machine.
We are using Foreign JMS and I m getting the error as follow:
####<Jun 19, 2009 3:30:53 PM IST> <Warning> <EJB> <iflexpkw513> <Managed1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245405653881> <BEA-010061> <The Message-Driven EJB: TestJMSALSB is unable to connect to the JMS destination: fcssi/FCSSI. The Error was:
Can not get distribute destination information. The destination JNDI name is fcssi/FCSSI, the provider URL is null>
Not able to understand what is the problem here...
ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar id="ejb-jar_ID">
<enterprise-beans>
<message-driven>
<ejb-name>TestJMSALSB</ejb-name>
<ejb-class>samplemdb.TestJMSALSB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination id="MessageDrivenDestination_1169302343246">
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>TestJMSALSB</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>fcssi/FCSSI</destination-jndi-name>
<connection-factory-jndi-name>iflex/fcssiQCF</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Can anyone provide some help on this.....

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

Oracle 10g R2 jms server

Hi All
i want to know , how can create more than one jms server, because our application now run on the weblogic 8.1 and 9.1 as well,for weblogic configaration we configee more than one jms server,what i really want to know how i can do that using oracle ...
and also i like to know what is good information source about the weblogic 8.1 to oracle migration ...
Thankx
Asnaka Priyanjith

The only way to start more than one JMS server is to start up multiple OC4J JVMs, each with its own JMS server.

JMS Server targeted to Server cluster

Hi , Can JMS Server be targeted to Server Cluster? Are there any
          architectural best practices for this?

Thanks Tom.
          <Tom Barnes> wrote in message news:[email protected]...
          There's no underlying machinery (code) that supports targeting a JMS server
          to a cluster.
          The targeting problem can actually get fairly involved - for a variety of
          reasons, I tend to recommend the following cookie cutter approach.
          This is a cut-and-paste from my notes:
          (1) Create a custom WL store on each server, and target it to a migratable
          target (most of the time you can use the default migratable target that each
          server provides).
          (2) Target the JMS servers to a migratable target each, the same MT as the
          store (don't worry, the JMS server won't wander to a different server
          unless you configure the MT to allow this!)
          (3) Target jms configuration system modules to the cluster (that's it! - not
          to anything else)
          (4) Create one subdeployment per module (and only one), populate the
          subdeployment only with JMS servers from step (2) above.
          (5) When targeting destinations always use advanced targeting to target
          destinations to the subdeployment from above - not the 'default target'.
          If you have both non-distributed and distributed destinations, use two
          different JMS modules. (The idea is to keep things simple to understand -
          each module should yield the same targeting solution for all of its
          component resources. Default targetting can be problematic - it is far too
          easy for destination members to end up on JMS servers that you don't want
          them on.).
          (6) When targeting a CF you have two options (A) use advanced targeting to
          target it to the subdeployment (for access by applications that are remote
          to the cluster) or (B) don't target it all (this will cause it to use the
          module target, which if you recall, we just set to the cluster, (for access
          by applications that run on a server within the cluster). The choice
          actually depends on how you plan to use the CF - use (B) for apps running on
          servers within the cluster, and (A) for apps running remote to the cluster.
          See the otherwise-largely-outdated JMS Performance Guide for the reasoning.
          It may be that you don't have to use migratable targets, as you may not have
          a use for "migration" at the moment - but it'll help in the future if you
          ever plan to use the migration features.
          Tom

JMS Server Target & Deploy error

          Hi All,
          I am getting the error while creating the JMS Server.
          I have created the JMS Server and on Target and Deploy tab,when I select the server
          name as target and hit the Apply button, I get the following error
          An unexpected error occurred while setting Target to mydomain:Name=myserver(migratable),Type=MigratableTarget.
          what could be the reason?
          Thanks
          WD


It still seems like it is your app that is throwing the exception.
          If you post the full log message, not just the excerpted text,
          the problem might be self evident.
          WD wrote:
          > The applications code is fine. With the same ear file,I am getting this error
          > intermittently. My suspicions is that sometimes when I redeploy the same application(without
          > anything changed), wls does not deploy it properly. Because when I was getting
          > this error,I just undeployed and deployed the app and it worked.
          > Have you seen this kind of behavior with wls?
          >
          > Thanks
          > WD
          >
          >
          >
          > Tom Barnes <[email protected].bea.com>
          > wrote:
          >
          >>It is unusual not to have a full stack trace - particularly
          >>for application generated exceptions. My first
          >>suspicions is that your app is creating a producer
          >>without specifying a destination (a non-pinned producer),
          >>and then attempting to send a message without specifying
          >>a destination.
          >>
          >>WD wrote:
          >>
          >>>The only log message I have is the one I posted earlier. It is from
          >>
          >>the log file.
          >>
          >>>
          >>>
          >>>Tom Barnes <[email protected].bea.com>
          >>>wrote:
          >>>
          >>>
          >>>>OK. For this new exception, do you have the full
          >>>>log message/stack trace?
          >>>>
          >>>>WD wrote:
          >>>>
          >>>>
          >>>>
          >>>>>I just left the app alone for the weekend and when I tried to do it
          >>>>
          >>>>again today,it
          >>>>
          >>>>
          >>>>>just worked. I do not know what was wrong with it on friday.
          >>>>>
          >>>>>But now I am running into another weird error. I have deployed my
          >>
          >>application
          >>
          >>>>>and it works fine and MyMDB also works fine. But sometimes I am getting
          >>>>
          >>>>the following
          >>>>
          >>>>
          >>>>>error. It is happening very intermittently.
          >>>>>
          >>>>>Exception in MyMDB.onMessage()Must provide destination
          >>>>>
          >>>>>Thanks
          >>>>>WD
          >>>>>
          >>>>>
          >>>>>Tom Barnes <[email protected].bea.com>
          >>>>>wrote:
          >>>>>
          >>>>>
          >>>>>
          >>>>>>Do you have the full log message/stack trace?
          >>>>>>
          >>>>>>WD wrote:
          >>>>>>
          >>>>>>
          >>>>>>
          >>>>>>
          >>>>>>>Hi All,
          >>>>>>>I am getting the error while creating the JMS Server.
          >>>>>>>I have created the JMS Server and on Target and Deploy tab,when
          >>
          >>I
          >>
          >>>>select
          >>>>
          >>>>
          >>>>>>the server
          >>>>>>
          >>>>>>
          >>>>>>
          >>>>>>>name as target and hit the Apply button, I get the following error
          >>>>>>>
          >>>>>>>An unexpected error occurred while setting Target to mydomain:Name=myserver(migratable),Type=MigratableTarget.
          >>>>>>>
          >>>>>>>what could be the reason?
          >>>>>>>
          >>>>>>>Thanks
          >>>>>>>WD
          >>>>>>>
          >>>>>>>
          >>>>>>
          >

Weblogic Service Migration - JMS Servers and JTA

We are having 2 node managed server Custer - active- active configuration. We are planning to use Weblogic Service Migration to migrate JMS servers and JTA in case of Failure to the available node in the cluster.
===> There is a problem in node1; Due to the failure of node1, JMS servers and JTA do get migrated to Node2.
===> Problem in node 1 is resolved and is available.
===> How to revert the migrated JMS servers and JTA back to node 1?
Thanks

If I have a 2-node cluster, that means I have to take an outage ? There is no elegant solution to this ?
Thank you !

Migratable JMS server

Similar Messages

Maybe you are looking for