JMS Server and Service Migration....!

Hi,
          I am working on Weblogic 9.1 and JMS. I was reading through the weblogic 9.1 documentation and found that it supports Server Migration and Service Migration both manually and automatically to handle failover. Is that true? Can anyone give more insight how it can be achieved in a clustered enviroment with 3 managed servers with an example if possible.
          Thanks in advance.
          kris.

Cross post your query in Weblogic JMS forum please -
WebLogic Server - JMS
As far as I know server migration should not affect the existing message's processing.
Regards,
Anuj

Similar Messages

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.

JMS Server and MySQL Persistent Store

          I set up a JDBC connection pool in Weblogic 8.1 with MySQL dbms. When I tried to
          create a JMS server and use the connection pool as the Persistent Store, then
          try to target the JMS to a managed server. I got the following error, any idea
          what the problem is?
          weblogic.management.DistributedManagementException: Distributed Management [1
          exceptions]
          JMS JDBC store, connection pool = , prefix = : unsupported DBMS
               at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:1133)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:462)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
               at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:765)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
               at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
               at weblogic.management.configuration.ServerMBean_Stub.addDeployment(ServerMBean_Stub.java:7929)
               at weblogic.management.internal.DynamicMBeanImpl.unprotectedUpdateDeployments(DynamicMBeanImpl.java:1795)
               at weblogic.management.internal.DynamicMBeanImpl.access$100(DynamicMBeanImpl.java:95)
               at weblogic.management.internal.DynamicMBeanImpl$2.run(DynamicMBeanImpl.java:1708)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1704)
               at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1128)
               at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:311)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
               at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
               at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:367)
               at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:741)
               at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
               at weblogic.management.configuration.JMSServerMBean_Stub.setTargets(JMSServerMBean_Stub.java:1247)
               at weblogic.management.console.webapp._domain.__jmsserver$ServerAndMigratableTargetAttribute.doSet(__jmsserver.java:109)
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:256)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          java.io.IOException: JMS JDBC store, connection pool = , prefix = : unsupported
          DBMS
               at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:359)
               at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1613)
               at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:426)
               at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
               at weblogic.jms.backend.BEStore.open(BEStore.java:262)
               at weblogic.jms.backend.BEStore.start(BEStore.java:151)
               at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
               at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1287)
               at weblogic.jms.JMSService.addJMSServer(JMSService.java:2167)
               at weblogic.jms.JMSService.addDeployment(JMSService.java:1938)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:201)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:747)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:726)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:458)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
               at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:765)
               at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
               at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          --------------- nested within: ------------------
          weblogic.management.console.utils.SetException: An error occurred while updating
          MigratableTarget on [Caching Stub]Proxy for dotnet:Name=CSJMSServer,Type=JMSServer
          - with nested exception:
          [weblogic.management.DistributedManagementException: Distributed Management [1
          exceptions]
          JMS JDBC store, connection pool = , prefix = : unsupported DBMS]
               at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:311)
               at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
               at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Console Release Build8.1.1.0Server Release Build8.1.1.0Server BuildWebLogic Server
          8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 All Server Product VersionsWebLogic
          Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 WebLogic XMLX Module 8.1 SP1
          Fri Jun 20 23:06:40 PDT 2003 271009 WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40
          PDT 2003 271009 WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 WebLogic
          Portal 8.1 Thu Jul 10 20:09:22 PDT 2003 84868


