ActiveMQJMSConsumer (Red Hat JBoss Enterprise Application Platform 7.2.0.Beta public API)

java.lang.Object
- org.apache.activemq.artemis.jms.client.ActiveMQJMSConsumer

All Implemented Interfaces:: AutoCloseable, JMSConsumer

public class ActiveMQJMSConsumer
extends Object
implements JMSConsumer

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`close()` Closes the `JMSConsumer`.
`MessageListener`	`getMessageListener()` Gets the `JMSConsumer`'s `MessageListener`.
`String`	`getMessageSelector()` Gets this `JMSConsumer`'s message selector expression.
`Message`	`receive()` Receives the next message produced for this `JMSConsumer`.
`Message`	`receive(long timeout)` Receives the next message that arrives within the specified timeout interval.
`<T> T`	`receiveBody(Class<T> c)` Receives the next message produced for this `JMSConsumer` and returns its body as an object of the specified type.
`<T> T`	`receiveBody(Class<T> c, long timeout)` Receives the next message produced for this `JMSConsumer` that arrives within the specified timeout period and returns its body as an object of the specified type.
`<T> T`	`receiveBodyNoWait(Class<T> c)` Receives the next message produced for this `JMSConsumer` if one is immediately available and returns its body as an object of the specified type.
`Message`	`receiveNoWait()` Receives the next message if one is immediately available.
`void`	`setMessageListener(MessageListener listener)` Sets the `JMSConsumer`'s `MessageListener`.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Method Detail
  - getMessageSelector
```
public String getMessageSelector()
```
    Description copied from interface: JMSConsumer
    
    Gets this JMSConsumer's message selector expression.
    
    Specified by:
    
    getMessageSelector in interface JMSConsumer
    
    Returns:
    
    this JMSConsumer's message selector, or null if no message selector exists for the JMSConsumer (that is, if the message selector was not set or was set to null or the empty string)
  - getMessageListener
```
public MessageListener getMessageListener()
                                   throws JMSRuntimeException
```
    Description copied from interface: JMSConsumer
    
    Gets the JMSConsumer's MessageListener.
    This method must not be used in a Java EE web or EJB application. Doing so may cause a JMSRuntimeException to be thrown though this is not guaranteed.
    Specified by:
    
    getMessageListener in interface JMSConsumer
    
    Returns:
    
    the JMSConsumer's MessageListener, or null if one was not set
    
    Throws:
    JMSRuntimeException - if the JMS provider fails to get the MessageListener for one of the following reasons:
    
    an internal error has occurred or
    this method has been called in a Java EE web or EJB application (though it is not guaranteed that an exception is thrown in this case)
    See Also:
    
    JMSConsumer.setMessageListener(javax.jms.MessageListener)
  - setMessageListener
```
public void setMessageListener(MessageListener listener)
                        throws JMSRuntimeException
```
    Description copied from interface: JMSConsumer
    
    Sets the JMSConsumer's MessageListener.
    Setting the MessageListener to null is the equivalent of unsetting the MessageListener for the JMSConsumer.
    The effect of calling this method while messages are being consumed by an existing listener or the JMSConsumer is being used to consume messages synchronously is undefined.
    This method must not be used in a Java EE web or EJB application. Doing so may cause a JMSRuntimeException to be thrown though this is not guaranteed.
    Specified by:
    
    setMessageListener in interface JMSConsumer
    
    Parameters:
    
    listener - the listener to which the messages are to be delivered
    
    Throws:
    JMSRuntimeException - if the JMS provider fails to set the JMSConsumer's MessageListener for one of the following reasons:
    
    an internal error has occurred or
    this method has been called in a Java EE web or EJB application (though it is not guaranteed that an exception is thrown in this case)
    See Also:
    
    JMSConsumer.getMessageListener()
  - receive
```
public Message receive()
```
    Description copied from interface: JMSConsumer
    
    Receives the next message produced for this JMSConsumer.
    This call blocks indefinitely until a message is produced or until this JMSConsumer is closed.
    If this receive is done within a transaction, the JMSConsumer retains the message until the transaction commits.
    
    Specified by:
    
    receive in interface JMSConsumer
    
    Returns:
    
    the next message produced for this JMSConsumer, or null if this JMSConsumer is concurrently closed
  - receive
```
public Message receive(long timeout)
```
    Description copied from interface: JMSConsumer
    
    Receives the next message that arrives within the specified timeout interval.
    This call blocks until a message arrives, the timeout expires, or this JMSConsumer is closed. A timeout of zero never expires, and the call blocks indefinitely.
    
    Specified by:
    
    receive in interface JMSConsumer
    
    Parameters:
    
    timeout - the timeout value (in milliseconds)
    
    Returns:
    
    the next message produced for this JMSConsumer, or null if the timeout expires or this JMSConsumer is concurrently closed
  - receiveNoWait
