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

Similar Messages

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!

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.

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

Verity and Clustered Coldfusion Servers

Hi All,
I am currently looking at using Verity with our clustered
coldfusion servers but seem to have an issue. We currently have
three coldfusion servers but the version of verity included with
coldfusion only allows a connection from one server.
Has anyone else been in the same situation where they need
more than one coldfusion server talking to the same verity server?
If so how did you solve this issue? ( We have looked at purchasing
the full version of verity but it is to expensive.)
Thanks
Paul

I'll restate this in simpler fashion.
Can you retrieve MX 7 verity search results on a MX 6.1
server?
Can this be done via CFHTTP or any other similar method?
Thanks

Single MDB on a clustered JMS queues(2)

I have 2 JMS servers in a cluster and each server has a JMS queue, which forms the distributed destination. Now I need a MDB to listen on both these queues. Is it possible?
Thanks
-Ankur

Yes - thats the usual purpose of distributed queues, to allow consumers to consume from the distributed queue (wherever its hosted).
Though distributed destinations are JMS provider specific so do check your providers documentation on using distributed queues. In some providers, like ActiveMQ, distributed queues look and act just like regular queues so they just work from inside a JMS client or MDB.
James
http://logicblaze.com/

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

Apache HTTP proxying for load balancing only to a group of non-clustered WL servers

          Hi,
          We're running WL Server 6.1 SP 2 on Solaris 2.8.
          For the Apache HTTP proxy plugin, if you use the WebLogicCluster http.conf option,
          do the WL servers you want to load balance across have to be part of a WebLogic
          cluster (if you are prepared to do without failover, as I know it would need to be
          a proper WL cluster to replicate session info for failover). Can you load balance
          across a group of non-clustered WL servers, and maintain the user session to the
          one WL server so that it doesn't switch between servers on alternate requests for
          the same user session, or must the servers be configured as a WebLogic cluster?
          Paul
          We find that if you have a collection of WL servers that are not configured as a
          cluster, that it will load balance alternate requests to each server, but it will
          not pin a user to a single machine according to their session so for 2 servers, 2
          differetn sessions get created, one on each machine.
          Is this because it doesn't normally do this, but sends the user alternately to a
          primary then secondary which works in a cluster because the session is replicated.
          I thought the secondary was only used when the primary failed.


We're running WL Server 6.1 SP 2 on Solaris 2.8.          >
          > For the Apache HTTP proxy plugin, if you use the WebLogicCluster http.conf
          option,
          > do the WL servers you want to load balance across have to be part of a
          WebLogic
          > cluster (if you are prepared to do without failover, as I know it would
          need to be
          > a proper WL cluster to replicate session info for failover). Can you load
          balance
          > across a group of non-clustered WL servers, and maintain the user session
          to the
          > one WL server so that it doesn't switch between servers on alternate
          requests for
          > the same user session, or must the servers be configured as a WebLogic
          cluster?
          You don't have to use the clustering option. To get failover, you'll have to
          use the JDBC persistence option of WL.
          > We find that if you have a collection of WL servers that are not
          configured as a
          > cluster, that it will load balance alternate requests to each server, but
          it will
          > not pin a user to a single machine according to their session so for 2
          servers, 2
          > differetn sessions get created, one on each machine.
          >
          > Is this because it doesn't normally do this, but sends the user
          alternately to a
          > primary then secondary which works in a cluster because the session is
          replicated.
          > I thought the secondary was only used when the primary failed.
          The primary/secondary stuff requires clustering. If Apache continues to
          "load balance" after the first request, you need to either use JDBC session
          persistence or use a different load balancer (like mod_jk for Apache or a
          h/w load balancer with support for sticky).
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Paul Hammond" <[email protected]> wrote in message
          news:[email protected]...
          >

Clustered blade servers

We're currently investigating a hardware refresh of our production landscape and we've come across a bit of a stumbling block. For the record, we're not particularly big, currently running ERP 2005 with a database instance and the central instance on dual quad-core x64 1.83GHz processors with 16GB RAM each and two application servers on four quad-core x64 pre-Core-architecture processors with 8GB RAM each. It's all hooked together on a gigabit Ethernet switch (two gigabit connections per server using teaming) and all storage is internal to each server except for the database instance which has an external SCSI RAID array.
We're now upsizing and are finding ourselves once again on the very limits of what the x86/x64 systems available to us can offer, except this time, we're not sure it's enough. We're investigating blade servers as a potential way to move forward but the documentation of how a "clustered blade" server works is sketchy at best. Itanium, for us, doesn't really hold the answer; sure you can fit 128 processors into the same server but we don't have £1m to spend!
So, my questions are:
What actually is a clustered blade server?
How does it work? Do I assign physical blades to a logical server and they all work together as one much faster server, or is it just for failover purposes?
Is it still possible to use SAP's recommendations about keeping the operating system, SAP executables, the database, the database log file and the swap space (etc. etc.) on physically seperate drives if we move to Fibre Channel based storage, or is that no longer something to worry about, does it even matter any more?
Do SAP have any recommendations with regards clustered blade servers?
Has anyone ever had experience of using clustered blade servers to run ERP 2005? Anything I should know?
The impression I get of blade servers is that they are to servers what RAID is to hard disk drives, but I'd just like a bit of advice from anyone who can give it before I start spending money!
Many thanks,
Rob Moss
Mark Two
Bolton, UK

