JMS limiting number of messages

Is there a way to limit the number of messages or the amount of memory a jms queue uses? Currently having a problem with a queue bringing down the entire system when it gets flooded with messages.

Is this not possible with jms in oracles application server?

Similar Messages

My JMS 2 wish list - Part 3, number of message deliveries

I attended the JavaOne 2010 session on future JMS evolutions. During the session I described some current limitations or issues I'd like to be solved in a portable way. I've been adviced to share the issues to get feedback from the community. I will post each issue in a dedicated thread.
Issue 3 - How many times are topic messages delivered ?
This may seem to be a trivial question, but when clustering is involved, it's not.
JEE has strong support for clustering, but many JEE specifications do not define what is actually supported, and leaves room for application server specific features. This is the case for JMS in the various specifications involved (JMS, JEE, EJB, JCA).
The question is how many times are messages delivered and treated (e.g. once per cluster or once per application server)?
Note that to simplify the problem I will not address selectors, delivery modes or acknowledgement considerations. I will also only address business application clustering, not JMS implementation clustering.
When Queues are used the situation is quite clear, the message is delivered once whether you use clustering or not. But when Topics are used, there is no simple answer.
When a message is sent to a Topic, each currently active non-durable subscriber should receive the message once. If the receiving application is clustered, the message should be received one time per application server instance in the cluster. That's what we get with JBoss 4.2.3.
This is actually not always the case. One example with WebSphere 6.1:
- A business application is deployed to a cluster of two application servers
- The JMS message engine is also deployed to a cluster of two application servers
- The application uses a MDB with a non-durable subscription to a Topic
- A message is sent to that Topic
If the two clusters are different, then the message is received by one MDB on each application instance, so the message is treated twice. But if the two clusters are actually the same, then the message is only received by one MDB instance on the application server where the message engine instance runs, so the message is treated once instead of twice. Painful.
For reliability considerations, enterprise applications often use durable subscriptions to Topics. This makes the situation even more complicated.
Durable subscriptions are identified by a subscription name. This defines the number of deliveries, meaning that the message should be delivered once per distinct subscription name.
JMS offers three ways to receive messages: Message Driven Beans (MDB), synchronous receptions using MessageConsumer:receive and explicit message listeners using MessageConsummer:setMessageListener. We won't address message listeners as they are forbidden on the server side by the JEE specifications.
When doing synchronous receptions or message listeners, the durable subscription name is managed by the developper using Session:createDurableSubscriber. This way it is possible (it is actually required by the JMS specification) to give a different name per application instance in the cluster to choose the number of times the messages are received.
With MDB we cannot officially manage the subscription name, so there is not portable control of the number of messages delivery. Note that we cannot manage the client ID either. In more details, both client ID and subscription name are valid parameters as per the JCA specification, but they are not according to the EJB specification.
We need precise, portable and cluster compliant semantics about the number of time JMS messages get delivered.

gimbal2 wrote:
A portable solution would be useful.You could already do it now by leveraging the Timer functionality that has been part of the EJB spec since JEE 1.4. In stead of sending the message directly, let the timer do it after the delay you specify. That would make it portable with current tech.
I can't be sure what other implications that might have though, such as in the area of performance and resource usage - I can imagine you wouldn't want to use a timer when you need to send large volumes of messages.In the original requirement, the message is put in the queue immediately by a call to queuesender.send(message) and there's a delivery in delay to a consumer.
Whereas in this solution, the delay is in the message delivery to the queue itself.
IMHO there's a subtle but important difference here.What would for example happen if posting the message to the queue is in the scope of a distributed JTA transaction? You can definitely include the timer call to be in the scope of the transaction, but now you will have to account for the fact and there may be an error when the message is delivered which has to be handled explicitly. In the original scenario the tx would automatically rollback.
cheers,
ram.

TS2755 how do i track the number of messages sent? i am on a limited sms plan so i want to know how many messages was i able to send in a month. is there an (free) app for it??

how do i track the number of messages sent? i am on a limited sms plan so i want to know how many messages was i able to send in a month. is there an (free) app for it??

Doubtful unless your carrier has an app that includes the option.
My carrier has an app that I can check current usage and past usage with a previous bill and pay the bill.

JMS: limiting message read