```
public Message receiveNoWait()
```
    Description copied from interface: JMSConsumer
    
    Receives the next message if one is immediately available.
    
    Specified by:
    
    receiveNoWait in interface JMSConsumer
    
    Returns:
    
    the next message produced for this JMSConsumer, or null if one is not available
  - close
```
public void close()
```
    Description copied from interface: JMSConsumer
    
    Closes the JMSConsumer.
    Since a provider may allocate some resources on behalf of a JMSConsumer outside the Java virtual machine, clients should close them when they are not needed. Relying on garbage collection to eventually reclaim these resources may not be timely enough.
    This call will block until a receive call in progress on this consumer has completed. A blocked receive call returns null when this consumer is closed.
    If this method is called whilst a message listener is in progress in another thread then it will block until the message listener has completed.
    This method may be called from a message listener's onMessage method on its own consumer. After this method returns the onMessage method will be allowed to complete normally.
    This method is the only JMSConsumer method that can be called concurrently.
    
    Specified by:
    
    close in interface AutoCloseable
    
    Specified by:
    
    close in interface JMSConsumer
  - receiveBody
```
public <T> T receiveBody(Class<T> c)
```
    Description copied from interface: JMSConsumer
    Receives the next message produced for this JMSConsumer and returns its body as an object of the specified type. This method may be used to receive any type of message except for StreamMessage and Message, so long as the message has a body which is capable of being assigned to the specified type. This means that the specified class or interface must either be the same as, or a superclass or superinterface of, the class of the message body. If the message is not one of the supported types, or its body cannot be assigned to the specified type, or it has no body, then a MessageFormatRuntimeException is thrown.
    This method does not give access to the message headers or properties (such as the JMSRedelivered message header field or the JMSXDeliveryCount message property) and should only be used if the application has no need to access them.
    This call blocks indefinitely until a message is produced or until this JMSConsumer is closed.
    If this method is called within a transaction, the JMSConsumer retains the message until the transaction commits.
    The result of this method throwing a MessageFormatRuntimeException depends on the session mode:
    - AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE: The JMS provider will behave as if the unsuccessful call to receiveBody had not occurred. The message will be delivered again before any subsequent messages.
      This is not considered to be redelivery and does not cause the JMSRedelivered message header field to be set or the JMSXDeliveryCount message property to be incremented.
    - CLIENT_ACKNOWLEDGE: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again.
      As with any message that is delivered with a session mode of CLIENT_ACKNOWLEDGE, the message will not be acknowledged until acknowledge is called on the JMSContext. If an application wishes to have the failed message redelivered, it must call recover on the JMSContext. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
    - Transacted session: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again.
      As with any message that is delivered in a transacted session, the transaction will remain uncommitted until the transaction is committed or rolled back by the application. If an application wishes to have the failed message redelivered, it must roll back the transaction. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
    Specified by:
    
    receiveBody in interface JMSConsumer
    
    Parameters:
    
    c - The type to which the body of the next message should be assigned.
    If the next message is expected to be a TextMessage then this should be set to String.class or another class to which a String is assignable.
    If the next message is expected to be a ObjectMessage then this should be set to java.io.Serializable.class or another class to which the body is assignable.
    If the next message is expected to be a MapMessage then this should be set to java.util.Map.class (or java.lang.Object.class).
    If the next message is expected to be a BytesMessage then this should be set to byte[].class (or java.lang.Object.class).
    
    Returns:
    
    the body of the next message produced for this JMSConsumer, or null if this JMSConsumer is concurrently closed
  - receiveBody
