Can JMS topics and queues be clustered in a WLS 7.0 Cluster?

We are installing a weblogic 7.0 cluster with 1 admin server and 2 managed
          node servers. Two nodes have been clustered. We are at the point where we
          need to configure JMS. Has any one implemented JMS in WLS 7 clustered
          environment? What are the things to watch out when clustering JMS? Can JMS
          topics and queues be clustered?
          TIA for any helpful hints and comments.
          Regards

"Karim Ali" <[email protected]> wrote:
          >> Has any one implemented JMS in WLS 7 clustered
          >> environment?
          I'm currently working on a project with WLS 7 here at work, involving
          the implementation of BEA's JMS Cluster. So far, I really haven't had
          many hiccups.
          "Karim Ali" <[email protected]> wrote:
          >> What are the things to watch out when clustering JMS?
          At least in WLS 7, the biggest thing that stands out is the lack of
          automatic failover. Also, Message Paging -- make sure you configure
          paging high/low thresholds. Or, if you don't wish for it to occur but
          can't stop the server (very common these days with SLAs), set that
          byte/message high threshold to a very large number (correct me if I'm
          wrong, but I believe BEA recommends 2^63 -1).
          "Karim Ali" <[email protected]> wrote:
          >> Can JMS topics and queues be clustered?
          Well, since Topics and Queues are extensions of the
          javax.jms.Destination interface, the answer is: Yes!
          (SIDE NOTE: most people usually refer to them as a [JMS] "destination"
          -- it avoids a lot of conceptual baggage and plus, less typing!)
          You'll probably want to see this section of BEA's e-docs:
          http://edocs.bea.com/wls/docs70/adminguide/jms.html#config_distributed_destinations
          later,
          Brian J. Mitchell
          BEA Systems Administrator
          TRX
          Atlanta, GA
          email: [email protected]
          office: 404-327-7238
          mobile: 678-283-6530

Similar Messages

Creating topics and queues programatically

Hi,
Here i my scenario.
1. I have created the required number of queues and topics using the SunOne MQ's imqcmd command.
2. I want to use the jndi apis to register the jndia names for these queues in the appserver. How do we do this?
3. How to make an entry in the server.xml file programatically?
Note:- i do no t want to use the asadmin-utility for this.
i want to use the standard api's available to do this task.
Pls help
regards
raghu

Hi Raghu,
You appear to have created various topics and queues
on a MQ broker via the imqcmd command (independent
of app server).
For JMS clients to access/use the above topics/queues,
JMS resources of type javax.jms.Topic and javax.jms.Queue
need to be created and exposed to app server's JNDI
context.
Running this command:
asadmin create-jms-resource ...
Creates a new jms-resource entry in server.xml and
the command:
asadmin reconfig ...
Creates the actual java object and introduces it into
app server's JNDI context. (A server restart does this too).
You mention that you want to do the above from your code.
I don't think it is possible to programatically add new
resources into server.xml. If there was a way, I wouldn't
recommend it be done from J2EE applications since JMS resource
management is an administrative task. Note that using
JNDI to bind an object from an application (I haven't tried it
in app server) may appear to work but this resource is not
persisted across restarts since it is not in server.xml.
Why do you want to do this ? Why does your application need to do
what asadmin already does today ?
Perhaps if I can better understand why you want to do this I can
help suggest other solutions.
regards,
-isa

JMS Topics and Selectors

I'm running into a problem when using JMS Topics and selectors.
If I just use:
subscriber = session.createSubscriber(topic);
everything works fine.
However, if I use
subscriber = session.createSubscriber(topic, "Property = 'Value'", false);
I get an invalid topic exception from EvermindTopicSession.createSubscriber() line 84.
I'm using OC4J 9.0.3 standalone.
What might I be doing wrong?

[bump]
Incidentally, I've also noticed that JMSTimestamp is not set. I've even tried setDisableTimestamp(false). The timestamp still won't be set. I can set the timestamp manually myself using setJMSTimestamp. Also, message time to live doesn't seem to work with Topics (not sure about queues).
Is this a well known problem?
Is it an OC4J problem or a JMS problem?

