JMS Timestamp in a uniform distributed queue on Weblogic Console

Similar Questions

• How to put on a uniform Distributed queue/topic break

  Good day to all.  I'm under WebLogic 10.3.6.0.  When I create a standard queue or a topic, I have a control tab on the settings of the queue.  In this tab control, I can pause all of good things, production, consumption.

  When I went to HA, I made a uniform distributed queue.  I don't have the control tab.  The only option I see is to pause at startup.  Pause for a direct queue was very helpful.  How can you do with a distributed queue?

  Well, actually it does:

  "You can pause or resume the insertion during execution for all destinations on a JMS server, to a group of destinations that link to the same JMS model or to different destinations. The most recent configuration change always have priority, regardless of the level at which it is made (Server JMS, JMS model or level of destination). »

  So when you use a JMS server for your distributed destination, you can pause production, insertion and consumption on the JMS server.

  

  the Tracking tab shows what queues distributed it is 'manage '.

  

  by using the tab control, you can suspend and resume operations.

• BAM consume does not correctly uniform distributed queue?

  Hello

  We see that the EMS uses not correctly uniform Distributed queue, this is a limitation or're missing us some configurations?

  Thank you.

  Finally understood... looks like that BAM EMS does not create many consumers connecting to a UDQ

  Technical support article: BAM doesn't have several consumer for JMS (Doc ID 1493533.1) queues

  Open enhancement, delivery possible in 12 c

• Reading Messages from a uniform distributed queue without an MDB

  WebLogic Server Version: 10.3.4.0
  
  I am currently facing a problem trying to read messages from a queue of distributed uniform with a spring JMSTemplate Weblogic.
  We have a cluster created with 2 servers.
  Each server in the cluster has it's own server JMS (JMSServer-1, JMSServer-2), each has its own persistent store
  We have a JMSModule. This JMSModule contains a factory connections (Subdeployment = sub1 Target = mycluster) and also contains a uniform tail (Subdeployment = sub1 Target = MyCluster) distributed
  
  A peak at our Spring JNDITemplate configuration looks like:
  < bean id = "messagingJndiTemplate" class = "org.springframework.jndi.JndiTemplate" >
  < property name = "environment" >
  < Accessories >
  < prop key = "java.naming.factory.initial" > weblogic.jndi.WLInitialContextFactory < / prop >
  < prop key = "java.naming.provider.url" > t3://some.server.name1,some.server.name2:8001 < / prop >
  < / Accessories >
  < / property >
  < / bean >
  
  It seems that every time that I call the JMSTemplate.browse function in my client, I'll read the messages in the server 1. Then the next bed request messages that are found on server 2. Each request is sent around in circles.
  
  I then tried to change the JMSModule. The new JMSModule contains a factory connections (Subdeployment = sub1 Target = mycluster) and also contains a uniform distributed Queue (Subdeployment = sub2 Target = JMSServer-1, JMSServer-2)
  
  After this change, it seems that every time that I call the JMSTemplate.browse function, I'll read the messages in any server, I have a session with my client. If I'm logged on server 1, I can only see messages in Server 1 and vice versa.
  
  
  My question is, how to configure Weblogic to pass messages from TWO servers in my cluster? I guess since it was a cluster installation, I would get some sort of uniform distributed queue unique view to access via JNDI, but appears not to be the case.
  Thanks in advance.

  Browsers and receivers always attach to a single member of a destination distributed.

  WebLogic BMD, on the other hand, automatically handle the task of fixing the receivers to each Member and are fairly simple to code and use these days. If you have the possibility to use WL BMD, I recommend their use. (There is no equivalent for the browsers).

  Spring does not have the same STANDARD, but it seems not be a workaround for the spring receiver number (but not for browsers - receivers only). Here is a sample spring impl that attaches a subscription for each Member of a subject is distributed:
  http://sleeplessinslc.blogspot.com/2011/12/WebLogic-JMS-partitioned-distributed.html.

  If the foregoing is not useful and that you must scroll through each message on each server in the cluster, then you must write special code case to check each separately. There are two options to list the destinations and work with each of them - 'messages management' JMX mbean API (WLST Jython scripting or Java-based) and the availability of destination weblogic.jms.extensions API.

  HTH,

  Tom

