Class ActiveMQJMSConsumer
- All Implemented Interfaces:
JMSConsumer,AutoCloseable
-
Method Summary
Modifier and TypeMethodDescriptionvoidclose()Closes theJMSConsumer.Gets theJMSConsumer'sMessageListener.Gets thisJMSConsumer's message selector expression.receive()Receives the next message produced for thisJMSConsumer.receive(long timeout) Receives the next message that arrives within the specified timeout interval.<T> TreceiveBody(Class<T> c) Receives the next message produced for thisJMSConsumerand returns its body as an object of the specified type.<T> TreceiveBody(Class<T> c, long timeout) Receives the next message produced for thisJMSConsumerthat arrives within the specified timeout period and returns its body as an object of the specified type.<T> TreceiveBodyNoWait(Class<T> c) Receives the next message produced for thisJMSConsumerif one is immediately available and returns its body as an object of the specified type.Receives the next message if one is immediately available.voidsetMessageListener(MessageListener listener) Sets theJMSConsumer'sMessageListener.
-
Method Details
-
getMessageSelector
Description copied from interface:JMSConsumerGets thisJMSConsumer's message selector expression.- Specified by:
getMessageSelectorin interfaceJMSConsumer- Returns:
- this
JMSConsumer's message selector, or null if no message selector exists for theJMSConsumer(that is, if the message selector was not set or was set to null or the empty string)
-
getMessageListener
Description copied from interface:JMSConsumerGets theJMSConsumer'sMessageListener.This method must not be used in a Jakarta EE web or EJB application. Doing so may cause a
JMSRuntimeExceptionto be thrown though this is not guaranteed.- Specified by:
getMessageListenerin interfaceJMSConsumer- Returns:
- the
JMSConsumer'sMessageListener, or null if one was not set - Throws:
JMSRuntimeException- if the Jakarta Messaging provider fails to get theMessageListenerfor one of the following reasons:- an internal error has occurred or
- this method has been called in a Jakarta EE web or EJB application (though it is not guaranteed that an exception is thrown in this case)
- See Also:
-
setMessageListener
Description copied from interface:JMSConsumerSets theJMSConsumer'sMessageListener.Setting the
MessageListenerto null is the equivalent of unsetting theMessageListenerfor theJMSConsumer.The effect of calling this method while messages are being consumed by an existing listener or the
JMSConsumeris being used to consume messages synchronously is undefined.This method must not be used in a Jakarta EE web or EJB application. Doing so may cause a
JMSRuntimeExceptionto be thrown though this is not guaranteed.- Specified by:
setMessageListenerin interfaceJMSConsumer- Parameters:
listener- the listener to which the messages are to be delivered- Throws:
JMSRuntimeException- if the Jakarta Messaging provider fails to set theJMSConsumer'sMessageListenerfor one of the following reasons:- an internal error has occurred or
- this method has been called in a Jakarta EE web or EJB application (though it is not guaranteed that an exception is thrown in this case)
- See Also:
-
receive
Description copied from interface:JMSConsumerReceives the next message produced for thisJMSConsumer.This call blocks indefinitely until a message is produced or until this
JMSConsumeris closed.If this
receiveis done within a transaction, the JMSConsumer retains the message until the transaction commits.- Specified by:
receivein interfaceJMSConsumer- Returns:
- the next message produced for this
JMSConsumer, or null if thisJMSConsumeris concurrently closed
-
receive
Description copied from interface:JMSConsumerReceives the next message that arrives within the specified timeout interval.This call blocks until a message arrives, the timeout expires, or this
JMSConsumeris closed. Atimeoutof zero never expires, and the call blocks indefinitely.- Specified by:
receivein interfaceJMSConsumer- Parameters:
timeout- the timeout value (in milliseconds)- Returns:
- the next message produced for this
JMSConsumer, or null if the timeout expires or thisJMSConsumeris concurrently closed
-
receiveNoWait
Description copied from interface:JMSConsumerReceives the next message if one is immediately available.- Specified by:
receiveNoWaitin interfaceJMSConsumer- Returns:
- the next message produced for this
JMSConsumer, or null if one is not available
-
close
public void close()Description copied from interface:JMSConsumerCloses theJMSConsumer.Since a provider may allocate some resources on behalf of a
JMSConsumeroutside 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
receivecall in progress on this consumer has completed. A blockedreceivecall 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
onMessagemethod on its own consumer. After this method returns theonMessagemethod will be allowed to complete normally.This method is the only
JMSConsumermethod that can be called concurrently.- Specified by:
closein interfaceAutoCloseable- Specified by:
closein interfaceJMSConsumer
-
receiveBody
Description copied from interface:JMSConsumerReceives the next message produced for thisJMSConsumerand returns its body as an object of the specified type. This method may be used to receive any type of message except forStreamMessageandMessage, 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 aMessageFormatRuntimeExceptionis thrown.This method does not give access to the message headers or properties (such as the
JMSRedeliveredmessage header field or theJMSXDeliveryCountmessage 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
JMSConsumeris closed.If this method is called within a transaction, the
JMSConsumerretains the message until the transaction commits.The result of this method throwing a
MessageFormatRuntimeExceptiondepends on the session mode:AUTO_ACKNOWLEDGEorDUPS_OK_ACKNOWLEDGE: The Jakarta Messaging provider will behave as if the unsuccessful call toreceiveBodyhad not occurred. The message will be delivered again before any subsequent messages. This is not considered to be redelivery and does not cause theJMSRedeliveredmessage header field to be set or theJMSXDeliveryCountmessage property to be incremented.CLIENT_ACKNOWLEDGE: The Jakarta Messaging provider will behave as if the call toreceiveBodyhad been successful and will not deliver the message again. As with any message that is delivered with a session mode ofCLIENT_ACKNOWLEDGE, the message will not be acknowledged untilacknowledgeis called on theJMSContext. If an application wishes to have the failed message redelivered, it must callrecoveron theJMSContext. The redelivered message'sJMSRedeliveredmessage header field will be set and itsJMSXDeliveryCountmessage property will be incremented.- Transacted session: The Jakarta Messaging provider will behave as if the call to
receiveBodyhad 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'sJMSRedeliveredmessage header field will be set and itsJMSXDeliveryCountmessage property will be incremented.
- Specified by:
receiveBodyin interfaceJMSConsumer- Type Parameters:
T- The type of the message body- Parameters:
c- The type to which the body of the next message should be assigned.
If the next message is expected to be aTextMessagethen this should be set toString.classor another class to which aStringis assignable.
If the next message is expected to be aObjectMessagethen this should be set tojava.io.Serializable.classor another class to which the body is assignable.
If the next message is expected to be aMapMessagethen this should be set tojava.util.Map.class(orjava.lang.Object.class).
If the next message is expected to be aBytesMessagethen this should be set tobyte[].class(orjava.lang.Object.class).- Returns:
- the body of the next message produced for this
JMSConsumer, or null if thisJMSConsumeris concurrently closed
-
receiveBody
Description copied from interface:JMSConsumerReceives the next message produced for thisJMSConsumerthat 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 forStreamMessageandMessage, 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 aMessageFormatRuntimeExceptionis thrown.This method does not give access to the message headers or properties (such as the
JMSRedeliveredmessage header field or theJMSXDeliveryCountmessage 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
JMSConsumeris closed. A timeout of zero never expires, and the call blocks indefinitely.If this method is called within a transaction, the
JMSConsumerretains the message until the transaction commits.The result of this method throwing a
MessageFormatRuntimeExceptiondepends on the session mode:AUTO_ACKNOWLEDGEorDUPS_OK_ACKNOWLEDGE: The Jakarta Messaging provider will behave as if the unsuccessful call toreceiveBodyhad not occurred. The message will be delivered again before any subsequent messages. This is not considered to be redelivery and does not cause theJMSRedeliveredmessage header field to be set or theJMSXDeliveryCountmessage property to be incremented.CLIENT_ACKNOWLEDGE: The Jakarta Messaging provider will behave as if the call toreceiveBodyhad been successful and will not deliver the message again. As with any message that is delivered with a session mode ofCLIENT_ACKNOWLEDGE, the message will not be acknowledged untilacknowledgeis called on theJMSContext. If an application wishes to have the failed message redelivered, it must callrecoveron theJMSContext. The redelivered message'sJMSRedeliveredmessage header field will be set and itsJMSXDeliveryCountmessage property will be incremented.- Transacted session: The Jakarta Messaging provider will behave as if the call to
receiveBodyhad 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'sJMSRedeliveredmessage header field will be set and itsJMSXDeliveryCountmessage property will be incremented.
- Specified by:
receiveBodyin interfaceJMSConsumer- Type Parameters:
T- The message body type- Parameters:
c- The type to which the body of the next message should be assigned.
If the next message is expected to be aTextMessagethen this should be set toString.classor another class to which aStringis assignable.
If the next message is expected to be aObjectMessagethen this should be set tojava.io.Serializable.classor another class to which the body is assignable.
If the next message is expected to be aMapMessagethen this should be set tojava.util.Map.class(orjava.lang.Object.class).
If the next message is expected to be aBytesMessagethen this should be set tobyte[].class(orjava.lang.Object.class).timeout- The maximum amount of time this method blocks. Zero means blocking indefinitely.- Returns:
- the body of the next message produced for this
JMSConsumer, or null if the timeout expires or thisJMSConsumeris concurrently closed
-
receiveBodyNoWait
Description copied from interface:JMSConsumerReceives the next message produced for thisJMSConsumerif 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 forStreamMessageandMessage, 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 aMessageFormatRuntimeExceptionis thrown.This method does not give access to the message headers or properties (such as the
JMSRedeliveredmessage header field or theJMSXDeliveryCountmessage 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
JMSConsumerretains the message until the transaction commits.The result of this method throwing a
MessageFormatRuntimeExceptiondepends on the session mode:AUTO_ACKNOWLEDGEorDUPS_OK_ACKNOWLEDGE: The Jakarta Messaging provider will behave as if the unsuccessful call toreceiveBodyNoWaithad not occurred. The message will be delivered again before any subsequent messages. This is not considered to be redelivery and does not cause theJMSRedeliveredmessage header field to be set or theJMSXDeliveryCountmessage property to be incremented.CLIENT_ACKNOWLEDGE: The Jakarta Messaging provider will behave as if the call toreceiveBodyNoWaithad been successful and will not deliver the message again. As with any message that is delivered with a session mode ofCLIENT_ACKNOWLEDGE, the message will not be acknowledged untilacknowledgeis called on theJMSContext. If an application wishes to have the failed message redelivered, it must callrecoveron theJMSContext. The redelivered message'sJMSRedeliveredmessage header field will be set and itsJMSXDeliveryCountmessage property will be incremented.- Transacted session: The Jakarta Messaging provider will behave as if the call to
receiveBodyNoWaithad 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'sJMSRedeliveredmessage header field will be set and itsJMSXDeliveryCountmessage property will be incremented.
- Specified by:
receiveBodyNoWaitin interfaceJMSConsumer- Type Parameters:
T- The type of the message body- Parameters:
c- The type to which the body of the next message should be assigned.
If the next message is expected to be aTextMessagethen this should be set toString.classor another class to which aStringis assignable.
If the next message is expected to be aObjectMessagethen this should be set tojava.io.Serializable.classor another class to which the body is assignable.
If the next message is expected to be aMapMessagethen this should be set tojava.util.Map.class(orjava.lang.Object.class).
If the next message is expected to be aBytesMessagethen this should be set tobyte[].class(orjava.lang.Object.class).- Returns:
- the body of the next message produced for this
JMSConsumer, or null if one is not immediately available or thisJMSConsumeris concurrently closed
-