JMS Servers - no "Clusters" tab ??

          Setting up a cluster with WL6.1; I'm adding a second app server
          machine to an existing app svr box + db box (the non-clustered environment has worked
          just fine).
          Everything seems pretty straightforward, except for JMS Servers.
          Under "Targets", there is no "Clusters" tab, even though the Help
          "Assign a JMS Server" section refers to the "Clusters" tab. All
          I have is a "Servers" tab that lists the two servers I created,
          plus "myserver." Do I need to clone each JMS Server, then assign each one to a specific
          Server?
          Thanks for any assistance!
          

          JMS server cannot be assigned to cluster. You have to create a JMS server for each
          individual weblogic server.
          "Eric Doherty" <[email protected]> wrote:
          >
          >Setting up a cluster with WL6.1; I'm adding a second app server
          >machine to an existing app svr box + db box (the non-clustered environment
          >has worked
          >just fine).
          >
          >Everything seems pretty straightforward, except for JMS Servers.
          >Under "Targets", there is no "Clusters" tab, even though the Help
          >"Assign a JMS Server" section refers to the "Clusters" tab. All
          >I have is a "Servers" tab that lists the two servers I created,
          >plus "myserver." Do I need to clone each JMS Server, then assign each one
          >to a specific
          >Server?
          >
          >Thanks for any assistance!
          