• JMS uniform distributed Queue control unit, problem when a node crashes

  Hello
  I have the code according to which a post (with all of the control unit) to a line of uniform distribution in a cluster with two servers (Server1 and Server2) members.
  UDQ - addressing a subdeployment mapped to two servers JMS pointing to each of the Member servers
  -Factory connections using default targeting (I tried mapping them to deployment Sub too)
  
  serverContext javax.naming.InitialContext = 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 = qSession.createProducer (q) (weblogic.jms.extensions.WLMessageProducer);
  qSender.setUnitOfOrder ("MyUnitOfOrder");
  javax.jms.ObjectMessage message = qSession.createObjectMessage ();
  < String, Object > HashMap map = new HashMap < String, Object > ();
  Map.put ("something", "SomeObject" "");
  message.setObject (map);
  qSender.send (message);
  } catch (Exception e) {}
  }
  
  Steps followed:
  1 post a message of "Server1."
  2. the message picked up by "Server2."
  3. all fine
  4. stop "Server2."
  5 post a message of "Server1."
  6 ERROR: ' chopped format member of MyAppJMSModule! MyDistributedQ is MyAppJMSModule! MyJMSServer-2@MyDistributedQ who is not available.
  
  WebLogic version: 10.3.5
  
  Is there a way (except Path Service configuration) to operate "with control unit" for a UDQ, even if some Member servers go down this code?
  
  Thank you very much for your time.

  If you want to avoid using the Service path, then the alternative is to make members of highly available destination. This will help to ensure that the host for a particular Member PUA is in place.

  One approach to HA is to set up "service migration." For more information, see the white paper of the automatic Migration of Service to
  http://www.Oracle.com/technology/products/WebLogic/PDF/WebLogic-automatic-Service-Migration-whitepaper.PDF

  In addition, I recommend SEO best practices for JMS beginners and advanced users
  http://docs.Oracle.com/CD/E17904_01/Web.1111/e13738/best_practice.htm#JMSAD455 to help WL configuration in general.

  Hope this helps,

  Tom

• The OSB distributed queue proxy configuration

  I implemented a distributed WeblogicServer queue and I wonder how can I configure proxy OSB to consume her JMS messages. I have read the documentation on the Oracle website, and he told a group of distributed queues a bunch of local JMS queues in different servers which can be accesed through a JNDI name. This failover and load to provide balance to put in the queue of messages.
  The BSO a JMS destination proxy is configured with the following URL: jms://server:port / destination. So if I have a distributed queue that maps to two JMS, what server and port servers do I set proxy URL? Do I need to configure two different agents and one for JMS server1 to server2 JMS?
  
  Kind regards
  
  CCI

  For weblogic JMS, producer of message load balancing happens in 3 different places.

  1. to search for initial context - it depends on the URI that you specify in the call for Initial context. for example if you specify t3: / / localhost:7002, localhost:7003, all research context occur on port 7002. Port 7003 is used only if 7002 is out of service. So this supports the failover instead of the load balancing. If you want the load balancer for executive search, then you must use a dns based address dns cluster where the name to a resolution address different every time.

  2 - when a jms connection is created. The jms connection can be created with any managed server to which the connection factory caters to the. So, you can have your search for context on 7002, but real jms connection can get created on 7003. If the server affinity is enabled for the connection factory and then the jms connection will be created to the same server instance managed that in search of context that's happened.

  3 - when a message send a producer is run. Send message can land on any member of the cluster dd if NLB is enabled. If the server affinity is enabled, then the message will end up on dd members on the same instance of the server to which the jms connection has been made. For example suppose you have your jms client application has a connection to jms on ms1 and product message ends up on top of ms2, then the following path would have been taken.

  JMS client app - via jms---> ms1 - in-house connection transmits---> ms2 - message puts---> dd2

  I recommend you read the chapter JMS the book professional Oracle Weblogic Server where it is explained clearly.

