OSB distributed queue proxy configuration

I have set up a distributed queue in WeblogicServer and I wonder how should I configure OSB proxy to consume JMS messages from it. I have read documentation at Oracle site and it says a distributed queue groups a bunch of local JMS queues in different servers that can be accesed through a common JNDI name. This provide load balancing and failover to messages put in the queue.
In OSB proxy a JMS destination is configured with following URL: jms://server:port/destination. So if I have a distributed queue that maps to two JMS servers, what server and port must I set in proxy URL? Do I need to setup two different proxies, one for JMS server1 and another for JMS server2?
Regards,
DC.

For weblogic JMS message producer load balancing happens at 3 different places.
1- For intial context lookup - this depends upon the URI you specify in the Initial Context Call. e.g. if you specify t3://localhost:7002,localhost:7003 , all context lookups happen on port 7002. Port 7003 is used only if 7002 is down. Thus this supports failover instead of load balancing. If you want load balancing for context lookup then you have to use a dns based cluster address where dns does the name resolution to a different address each time.
2- When a jms connection is created. The jms connection can be created to any managed server to which the Connection factory is targeted to. Thus you can have your context lookup on 7002 , but the actual jms connection can get created on 7003. If server affinity is enabled for the connection factory then the jms connection will be created to the same managed server instance as on which context lookup happened.
3- When a message Producer send is executed. The message send can land on any dd member in the cluster if load balancing is enabled. If server affinity is enabled, then the message will end up on dd member on the same managed server instance to which the jms connection was made. For e.g. assume you have your jms client app has a jms connection on ms1 and the message produced ends up on ms2, then the following path would have been taken.
jms client app --------Over jms connection-------> ms1 -------internally forwards ----------> ms2 ------puts message ---> dd2
I would recommend you to read the JMS chapter of Professional Oracle Weblogic Server book where this is explained clearly.

Similar Messages

Programming for Using JMS Distributed Queues

Hi,
Does anyone know specifically how your meant to write java code in order to fully make use of JMS Distributed queues. At the moment we have a 3rd party app, which I don't think is written correctly, as it always locks up after using a distributed queue, or a consumer is at 0 on one of the members of the distributed queue, when it should always should be constant and uniform.
Its as if their code hasn't been written correctly.

Distributed queue applications are encouraged to leverage WebLogic MDBs, which automatically ensure that consumers are attached to each distributed queue member, and to write applications in a way that has no dependency on which JVM a particular message is processed.
At a guess, the third party product is setting up a consumer on one member of the distributed Q, while messages are being produced to the other member. If this assumption is true, here are some thoughts:
* Consider using a single Q for the third party product's usage instead of a distributed queue. Configuring a distributed queue is not adding any high availability, as the product is expecting all messages to pin to the same Q instance.
* Producers and consumers load-balance independently, but, when "affinity" and "load balance" are both configured to false on a Producer's connection factory, producers will have a tendency to load balance to the member that hosts more than one consumer. This might help somewhat, but my guess is that it won't help in all cases -- for example, after a restart I'm not sure that there's a guarantee that the consumer won't load balance to the "wrong" member (the member that has no messages).
* It might help to enable "queue forwarding" on the distributed queue configuration. This feature automatically forwards messages trapped in a destination that has no consumers to a queue that has consumers. "Queue forwarding" is not compatible with WebLogic's "unit-of-order" feature, but it's likely the third party product isn't using this feature. Queue forwarding also imposes a performance penalty - but whether you notice the difference depends on whether you have high performance requirements.
Hope this helps,
Tom
Edited by: TomB on Mar 9, 2011 6:28 PM

OSB 10gR3 (WLS 10.3) - Distributed Queues & Load Balancing