Similar Messages

  • How do you span a jta usertransaction across multiple jms servers?

    I have an ejb that connects to multiple jms servers (non-clustered) and
              retrieves messages. Those messages are concatenated together and placed on
              another jms queue. Is it possible to do all of this inside of one
              transaction? I am having trouble pulling this off.
              

    Sure, you can do this. Assuming you're using WLS JMS, you have to make sure that for all the JMS servers you're talking to, you use a connection factory with the "XA Connection Factory Enabled" flag set. You also need to make sure that you use JTA to start a transaction before retrieving the first message, and commit it after you're done with the final send.

  • Clustered JMS Servers

              I'm having problems with binding the JNDI tree for the other than the first server
              started in the cluster.
              The error looks like this.
              <2001-aug-22 14:31:41 GMT+02:00> <Error> <Cluster> <Conflict start: You tried
              to bind an object under the name EngineRegTopic in the jndi tree. The object you
              have bound weblogic.jms.common.DestinationImpl from 172.18.61.17 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.>
              How come?
              / Martin
              

    I am afraid JMS is not clusterable in WL6.0. Maybe you could try 6.1.
              "Martin" <[email protected]> ¼¶¼g©ó¶l¥ó
              news:3b83ad87$[email protected]..
              >
              > I'm having problems with binding the JNDI tree for the other than the
              first server
              > started in the cluster.
              > The error looks like this.
              > <2001-aug-22 14:31:41 GMT+02:00> <Error> <Cluster> <Conflict start: You
              tried
              > to bind an object under the name EngineRegTopic in the jndi tree. The
              object you
              > have bound weblogic.jms.common.DestinationImpl from 172.18.61.17 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.>
              > How come?
              > / Martin
              

  • WebLogic 12.1.2 erases subdeployment on Distributed Queue when targeted to multiple JMS Servers

    Update: verified in a 12.1.1.0 (JDK6) cluster - bug does not occur there.
    Hi,
      I have been migrating an 10.3.5.0 server to WebLogic 12.1.2.0 and have been unable to keep the subdeployment dropdown populated in the subdeployment tab of a uniform distributed queue when the subdeployment targets more than 1 JMS Server.
      If I uncheck one of the servers - I work fine - however I would like to target all JMS Servers in the cluster - this used to work fine in 10.3.5.0
      Following
    http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24401/taskhelp/jms_modules/distributed_queues/CreateUniformDistributedQueues.html
      I am able to create a new queue no problem against the multiple-server subdeployment - but when I navigate to the subdeployment dropdown - the target is erased with "None".
    If I save the subdeployment after setting it during the queue create - it is erased
    <sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
    Before:
    <weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
      <uniform-distributed-queue name="HousekeeperControlQueue">
        <sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
        <jndi-name>jms/HousekeeperControlQueue</jndi-name>
      </uniform-distributed-queue>
    </weblogic-jms>
    After:
    <weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
      <uniform-distributed-queue name="HousekeeperControlQueue">
        <jndi-name>jms/HousekeeperControlQueue</jndi-name>
      </uniform-distributed-queue>
    </weblogic-jms>
    Workaround:
    - upon server startup the config is valid - just dont re-save the jms module or the subdeployment target will be erases
    - also when creating a new subdeployment you will be able to select it from a jms distributed queue in the advanced targeting section even if it contains expected multiple JMS servers
    - you will not however be able to edit the JMS queue once created - if there is any change to targeting - recreating the queue is required
      thank you
      /michael

    Update: verified in a 12.1.1.0 (JDK6) cluster - bug does not occur there.
    Hi,
      I have been migrating an 10.3.5.0 server to WebLogic 12.1.2.0 and have been unable to keep the subdeployment dropdown populated in the subdeployment tab of a uniform distributed queue when the subdeployment targets more than 1 JMS Server.
      If I uncheck one of the servers - I work fine - however I would like to target all JMS Servers in the cluster - this used to work fine in 10.3.5.0
      Following
    http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24401/taskhelp/jms_modules/distributed_queues/CreateUniformDistributedQueues.html
      I am able to create a new queue no problem against the multiple-server subdeployment - but when I navigate to the subdeployment dropdown - the target is erased with "None".
    If I save the subdeployment after setting it during the queue create - it is erased
    <sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
    Before:
    <weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
      <uniform-distributed-queue name="HousekeeperControlQueue">
        <sub-deployment-name>MW-JMS-SubDeployment</sub-deployment-name>
        <jndi-name>jms/HousekeeperControlQueue</jndi-name>
      </uniform-distributed-queue>
    </weblogic-jms>
    After:
    <weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
      <uniform-distributed-queue name="HousekeeperControlQueue">
        <jndi-name>jms/HousekeeperControlQueue</jndi-name>
      </uniform-distributed-queue>
    </weblogic-jms>
    Workaround:
    - upon server startup the config is valid - just dont re-save the jms module or the subdeployment target will be erases
    - also when creating a new subdeployment you will be able to select it from a jms distributed queue in the advanced targeting section even if it contains expected multiple JMS servers
    - you will not however be able to edit the JMS queue once created - if there is any change to targeting - recreating the queue is required
      thank you
      /michael

  • Setting up JMS in a clustered SAP WAS 6.40

    Hello all,
    We are trying to start our app in the clustered SAP WAS 6.30 Patch Level 77737.313 and application start fails with a JMS Error:
    Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: JMS error.
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadDestination(ContainerImpl.java:1874)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.prepareStart(ContainerImpl.java:717)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:347)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:309)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:308)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.run(ParallelAdapter.java:73)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:72)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:126)
    Caused by: javax.jms.JMSException: ConnectionFactory with name com.ttt.jms.TTTTopicFactory does not exist.
    Same app starts up fine in a non-clustered environment.
    The JMS error says that application can't find the specified JMS Factory name. So it can be an issue with JNDI replication.
    The jms deployment descriptors we are using are:
    <jms-factories>
         <connection-factory>
              <connection-factory-type>QueueConnectionFactory</connection-factory-type>
              <factory-name>com.ttt.jms.TTTQueueFactory</factory-name>
              <context-factory-type>
                   <link-factory-name>jmsfactory/TTT/com.ttt.jms.TTTQueueFactory</link-factory-name>
                       <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
              </context-factory-type>
         </connection-factory>
         <connection-factory>
              <connection-factory-type>QueueConnectionFactory</connection-factory-type>
              <factory-name>com.ttt.jms.enterprise.TTTQueueFactory</factory-name>
              <context-factory-type>
                   <link-factory-name>jmsfactory/TTT/com.ttt.jms.enterprise.TTTQueueFactory</link-factory-name>
                       <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
              </context-factory-type>
         </connection-factory>
         <connection-factory>
              <connection-factory-type>TopicConnectionFactory</connection-factory-type>
              <factory-name>com.ttt.jms.TTTTopicFactory</factory-name>
              <context-factory-type>
                   <link-factory-name>jmsfactory/TTT/com.ttt.jms.TTTTopicFactory</link-factory-name>
                       <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
              </context-factory-type>
         </connection-factory>
    </jms-factories>
    <jms-destinations>
         <destination>
              <connection-factory>com.ttt.jms.TTTTopicFactory</connection-factory>
              <destination-name>com.ttt.jms.Topic1</destination-name>
         </destination>
         <destination>
              <connection-factory>com.ttt.jms.TTTQueueFactory</connection-factory>
              <destination-name>com.ttt.jms.Queue1</destination-name>
         </destination>
         <destination>
              <connection-factory>com.ttt.jms.TTTQueueFactory</connection-factory>
              <destination-name>com.ttt.jms.Queue2</destination-name>
         </destination>
         <destination>
              <connection-factory>com.ttt.jms.enterprise.TTTQueueFactory</connection-factory>
              <destination-name>com.ttt.jms.enterprise.Queue1</destination-name>
         </destination>
         <destination>
              <connection-factory>com.ttt.jms.enterprise.TTTQueueFactory</connection-factory>
              <destination-name>com.ttt.jms.enterprise.Queue2</destination-name>
         </destination>
    </jms-destinations>
    JMS Provider is configured with JMS server TTT and corresponding 4 queue factories and 1 topic factory.
    If you can see anything wrong with this configuration, I would really appreciate your comments.
    Maybe there is something specific that must be configured for JMS in a clustered environment?
    Thanks.

    Yuri:
    there may be cluster Q , check once or you should change the values in all cluster servers locally .

  • API to list Uniform Distributed Queue JMS Servers

    Hi all,
    I posted this in the SOA suite forum but this one may be better.
    I am writing a POJO webservice to synchronously read a message from a JMS queue. Unfortunately the queue is actually a uniform distributed queue so I actually need to look for messages in each of the local queues.
    I have written code to find the JNDI names of the local queues as follows:
    StringArray DistribMemberNames = new StringArray();
    String ttt;
    ttt = JMSHelper.uddMemberJNDIName("IMPJMSServer_1", part1.getJNDIName());
    DistribMemberNames.add(ttt);
    ttt = JMSHelper.uddMemberJNDIName("IMPJMSServer_2", part1.getJNDIName());
    DistribMemberNames.add(ttt);
    This works fine but I have hard coded the names of the JMS Servers and this is bad practice. I need to find a method where I can take the JNDI name of the uniform distributed queue and find all the JMSServer names. I have been looking for days but I can’t find anywhere in the API documentation that describes this.
    Does anyone have any suggestions?
    Thanks
    Robert
    (I am using 11.1.1.5 on a clustered weblogic enviroment)

    Hi,
    I have managed to answer this question myself.
    I needed to create a context:
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    m_jndiContext = new InitialContext(env);
    Look up the main runtime mbean
    MBeanServer server;
    server = (MBeanServer) m_jndiContext.lookup("java:comp/env/jmx/runtime");
    Navigate down the domain configuration to get the JMSServers
    ObjectName service = null;
    ObjectName domainConfiguration = null;
    ObjectName[] jmsServers = null;
    service = new ObjectName(
    "com.bea:Name=RuntimeService,"
    + "Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean");
    domainConfiguration = (ObjectName) server.getAttribute(service, "DomainConfiguration");
    jmsServers = (ObjectName[]) server.getAttribute(domainConfiguration, "JMSServers");
    For each server you can retrive it's name:
    for (int i = 0; i < length_serverRT; i++) {
    String jmsServerName = "";
    jmsServerName = (String) server.getAttribute(serverRT, "Name");
    I had to do some additional filtering for my own requirements
    Robert

  • Looking up JMS destinations with clustered WLS

              From scanning the postings, it appears that in a clustered WLS environment, the
              JMS servers are not clustered. As a result, the JMS destinations must be unique
              across all of the WLS in the cluster. In addition, there is no failover available
              when a JMS server goes down.
              With that stated, what I want to know is:
              When establishing a JMS connection with a JMS server in a WLS cluster, do I need
              to know the JNDI URL for each specific JMS server that is managing the destination(s)
              I wish to pub/sub?
              Or, is there a 'global' JNDI tree that I can reference and the clustered WLS behind
              the scenes will route me to the appropriate JMS server?
              If resolving the URL is a manual process, I will need to keep track of which destinations
              reside on which JMS servers. This adds an additional maintenance point that I
              would like to avoid if possible.
              Thanks,
              Bob.
              

    One can use Connection Factory to establish connection to particular
              destination (queue/topic). connection factories are clustered. so, one don't
              need to have knowledge of particular WLS.
              "Neal Yin" <[email protected]> wrote in message
              news:[email protected]...
              > Although there is only one JMS server instance, you can lookup it from
              > anywhere in a cluster.
              > In another words, JNDI tree is global in a WLS cluster. Just give cluster
              > DNS name in your
              > URL, you will be fine.
              >
              > -Neal
              >
              >
              > "Bob Peroutka" <[email protected]> wrote in message
              > news:[email protected]...
              > >
              > > From scanning the postings, it appears that in a clustered WLS
              > environment, the
              > > JMS servers are not clustered. As a result, the JMS destinations must
              be
              > unique
              > > across all of the WLS in the cluster. In addition, there is no failover
              > available
              > > when a JMS server goes down.
              > >
              > > With that stated, what I want to know is:
              > >
              > > When establishing a JMS connection with a JMS server in a WLS cluster,
              do
              > I need
              > > to know the JNDI URL for each specific JMS server that is managing the
              > destination(s)
              > > I wish to pub/sub?
              > >
              > > Or, is there a 'global' JNDI tree that I can reference and the clustered
              > WLS behind
              > > the scenes will route me to the appropriate JMS server?
              > >
              > > If resolving the URL is a manual process, I will need to keep track of
              > which destinations
              > > reside on which JMS servers. This adds an additional maintenance point
              > that I
              > > would like to avoid if possible.
              > >
              > > Thanks,
              > >
              > > Bob.
              > >
              > >
              > >
              >
              >
              

  • JMS is not clustering correctly anymore

    Hi all,
              I'm knee deep in a problem that has completely perplexed me. We have a
              cluster of two managed servers ms1, ms2 they are clustered together.
              They run on separate machines. We also have two JMS servers
              JMSServer1, and JMSServer2. JMSServer1 runs on ms1, JMSServer2 runs on
              ms2. We have a distributed queue with physical queue members that
              belong on both JMSServer1 and JMSServer2, our client application
              creates temporary topics, attaches itself as a listener to each temp
              topic it creates, then fires off a message to the distributed queue,
              with the message's JMSReplyTo field set to the temp topic that was
              created. A MDB reads the message off of the dist queue and then fires
              messages to the temp topic referenced in the JMSReplyTo field. Our
              configuration used to work great such that each temp topic that got
              created round robined between each JMSServer (JMSServer1, and
              JMSServer2), and which ever MDB was servicing the message from the
              queue had no problem locating and then sending the response messages to
              the appropriate temp topic whether the temp topic so happened to be
              located on the same managed server as the MDB or not.
              But then I was forced to dismantle the cluster, and had to make a whole
              bunch of changes. Later I went back to my cluster configuration, and
              at the same time our networking folks made a whole bunch of changes to
              the machines that the managed servers run on. So I had to adjust ip
              addresses and host names, and thought I got everything back together
              again, however now when the client creates each temp topic they are all
              created on the same managed server/JMSServer they are no longer round
              robined (i.e ms2) Also the MDB that services the message is always on
              the opposite mangaged server (i.e ms1), and when it tries to send its
              response messages to the temp topic I now get Destination not found
              errors, and when I look deeper in the stack trace weblogic reports that
              it can't do a JNDI lookup on weblogic.jms.S:<name of managed server>
              So I went and verified my cluster configuration is the same as it used
              to be except for IP addresses and it is... Also I went and looked at
              the JNDI tree for each managed server, and I noticed that for ms1 there
              is an entry of weblogic.jms.S:ms1, and for ms2 there is a JNDI entry of
              weblogic.jms.S:ms2, so the problem is the MDB that is servicing the
              message needs to get to the other managed server but it cannot find
              it...which makes sense because it is not listed in the JNDI tree. But
              why is not listed in the JNDI tree??? I went and looked at a cluster
              we have running in development and noticed that for ms1 I have JNDI
              entries of both weblogic.jms.S:ms1 AND weblogic.jms:Sms2, and the same
              for when I look at the JNDI entries of ms2. So I've also tried
              creating a brand new cluster from scratch with brand managed servers on
              dev, and everytime I add the managed servers to the cluster and view
              the JNDI tree for each managed server I see both managed servers
              listed. This seems correct, and things work fine in dev! For our test
              env I only see one weblogic.jms.S:<managed server> entry per managed
              server! I have no idea why this occurs. I see no errors in the
              managed server logs or admin logs when starting the cluster. I've run
              the multicast tool and multicast reports things are working correctly.
              The test cluster from a setup and startup standpoint acts like it is
              clustered correctly but when I try to attach a client now it acts as if
              its not clustered correctly WEIRD!?
              I'm assuming that whenver you create a new cluster that for each
              managed server that is part of the cluster all managed servers should
              be listed (weblogic.jms:Sms1, weblogic.jms.S:ms2,etc) for each JNDI
              tree on every managed server correct? What could cause this NOT to
              happen. Should I reinstall weblogic, I've tried creating new clusters,
              brand new domains and everytime now I can never get the managed servers
              JNDI trees to listed the other managed server!
              This is weblogic 8.1 sp3 BTW
              Please Help!

    I don't think a re-install is in order. Usually, the first thing to check is if multicast is working on your network. You can use the following stand-alone utility:
              http://e-docs.bea.com/wls/docs81/admin_ref/utils25.html
              For further advice, you can try the "clustering" newsgroup.
              Tom

  • Paging in JMS servers

    hi
              I am working on WLS 8.1. I developed a script using weblogic.admin to get the information about all the JMS servers in a cluster. It was working fine. But now as I configured paging and distributed queues to my JMS servers, that script is only getting the information of the JMS servers which dont have these added features with the same. I appreciate if somebody can tell me the reason those servers are not active.
              thanks in advance

    Hi,
              It sounds like you may have a generic mbean problem and not something unique to JMS. The "management" newsgroup may be able to help if you post more info there.
              Meanwhile, in case you're unaware, there's a simple JMS stat dump sample program for 8.1 called "JMSStats.java" available on dev2dev. Search code-share for jmstats, or one of these links might work:
              https://codesamples.projects.dev2dev.bea.com/servlets/ScarabDownload/resultpos/-1/nbrresults/0/remcurreport/true/template/ViewAttachment.vm/attachid/311/filename/JMSStats.zip
              https://codesamples.projects.dev2dev.bea.com/servlets/Scarab/remcurreport/true/template/ViewIssue.vm/id/S52/eventsubmit_dosetissueview/foo/resultpos/-1/nbrresults/0/action/ViewIssue/tab/4/readonly/false
              Tom

  • Transaction span two WLS managed servers (non-clustering)

    (Weblogic 6.1 - non-clustering version)
    I have two managed servers configured on a single machine on different
    ports, and I am not using clustering weblogic. Assuming I have EJB A
    deployed on managed server 1, and EJB B deployed on managed server 2.
    I want to have EJB A to invoke EJB B. In EJB A, I guess I will
    probably create the InitialContext with the URL of managed server 2,
    then do the JNDI look up and call EJB B.
    My questions are:
    - Can weblogic handle transaction that spans two managed servers
    (non-clustering setting)?
    - Does weblogic use XA to handle transaction between managed servers?
    - Do I need to do any JTA code in order to achieve that (instead of
    just letting the EJB container to handle the transaction for me)?
    Thanks in advance!
    B.L.

    Hi,
    "benson" <[email protected]> wrote in message
    news:[email protected]..
    (Weblogic 6.1 - non-clustering version)
    I have two managed servers configured on a single machine on different
    ports, and I am not using clustering weblogic. Assuming I have EJB A
    deployed on managed server 1, and EJB B deployed on managed server 2.
    I want to have EJB A to invoke EJB B. In EJB A, I guess I will
    probably create the InitialContext with the URL of managed server 2,
    then do the JNDI look up and call EJB B.
    My questions are:
    - Can weblogic handle transaction that spans two managed servers
    (non-clustering setting)?Yes, it can.
    - Does weblogic use XA to handle transaction between managed servers?Yes, it does. Make sure you use TX DataSources. If the servers are connected
    to different databases, TX DataSources should be based on connection pools
    used XA drivers.
    - Do I need to do any JTA code in order to achieve that (instead of
    just letting the EJB container to handle the transaction for me)?No, you don't. WebLogic will take care about handling
    distributed TXs.
    Regards,
    Slava Imeshev

  • How to confirm that servers are clustered in WL 5.1

              I have two machines ready for clustering. I started the two machines. How do I
              know whether these machines are in cluster? I went through the console in one
              the machine and it shows both the servers name under the cluster name. Does the
              entries in the Console under the cluster name confirms that both the servers are
              clustered?
              

    From my experience, yes.
              suresh wrote:
              > I have two machines ready for clustering. I started the two machines. How do I
              > know whether these machines are in cluster? I went through the console in one
              > the machine and it shows both the servers name under the cluster name. Does the
              > entries in the Console under the cluster name confirms that both the servers are
              > clustered?
              /\/\i|<e
              Mike Kincer
              Solutions Developer/Engineer
              Atlas Commerce "ebusiness evolved"
              Office phone: +1-607-741-8877
              mailto:[email protected] [http://www.atlascommerce.com]
              

  • Can BEA JMS C APIs be used to communicate with other JMS servers?

    Hello,
              Can BEA JMS C APIs be used to communicate with other JMS servers?
              If yes, is it enough to download, compile the JMS C APIs, and link the C applications to the libraries (shared or static) produced?
              If not, can you point me to an open source framework that can be used to enable C applications to communicate with JMS servers?
              I have HP-UX server that has both C and Java compilers (Java 1.5).

    The JMS C client is a pre-compiled library - we don't supply the source - so C applications link to it. If I recall correctly, there is an HP version. The C client library is actually thin layer that uses JNI to directly invoke a Java JMS client running in an embedded JVM.
              The library might work with other vendor's Java JMS clients, but BEA does not officially support this usage.
              Tom

  • Post JMS Messages Across Clusters

    Hi All,
              I am using Weblogic8.1 and i have a need to post JMS messages across clusters.
              The scenario is like this; i have an application that is deployed in Cluster "A" and another application deployed in another Cluster "B". Both clusters are managed by the same Admin server. Now i need to post a heartbeat message to Cluster "B" from an application deployed in Cluster "A".
              I initally thought that i can use distributed destinations and create member for that destination only on the server's in Cluster "B". That way my application in Cluster "A" could lookup the distributed destination, but the actual message would go to Cluster "B". But that doesn't seem to work. Should this work?
              In weblogic 9.0 there is something called JMS store and forward...that is sort of what i need.
              Any help would be greatly appreciated.
              Thanks
              Abhi

    I'm having the same problem!
    The interesting part is that I've tried to set the propertie for the Initial Context (like PROVIDER_URL,INITIAL_CONTEXT_FACTORY) but all the properties were ignored if I'm running the client from the same machine with that on which the J2EE server is running. Can anybody tell me why?
    While I was trying to run the JMS client on a remote machine I got the following exception (in fact expected since the context properties were ignored)
    JNDI lookup failed:javax.naming.CommunicationException: Can't find SerialContextProvider
    Can this problem be solved on a J2EE RI 1.3 server ?

  • Scaling JMS Servers

    I have a requirement to scale very large volumes of JMS messages (300+ million messages per day). I am concerned that the JMS server will become a bottleneck in the cluster. Is it possible to add additional JMS servers and use distributed destinations to load balance JMS traffic and maintain transparency to the JMS consumers/producers?

    Yes, distributed destinations are transparent. They appear as a single logical destination to the application. For messaging applications, other major items may also impact performance/scalability. Working on these sometimes reduces the need for distributed destinations (tuning, batching, WL version, etc.)
              Tom

  • Connecting JMS servers together into a cluster

              Hi
              I am just wondering if anyone tried (or is it even possible) to connect JMS servers
              from different providers (say BEA and Sonic) together in a cluster of some sorts?
              Thanks
              

    Integrating foreign vendors with WL has come up many times in this newsgroup.
              Search for "MQ" (MQSeries) and "Sonic".
              Tom
              Alex wrote:
              > Hi
              >
              > I am just wondering if anyone tried (or is it even possible) to connect JMS servers
              > from different providers (say BEA and Sonic) together in a cluster of some sorts?
              >
              > Thanks
              

Maybe you are looking for

  • How to compare 2 dates, on date and on time

    Hi, Can anyone explain me how I can compare 2 dates! I can compare them by date, but not by time. For example: Date1 = '2003-07-25 16:50:15.0' Date2 = '2003-07-25 14:20:48.0' I want to get the dates that are bigger than the date '2003-07-25 15:30:57.

  • How do I install raw update in PSE 10?

    I have PSE10 and Win 8.1 and want to try editing raw files. I have tried to install both Camera Raw 6.6 update for Elements 10 and Camera Raw 6.5 update for Elements 10 but the install fails with the following error message Elements Camera Raw 6.5 Up

  • IIS 6 and CF MX 7 on separate boxes

    Is it possible to have ISS6 on one box and CF MX 7 on another box? If yes, how do you map iis6 to ddl file on CFMX7 box?

  • Problems with exporting slideshows (Origami)

    Is anyone else having this problem: can' export any slideshow that has the Origami theme applied to it. All other themes seem to export with no problem. Incidentally, the exact same scenario is not working with Aperture.

  • Burning a video to an external DVD writer

    I have just bought a new G4 laptop and (stupidly, as it turns out) did not opt for the Superdrive, so I am trying to burn a short video to an external Freecom burner. All seemed to be going well. My plan was to save as a disc image and then use the U