Exactly what it says: unsupported DBMS.
          But but but...
          OK, I'll be nice (just couldn't resist).
          The next 8.1 SP will contain the DDL for MySQL, but for
          now you can run it manually. Prepend your catalog,
          schema, and prefix before JMSState and JMSStore to
          match what you configured as a prefix in your
          JMS JDBC store, and run the commands:
          CREATE TABLE JMSState (recordHandle int, recordState int,
          recordGeneration int);
          CREATE TABLE JMSStore (recordHandle int, recordState int, record longblob);
          CREATE INDEX JMSMSG_X ON JMSState (recordHandle);
          CREATE INDEX JMSMSGQ_X ON JMSStore (recordHandle);
          COMMIT;
          Note that a file store may be preferable instead
          of using a database store, there is
          likely no performance advantage to MySQL (in fact
          there is likely a significant performance penalty), and a file
          store is just as transactionally safe as a database
          store.
          Tom
          dahan wrote:
          > I set up a JDBC connection pool in Weblogic 8.1 with MySQL dbms. When I tried to
          > create a JMS server and use the connection pool as the Persistent Store, then
          > try to target the JMS to a managed server. I got the following error, any idea
          > what the problem is?
          >
          > weblogic.management.DistributedManagementException: Distributed Management [1
          > exceptions]
          > JMS JDBC store, connection pool = , prefix = : unsupported DBMS
          >      at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:1133)
          >      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:462)
          >      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          >      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          >      at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:765)
          >      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          >      at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >      at weblogic.management.configuration.ServerMBean_Stub.addDeployment(ServerMBean_Stub.java:7929)
          >      at weblogic.management.internal.DynamicMBeanImpl.unprotectedUpdateDeployments(DynamicMBeanImpl.java:1795)
          >      at weblogic.management.internal.DynamicMBeanImpl.access$100(DynamicMBeanImpl.java:95)
          >      at weblogic.management.internal.DynamicMBeanImpl$2.run(DynamicMBeanImpl.java:1708)
          >      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          >      at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1704)
          >      at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1128)
          >      at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:311)
          >      at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
          >      at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
          >      at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:367)
          >      at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:741)
          >      at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
          >      at weblogic.management.configuration.JMSServerMBean_Stub.setTargets(JMSServerMBean_Stub.java:1247)
          >      at weblogic.management.console.webapp._domain.__jmsserver$ServerAndMigratableTargetAttribute.doSet(__jmsserver.java:109)
          >      at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:256)
          >      at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
          >      at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          >      at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          >      at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
          >      at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
          >      at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
          >      at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
          >      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          >      at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
          >      at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
          >      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          >      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > java.io.IOException: JMS JDBC store, connection pool = , prefix = : unsupported
          > DBMS
          >      at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:359)
          >      at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1613)
          >      at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:426)
          >      at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          >      at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          >      at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          >      at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          >      at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1287)
          >      at weblogic.jms.JMSService.addJMSServer(JMSService.java:2167)
          >      at weblogic.jms.JMSService.addDeployment(JMSService.java:1938)
          >      at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          >      at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:201)
          >      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          >      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          >      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          >      at java.lang.reflect.Method.invoke(Method.java:324)
          >      at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:747)
          >      at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:726)
          >      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:458)
          >      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          >      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          >      at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:765)
          >      at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
          >      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
          >      at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
          >      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
          >      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
          >      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
          >      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
          >      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          >      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > --------------- nested within: ------------------
          > weblogic.management.console.utils.SetException: An error occurred while updating
          > MigratableTarget on [Caching Stub]Proxy for dotnet:Name=CSJMSServer,Type=JMSServer
          > - with nested exception:
          > [weblogic.management.DistributedManagementException: Distributed Management [1
          > exceptions]
          > JMS JDBC store, connection pool = , prefix = : unsupported DBMS]
          >      at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:311)
          >      at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
          >      at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
          >      at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          >      at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
          >      at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
          >      at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
          >      at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
          >      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          >      at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
          >      at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
          >      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          >      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          >
          >
          > --------------------------------------------------------------------------------
          >
          > Console Release Build8.1.1.0Server Release Build8.1.1.0Server BuildWebLogic Server
          > 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 All Server Product VersionsWebLogic
          > Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 WebLogic XMLX Module 8.1 SP1
          > Fri Jun 20 23:06:40 PDT 2003 271009 WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40
          > PDT 2003 271009 WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 WebLogic
          > Portal 8.1 Thu Jul 10 20:09:22 PDT 2003 84868
          >

What is the association between JMS Server and JMS Module in weblogic 10?

Hi,
I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
And I have created a JMS Server and Targetted to the current running server (Admin Server).
But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
queue = (Queue) initialContext.lookup("jndi_queue");
Exception:
javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
How JMS Module and JMS server are associated.
My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
Please advice.
Thanks....

Hi,
Once you have JMS servers configured:
Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
For more information, reference the "best practices" chapter of the JMS configuration guide:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
Hope this helps,
Tom

Load balancing MQ 7.0 Foreign JMS Server and Weblogic 10 MDBs?

We have the following configuration and we are trying to troubleshoot what appears to be a load balancing issue.
We have 3 Solaris servers. Each Solaris server has two Weblogic managed servers running on it. There are a total of 6 managed servers in the Weblogic cluster.
MQ Series 7.0 is also installed on each Solaris server. The MQ queue managers are in a MQ cluster. Each queue manager has the same queues defined.
We have a foreign JMS Server configured on Weblogic that has destinations and a connection factory defined. There aren't many configuration options available for the connection factory. The destinations are bound to the queues defined on MQ using the MQ bindings file.
The MQ bindings file was generated using the TRANSPORT(BIND) mechanism. Each bindings file points to the queue manager running on that machine. So the 2 managed servers running on one machine are accepting messages from the queue manager on that machine.
The MDB's listenning for messages on the MQ queues are configured as follows in the weblogic-ejb-jar.xml:
<max-beans-in-free-pool>16</max-beans-in-free-pool>
We also created a custom work manager with min threads constraint=5 and max threads constraint=16. The dispatch-policy of all the MDBs is set to the custom work manager.
The open input count on each MQ queue managers shows up as 32 which is expected.
The default load algorithm on the cluster is round-robin.
When we run a load test (injecting 40 messages per second on one MQ queue), we notice that one managed server ends up being significantly loaded than the other. Each MQ queue manager in the MQ cluster receives approximately the same number of messages in the load test. But it seems like one managed server is preferred over the other in Weblogic.
What can be done to equally balance the load among the two managed servers on each Solaris server?
Thanks for the help.