Hi,
In our solution, the proxy service reads from the source JMS topic, and query a table based in the request message. Then does the transformation to send the message to target system.
In the source JMS topic, at the same time 5000 messages are getting published. But the proxy is unable to process all of them. We are getting "BEA-380000 Error Reason : Read timed out " error from the business service which queries a table.
Is there a way to restrict the number of messages picked from JMS.
Thanks,
Vinoth

Hi,
In our solution, the proxy service reads from the source JMS topic, and query a table based in the request message. Then does the transformation to send the message to target system.
In the source JMS topic, at the same time 5000 messages are getting published. But the proxy is unable to process all of them. We are getting "BEA-380000 Error Reason : Read timed out " error from the business service which queries a table.
Is there a way to restrict the number of messages picked from JMS.
Thanks,
Vinoth

How do i find the number of messages in a queue

Sorry if this is too trivial, but i haven't been able to figure out how to determine the number of messages in a queue. business case being that i can only have 3 messages in the send queue, so i need to stop sending if there are 3 outstanding messages still in the send queue.
Can someone point the way?
Thanks,
Nilesh

Hi,
To get the depth using JMS you must create a QueueBrowse and browse the entire queue. Its generally horribly inefficient if you want to do it with any regularity.
In Hermes I have had to write plugins that open separate connections to providers using their non-JMS APIs or JMX and get that kind of information that way.
Look at the getDepth() method in this JBoss plugin for an example that uses JMX:
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/jbossmq/JBossMQAdmin.java?view=markup
And here is one for WebSphereMQ that uses one of its many APIs..
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/mq/MQSeriesAdmin.java?view=markup
Colin.
http://hermesjms.com

Ways to Calculate Number of Messages in OpenMQ

Hello All,
I was wondering if there is a way to calculate Number of messages already present in a Queue (OpenMQ).
1. One way is to make a synchronized static variable .. On each push increment and on listeners pull decrement it. But it have its own flaws i.e On system shutdown we will loss this info even if the messages exists in the queue. OR if me make it persistent then it will take extra processing time.
Do some body know any other way to do it ? I have to do it using JAVA code.
Kind Regards
Shakeel Abbas