I have a question in relation to distributed queues and its JMS proxy service consumer in OSB
I've set up a uniform distributed queue deployed using a sub-deployment resulting in the queue being targeted to the respective JMS servers in the cluster.
I've then set up a messaging service using JMS as the transport with the following URI
jms://server1:7011,server2:7012/weblogic.jms.XAConnectionFactory/myQueue
When I look at the monitoring tab of my distributed queue, I can see 16 current consumers to one of the members but none for the other one. My understanding is that the proxy is just a mere MDB and as such I thought WLS was optimised to make sure all MDB instances would listen to all members of the distributed queue. Why do I have 16 consumers to one member only?
Since only one member has consumers, any producer will always push messages to this member only. (I believe it is optimised to get a member with consumer(s) if any available)
I've also tried to use a custom Connection Factory deployed the same way my distributed queue was, and ensure the connection factory had load balancing enabled. But no success with this either.
jms://server1:7011,server2:7012/jms.MyConnectionFactory/myQueue
I looked at the deployment - though not directly performed by me but rather the bus console - and it looks like the application is targeted to the cluster.
How can I achieve true load balancing here, ensuring both members are consumed by my JMS proxy service?
In that case, would any produced message go to either member then as both have consumers?
Also, is the load balancing decision made by the producer when the Queue connection is created?
If so, how do you achieve true load balancing? Do you need to ask for a new Q connection each time you want to send a message rather than caching the connection?
Hope I am clear enough
Thanks
Arnaud

This confused me too!
The way I understand it, is that, as you say, a proxy service is like a single MDB. The MDB will bind to the queue it first finds when it connects.
The URL that you specify which contains your two servers but the first address in the URL is the one that will be used for the connection. If the first server is unavailable, then the second one will be used.
If you have a distributed queue, this doesn’t help much, as you do end up with one of the queue members with no consumers on it.
You can configure a forward delay for the distributed queue, which will cause WLS to forward messages to a queue with consumers, but this isn’t a good idea if you have large JMS messages as WLS needs to serialize and de-serialize across the network to move the message.
I think that what you have to do, is define two proxy services, one connecting to the first server, and the other connecting to the second.
I haven’t found a better way so far, but it does seem a bit over the top, but then, if you wrote a an external java client which attached to a distributed queue you would specify the connection url and it would behave in the same way – if you wanted it to bind to both distributed destination members, you would have to code it or run two instances, so maybe its just working as it should – even though it seems strange.
I think the producer will simply load balance across the distributed queue members, it doesn’t pay any attention whether there are to consumers attached – this happened to me the other day!!
Pete

OSB 11g: Business Service not getting reply back from distributed queue

Here is the scenario:
OSB Domain A has a Business service that does a JMS send to a distributed JMS queue hosted on another WLS domain.
It expects a response from a distributed queue sitting on this same remote WLS domain.
The remote WLS domain is configured as a Foreign JNDI Provider in the OSB Domain with the request and response queues defined. Testing this business service, we see that messages are being posted to the remote request queue fine, and that the message are being picked up and processed. The response was sent to the response queue, but the message just sits there, the OSB business service did not pick it up. I can see 16 active Consumers on the response queue, presumably from the OSB business service?
Using CorrelationID.
URI for request/response queues are using the locally defined JNDI name for the queues and connection factories from the Foreign JNDI Provider definition:
- URI for request queue: jms:///[RemoteXAConnectionFactoryX]/[LocalJNDINameForRequestQueue]
- URI for response queue: jms:///[RemoteXAConnectionFactoryX]/[LocalJNDINameForResponseQueue]
Completely stumped at the moment...anybody has any ideas?
Thanks,
Melvin

Hi,
I am also facing the similar kind of issue as below. After placing the message in to request Queue, I need that message Id as response to that Business service. Please provide the solution for the below issue. Thanks in advance.
Thanks,
bharath.