Dynamic topics and queues

I'd like to know if a JMS client can create a topic or queue dynamically to be used by others JMS clients, or this is a operation which only can be performed by JMS server.
Thanks in advance.

I should add that the JMS spec does define an API for creating 'temporary destinations', e.g., using the QueueSession.createTemporaryQueue() method. However these have a few limitations over standard destinations: firstly, they only survive for the lifetime of the connection from which they were created, when the connection is closed the destination is destroyed and the contents is lost; secondly, although producers from any connection can produce messages to a temporary destination, only consumers that belong to the same connection within which the temporary destination was created are able to consume from a given temporary destination. All that said, temporary destinations can often be useful, particularly for handling request/response type interactions - see QueueRequestors too for more info.
Best regards,
David Ingham
Arjuna Technologies - http://www.arjuna.com

Newbie question about JMS topic and OSB

So here is what I want to achieve:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. The way I picture this is that a producer will invoke a proxy to publish a message. The subscriber will (asynchronously) invoke another proxy to pickup the message.
Is this possible and how do I go about doing this?
thanks
Edited by: user10341230 on Apr 28, 2010 8:49 AM

Hi there,
user10341230 wrote:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. > it's not really clear what you want to achieve here.
you say
user10341230 wrote:
The way I picture this is that a producer will invoke a proxy to publish a message.you need a proxy with whatever inbound protocol you like (http, file, mail...), which through a jms business service push the message to the Topic.
you say
user10341230 wrote:
The subscriber will (asynchronously) invoke another proxy to pickup the messagethe subscriber can be either asyncrhnous, in which case you need a proxy service with inbound protocol jms. or as you probably need a synchronous one
in which case you need another proxy with whatever inbound protocol you like whch once called in its pipeline calls some pojo class to read from this topic synchrnously (you need a durable subsciber).
Regards,
Tony
ps: have a look http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/jms/design_best_practices.html#wp1058694

1 "simple" JMS topic and 2 cluster elements with OSB

Hi,
I have 1 simple jms topic (not distributed, not on migratable target) and cluster with 2 members - OSB as main application. My OSB proxy service reads from this topic and saves data to file.
The problem is that reading from topic appears twice - once by each cluster member. How to configure topic or proxy service for only one reading?

FYI - At this year's Oracle OpenWorld, which is being held in conjunction with this year's JavaOne, Oracle will be announcing a set of enhancements that are designed to cover this exact use case.
Tom Barnes
Session ID: S317469
Title: New Service-Oriented Architecture Patterns with Enterprise Grid Messaging
Abstract: Messaging systems are essential in enabling the flexibility and loosely coupled nature of a service-oriented architecture (SOA). Oracle WebLogic Java Message Service (JMS) includes new pub-sub capabilities that make architectures more adaptable, allowing message producers to be ignorant of who is the consumer of a message or how many consumers there are. It also enables easy scale out and dynamic adaptability through clustering and message-driven bean (MDB) enhancements, all while still guaranteeing strict message ordering. This session will outline new JMS capabilities and show how they enable new designs with Oracle WebLogic Server and Oracle Service Bus.
Speaker(s): Dongbo Xiao, Oracle, Principal Member of Technical Staff
Biography not available.
David Cabelus, Oracle USA, Senior Principal Product Manager
Dave Cabelus is a Senior Principal Product Manager in the WebLogic Server group at Oracle. Dave's responsibilities include product strategy and direction for various pieces of WebLogic Server, including Java Messaging, Operations and Management, Diagnostics, and various other initiatives, and previously included database connectivity, transactions, and Web tier integration. In the industry since 1996 and involved in Java since 1999, Dave worked at various software companies including Logic Works, Platinum Software, Kana, and a few startups before coming to Oracle (BEA) in 2001.
Event: JavaOne and Oracle Develop
Stream(s): ORACLE DEVELOP, DEVELOP
Track(s): Application Grid and Oracle WebLogic
Tags: Add
Session Type: Conference Session
Session Category: Features
Duration: 60 min.
Schedule: Thursday, September 23, 11:00AM | Hotel Nikko, Nikko Ballroom II Available
Edited by: TomB on Aug 12, 2010 1:21 PM