Thank you Nigel,
For others information i am pasting some code here..
import java.io.IOException;
import javax.management.JMException;
import javax.management.MBeanServerConnection;
import javax.management.MalformedObjectNameException;
import javax.management.ObjectName;
import javax.management.remote.JMXConnector;
import com.sun.messaging.AdminConnectionFactory;
import com.sun.messaging.jms.management.server.DestinationAttributes;
import com.sun.messaging.jms.management.server.DestinationType;
import com.sun.messaging.jms.management.server.MQObjectName;
Public Class MonitorQueue
public static void main(String[] args) {
          try {
               ObjectName destMonitorName
               = MQObjectName.createDestinationMonitor(DestinationType.QUEUE, "queueNAme");
               // Create admin connection factory for default host and port (localhost:7676)
                  AdminConnectionFactory acf = new AdminConnectionFactory();
               // Get JMX connector using default user name (admin) and password (admin)
                  JMXConnector jmxc = acf.createConnection("admin","admin");
               // Get MBean server connection
                  MBeanServerConnection mbsc = jmxc.getMBeanServerConnection();
                  System.out.println(mbsc.getAttribute(destMonitorName, DestinationAttributes.NUM_MSGS));
          } catch (MalformedObjectNameException e1) {
               // TODO Auto-generated catch block
               e1.printStackTrace();
          } catch (NullPointerException e1) {
               // TODO Auto-generated catch block
               e1.printStackTrace();
          } catch (JMException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
          } catch (IOException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
}Stay Happy Cheers
Shakeel Abbas

Count the number of message in remote queue.

Does any method in MQSeries or JMS, can count the number of message in remote queue.
I try to use QueueBrowser to browser, but got exception when browse the remote queue.
thanks.

You cannot read from, browse or query a remote MQ Queue, only write to it. Try www.mqseries.net or ibm website for any ways around this...

Number of Messages for a Topic

Hi Jeff,
          I suggest that you open a case with Customer Support.
          Jane Sampson
          Developer Relations Engineer
          BEA Support
          "Jeff Carey" <[email protected]> wrote in message
          news:[email protected]...
          >
          > A startup class reads a Topic that contains e-mail messages from the
          applications
          > of our CRM system. Due to a bug in the startup class a suitable course of
          action
          > wasn't followed upon receipt of an mail Exception. That resulted in
          e-mail not
          > being sent and many messages backed-up.
          >
          > Because e-mail is a critical part of our CRM system, our requirements
          providers
          > want E-mail monitored. The problem is how to do that for a Topic.
          >
          > Responses from you and others indicate there isn't a good solution. If
          querying
          > the JMS tables is as good a solution as any, what status of a message
          associated
          > with the Topic would indicate a message not yet processed? A count of
          those that
          > exceeds a configured value could indicate a mail problem may exist.
          >
          > "Jane Sampson" <[email protected]> wrote:
          > >Hi Jeff,
          > >
          > >WebLogic uses internal implementation to collect this information. There
          > >is
          > >no method that I know of in the JMS API to allow this. Is there a
          > >particular reason that your application needs to do this?
          > >
          > >Jane Sampson
          > >Developer Relations Engineer
          > >BEA Support
          > >
          > >"Jeff Carey" <[email protected]> wrote in message
          > >news:[email protected]...
          > >>
          > >> How can an application learn the number of messages on a Topic?
          > >>
          > >> The WebLogic Console in JMS/Durable Subscribers/<subscriber> shows
          > >the
          > >number
          > >> of unprocessed messages for the Destination Topic.
          > >>
          > >> Review of documentation didn't reveal either a JMS or WebLogic method
          > >to
          > >get the
          > >> number of messages. Did the WebLogic console get the information by
          > >querying
          > >> the database table jmsmessage for messages for the destid associated
          > >with
          > >the
          > >> Topic and with a particular status? If so, what status?
          > >>
          > >> We are using WebLogic 5.1.
          > >>
          > >> Thank you.
          > >
          > >
          >

JMS Binding: in/out message

Hi there,
Could anyone help with the following problem I'm facing with?
The problem is, the JMS Binding Component complains about the JMS MapMessage it received from a queue that was sent by an application client. Since the WSDL operation is in/out, according to the log JMS BC thinks
the JMSReplyTo field of the JMS message is not set. However, my application client does set this field.
On open esb, I have a JMS SU that provides request/reply JMS service. The WSDL for it is as follows:
<binding ...>
<jms:binding/>
<operation name="docServiceOperation">
<jms:operation destination="XWPDocQueue" destinationType="Queue" timeToLive="60000" redeliveryHandling="1:1000; 3:5000; 4:move(queue:DeadQueue)"/>
<input>
<jms:message messageType="MapMessage">
<jms:mapmessage>
<jms:mappart name="serviceName" part="serviceName" type="string"/>
</jms:mapmessage>
</jms:message>
</input>
<output>
<jms:message messageType="MapMessage">
<jms:mapmessage>
<jms:mappart name="message" part="message" type="string"/>
</jms:mapmessage>
</jms:message>
</output>
</operation>
</binding>
It's backed up by a BPEL SU.
The service assembly (with BPEL and JMS SU) is correctly deployed.
Now the problem is when the application client sends a MapMessage to the queue DocQueue, the JMS BC throws an erorr which says the JMS message is premature.
The application client code is something like this:
@Resource(mappedName = "jms/ConnectionFactory")
private static ConnectionFactory connectionFactory;
@Resource(mappedName = "XWPDocQueue")
private static Queue queue;
@Resource(mappedName="jms/XWPDocReplyQueue")
private static Queue replyQueue;
* Main method.
* @param args the destination used by the example
* and, optionally, the number of
* messages to send
public static void main(String[] args) {
try {
connection = connectionFactory.createConnection();
Session session = connection.createSession(
false,
Session.AUTO_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(dest);
MapMessage message = session.createMapMessage();
for (int i = 0; i < NUM_MSGS; i++) {
System.out.println("replayQueue="+replyQueue);
message.setJMSReplyTo(replyQueue);
message.setString("serviceName", "transformImmediateXBRL");
message.setString("version", "1.0");
message.setString("corelationid", "");
message.setString("env", "DEV");
message.setBoolean("timingReq", false);
message.setString("metadata", FileHelper.loadContent(metatdataFilename));
message.setString("payload", FileHelper.loadContent(payloadFilename));
message.setInt("status", 0);
message.setString("message", "");
message.setString("timingInfo", "");
producer.send(message);
* Send a non-text control message indicating end of
* messages.
producer.send(session.createMessage());
} catch (JMSException e) {
System.err.println("Exception occurred: " + e.toString());
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
The error trace on the server is:
[#|2008-05-27T12:54:22.512+1000|SEVERE|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=365;_ThreadName=JMSJCA sync #0(XWPDocQueue);_RequestID=ab5b3f47-ebde-48cd-bba9-82d3b0ff41c7;|JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WMessageIn@1201bbe] in onMessage: JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154
com.sun.jbi.jmsbc.MessageExchangeProcessingException: JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.processInboundRequest(InboundMessageProcessorListenerEndpoint.java:399)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.onMessage(InboundMessageProcessorListenerEndpoint.java:225)
at com.stc.jmsjca.core.Delivery.deliverToEndpoint(Delivery.java:1105)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.runOnceStdNoXA(SyncDelivery.java:700)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.run(SyncDelivery.java:757)
|#]
[#|2008-05-27T12:54:22.606+1000|INFO|sun-appserver9.1|com.stc.jmsjca.core.Delivery|_ThreadID=365;_ThreadName=JMSJCA sync #0(XWPDocQueue);|JMSJCA-E027: Message with msgid=[ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154] was seen 4 times. It will be forwarded (moved) to queue DeadQueue with msgid [ID:42905-137.172.75.188(eb:2d:3d:71:d4:7d)-4557-1211856862606]|#]
[#|2008-05-27T12:54:22.621+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=380;_ThreadName=JMSJCA sync #14(XWPDocQueue);_RequestID=642c7e8b-0fd9-404a-b494-dc8daa956325;|[Fatal Error] :1:1: Premature end of file.
|#]
[#|2008-05-27T12:54:22.621+1000|SEVERE|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=380;_ThreadName=JMSJCA sync #14(XWPDocQueue);_RequestID=642c7e8b-0fd9-404a-b494-dc8daa956325;|JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WMapMessageIn@451566] in onMessage: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:239)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at com.sun.jbi.jmsbc.XmlUtil.createDocumentFromInputSource(XmlUtil.java:74)
at com.sun.jbi.jmsbc.XmlUtil.createDocumentFromXML(XmlUtil.java:90)
at com.sun.jbi.jmsbc.JMSNormalizer.addPart(JMSNormalizer.java:587)
at com.sun.jbi.jmsbc.JMSNormalizer.buildMessagePayloadFromMapMessage(JMSNormalizer.java:339)
at com.sun.jbi.jmsbc.JMSNormalizer.buildMessagePayload(JMSNormalizer.java:232)
at com.sun.jbi.jmsbc.JMSNormalizer.normalize(JMSNormalizer.java:178)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.normalizeMessage(InboundMessageProcessorListenerEndpoint.java:691)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.processInboundRequest(InboundMessageProcessorListenerEndpoint.java:423)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.onMessage(InboundMessageProcessorListenerEndpoint.java:225)
at com.stc.jmsjca.core.Delivery.deliverToEndpoint(Delivery.java:1105)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.runOnceStdNoXA(SyncDelivery.java:700)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.run(SyncDelivery.java:757)
|#]
The JMS BC thinks the JMS message it received does not have a JMSReplyTo field, but my client does set this field to a live queue.
Does anyone know why? Thanks very much.
Skysword
Edited by: Skysword on May 27, 2008 11:59 PM

PicFlix is picture/video messaging. You can try removing that feature

Question When I do a search for an image I only have a limited number of images. There used to be a ton of pictures on my screen and an unlimited amount of pictures to look through. Is there a way of changing this back to the way it used to be???

Question
When I do a search for an image I only have a limited number of images. There used to be a ton of pictures on my screen and an unlimited amount of pictures to look through. Is there a way of changing this back to the way it used to be???

Thanks. So there's no means of knowing whether a text message has been delivered, not to mention time of delivery. Perhaps I've gone for the wrong phone. It might do a lot but seems to miss out on some basics.

Business Application Log how to suppress 'Number' of messages column

Dear SDN Members,
how is it possible to suppress the 'Number' column in a BAL output where the number of messages is printed?
Thanks and kind regards,
Cedrik

HI,
1. SERVERTHREADS does not contain/limit the count of sessions one can have .
2. Count of ports will help you decide what is the default SERVERTHREAD count , in your case its 20.
3. the count 20 signifies the number of threads which a transaction can use ( here threads are nothing by the operating system level threads, to do with the processes and processor).
4. If you have multiple transactions and you want to improve the performance of them ( in case of slow response or so). You can increase the thread count , to make more threads work for your transactions. Again , this does not limit the count of sessions .
5. I did not understand the obejctive behind limiting the sessions and avoiding users from accessing . I think , this defeats the whole purpose of having cubes then. You have many cubes ,and huge number of users who pull data and essbase and its kernel are capable of handling this . If you still want to restrcit, might as well set their security ( by letting them not to access cubes).
Hope this adds value
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

-1 number of messages in messages application

Hi,
Did anybody see -1 number of messages in messages application notification ?
I took screenshot quickly when i saw that. after that it disappear.
Just curious what causes that.

The only pure JMS solution is to create a QueueBrowser, iterate and count. Most JMS providers have a more efficient but proprietary API to do the same thing.
Dwayne

Maximum number of messages sent to a Queue?I hav

I am currently using Glassfish v2.1 and I have set up a queue to send and receive messages from with Sesion beans and MDBs respectively. However, I have noticed that I can send only a maximum of 1000 messages to the queue. Is there any reason why I cannot send more than 1000 messages to the queue? I do have a "developer" profile setup for the glassfish domain. Could that be the reason? Or is there some resource configuration setting that I need to modify?
I have setup the configuration properties as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 Resource Definitions //EN" "http://www.sun.com/software/appserver/dtds/sun-resources_1_3.dtd">
<resources>
<admin-object-resource
        enabled="true"
        jndi-name="jms/UpdateQueue"
        object-type="user"
        res-adapter="jmsra"
        res-type="javax.jms.Queue">
    <description/>
    <property name="Name" value="UpdatePhysicalQueue"/>
</admin-object-resource>
<connector-resource
        enabled="true" jndi-name="jms/UpdateQueueFactory"
        object-type="user"
        pool-name="jms/UpdateQueueFactoryPool">
    <description/>
</connector-resource>
<connector-connection-pool
        associate-with-thread="false"
        connection-creation-retry-attempts="0"
        connection-creation-retry-interval-in-seconds="10"
        connection-definition-name="javax.jms.QueueConnectionFactory"
        connection-leak-reclaim="false"
        connection-leak-timeout-in-seconds="0"
        fail-all-connections="false"
        idle-timeout-in-seconds="300"
        is-connection-validation-required="false"
        lazy-connection-association="false"
        lazy-connection-enlistment="false"
        match-connections="true"
        max-connection-usage-count="0"
        max-pool-size="32"
        max-wait-time-in-millis="60000"
        name="jms/UpdateFactoryPool"
        pool-resize-quantity="2"
        resource-adapter-name="jmsra"
        steady-pool-size="8"
        validate-atmost-once-period-in-seconds="0"/>
</resources>Edited by: happy_go_lucky_mate on Nov 16, 2009 10:00 AM

The imqbroker log states:
[17/Nov/2009:10:27:57 CST] ERROR sendMessage: Sending message failed. Connection ID: 427038234214377984:
com.sun.messaging.jmq.jmsserver.util.BrokerException: transaction failed: [B4303]: The maximum number of messages [1,000] that the producer can process in a single transaction (TID=427038234364096768) has been exceeded. Please either limit the # of messages per transaction or increase the imq.transaction.producer.maxNumMsgs property.Looks like the imq.transaction.producer.maxNumMsgs property is set to the default value of 1000. As per the documentation,
The maximum number of messages that a producer can process in a single transaction. It is recommended that the value be less than 5000 to prevent the exhausting of resources.
So what do I need to do if I need to send more than 5000 messages?

Is it possible to limit number of messages in Inbox?

Hello all,
I was wondering if there is any way to limit the number of messages that show in your Mail inbox. Similar to how the iPhone limits it to 200...
Thanks in advance,
-Chris

You could set up a smart mailbox to only show 200 of the messages in your inbox, with priority given to those most recently received...

How To list Total Number Of Message in specific queue

Hi All,
Message queue
How to list total number of message in specific queue using wlst command
Edited by: 666666 on Mar 8, 2012 4:42 AM

You might have better luck posting this one on the JMS forum....

JMS limiting number of messages

Similar Messages

Maybe you are looking for