Accessing Distributed Queue In a Cluster via the Proxy Server

          I am running WL 8.1 SP2. I have a configuration where I have 3 servers (on two
          different machines) running in a cluster. I have a separate server on a 3rd machine
          running the cluster proxy server for a single point of access to the cluster.
          I have configured a distributed queue and a distributed topic, each targeted
          to all servers in the cluster.
          Now I have a JMS client which is a separate java application that is trying to
          connect to the distributed queue and topic in the cluster. If the client connects
          directly to one of the cluster machines, it is able to successfully interact with
          the JMS queue and topic. But if it attempts to connect via the proxy server it
          gets an error saying the queue and topic does not exist.
          So what am I missing? Do I need to configure a separate JMS server on the proxy
          server and add that as part of the distributed queue & topic (this didn't seem
          to allow me to add anything outside of the cluster). Is there any special configuration
          in the proxy to pass through JMS requests? I'm currently using a WL logic server
          as my front-end proxy server but does anything change if I want to use Apache
          with the WL Proxy plug-in??
          Jerald


          "Jerald Pratt" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am running WL 8.1 SP2. I have a configuration where I have 3 servers
          (on two
          > different machines) running in a cluster. I have a separate server on a
          3rd machine
          > running the cluster proxy server for a single point of access to the
          cluster.
          > I have configured a distributed queue and a distributed topic, each
          targeted
          > to all servers in the cluster.
          >
          > Now I have a JMS client which is a separate java application that is
          trying to
          > connect to the distributed queue and topic in the cluster. If the client
          connects
          > directly to one of the cluster machines, it is able to successfully
          interact with
          > the JMS queue and topic. But if it attempts to connect via the proxy
          server it
          > gets an error saying the queue and topic does not exist.
          Yup... That makes sense...
          >
          > So what am I missing? Do I need to configure a separate JMS server on the
          proxy
          > server and add that as part of the distributed queue & topic (this didn't
          seem
          > to allow me to add anything outside of the cluster). Is there any special
          configuration
          > in the proxy to pass through JMS requests? I'm currently using a WL logic
          server
          > as my front-end proxy server but does anything change if I want to use
          Apache
          > with the WL Proxy plug-in??
          One option I have used frequenly is specifying java.naming.provider.url as
          cluster address (e.g. t3://server1:7001,server2:7001
          You may also want to look into tunnelling...
          >
          > Jerald
          >

Oracle service bus file protocol issue with distributed queue

Hi,
I have created a file protocol based proxy service and it is deployed to a clustered environment. The clustered environment has -
Machine 1 - Admin server(AS) and Managed server 1 (MS1)
Machine 2 - Managed server 2(MS2)
There are 2 JMS servers jms1 and jms2 which are targeted to MS1 and MS2 respectively.There are 2 JMS queues(queue1 and queue 2) created, one each targeted to jms1 and jms2. The system module under which the queues are created is targeted to the cluster. There is uniform distributed queue(bind to wlsb.internal.transport.task.queue.file) created under the same system module of which queue1 and queue 2 are members.
Currently when the proxy service poller server is given as MS1 then if the file is picked up and send to queue 1 then it gets processed successfully but if the file is send to the queue 2 then it remains in the stage directory of the proxy service. Similarly if the proxy service poller server is given as MS2 then its get processed through queue 2 but if it is picked up in queue1 then it remains in the staging directory.
Am i missing any configuration here related to the queues set up ? Why file does not get processed if it is send to the queue(which is other than the poller managed server) ?
Please help
Thanks

I have installed OEPE 11.1.1.6.1 now in the same middleware home as weblogic server but when i try to install OSB 11.1.1.4 in the same middleware home, it asks for OEPE home location. Even though i provide the OEPE home location , it displays as "invalid oepe home location".
I have been struggling to get this sorted out so that i can carry out IDE development in OSB 11.1.1.4
Below are the paths where sfotware are installed -
JDK - C:\Oracle\Middleware\Java\jdk1.6.0_21
Weblogic server - C:\Oracle\Middleware\wlserver_10.3
OEPE - C:\Oracle\Middleware\oepe-galileo-all-in-one-11.1.1.6.0.201007221355-win32-x86_64
Thanks

Increases number of JMS consumers in an OSB jms-polling proxy service

Hi All,
I'm looking for an option of increasing the number of JMS consumers in a JMS OSB proxy service. I know that this is possible by modifying the ejb, but I'm looking for any other option by using weblogic/proxy configuration. When I monitor the queue I have a number of 16 message consumers, but I would need to increse it to a higher number in order to improve the performance.
Please send me any suggestion o advice to solve it.
Thanks in advance
Luis

Sorry I sent it to the wrong place. I have moved it to Weblogic

Messages in Distributed Queue remain on one JMSServer in Cluster

Hi,
          the situation is as follows:
          We're having Distributed Queues on a two-Node server setup. A queue therefore exists two times, once on each JMSServer on each node.
          Forward-Delay has been set on the DistibutedQueue to value 1 second (we tested with values 0 and 10, too).
          External Java client (both cluster nodes in the provider_url for initialcontext) connects to the DistributedQueue and sends messages. In the weblogic console you can see these messages on the physical queue on the JMSServer, let's call it QueueA on NodeA.
          An external java process to consume messages (again both clusters nodes in the jndi-connection-string) is started to consume messages. Because of round-robin it sometimes get's connections to QueueB (part of same DistributedQueue as QueueA, but on the other node in the cluster).
          When connected to QueueB on NodeB no single message is received. You can even see in the weblogic console that QueueA on NodeA has zero consumers and 50 messages, QueueB on NodeB has zero messages but one consumer.
          When we restart the consumer java process and it randomly get's connected to QueueA on NodeA it consumes fine, as it should.
          Should'nt Forward-Delay do exactly this? Transport messages from QueueA on NodeA with zero consumers to QueueB on NodeB which actually has consumers?
          Any help would be appreciated.
          Axel van Lil

Hi,
          thanks for your answer. We opened a support case today for this issue... I don't know. Cluster seems to run fine, no warnings, no exceptions.
          The next step of this issue is the following (just to give an idea of our upcoming problems :-)
          External Java process listens on QueueA on NodeA (QueueA is part of a Distributed Queue). Currently receives all the messages located on that queue. We kill NodeA on that machine to simulate failover.
          The external process failovers immediately to NodeB (which is good! proven by netstat and debugger) but just doesn't receive messages even though there are messages in that queue! It seems that the new consumer is just being forgotten by the BEA server.
          I don't know... somehow our configuration is quirked... or the BEA implementation doesn't work at all...
          Rgds,
          Axel

Distributed queue usage with custom queue listeners in cluster

Hi,
Can someone help in solving the issue. We have a web application which will create consumers(threads in infinite loop) for an inbound queue(name comes from DB table) and after doing certain process result will be pushed to outbound queue(name comes from DB table).
When application runs in single managed server(without clustering) every thing works fine.
If I want to deploy the same application in two managed servers (with are under same cluster) which talks to same DB how to handle above scenario
1. Create 2 JMS servers one on each managed server(on different machines)
2. Create queue one for each JMS server
3. Create distributed queue and add above two queues as members of it
4. Create connection factory and target it to cluster
After creating above instrastructure(similar infrastructure will be created for inbound and outbound queue), can I use distributed queue JNDI name to create listeners(threads) to read messages? Or do I need to create listeners for each individual member in the distributed queue?
I know that while sending message to distributed queue, I can create sender on distributed queue and weblogic automatically takes care of sending the message to appropriate member in the DQ, but how it works for distributed queue?
Also, want to know how can I access distributed queue? For example, if managed server 1 is accessed by http://10.11.134.24:7001 and managed server 2 is accessed by http://10.11.134.25:7001. which URL I need use in JNDI context provider URL to access distributed queue? can I use any URL will it make any difference?
Generally for servlets/JSPs we create proxy server to access it through cluster, instead of directly using managed server URLs. But how it works for distributed queue?
Thanks
Santhosh
Edited by: user8676720 on Oct 4, 2011 8:35 AM

          Yes.
          It turns out that if replicate local queue jndi name in cluster is set to false
          the message did not get forward :(
          Dongbo Xiao <[email protected]> wrote:
          >Sorry, the attribute is ForwardDelay, not ForwardPolicy.
          >
          >Dongbo
          >
          >Dongbo Xiao wrote:
          >
          >> Hi Eran,
          >>
          >> Have you set up the ForwardPolicy for the Distributed Queue?
          >> By default, the ForwardPolicy is -1, which turns off the forwarding.
          >>
          >> Dongbo
          >>
          >> eran wrote:
          >>
          >> > Hello,
          >> > I have 2 nodes in cluster each one has a pinned JMS server with a
          >queue QueueA
          >> > and QueueA2
          >> > respectively both mebers in a distributed destination dist_queue.
          >> > There is a consumer on QueueA only (startup class).
          >> > In case of a message sent to QueueA2 a consumer is created for QueueA2
          >automaticly
          >> > (seen in the admin console) out of the blue, and the message do not
          >get forward
          >> > to QueueA where my consumer is listening.
          >> > Monitoring JMS connections of both servers shows only my consumers'
          >connection.
          >> > Our application depends on the forward feature.
          >> > Am I doing something wrong? any ideas?
          >> >
          >> > Thanks.
          >> > Eran
          >

Issue with Distributed Queue and WebLogic Clustering

Hi, When a message is received by distributed queue, MDB is processing the message on two managed servers. There seems to be issue with clustering and the physical queues present on both the managed servers are receving the message.
Our environment configuration details are as below:
One Web logic Cluster with 2 nodes (2 managed web logic servers).
One MDB deployed on the cluster listening to a queue with JNDI name “xng/jms/CODEventsQueue”
One Distributed queue with two members on the two nodes of the cluster, and with JNDI name “xng/jms/CODEventsQueue”
Two members of the distributed queue deployed on two JMS servers, which are separately deployed on each managed server .
And the distributed queue is deployed on the cluster.
Any help is appreciated.
Thanks
Sampath

It is not clear to me how you concluded that "both the managed servers are receiving the message". Did you monitor the queues' statistics, or did you see both MDB instances received the same message?
It looks like that you using a weighted distributed queue. Do the two physical queues that compose the distributed queue have their own JNDI names? If so, what are they?
Have you tried to use a uniform distributed queue and see if the same behavior shows up?
You can find more about uniform distributed destination at
http://edocs.bea.com/wls/docs103/jms/dds.html#wp1313713
BTW, which WebLogic Server releases are you using? Could you provide the distributed queue configuration?
Thanks,
Dongbo

Message payload logging for Uniform Distribute Queue

Hi All,
We have a requirement to log the message payload, of every jms message received in a Uniform Distribute Queue in Weblogic.
Please let us know how can we achieve this.
Thanks.

If you want to avoid use of the Path Service, then the alternative is to make the destination members highly available. This will help ensure that the host member for a particular UOO is up.
One approach to HA is to configure "service migration". For more information see the Automatic Service Migration white-paper at
http://www.oracle.com/technology/products/weblogic/pdf/weblogic-automatic-service-migration-whitepaper.pdf
In addition, I recommend referencing Best Practices for JMS Beginners and Advanced Users
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455 to help with WL configuration in general.
Hope this helps,
Tom

JMS Uniform Distribute Queue Unit Of Order, problem when one node goes down

Hi ,
I have the following code which post a message (with Unit of Order set ) to a Uniform Distribute Queue in a cluster with two member servers (server1 and server2).
--UDQ is targeted to a subdeployment that is mapped to two JMS servers pointing to each member servers
--Connection Factory is using default targeting ( i tried mapping to Sub deployment also)
javax.naming.InitialContext serverContext = new javax.naming.InitialContext();
javax.jms.QueueConnectionFactory qConnFactory = (javax.jms.QueueConnectionFactory)serverContext.lookup(jmsQConnFactoryName);
javax.jms.QueueConnection qConn = (javax.jms.QueueConnection)qConnFactory.createConnection();
javax.jms.QueueSession qSession = qConn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
javax.jms.Queue q = ( javax.jms.Queue)serverContext.lookup(jmsQName);
weblogic.jms.extensions.WLMessageProducer qSender = (weblogic.jms.extensions.WLMessageProducer) qSession.createProducer(q);
qSender.setUnitOfOrder("MyUnitOfOrder");
javax.jms.ObjectMessage message = qSession.createObjectMessage();
HashMap<String, Object> map = new HashMap<String, Object>();
map.put("something", "SomeObject");
message.setObject(map);
qSender.send(message);
} catch (Exception e) {
Steps followed:
1. Post a message from "server1"
2. Message picked up by "server2"
3. Everything fine
4. Shutdown "server2"
5. Post a message from "server1"
6. ERROR: "hashed member of MyAppJMSModule!MyDistributedQ is MyAppJMSModule!MyJMSServer-2@MyDistributedQ which is not available"
WebLogic version : 10.3.5
Is there a way (other than configuring Path Service ) to make this code work "with unit of order" for a UDQ even if some member servers go down ?
Thanks very much for your time.

If you want to avoid use of the Path Service, then the alternative is to make the destination members highly available. This will help ensure that the host member for a particular UOO is up.
One approach to HA is to configure "service migration". For more information see the Automatic Service Migration white-paper at
http://www.oracle.com/technology/products/weblogic/pdf/weblogic-automatic-service-migration-whitepaper.pdf
In addition, I recommend referencing Best Practices for JMS Beginners and Advanced Users
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455 to help with WL configuration in general.
Hope this helps,
Tom

Message Listener Listening to only 1 queue in distributed queue setup!

Hi guys,
This may be the wrong place to place this post.
We created a message system with OSB proxies moving messages back and forth between distributed queues. After all this shuffling messages around, the messages end up in a distributed queue where a java client is waiting to pick up results. Our problem is, it's only reading one of the queues in this distributed queue.
The following is the code segment that waits for the message with a specific id:
public Message receiveMessage(String queueName, String messageId) throws FrameworkException {
BytesMessage bytesMessage = null;
if (null == queueSession) {
init();
try {
Queue receiveQueue = lookupQueue(queueName);
QueueReceiver queueReceiver = null;
String selector =null;
if (null == messageId) {
queueReceiver = queueSession.createReceiver(receiveQueue);
} else {
selector = "JMSCorrelationID = '" + messageId + "'";
queueReceiver = queueSession.createReceiver(receiveQueue, selector);
bytesMessage =(BytesMessage) queueReceiver.receive();
queueReceiver.close();
}catch{...
Will queueReceiver.receive() listen to every member in a distributed queue (spread across 2 managed servers in a cluster)?
Thanks alot

Yes, the uniform distributed queue should be available on all targeted servers, providing that the jms module has been targeted to all of the OSB servers, and that your java app ( .war file? ) is targeted to both.
You can stop the java application so that messages remain in the queue "long enough" for you to see them from within the WL console. Then you can shutdown nodes in your cluster individually, so conform that the message is truly being distributed. Then the issue is whether the java app is reading from the entire distributed queue instead of just one node.
When you use the monitoring tab on your queue, do you see a queue entry for each jms server ( each mgd server needs one )?
Or is the issue that the java client is only reading from one server?

Looking up a distributed queue with two persistent stores using two JMS Svr

I am trying to do the following:
1. Setup a distributed queue, i have two servers which are part of the cluster:
Server A: t3://localhost:7003
Server B: t3://localhost:7005
I go in and create two jms servers:
JMS Server JA: Target on Server A
JMS Server JB: Target on Server B
Now as the jms servers need to use a seperate persistent store for each one of them i create two persistent stores.
2. Now from my MDB which is deployed on another server i lookup the queue using
t3://localhost:7003,localhost:7005 as the provider url
My problem is that i always end up listening to the messages on the first jms server and never get to read the messages on jms server JB as i guess i am able to connect to JMS Server JA so i never try and connect to JB? What to do about this?
Edited by: user4828945 on Mar 23, 2009 2:32 PM

Allocation of consumers wouldn't take into account the number of messages on the queue - they'd be allocated randomly. The scenario you're proposing shouldn't happen though - WebLogic Server takes into account whether a member has consumers when sending to a distributed destination, but otherwise, assuming that Queue 1 and Queue 2 both have consumers, then distribution of load will be equal. It's not the amount of consumers that determine how many messages get sent to a distributed destination member - it's whether it has members at all.
Assuming that did occur initially though, you'd expect processing to be a little bit more intensive on the server with the queue holding 30 messages. It would pretty quickly even up though.
From that point forward, it would be somewhere between difficult and impossible to get to the second scenario, where you have an unequal number of messages in each distributed destination member, unless the work being sent with each message to an MDB can vary significantly in how long it would take to process.
Assuming (and it's a big if) you could get to that scenario, then the MDBs wouldn't switch over - they stay connected to a particular distributed destination member. And it's their connection to a member as a consumer that controls how WebLogic Server load balances messages (assuming default configuration) so that's part of what makes it unlikely to get there.
From going back to first principles in the documentation, it seems like your best result would actually be from deploying the MDB to the cluster - that way, there's no remote connections to JMS queues, and you get a pool of MDBs on each server instance.
Ref here: http://e-docs.bea.com/wls/docs81/ejb/message_beans.html

JMS Timestamp in a Uniform Distributed Queue on Weblogic Console

Dear Experts,
I should need a clarification on how JMS Timestamp is valorized in a Uniform Distributed Queue. I explain me better :
I will use the JMS Timestamp to re-order messages fetched from the Uniform Distributed Queue. Is it reliable ? How can I synchronize the this JMS property to be sure it is not dependent from physical machine where Uniform Distributed Queue is deployed ?
Thanks a lot,
Mike

Try posting this in the weblogic jms forum : WebLogic Server - JMS where you might get help from Tom Barnes who is the weblogic jms development team lead.
As far as I know time synchronization across machines should be a routine task for system admins. We had windows environment , where it was done using windows time service. The time server was configured on the domain controller and the time service running on the windows nodes periodically resynchronized its time with that of the time server.

OSB distributed queue proxy configuration

Similar Messages

Maybe you are looking for