```
public <T> T receiveBody(Class<T> c,
                         long timeout)
```
    Description copied from interface: JMSConsumer
    Receives the next message produced for this JMSConsumer that arrives within the specified timeout period and returns its body as an object of the specified type. This method may be used to receive any type of message except for StreamMessage and Message, so long as the message has a body which is capable of being assigned to the specified type. This means that the specified class or interface must either be the same as, or a superclass or superinterface of, the class of the message body. If the message is not one of the supported types, or its body cannot be assigned to the specified type, or it has no body, then a MessageFormatRuntimeException is thrown.
    This method does not give access to the message headers or properties (such as the JMSRedelivered message header field or the JMSXDeliveryCount message property) and should only be used if the application has no need to access them.
    This call blocks until a message arrives, the timeout expires, or this JMSConsumer is closed. A timeout of zero never expires, and the call blocks indefinitely.
    If this method is called within a transaction, the JMSConsumer retains the message until the transaction commits.
    The result of this method throwing a MessageFormatRuntimeException depends on the session mode:
    - AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE: The JMS provider will behave as if the unsuccessful call to receiveBody had not occurred. The message will be delivered again before any subsequent messages.
      This is not considered to be redelivery and does not cause the JMSRedelivered message header field to be set or the JMSXDeliveryCount message property to be incremented.
    - CLIENT_ACKNOWLEDGE: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again.
      As with any message that is delivered with a session mode of CLIENT_ACKNOWLEDGE, the message will not be acknowledged until acknowledge is called on the JMSContext. If an application wishes to have the failed message redelivered, it must call recover on the JMSContext. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
    - Transacted session: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again.
      As with any message that is delivered in a transacted session, the transaction will remain uncommitted until the transaction is committed or rolled back by the application. If an application wishes to have the failed message redelivered, it must roll back the transaction. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
    Specified by:
    
    receiveBody in interface JMSConsumer
    
    Parameters:
    
    c - The type to which the body of the next message should be assigned.
    If the next message is expected to be a TextMessage then this should be set to String.class or another class to which a String is assignable.
    If the next message is expected to be a ObjectMessage then this should be set to java.io.Serializable.class or another class to which the body is assignable.
    If the next message is expected to be a MapMessage then this should be set to java.util.Map.class (or java.lang.Object.class).
    If the next message is expected to be a BytesMessage then this should be set to byte[].class (or java.lang.Object.class).
    
    Returns:
    
    the body of the next message produced for this JMSConsumer, or null if the timeout expires or this JMSConsumer is concurrently closed
  - receiveBodyNoWait
```
public <T> T receiveBodyNoWait(Class<T> c)
```
    Description copied from interface: JMSConsumer
    Receives the next message produced for this JMSConsumer if one is immediately available and returns its body as an object of the specified type. This method may be used to receive any type of message except for StreamMessage and Message, so long as the message has a body which is capable of being assigned to the specified type. This means that the specified class or interface must either be the same as, or a superclass or superinterface of, the class of the message body. If the message is not one of the supported types, or its body cannot be assigned to the specified type, or it has no body, then a MessageFormatRuntimeException is thrown.
    This method does not give access to the message headers or properties (such as the JMSRedelivered message header field or the JMSXDeliveryCount message property) and should only be used if the application has no need to access them.
    If a message is not immediately available null is returned.
    If this method is called within a transaction, the JMSConsumer retains the message until the transaction commits.
    The result of this method throwing a MessageFormatRuntimeException depends on the session mode:
    - AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE: The JMS provider will behave as if the unsuccessful call to receiveBodyNoWait had not occurred. The message will be delivered again before any subsequent messages.
      This is not considered to be redelivery and does not cause the JMSRedelivered message header field to be set or the JMSXDeliveryCount message property to be incremented.
    - CLIENT_ACKNOWLEDGE: The JMS provider will behave as if the call to receiveBodyNoWait had been successful and will not deliver the message again.
      As with any message that is delivered with a session mode of CLIENT_ACKNOWLEDGE, the message will not be acknowledged until acknowledge is called on the JMSContext. If an application wishes to have the failed message redelivered, it must call recover on the JMSContext. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
    - Transacted session: The JMS provider will behave as if the call to receiveBodyNoWait had been successful and will not deliver the message again.
      As with any message that is delivered in a transacted session, the transaction will remain uncommitted until the transaction is committed or rolled back by the application. If an application wishes to have the failed message redelivered, it must roll back the transaction. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
    Specified by:
    
    receiveBodyNoWait in interface JMSConsumer
    
    Parameters:
    
    c - The type to which the body of the next message should be assigned.
    If the next message is expected to be a TextMessage then this should be set to String.class or another class to which a String is assignable.
    If the next message is expected to be a ObjectMessage then this should be set to java.io.Serializable.class or another class to which the body is assignable.
    If the next message is expected to be a MapMessage then this should be set to java.util.Map.class (or java.lang.Object.class).
    If the next message is expected to be a BytesMessage then this should be set to byte[].class (or java.lang.Object.class).
    
    Returns:
    
    the body of the next message produced for this JMSConsumer, or null if one is not immediately available or this JMSConsumer is concurrently closed

Class ActiveMQJMSConsumer

Method Summary

Methods inherited from class java.lang.Object

Method Detail

getMessageSelector

getMessageListener

setMessageListener

receive

receive

receiveNoWait

close

receiveBody

receiveBody

receiveBodyNoWait