Load balancing generally applies at determing how many consumer threads has to be created on each of the clustered queue instance. In that sense you have achieved perfect load balancing as your queue instances has the same no of consumer threads.
Once you have set 'x' consumer threads on a queue, it is upto messaging provider to decide which thread to deliver a particular message and you will hardly have any control over this. Since your 32 threads are listening on the same queue, MQ can select any thread for delivering the message and the behaviour could be non deterministic.
One option to change your design is to have a dispacther mdb which picks the messages off the MQ and then routes to a weblogic distributed destination and you can have your core mdb which does all processing listen to this distributed destination. You can enable load balancing when the disaptcher mdb routes the message to the distributed destination. Since dispatcher MDB is nothing more than a router, the unbalanced consumption off the MQ shouldn't seriously affect the server.

Importance of TREX server and services for Services registry

Hello All
Is a TREX Server and TREX services mandatory to be able to connect to the services registry??
Because I have no trex server and when i browse the services registry , no results are yielded..
Need information on the TREX and relation with the registry.
Thanks
Vijay

TREX is not mandatory to connect to Service Registry. But to Search a service in the registry, TREX is used in the backend.
Regards,
Prateek

How to use weblogic api to set jms server and presistance store target?

Hi all,
I can do the following from the weblogic admin console..
1) Can set jmsServer target as ejbserver to ejbserver (migratable)(Example: from ejbnode1 to ejbnode (migratable)
2) can set persistance store target as ejbserver to ejbserver (migratble)(Example: from ejbnode1 to ejbnode (migratable)
Now my question is, how can i use the weblogic api to set those things through the coding?
Pl anyone answer my qn.
Thanks in advance.
-Amal

The following is code which im using now,
Here I added jmsserver's targer as "ejbnode1" ok, How can change it to "ejbnode1 (migratable)". I can do this with admin console, but im not sure to do with api.
Help me to do this.
private void createJMSServer(Node node, String suffix) {
          try {
               ObjectName cfgManager = getConfigurationManager();
               ObjectName srvr = (ObjectName) mbeanServer.invoke(
                         domainConfig, "lookupJMSServer", new Object[] { node
                                   .getName()
                                   + suffix }, new String[] { "java.lang.String" });
               if (null == srvr) {
                    srvr = (ObjectName) mbeanServer.invoke(domainConfig,
                              "createJMSServer",new Object[] { node.getName() + suffix },
                              new String[] { "java.lang.String" });
               ObjectName targetSrvr = (ObjectName) mbeanServer.invoke(domainConfig,
                         "lookupServer", new Object[] { node.getTargetNode()},
                         new String[] { "java.lang.String" });
               mbeanServer.invoke(srvr, "addTarget",
                         new Object[] { targetSrvr },
                         new String[] { "javax.management.ObjectName" });
               saveAndActivateChanges(cfgManager);
               ClusterUtil.print("CL_106", "JMSClusterSetup.createJMSServer()",
                         new Object[] { node.getName() + suffix });
          } catch (Exception e) {
               ClusterUtil.throwEx("CL_3006", "JMSClusterSetup.createJMSServer()",
                         e, new Object[] { node.getName() });
     }

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.

Issues with JMS Server migration

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

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

Migratable JMS server

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

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

Basic understanding about Essbase Server and Administration Services

Hi
I am a newbie to the Essbase. I am trying to figure out the diference between Server and Services.I am very confused.
Please clarify my understanding
Essbase Server - This is a server in which Essbase stores all the data.
Essbase Administration Services -This is a agent used to communicate to the Essbase Server from the front end ( Admin Console)
Admin Console - This is a front end client used to connect to different Essbase Servers. It is possible to have Essbase Servers to be installed on different machines.
Before connecting to client Admin console we should make sure Essbase SErver and Essbase Administration SErvices are up and running
Thanks
Arun

hello friend
what ever your saying about essbase server and EAS is correct.If you want more detailed explanation on this please have a look into essbase architecture check this link which gives you better insight
http://gerardnico.com/wiki/epm/essbase/essbase_architecture
it not necessary that Essbase server and EAS should be on the same machine.we can add differnt servers in EAS console.
As far as your last question(Before connecting to client Admin console we should make sure Essbase SErver and Essbase Administration SErvices are up and running)
Before logon to EAS we have to make sure that essbase server,essbase admin services and openldap are up and running
thanks
raj

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

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

JMS Server without J2EE server?

Hi,
We're working on a relatively small application where a small amount of messaging would be beneficial. What I ideally need is a free reference implementation of the JMS spec which does not require a full J2EE server with ORB, etc all being started up. I was looking at what comes with the j2sdkee 1.3.1 but I can not see how to configure JNDI to use anything other than the naming service provided by the ORB.
If anybody can recommend an implementation available that might be of use that would be great.
Thanks,
Aoife

HI rajdeepdua,
ur comments:
>>It seems that all the vendors are trying to promote their products
well, i am NOT a SonicSoftware Marketing person.
>>If you need a free jms server the i think you should go for either openjms or joram
But i did lot of testing with Different JMS Server And i am convinces that Sonic MQ performs the best. Their DRA (Dynamic Routing architecture) is fantastic and performs absouletly bugless unlike its competitors.

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
          >>>>>>>
          >>>>>>>
          >>>>>>
          >

JMS Server and Service Migration....!

Similar Messages

Maybe you are looking for