• Message Listener listens only 1 queue in the configuration of distributed queues!

  Hi guys,.
  
  This may be the wrong place for this post.
  
  We have created a system of e-mail with the OSB proxies come and messages between distributed queues. After all this messages autour brewing, the messages themselves in a distributed queue where a java client is waiting to pick up the results. Our problem is that it is only reading one of the queues in this queue distributed.
  
  The following is the code segment that wants the message with a specific id:
  public Message (String queueName, String messageId) receiveMessage throws {FrameworkException}
  BytesMessage, bytesMessage = null;
  If (null == queueSession) {}
  init();
  }
  try {}
  Queue receiveQueue = lookupQueue (queueName);
  QueueReceiver queueReceiver = null;
  Channel 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 {...
  
  
  QueueReceiver.receive () will listen to all members in a distributed queue (spread over 2 servers managed in a cluster)?
  
  Thank you very much

  No.. Since you have a single consumer, he can listen to only one destination member.

  Is your java client to run in Server or an external client? If its operation in Server convert the client to an mdb.

  Since this one issue of jms, try to post in the forum of jms:
  WebLogic Server - JMS

• How to get multiple queues in a single queue in weblogic?

  Hello

  I have three queue q1, q2, q3, in which the message is posted. Is it possible to route the receiveing all message queues three to the queue that is unique so that I can create only a single MDB who will listen to this new queue instead of creating multilateral 3 development registration to the queue waiting banks q1, q2, q3.

  Any suggestions would be a great help.

  Concerning

  -Vinod

  Hi Vinod,

  1. I think you intend to ask, is possible to send messages from multiple queues of Weblogic to a single MQ? Answer is Yes, but again, you should have several listener/Consumers(For ex: MDBs) to consume the message of Weblogic queues and the post of MQ.

  2. Yes, it is possible (which transfers the message from IBM MQ to Weblogic Distributed queue). Note: Only the Member would receive the message (the basic principle of the queue).

  The best way to incorporate Weblogic with IBM MQ series is via a foreign JMS server. You can find more information on Oracle Section KM 972848.1

  Concerning

  Rosario

• Using distributed queues and factories in a weblogic cluster

  Hi all
  in our environment, we have an area that has two machines. One runs the AdminServer and Node1 and Node2 2 machine operation.
  For each node, I created a JMS server and a file corresponding to each machine shop.
  
  I also created a JMS Module containing our queues required, plants and subjects. Queues and topics are of uniform type distributed.
  I targeted this module to the cluster and experimented with creating a subdeployment. But what I recon, since all my resources have by default targeting
  activated, a subdeployment is unnecessary, they target which is covered by the JMS Module, right?
  
  However, I get an exception when the two nodes are rising:
  

   <Nov 4, 2008 11:47:01 AM EET> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member        
  MyJMSModule!MyJMSServer@myTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Couldn't connect to weblogic.rjvm.RJVMImpl@187766d - id: '-1415064081927280896S:10.0.0.5:
  [7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain        :NodeApp2' connect time: 'Tue Nov 04 11:47:01 EET 2008' - it is likely that the connection has already been shut down; nested exception is:
  5564732         java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@187766d - id: '-1415064081927280896S:10.48.92.70:[7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp2' 
  connect time: 'Tue Nov 04 11:47:01 EET 2008' - it is likely that the connection has already been shut down

  The two nodes are on the rise and running and management node. Is this the correct way to create the queues and topics for a clustered environment?
  
  Thank you
  
  Published by: dvm on November 4, 2008 03:12

  unicast is much easier to configure than multicast - not sure 100% of the consequences, but it works in my environment.

• Distributed queue is empty

  Hi all
  I have the following Setup on a cluster configuration:
  For each server managed, I created another JMS server (each using its own store of files) target the managed server.
  I also created a JMS Module referred to in the cluster, and there I have a distributed e-mail queue.
  
  After clearing the database of the application, he had a couple of (e-mail) messages left in the queue, what is the application
  trying to send. But given that the users have been removed, the MDB onMessage method gets a NullPointerException at some point.
  
  Is there a way I could safely remove this two messages in the queue? I think to delete manually the file that contains the file store
  on each server, but how I'd be certain that I don't remove any other message along?
  
  Currently I see in the newspapers that he tried to send e-mail as 7,000 times. I also put return limit in the queue at 3, but it
  does not appear to affect the old messages in the queue, it?
  
  Thank you

  In WL 10.3:

  -> Services-Messaging JMS Modules >-> > your_queue-> monitoring

  There is a button 'Show the Messages' normally grayed out above the queue members; Select the Member to press. You can delete messages.

• Connect to the Glassfish jms from the stand-alone client queue

  Hello
  I want to connect to the jms client standalone of jms queue. It works fine, when I left factory connections with default settings. When I change the UserName and Password properties (path in the Glassfish admin console: resources-> JMS resources-> connection-> myFactory factories) I get the following error:

  SEVERE: MQJMSRA_MC4001: constructor:Aborting:JMSException on createConnection=[C4060]: Login failed:  user=test, broker=hostaname:7676(59148)
  com.sun.messaging.jms.JMSSecurityException: [C4060]: Login failed:  user=test, broker=hostname:7676(59148)
       at com.sun.messaging.jmq.jmsclient.ProtocolHandler.authenticate(ProtocolHandler.java:1094)
       at com.sun.messaging.jmq.jmsclient.ProtocolHandler.hello(ProtocolHandler.java:1001)
       at com.sun.messaging.jmq.jmsclient.ProtocolHandler.hello(ProtocolHandler.java:896)
       at com.sun.messaging.jmq.jmsclient.ConnectionImpl.hello(ConnectionImpl.java:552)
       at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:2393)
       at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:1044)
       at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:430)
       at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:60)
       at com.sun.messaging.jmq.jmsclient.XAConnectionImpl.<init>(XAConnectionImpl.java:58)
       at com.sun.messaging.XAConnectionFactory.createXAConnection(XAConnectionFactory.java:91)
       at com.sun.messaging.jms.ra.ManagedConnection.<init>(ManagedConnection.java:194)
       at com.sun.messaging.jms.ra.ManagedConnectionFactory.createManagedConnection(ManagedConnectionFactory.java:223)
       at com.sun.enterprise.resource.ConnectorAllocator.createResource(ConnectorAllocator.java:136)
       at com.sun.enterprise.resource.AbstractResourcePool.createResource(AbstractResourcePool.java:937)
       at com.sun.enterprise.resource.AbstractResourcePool.createSingleResource(AbstractResourcePool.java:913)
       at com.sun.enterprise.resource.AbstractResourcePool.createResourceAndAddToPool(AbstractResourcePool.java:1883)
       at com.sun.enterprise.resource.AbstractResourcePool.createResources(AbstractResourcePool.java:979)
       at com.sun.enterprise.resource.AbstractResourcePool.initPool(AbstractResourcePool.java:228)
       at com.sun.enterprise.resource.AbstractResourcePool.internalGetResource(AbstractResourcePool.java:531)
       at com.sun.enterprise.resource.AbstractResourcePool.getResource(AbstractResourcePool.java:458)
       at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:248)
       at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:176)
       at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:337)
       at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)
       at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
       at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:158)
       at com.sun.messaging.jms.ra.ConnectionFactoryAdapter._allocateConnection(ConnectionFactoryAdapter.java:179)
       at com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createConnection(ConnectionFactoryAdapter.java:166)
       at org.jetel.connection.jms.JmsConnection.initConnection(JmsConnection.java:393)
       at org.jetel.connection.jms.JmsConnection.preExecute(JmsConnection.java:359)
       at org.jetel.graph.TransformationGraph.preExecute(TransformationGraph.java:476)
       at org.jetel.graph.runtime.WatchDog.call(WatchDog.java:191)
       at org.jetel.graph.runtime.WatchDog.call(WatchDog.java:64)
       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
       at java.util.concurrent.FutureTask.run(FutureTask.java:138)
       at java.lang.Thread.run(Thread.java:680)

  regardless that I provided as user and password.
  The code is:

                                Hashtable<String, String> properties = new Hashtable<String, String>();
                                properties.put(Context.INITIAL_CONTEXT_FACTORY, iniCtxFtory);
                                properties.put(Context.PROVIDER_URL, providerUrl);
                                initCtx = new InitialContext(properties);
                                ConnectionFactory factory = initCtx.lookup(conFtory);
                                connection = factory.createConnection(user, pwd);

  The last line throws the exception.
  For default parameters, the runtime of the line before the last that I have in the console:

  26-Jan-2011 09:33:55 com.sun.messaging.jms.ra.ResourceAdapter start
  INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
  26-Jan-2011 09:33:55 com.sun.messaging.jms.ra.ResourceAdapter start
  INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started:REMOTE
  26-Jan-2011 09:33:55 com.sun.messaging.jms.ra.ManagedConnectionFactory setPassword
  INFO: MQJMSRA_MF1101: setPassword:NOT setting default value
  26-Jan-2011 09:33:55 com.sun.messaging.jms.ra.ManagedConnectionFactory setUserName
  INFO: MQJMSRA_MF1101: setUserName:NOT setting default value=guest

  It also does not depend (as is < b > before asking the < /b >) the supplied user name and password.
  I have spent a lot of time looking for the solution on the internet, I found some similar questions, but not a solution. Someone at - it solved a similar problem? It is possible at all?

  You have created the user in the wrong place. Use the imqusermgr command line tool to create the user if you do not find the JMS admin section to create users (according to version GF you use)