JMS destination and queue in jndi.properties

I am using activemq to create a very simple jms application.
But there is a point I have not understand.The administered connection factory object that I use is org.activemq.jndi.ActiveMQInitialContextFactory which is the ActiveMq specific object. Do I have to do the same with the destination object?I read that Destination is also an administered object so I have to use an object of the ActiveMq? Specifically in the jndi properties where I define the queue property the value must be:
1.an activeMq object
2.a java class that implements the javax.jsm.Queue interface
3.a physical name of another server?
and in the code where I look up the destination object
Destination destination = (Destination) jndiContext.lookup(queueProp);What exactly will be the queueProp? I would appreciate an example
Thanking you in advance.

I've read the documentation but I am afraid I miss some points.
First of all I use the following code from an example in the net where the <b> activemq.jar is >/b> used and the jndi.properties is not used at all and the following code is working:package jms;
import org.activemq.ActiveMQConnectionFactory;
import javax.jms.Connection;
import javax.jms.DeliveryMode;
import javax.jms.Destination;
import javax.jms.ExceptionListener;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageProducer;
import javax.jms.Session;
import javax.jms.TextMessage;
* Hello world!
public class App {
    public static void main(String[] args) throws Exception {
        thread(new HelloWorldBroker(args), true);
        Thread.sleep(1000);
        thread(new HelloWorldProducer(), false);
        thread(new HelloWorldProducer(), false);
        thread(new HelloWorldConsumer(), false);
        Thread.sleep(1000);
        thread(new HelloWorldConsumer(), false);
               Thread.sleep(1000);
        thread(new HelloWorldConsumer(), false);
        thread(new HelloWorldProducer(), false);
                Thread.sleep(1000);
             thread(new HelloWorldProducer(), false);
        thread(new HelloWorldConsumer(), false);
    public static void thread(Runnable runnable, boolean daemon) {
        Thread brokerThread = new Thread(runnable);
        brokerThread.setDaemon(daemon);
        brokerThread.start();
    public static class HelloWorldBroker implements Runnable {
        private final String[] args;
        public HelloWorldBroker(String[] args) {
            this.args = args;
        public void run() {
            org.activemq.broker.impl.Main.main(args);
    public static class HelloWorldProducer implements Runnable {
        public void run() {
            try {
                // Create a ConnectionFactory
                ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
                // Create a Connection
                Connection connection = connectionFactory.createConnection();
                connection.start();
                // Create a Session
                Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
                // Create the destination (Topic or Queue)
                Destination destination = session.createQueue("TEST.FOO");
                // Create a MessageProducer from the Session to the Topic or Queue
                MessageProducer producer = session.createProducer(destination);
                producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
                // Create a messages
                String text = "Hello world! From: " + Thread.currentThread().getName() + " : " + this.hashCode();
                TextMessage message = session.createTextMessage(text);
                // Tell the producer to send the message
                System.out.println("Sent message: "+ message.hashCode() + " : " + Thread.currentThread().getName());
                producer.send(message);
                // Clean up
                session.close();
                connection.close();
            catch (Exception e) {
                System.out.println("Caught: " + e);
                e.printStackTrace();
    public static class HelloWorldConsumer implements Runnable, ExceptionListener {
        public void run() {
            try {
                // Create a ConnectionFactory
                ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
                // Create a Connection
                Connection connection = connectionFactory.createConnection();
                connection.start();
                connection.setExceptionListener(this);
                // Create a Session
                Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
                // Create the destination (Topic or Queue)
                Destination destination = session.createQueue("TEST.FOO");
                // Create a MessageConsumer from the Session to the Topic or Queue
                MessageConsumer consumer = session.createConsumer(destination);
                // Wait for a message
                Message message = consumer.receive(1000);
                if (message instanceof TextMessage) {
                    TextMessage textMessage = (TextMessage) message;
                    String text = textMessage.getText();
                    System.out.println("Received: " + text);
                } else {
                    System.out.println("Received: " + message);
                consumer.close();
                session.close();
                connection.close();
            } catch (Exception e) {
                System.out.println("Caught: " + e);
                e.printStackTrace();
        public synchronized void onException(JMSException ex) {
            System.out.println("JMS Exception occured. Shutting down client.");
}But I want to make it work with jndi.properties.
So I am trying to use a code where connectionFactory and Destination are loaded from the jndi properties.After experimenting with code
the following is working
     try {
               connectionFactory = (ConnectionFactory) jndiContext.lookup("connectionFactory");
              Destination destination = (Destination) jndiContext.lookup("QUEUE/MYQUEUE");
          Connection connection = connectionFactory.createConnection();
          Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);if only I go to the activeqm/bin folder and open the broker.If I did that in the previous code(with no jndi prop)
there was an exception that was saying that the port was already used.So I do not understand why in the one case opening broker is necessary for the connection and on the other hand it causes a problem.
Moreover in the case that I invoke broker from bin folder. In this case I would like to ask a question.The activemq.xml is necessary? If yes it is there where we define the queue?
If not where else apart from the jndi.properties do we define queue?
Please if is possible provide me with an example of the necessary places that we define a queue.
Thank you

Distinguishing between topics and queues

          Hi,
          I have a generic piece of code that takes a javax.jms.Destination that does different
          things depending if the destination is a queue or a topic.
          The problem is that it seems that destinations in Weblogic implement both queue
          and topic:
          instanceof queue <new_JMSTopic_1>
          queue name: <new_JMSTopic_1>
          weblogic.jms.common.InvalidDestinationException: Destination must be a queue,
          ne
          w_JMSTopic_1
          at weblogic.jms.common.Destination.checkDestinationType(Destination.java
          :113)
          at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1516)
          at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1500)
          at Test.run(Test.java:100)
          at Test.main(Test.java:311)
          Is there anyway for me to programatically distinguish between queues and topics
          as there seems not to be any javadoc on weblogic.jms.common.Destination and instanceof
          does not work? I would prefer not to rely on exceptions.
          I'm using Weblogic 8.1 sp2.
          Thanks
          Riad


          Cool. Thanks for your help Tom.
          Riad
          Tom Barnes <[email protected]> wrote:
          >Hi Riad,
          >
          >This has come up before.
          >
          >For now, you may cast dest to weblogic.jms.common.DestinationImpl
          >and call "isQueue()". Normally, only the javadoc'd methods
          >in weblogic.jms.extensions are intended for public use,
          >but for this case we make an exception.
          >
          >In the next release, this method will be exposed through
          >a new public WL JMS API extension:
          >weblogic.jms.extensions.WLDestination,
          >and might not be available otherwise.
          >
          >Tom, BEA
          >
          >P.S. A java tip: The JDK's built-in "javap"
          >is useful for viewing an arbitrary class api.
          >As in "javap weblogic.jms.extensions.JMSHelper".
          >
          >Riad wrote:
          >> Hi,
          >>
          >> I have a generic piece of code that takes a javax.jms.Destination that
          >does different
          >> things depending if the destination is a queue or a topic.
          >>
          >> The problem is that it seems that destinations in Weblogic implement
          >both queue
          >> and topic:
          >> instanceof queue <new_JMSTopic_1>
          >> queue name: <new_JMSTopic_1>
          >> weblogic.jms.common.InvalidDestinationException: Destination must be
          >a queue,
          >> ne
          >> w_JMSTopic_1
          >> at weblogic.jms.common.Destination.checkDestinationType(Destination.java
          >> :113)
          >> at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1516)
          >> at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1500)
          >> at Test.run(Test.java:100)
          >> at Test.main(Test.java:311)
          >>
          >> Is there anyway for me to programatically distinguish between queues
          >and topics
          >> as there seems not to be any javadoc on weblogic.jms.common.Destination
          >and instanceof
          >> does not work? I would prefer not to rely on exceptions.
          >>
          >> I'm using Weblogic 8.1 sp2.
          >>
          >> Thanks
          >> Riad
          >

Configuring JMS factories and queues INSIDE application?

When I package my EAR, it can contain an "orion-application.xml" file, a "data-sources.xml" file, and a "principals.xml" file. It appears that all of these are used when deploying the application, as they all end up (in some form) in the named subdirectory of "application-deployments".
However, I also need to configure a JMS ConnectionFactory and two JMS Queues. I tried putting a "jms.xml" file into the EAR, but this appeared to have no effect on the deployment.
When I shutdown the server and modified the file "$OC4J_HOME/j2ee/home/config/jms.xml" to specify my factory and queues, then my application started up, and was able to find the factory and queues.
So, is there any way to package my JMS configuration as part of the EAR, so I don't have to specify any manual configuration information in order to deploy my EAR?

Just so we're clear, I wasn't asking how I can specify JMS configuration inside the "orion-application" element, but how I can specify JMS configuration in my EAR. Along with the J2EE "application.xml" file, you can place an "orion-application.xml" file, a "data-sources.xml" file, and a "principals.xml" file. I was wondering whether I could also put a "jms.xml" file in the same directory in the EAR.
Your first sentence is relatively clear on this, but when you supplied the link to the "orion-application.xml" dtd, I wondered whether we were talking about the same thing. The DTD for "orion-application" wouldn't (I assume) say anything about the other configuration files.

How can i segregate an array of clusters with channels id in the cluster

Hi All
i am using a keithley 2010 DMM for power measurements,
i am using the 2010 scan read VI which gives the reading output as an array of clusters, these clusters contain the measurement,units,channel.
i have 6 channels for measuring voltage across and i want to make 5 readings per second on each channel which makes upto 30 readings per second.
i want to segregate these clusters from the array according to the channel id and take the results,
please tell me if we have function for this or you have any possible solution for the same.
i would be very happy to hear from you and get this solved
please help
Thanks in advance
Sandeep K Shyam

yeah this looks great...thanks for your response,
i have modified accordingly and attaching the VI, can you please look into this once
also one more problem i have with this VI is whenever i am trying to run the VI, the sub VI (Scan config.vi) gets popped up and waits for user response (next) cntrl+right arrow, how can i get rid of this and run the VI in continues mode?
i am attaching my VI along with the kei2010 lib,
please check this
Thanks again
sandeep K shyam
Attachments:
sandeep-FinalKeithley20101.vi ‏822 KB
kei2010.llb ‏901 KB

How to configure a error queue for weblogic jms topic

Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
Mingzhuang

Mingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj

Request-Reply in JMSAdapter SOA 11g using a Topic and a Queue

Hi All
We are trying to implement JMS Request\Reply with Tibco EMS Server using JMS Request\Reply. Problem is that Tibco has exposed a topic (where request message has been enqueued) and replies the message is a pre defined JMS queue.
I am trying to use JMS adapter in SOA 11g (OSB doesnt support request\reply as soon as destination is selected as Topic ) with foreign JMS server setup in weblogic.
Problem is that when i invoke the composite, it errors out saying that request destination has to be a queue. I tried to find any sample that talks about request-reply with topics but could not find any.
Is request-reply pattern supported with topics or topic-queue combinations in JMS adapter 11g? Please let u know. Thanks

Hi All
The request-reply pattern is working with queues and topics, but not with topic and queue. The issue is with this:
<adapter-config name="RemoteOSBJMSService" adapter="JMS Adapter"
wsdlLocation="RemoteOSBJMSService.wsdl"
xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/JMS/RequestReplyTopic"
UIJmsProvider="WLSJMS" UiOperationMode="Asynchronous"
UIConnectionName="chdsez147855d"/>
<endpoint-activation portType="Reply_ptt" operation="Reply"
UITransmissionPrimitive="Request-response">
<activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
<property name="PayloadType" value="TextMessage"/>
<property name="UseMessageListener" value="false"/>
<property name="DestinationName" value="jms.soa.local.response.q"/>
</activation-spec>
</endpoint-activation>
<endpoint-interaction portType="Request_ptt" operation="Request"
UITransmissionPrimitive="Request-response">
<interaction-spec className="oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec">
<property name="TimeToLive" value="0"/>
<property name="PayloadType" value="TextMessage"/>
<property name="DeliveryMode" value="Persistent"/>
<property name="DestinationName" value="jms.soa.local.request.topic"/>
</interaction-spec>
</endpoint-interaction>
</adapter-config>
The connection factory "eis/JMS/RequestReplyTopic" can either hold isTopic as false or true. If i set it to false, it doesnt even let me enqueue and if i set it to true. The reply doesnt arrive.
Please help!

Flex with JMS Topic/Queue for Asynchronous messaging

I have been working on Flex and JMS integration using Data
Services for Asynchronous messaging. I am able to do this
successfuly. Now I am in need to do the same without using the Data
Services piece.
For doing this I have done the following ......
I have created a JMS Webservice in the Oracle JDeveloper 10G
along with Webservice Client.I am able to Listen to JMS Topic/Queue
( this has been created in the Oracle AS ) using this Webservice
and receive the messages from this JMS Topic/Queue
Asynchronously.....
But If I need to use the Flex Client , I am not able to
Communicate with this Webservice to listen to the JMS Topic/Queue.
Did any one in this forum tried to communicate with JMS
Topic/Queue without using Flex Data Service.If so please share your
inputs.

Here is my confusion (I'm using J2EESDK1.3).
On a local server I did the following
j2eeadmin -addJmsFactory jms/RemoteTCF topic -props url=corbaname:iiop:mars#mars
In the app client running on the local server I had the code
ic = new InitialContext();
// JNDI lookup. The resource factory ref points to the
// Remote Connection Factory I registered
tcf = (TopicConnectionFactory)ic.lookup("java:comp/env/jms/TopicConnectionFactory");
// The env ref points to jms/Topic of the local server
pTopic = (Topic)ic.lookup("java:comp/env/jms/PTopic");
So I'm assuming that I'm using a connection factory that connect to mars and a Topic on the local box.
On remote server mars, I deployed a MDB which use
jms/TopicConnectionFactory and jms/Topic. But I'm thinking this jms/Topic and the one I used on the local box are not the same one. Right? Then how could the app client and the MDB share messages?
Some of my explanation I don't if it makes sense or not.
ConnectionFactory is a way to tell what kind of connection it could generate (Queue, Topic, Durable etc) and Where the connection would go to (local or remote).'
As for as destination, I'm not sure. How could two server share one Topic?

Web Service Client - SOAP/jms: Specific response queue (not default queue)?

Hi @ll
I try to define a specific jms response queue for a web service client that communicates SOAP/jms, running on a WLS 9.2. The web service itself runs also on a WLS 9.2 where also the request and response queues are located. By default the client receives the responses from a temporary response queue. Is there a way to define a specific response queue e.g. setting the JMSReplyTo property in the request on the client side?
/cheers&greetz
Dani

WLS do not have a light SOAP client with callbacks yet. It is
not a planed feature for 7.0, but we will considering this for
post 7.0.
regards,
-manoj
"markhu" <[email protected]> wrote in message
news:[email protected]..
Hi, guys:
I have a system : client written in Java/Swing, HTTPS authentication,
and then subscribes to a WLS 61. SP2 based JMS Topic and also has the
ability to send message to a Queue, since I can not bring down the size of
the client side WLS JMS dependency lib, I am thinking about using SOAP /
web service as the communication tier between my client and server, so the
question is: since the client need get the price updates in a real time
mode, I need build a server side based PUSH for all the new price updates
which come into the JMS Topic, and broadcast as SOAP messages to client,is
this mean that I have to build the Call - Back for the Java Swing Client,so
it can automatically get the new price updates as it's getting from JMS
Topic now ? Any Idea on how to build server side PUSH based SOAP message
center as web service ?? Thanks a lot.
regards,
mark
FYI:
I need the same PUSH service for my .NET based client as well.

Reading old message from Topic or queue

How i can read old message from jms topic or queue?

It depends on what you mean by "old" and what your JMS implementation is. Old as in expired or as in previously delivered?
Sending expired or previously delivered messages with DropboxMQ is as simple as moving the message files around using a shell or file explorer.
http://dropboxmq.sourceforge.net
Dwayne

Can JMS topics and queues be clustered in a WLS 7.0 Cluster?

Similar Messages

Maybe you are looking for