You can export a VM with snapshots and import those to a later version.
If your snapshots were taken while the VM was running, then the running VM state file needs to be deleted. (the .bin / .vsv) as the running memory state is never supported when upgrading.
Now, the other issue. 2012 R2 cannot import a VM from 2008 R2. Only 2012 can import any of the 2008 releases, and the 2012 R2 release. (yes, there was a fundamental change made and 2012 was the cross-over release).
The way to handle this is:
1) try copying the entire VM folder (without exporting) and import to 2012 R2 (test this please).
2) Use 2012 to Import the export from 2008 R2, then upgrade to 2012 R2.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Application Clustering & JMS

Hi All,
I am in the process of moving an existing application to WebLogic 11g. This applications used to run on OC4J and we used multiple JVMs for the OC4J container to get some scalability.
For WebLogic, we are considering a similar feature and arrived at the WebLogic Cluster with an HTTP-proxy for distributing the incoming traffic. The application depends on certain hard-coded resources.
We have a very simple cluster, consisting of 2 managed Servers: MS1, MS2.
MS1 is the server that physically holds the JMS Server, an MDB to process messages from this JMS queue.
The application is deployed to the entire cluster (MS1+MS2)
After restarting the cluster, we find that the application is available on MS1, but cannot be access from MS2 since the JNDI replication in the cluster seems to take place AFTER the MS2 server has tried to activate the application deployment. Hence, the application is in a failed state on MS2, having run into an javax.naming.NameNotFoundException (after this, WLS tries to perform the JNDI replication across the cluster and it is only after this that the JNDI entries do show on the MS2 server's JNDI tree).
We have multiple queues with multiple consumers, so we do not want to create a distributed queue, since then we would also need to create multiple instance for each consumer (viz. one for each actual destination) ?
This problem occurs both when using a regular and a migratable target for the JMS server setup ...
Any ideas how to prevent the application deployment/activation BEFORE JNDI replication ?
Thx,
Milco

We're having similar problem with distributed destinations:
- 2 managed servers in cluster - MS1 and MS2
- 2 default migratable targets - MS1 (migratable) and MS2 (migratable)
- 2 JMS Servers - JMSServer1 and JMSServer2, 1 on each migratable target
- System JMS Module targeted to cluster
in it: Connection factories targeted to cluster and topics and queues targeted to subdeployment "JMSServer1,JMSServer2"
EAR application, deployed to cluster, is trying to connect to JMS destinations from postStart(ApplicationLifecycleEvent evt).
Understanding is that by the time postStart is called all JMS resources should've been created, but application is getting error
javax.naming.NameNotFoundException: Unable to resolve 'Queue JNDI Name'. Resolved '';
Could anybody help with this?..

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

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

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

Clustered JMS: license signature validation error

I have encountered the following error when I tried to send JMS message to a queue. Can anyone help to point out what license has been expired and where is it located? Please help
weblogic.jms.common.InvalidDestinationException: Error creating producer: License exception prevents access to destination ImportFileQueue
weblogic.jms.common.JMSException: Clustered JMS: license signature validation error!

JDK 1.2 is a bad choice. I have not seen directories called "java13".
Where, oh where, was my WLS installed?
$ cat $HOME/bea/beahomelist
Which version of WLS are you using?
Your JDK is most likely parallel to wlserver6.1 (?) in jdk131/jre/bin .
Happy Hunting,
Wayne Scott
dave robern wrote:
> After installing (solaris 8) I tried to start the examples server and first
> it could not find java_home (/opt/bea/java13 - I guess the install created
> teh java13 directory but nothing is installed?). I manually configured
> java_home=/usr/java1.2 and then tried again.
>
> Now after using the system password created during installation I get:
>
> $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
>
> Unable to start WebLogic Server !! WebLogic: license signature validation
> error!
>
> $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
>
> explain?
>
> Dave

Clustered JMS Servers

Similar Messages

Maybe you are looking for