• Activation of JMS logging to capture the body of the message for distributed Q uniform

  Hi all
  
  You have to connect the body of the JMS message for our PROD env. but we don't see any option 'All body' in JMSQueue-> registration for our uniform Distributed queue.
  
  Please let me know how we can meet our requirement.
  
  Thanks in advance.

  found the solution.
  This is a bug of know - [1377584.1 ID]

  Add under settings in the file config/jms should make the requirement. :

  
  true
  %header%,JMSCorrelationID,JMSDeliveryMode,JMSDestination,JMSExpiration,JMSMessageID,JMSPriority,JMSRedelivered,JMSReplyTo,JMSTimestamp,JMSType,%properties%,JMSXDeliveryCount,JMSXUserID,JMS_BEA_DeliveryTime,JMS_BEA_RedeliveryLimit,JMS_BEA_UnitOfOrder,*%body%*
  

  Published by: Bob may 10, 2013 11:53

• Message-Driven beans and the order of the messages in the JMS queues.

  Hi all

  We use Weblogic 10.3.6 and we have a cluster with 2 JMS servers. In our project, it is important to process messages in the order when they arrive in the queues.

  Our question is simple enough, the fact that Message-Driven Beans (of the sort that take up messages in parallel) follow the order of the messages? Or do we need to configure something to do this.

  Thank you!

  According to the oracle documentation:

  With the help of unit-of-Order with Destinations spread

  As already mentioned in the Message of treatment according to the specification of JMS, Service of Message in Java specifications (to http://www.oracle.com/technetwork/java/jms/index.html ) doesn't guarantee no message ordered delivery when applications use distributed queues. WebLogic JMS redirects messages with the same disorder unit and have a target distributed to the same distributed destination member. The Member is chosen by unit of the order of the destination configuration:

  • By using the Service path
  • The hash-based routing using

  You can also

  If you distribute, you can use control unit andmax-beans-in-free-pool:

  http://docs.Oracle.com/CD/E23943_01/Web.1111/e13814/mdbtuning.htm#BABBEFCA

  More information here:

  Using Message unit-of-Order - 11g Release 1 (10.3.6)

  Tuning Message-Driven Beans - 11g Release 1 (10.3.6)

  WebLogic Server (WLS) JMS mapping control unit works with uniform distribution Destinations (Doc ID 1310795.1)

  Best regards

  Luz

• WebLogic JMS queue - delayed Messages

  Hi all
  I am using WebLogic Server Version: 10.3.5.0 in a clustered environment.
  I use a uniform distributed queue. I investigated rate messages with a delivery so that they don't not be removed immediately and instead will wait until a specific time before their delivery. In the weblogic console, I see a field delivery time, but on all my posts, the value is (no value specified).
  I use BPEL and the JMS adapter to the queue of messages. Anyone know how I can configure this property to delay the messages?
  Thank you
  Robert

  I know that SOA JMS adapter has added new features to exploit features value-added WLS JMS in recent versions, but I don't think that the delivery time is in the plan.
  Your best bet would be to set the time to deliver on the factory of connections or the destination.

• Delay in the distributed forward queue attribute

  Dear experts,
  
  I have a question in mind about this attribute/property that you can set inside the line distributed in the administration console.
  
  According to the documentation/help for WebLogic 10.3
  This attribute (delay) has the following features:
  The number of seconds after which a member of the uniform of queues distributed with no consumer appliance will wait before his messages to other members of uniform distributed queues that have no consumer.
  
  Interpreting above, what I understand of the concept is that if a member in the distributed queue have not any consumer, the messages it will be passed on to other members with consumers. However, if a member who is already associated with a consumer and the consumer is killed after a period of time, will be transferred messages from that Member to other members with consumers?
  
  Since a member who, with no consumer is not considered for the production of message.
  
  Thank you.

  However, if a member who is already associated with a consumer and the consumer is killed after a period of time, will be transferred messages from that Member to other members with consumers?

  Yes.

  Tom