Class PulsarSession

java.lang.Object
com.datastax.oss.pulsar.jms.PulsarSession
All Implemented Interfaces:
AutoCloseable, Runnable, javax.jms.QueueSession, javax.jms.Session, javax.jms.TopicSession

public class PulsarSession extends Object implements javax.jms.Session, javax.jms.QueueSession, javax.jms.TopicSession
  • Field Summary

    Fields inherited from interface javax.jms.Session

    AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE, SESSION_TRANSACTED
  • Method Summary

    Modifier and Type
    Method
    Description
    void
     
    void
    Closes the session.
    void
    Commits all messages done in this transaction and releases any locks currently held.
    javax.jms.QueueBrowser
    createBrowser(javax.jms.Queue queue)
    Creates a QueueBrowser object to peek at the messages on the specified queue.
    javax.jms.QueueBrowser
    createBrowser(javax.jms.Queue queue, String messageSelector)
    Creates a QueueBrowser object to peek at the messages on the specified queue using a message selector.
    Creates a BytesMessage object.
    createConsumer(javax.jms.Destination destination)
    Creates a MessageConsumer for the specified destination.
    createConsumer(javax.jms.Destination destination, String messageSelector)
    Creates a MessageConsumer for the specified destination, using a message selector.
    createConsumer(javax.jms.Destination destination, String messageSelector, boolean noLocal)
    Creates a MessageConsumer for the specified destination, specifying a message selector and the noLocal parameter.
    javax.jms.MessageConsumer
    createDurableConsumer(javax.jms.Topic topic, String name)
    Creates an unshared durable subscription on the specified topic (if one does not already exist) and creates a consumer on that durable subscription.
    createDurableConsumer(javax.jms.Topic topic, String name, String messageSelector, boolean noLocal)
    Creates an unshared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription.
    javax.jms.TopicSubscriber
    createDurableSubscriber(javax.jms.Topic topic, String name)
    Creates an unshared durable subscription on the specified topic (if one does not already exist) and creates a consumer on that durable subscription.
    javax.jms.TopicSubscriber
    createDurableSubscriber(javax.jms.Topic topic, String name, String messageSelector, boolean noLocal)
    Creates an unshared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription.
    javax.jms.MapMessage
    Creates a MapMessage object.
    javax.jms.MapMessage
     
    javax.jms.Message
    Creates a Message object.
    javax.jms.ObjectMessage
    Creates an ObjectMessage object.
    javax.jms.ObjectMessage
    Creates an initialized ObjectMessage object.
    com.datastax.oss.pulsar.jms.PulsarMessageProducer
    createProducer(javax.jms.Destination destination)
    Creates a MessageProducer to send messages to the specified destination.
    javax.jms.TopicPublisher
    createPublisher(javax.jms.Topic topic)
     
    createQueue(String queueName)
    Creates a Queue object which encapsulates a specified provider-specific queue name.
    javax.jms.QueueReceiver
    createReceiver(javax.jms.Queue queue)
     
    javax.jms.QueueReceiver
    createReceiver(javax.jms.Queue queue, String s)
     
    javax.jms.QueueSender
    createSender(javax.jms.Queue queue)
     
    createSession(int sessionMode, Map<String,Object> customConfiguration)
    Build a new Sessopm that shares the same Connection, as JMSContext.createContext(int).
    javax.jms.MessageConsumer
    createSharedConsumer(javax.jms.Topic topic, String sharedSubscriptionName)
    Creates a shared non-durable subscription with the specified name on the specified topic (if one does not already exist) and creates a consumer on that subscription.
    createSharedConsumer(javax.jms.Topic topic, String sharedSubscriptionName, String messageSelector)
    Creates a shared non-durable subscription with the specified name on the specified topic (if one does not already exist) specifying a message selector, and creates a consumer on that subscription.
    javax.jms.MessageConsumer
    createSharedDurableConsumer(javax.jms.Topic topic, String name)
    Creates a shared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription.
    createSharedDurableConsumer(javax.jms.Topic topic, String name, String messageSelector)
    Creates a shared durable subscription on the specified topic (if one does not already exist), specifying a message selector, and creates a consumer on that durable subscription.
    javax.jms.StreamMessage
    Creates a StreamMessage object.
    javax.jms.TopicSubscriber
    createSubscriber(javax.jms.Topic topic)
     
    javax.jms.TopicSubscriber
    createSubscriber(javax.jms.Topic topic, String s, boolean b)
     
    javax.jms.TemporaryQueue
    Creates a TemporaryQueue object.
    javax.jms.TemporaryTopic
    Creates a TemporaryTopic object.
    javax.jms.TextMessage
    Creates a TextMessage object.
    javax.jms.TextMessage
    Creates an initialized TextMessage object.
    createTopic(String topicName)
    Creates a Topic object which encapsulates a specified provider-specific topic name.
    int
    Returns the acknowledgement mode of the session.
     
    javax.jms.MessageListener
    Returns the session's distinguished message listener (optional).
    boolean
    Indicates whether the session is in transacted mode.
    long
     
    boolean
     
    boolean
     
    boolean
     
    void
     
    void
    Stops message delivery in this session, and restarts message delivery with the oldest unacknowledged message.
    void
     
    protected void
    registerProducerWithTransaction(com.datastax.oss.pulsar.jms.PulsarMessageProducer producer)
     
    void
    Rolls back any messages done in this transaction and releases any locks currently held.
    void
    run()
    Optional operation, intended to be used only by Application Servers, not by ordinary JMS clients.
    void
    setJms20(boolean jms20)
     
    void
    setMessageListener(javax.jms.MessageListener listener)
    Sets the session's distinguished message listener (optional).
    void
    Unsubscribes a durable subscription that has been created by a client.

    Methods inherited from class java.lang.Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
  • Method Details

    • createSession

      public PulsarSession createSession(int sessionMode, Map<String,Object> customConfiguration) throws javax.jms.JMSException
      Build a new Sessopm that shares the same Connection, as JMSContext.createContext(int). But you can override some configuration settings, like "consumerConfig"
      Parameters:
      sessionMode -
      customConfiguration -
      Returns:
      a new Pulsar Session
      Throws:
      javax.jms.JMSException
    • registerProducerWithTransaction

      protected void registerProducerWithTransaction(com.datastax.oss.pulsar.jms.PulsarMessageProducer producer)
    • createBytesMessage

      public PulsarBytesMessage createBytesMessage() throws javax.jms.JMSException
      Creates a BytesMessage object. A BytesMessage object is used to send a message containing a stream of uninterpreted bytes.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createBytesMessage in interface javax.jms.Session
      Returns:
      A BytesMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createMapMessage

      public javax.jms.MapMessage createMapMessage() throws javax.jms.JMSException
      Creates a MapMessage object. A MapMessage object is used to send a self-defining set of name-value pairs, where names are String objects and values are primitive values in the Java programming language.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createMapMessage in interface javax.jms.Session
      Returns:
      A MapMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createMapMessage

      public javax.jms.MapMessage createMapMessage(Map<String,Object> body) throws javax.jms.JMSException
      Throws:
      javax.jms.JMSException
    • createMessage

      public javax.jms.Message createMessage() throws javax.jms.JMSException
      Creates a Message object. The Message interface is the root interface of all JMS messages. A Message object holds all the standard message header information. It can be sent when a message containing only header information is sufficient.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createMessage in interface javax.jms.Session
      Returns:
      A Message object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createObjectMessage

      public javax.jms.ObjectMessage createObjectMessage() throws javax.jms.JMSException
      Creates an ObjectMessage object. An ObjectMessage object is used to send a message that contains a serializable Java object.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createObjectMessage in interface javax.jms.Session
      Returns:
      A ObjectMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createObjectMessage

      public javax.jms.ObjectMessage createObjectMessage(Serializable object) throws javax.jms.JMSException
      Creates an initialized ObjectMessage object. An ObjectMessage object is used to send a message that contains a serializable Java object.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createObjectMessage in interface javax.jms.Session
      Parameters:
      object - the object to use to initialize this message
      Returns:
      A ObjectMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createStreamMessage

      public javax.jms.StreamMessage createStreamMessage() throws javax.jms.JMSException
      Creates a StreamMessage object. A StreamMessage object is used to send a self-defining stream of primitive values in the Java programming language.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createStreamMessage in interface javax.jms.Session
      Returns:
      A StreamMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createTextMessage

      public javax.jms.TextMessage createTextMessage() throws javax.jms.JMSException
      Creates a TextMessage object. A TextMessage object is used to send a message containing a String object.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createTextMessage in interface javax.jms.Session
      Returns:
      A TextMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • createTextMessage

      public javax.jms.TextMessage createTextMessage(String text) throws javax.jms.JMSException
      Creates an initialized TextMessage object. A TextMessage object is used to send a message containing a String.

      The message object returned may be sent using any Session or JMSContext. It is not restricted to being sent using the JMSContext used to create it.

      The message object returned may be optimised for use with the JMS provider used to create it. However it can be sent using any JMS provider, not just the JMS provider used to create it.

      Specified by:
      createTextMessage in interface javax.jms.Session
      Parameters:
      text - the string used to initialize this message
      Returns:
      A TextMessage object.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to create this message due to some internal error.
    • getTransacted

      public boolean getTransacted() throws javax.jms.JMSException
      Indicates whether the session is in transacted mode.
      Specified by:
      getTransacted in interface javax.jms.Session
      Returns:
      true if the session is in transacted mode
      Throws:
      javax.jms.JMSException - if the JMS provider fails to return the transaction mode due to some internal error.
    • getAcknowledgeMode

      public int getAcknowledgeMode() throws javax.jms.JMSException
      Returns the acknowledgement mode of the session. The acknowledgement mode is set at the time that the session is created. If the session is transacted, the acknowledgement mode is ignored.
      Specified by:
      getAcknowledgeMode in interface javax.jms.Session
      Returns:
      If the session is not transacted, returns the current acknowledgement mode for the session. If the session is transacted, returns SESSION_TRANSACTED.
      Throws:
      javax.jms.JMSException - if the JMS provider fails to return the acknowledgment mode due to some internal error.
      Since:
      JMS 1.1
      See Also:
      • Connection.createSession(boolean, int)
    • getTransactionStickyKey

      public long getTransactionStickyKey()
    • commit

      public void commit() throws javax.jms.JMSException
      Commits all messages done in this transaction and releases any locks currently held.

      This method must not return until any incomplete asynchronous send operations for this Session have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs.

      A CompletionListener callback method must not call commit on its own Session. Doing so will cause an IllegalStateException to be thrown.

      Specified by:
      commit in interface javax.jms.Session
      Throws:
      javax.jms.IllegalStateException -
      • the session is not using a local transaction
      • this method has been called by a CompletionListener callback method on its own Session
      javax.jms.JMSException - if the JMS provider fails to commit the transaction due to some internal error.
      javax.jms.TransactionRolledBackException - if the transaction is rolled back due to some internal error during commit.
    • rollback

      public void rollback() throws javax.jms.JMSException
      Rolls back any messages done in this transaction and releases any locks currently held.

      This method must not return until any incomplete asynchronous send operations for this Session have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs.

      A CompletionListener callback method must not call commit on its own Session. Doing so will cause an IllegalStateException to be thrown.

      Specified by:
      rollback in interface javax.jms.Session
      Throws:
      javax.jms.IllegalStateException -
      • the session is not using a local transaction
      • this method has been called by a CompletionListener callback method on its own Session
      javax.jms.JMSException - if the JMS provider fails to roll back the transaction due to some internal error.
    • close

      public void close() throws javax.jms.JMSException
      Closes the session.

      Since a provider may allocate some resources on behalf of a session outside the JVM, clients should close the resources when they are not needed. Relying on garbage collection to eventually reclaim these resources may not be timely enough.

      There is no need to close the producers and consumers of a closed session.

      This call will block until a receive call or message listener in progress has completed. A blocked message consumer receive call returns null when this session is closed.

      However if the close method is called from a message listener on its own Session, then it will either fail and throw a javax.jms.IllegalStateException, or it will succeed and close the Session, blocking until any pending receive call in progress has completed. If close succeeds and the acknowledge mode of the Session is set to AUTO_ACKNOWLEDGE, the current message will still be acknowledged automatically when the onMessage call completes.

      Since two alternative behaviors are permitted in this case, applications should avoid calling close from a message listener on its own Session because this is not portable.

      This method must not return until any incomplete asynchronous send operations for this Session have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs.

      For the avoidance of doubt, if an exception listener for this session's connection is running when close is invoked, there is no requirement for the close call to wait until the exception listener has returned before it may return.

      Closing a transacted session must roll back the transaction in progress.

      This method is the only Session method that can be called concurrently.

      A CompletionListener callback method must not call close on its own Session. Doing so will cause an IllegalStateException to be thrown.

      Invoking any other Session method on a closed session must throw a IllegalStateException. Closing a closed session must not throw an exception.

      Specified by:
      close in interface AutoCloseable
      Specified by:
      close in interface javax.jms.Session
      Throws:
      javax.jms.IllegalStateException -
      • this method has been called by a MessageListener on its own Session
      • this method has been called by a CompletionListener callback method on its own Session
      javax.jms.JMSException - if the JMS provider fails to close the session due to some internal error.
    • recover

      public void recover() throws javax.jms.JMSException
      Stops message delivery in this session, and restarts message delivery with the oldest unacknowledged message.

      All consumers deliver messages in a serial order. Acknowledging a received message automatically acknowledges all messages that have been delivered to the client.

      Restarting a session causes it to take the following actions:

      • Stop message delivery
      • Mark all messages that might have been delivered but not acknowledged as "redelivered"
      • Restart the delivery sequence including all unacknowledged messages that had been previously delivered. Redelivered messages do not have to be delivered in exactly their original delivery order.
      Specified by:
      recover in interface javax.jms.Session
      Throws:
      javax.jms.JMSException - if the JMS provider fails to stop and restart message delivery due to some internal error.
      javax.jms.IllegalStateException - if the method is called by a transacted session.
    • getMessageListener

      public javax.jms.MessageListener getMessageListener() throws javax.jms.JMSException
      Returns the session's distinguished message listener (optional).

      This method must not be used in a Java EE web or EJB application. Doing so may cause a JMSException to be thrown though this is not guaranteed.

      Specified by:
      getMessageListener in interface javax.jms.Session
      Returns:
      the distinguished message listener associated with this session
      Throws:
      javax.jms.JMSException - if the JMS provider fails to get the session's distinguished message listener for one of the following reasons:
      • an internal error has occurred
      • 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:
      • Session.setMessageListener(javax.jms.MessageListener)
      • ServerSessionPool
      • ServerSession
    • setMessageListener

      public void setMessageListener(javax.jms.MessageListener listener) throws javax.jms.JMSException
      Sets the session's distinguished message listener (optional).

      When the distinguished message listener is set, no other form of message receipt in the session can be used; however, all forms of sending messages are still supported.

      This is an expert facility not used by ordinary JMS clients.

      This method must not be used in a Java EE web or EJB application. Doing so may cause a JMSException to be thrown though this is not guaranteed.

      Specified by:
      setMessageListener in interface javax.jms.Session
      Parameters:
      listener - the message listener to associate with this session
      Throws:
      javax.jms.JMSException - if the JMS provider fails to set the session's distinguished message listener for one of the following reasons:
      • an internal error has occurred
      • 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:
      • Session.getMessageListener()
      • ServerSessionPool
      • ServerSession
    • run

      public void run()
      Optional operation, intended to be used only by Application Servers, not by ordinary JMS clients.

      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:
      run in interface Runnable
      Specified by:
      run in interface javax.jms.Session
      Throws:
      javax.jms.JMSRuntimeException - if 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:
      • ServerSession
    • createProducer

      public com.datastax.oss.pulsar.jms.PulsarMessageProducer createProducer(javax.jms.Destination destination) throws javax.jms.JMSException
      Creates a MessageProducer to send messages to the specified destination.

      A client uses a MessageProducer object to send messages to a destination. Since Queue and Topic both inherit from Destination, they can be used in the destination parameter to create a MessageProducer object.

      Specified by:
      createProducer in interface javax.jms.Session
      Parameters:
      destination - the Destination to send to, or null if this is a producer which does not have a specified destination.
      Returns:
      A MessageProducer to send messages.
      Throws:
      javax.jms.JMSException - if the session fails to create a MessageProducer due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid destination is specified.
      Since:
      JMS 1.1
    • createConsumer

      public PulsarMessageConsumer createConsumer(javax.jms.Destination destination) throws javax.jms.JMSException
      Creates a MessageConsumer for the specified destination. Since Queue and Topic both inherit from Destination, they can be used in the destination parameter to create a MessageConsumer.
      Specified by:
      createConsumer in interface javax.jms.Session
      Parameters:
      destination - the Destination to access.
      Returns:
      A MessageConsumer for the specified destination.
      Throws:
      javax.jms.JMSException - if the session fails to create a consumer due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid destination is specified.
      Since:
      JMS 1.1
    • createConsumer

      public PulsarMessageConsumer createConsumer(javax.jms.Destination destination, String messageSelector) throws javax.jms.JMSException
      Creates a MessageConsumer for the specified destination, using a message selector. Since Queue and Topic both inherit from Destination, they can be used in the destination parameter to create a MessageConsumer.

      A client uses a MessageConsumer object to receive messages that have been sent to a destination.

      Specified by:
      createConsumer in interface javax.jms.Session
      Parameters:
      destination - the Destination to access
      messageSelector - only messages with properties matching the message selector expression are delivered. A value of null or an empty string indicates that there is no message selector for the message consumer.
      Returns:
      A MessageConsumer for the specified destination.
      Throws:
      javax.jms.JMSException - if the session fails to create a MessageConsumer due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid destination is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      Since:
      JMS 1.1
    • createConsumer

      public PulsarMessageConsumer createConsumer(javax.jms.Destination destination, String messageSelector, boolean noLocal) throws javax.jms.JMSException
      Creates a MessageConsumer for the specified destination, specifying a message selector and the noLocal parameter.

      Since Queue and Topic both inherit from Destination, they can be used in the destination parameter to create a MessageConsumer.

      A client uses a MessageConsumer object to receive messages that have been published to a destination.

      The noLocal argument is for use when the destination is a topic and the session's connection is also being used to publish messages to that topic. If noLocal is set to true then the MessageConsumer will not receive messages published to the topic by its own connection. The default value of this argument is false. If the destination is a queue then the effect of setting noLocal to true is not specified.

      Specified by:
      createConsumer in interface javax.jms.Session
      Parameters:
      destination - the Destination to access
      messageSelector - only messages with properties matching the message selector expression are delivered. A value of null or an empty string indicates that there is no message selector for the message consumer.
      noLocal - - if true, and the destination is a topic, then the MessageConsumer will not receive messages published to the topic by its own connection.
      Returns:
      A MessageConsumer for the specified destination.
      Throws:
      javax.jms.JMSException - if the session fails to create a MessageConsumer due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid destination is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      Since:
      JMS 1.1
    • createSharedConsumer

      public javax.jms.MessageConsumer createSharedConsumer(javax.jms.Topic topic, String sharedSubscriptionName) throws javax.jms.JMSException
      Creates a shared non-durable subscription with the specified name on the specified topic (if one does not already exist) and creates a consumer on that subscription. This method creates the non-durable subscription without a message selector.

      If a shared non-durable subscription already exists with the same name and client identifier (if set), and the same topic and message selector value has been specified, then this method creates a MessageConsumer on the existing subscription.

      A non-durable shared subscription is used by a client which needs to be able to share the work of receiving messages from a topic subscription amongst multiple consumers. A non-durable shared subscription may therefore have more than one consumer. Each message from the subscription will be delivered to only one of the consumers on that subscription. Such a subscription is not persisted and will be deleted (together with any undelivered messages associated with it) when there are no consumers on it. The term "consumer" here means a MessageConsumer or JMSConsumer object in any client.

      A shared non-durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared non-durable subscription must use the same client identifier.

      If a shared non-durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the subscription, then a JMSException will be thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.

      Specified by:
      createSharedConsumer in interface javax.jms.Session
      Parameters:
      topic - the Topic to subscribe to
      sharedSubscriptionName - the name used to identify the shared non-durable subscription
      Returns:
      A shared non-durable subscription with the specified name on the specified topic.
      Throws:
      javax.jms.JMSException - if the session fails to create the shared non-durable subscription and MessageConsumer due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      Since:
      JMS 2.0
    • createSharedConsumer

      public PulsarMessageConsumer createSharedConsumer(javax.jms.Topic topic, String sharedSubscriptionName, String messageSelector) throws javax.jms.JMSException
      Creates a shared non-durable subscription with the specified name on the specified topic (if one does not already exist) specifying a message selector, and creates a consumer on that subscription.

      If a shared non-durable subscription already exists with the same name and client identifier (if set), and the same topic and message selector has been specified, then this method creates a MessageConsumer on the existing subscription.

      A non-durable shared subscription is used by a client which needs to be able to share the work of receiving messages from a topic subscription amongst multiple consumers. A non-durable shared subscription may therefore have more than one consumer. Each message from the subscription will be delivered to only one of the consumers on that subscription. Such a subscription is not persisted and will be deleted (together with any undelivered messages associated with it) when there are no consumers on it. The term "consumer" here means a MessageConsumer or JMSConsumer object in any client.

      A shared non-durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared non-durable subscription must use the same client identifier.

      If a shared non-durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the subscription, then a JMSException will be thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.

      Specified by:
      createSharedConsumer in interface javax.jms.Session
      Parameters:
      topic - the Topic to subscribe to
      sharedSubscriptionName - the name used to identify the shared non-durable subscription
      messageSelector - only messages with properties matching the message selector expression are added to the shared non-durable subscription. A value of null or an empty string indicates that there is no message selector for the shared non-durable subscription.
      Returns:
      A shared non-durable subscription with the specified name on the specified topic.
      Throws:
      javax.jms.JMSException - if the session fails to create the shared non-durable subscription and MessageConsumer due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      Since:
      JMS 2.0
    • createQueue

      public PulsarQueue createQueue(String queueName) throws javax.jms.JMSException
      Creates a Queue object which encapsulates a specified provider-specific queue name.

      The use of provider-specific queue names in an application may render the application non-portable. Portable applications are recommended to not use this method but instead look up an administratively-defined Queue object using JNDI.

      Note that this method simply creates an object that encapsulates the name of a queue. It does not create the physical queue in the JMS provider. JMS does not provide a method to create the physical queue, since this would be specific to a given JMS provider. Creating a physical queue is provider-specific and is typically an administrative task performed by an administrator, though some providers may create them automatically when needed. The one exception to this is the creation of a temporary queue, which is done using the createTemporaryQueue method.

      Specified by:
      createQueue in interface javax.jms.QueueSession
      Specified by:
      createQueue in interface javax.jms.Session
      Parameters:
      queueName - A provider-specific queue name
      Returns:
      a Queue object which encapsulates the specified name
      Throws:
      javax.jms.JMSException - if a Queue object cannot be created due to some internal error
    • createTopic

      public PulsarTopic createTopic(String topicName) throws javax.jms.JMSException
      Creates a Topic object which encapsulates a specified provider-specific topic name.

      The use of provider-specific topic names in an application may render the application non-portable. Portable applications are recommended to not use this method but instead look up an administratively-defined Topic object using JNDI.

      Note that this method simply creates an object that encapsulates the name of a topic. It does not create the physical topic in the JMS provider. JMS does not provide a method to create the physical topic, since this would be specific to a given JMS provider. Creating a physical topic is provider-specific and is typically an administrative task performed by an administrator, though some providers may create them automatically when needed. The one exception to this is the creation of a temporary topic, which is done using the createTemporaryTopic method.

      Specified by:
      createTopic in interface javax.jms.Session
      Specified by:
      createTopic in interface javax.jms.TopicSession
      Parameters:
      topicName - A provider-specific topic name
      Returns:
      a Topic object which encapsulates the specified name
      Throws:
      javax.jms.JMSException - if a Topic object cannot be created due to some internal error
    • createDurableSubscriber

      public javax.jms.TopicSubscriber createDurableSubscriber(javax.jms.Topic topic, String name) throws javax.jms.JMSException
      Creates an unshared durable subscription on the specified topic (if one does not already exist) and creates a consumer on that durable subscription. This method creates the durable subscription without a message selector and with a noLocal value of false.

      A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.

      A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method.

      This method may only be used with unshared durable subscriptions. Any durable subscription created using this method will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time. The term "consumer" here means a TopicSubscriber, MessageConsumer or JMSConsumer object in any client.

      An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier.

      If an unshared durable subscription already exists with the same name and client identifier, and the same topic, message selector and noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this method creates a TopicSubscriber on the existing durable subscription.

      If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown.

      If an unshared durable subscription already exists with the same name and client identifier but a different topic, message selector or noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.

      A shared durable subscription and an unshared durable subscription may not have the same name and client identifier. If a shared durable subscription already exists with the same name and client identifier then a JMSException is thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate.

      This method is identical to the corresponding createDurableConsumer method except that it returns a TopicSubscriber rather than a MessageConsumer to represent the consumer.

      Specified by:
      createDurableSubscriber in interface javax.jms.Session
      Specified by:
      createDurableSubscriber in interface javax.jms.TopicSession
      Parameters:
      topic - the non-temporary Topic to subscribe to
      name - the name used to identify this subscription
      Returns:
      An unshared durable subscription on the specified topic.
      Throws:
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.IllegalStateException - if the client identifier is unset
      javax.jms.JMSException -
      • if the session fails to create the unshared durable subscription and TopicSubscriber due to some internal error
      • if an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active
      • if a shared durable subscription already exists with the same name and client identifier
      Since:
      JMS 1.1
    • createDurableSubscriber

      public javax.jms.TopicSubscriber createDurableSubscriber(javax.jms.Topic topic, String name, String messageSelector, boolean noLocal) throws javax.jms.JMSException
      Creates an unshared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription.

      A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.

      A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method.

      This method may only be used with unshared durable subscriptions. Any durable subscription created using this method will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time. The term "consumer" here means a TopicSubscriber, MessageConsumer or JMSConsumer object in any client.

      An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier.

      If an unshared durable subscription already exists with the same name and client identifier, and the same topic, message selector and noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this method creates a TopicSubscriber on the existing durable subscription.

      If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown.

      If an unshared durable subscription already exists with the same name and client identifier but a different topic, message selector or noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.

      If noLocal is set to true then any messages published to the topic using this session's connection, or any other connection with the same client identifier, will not be added to the durable subscription.

      A shared durable subscription and an unshared durable subscription may not have the same name and client identifier. If a shared durable subscription already exists with the same name and client identifier then a JMSException is thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate.

      This method is identical to the corresponding createDurableConsumer method except that it returns a TopicSubscriber rather than a MessageConsumer to represent the consumer.

      Specified by:
      createDurableSubscriber in interface javax.jms.Session
      Specified by:
      createDurableSubscriber in interface javax.jms.TopicSession
      Parameters:
      topic - the non-temporary Topic to subscribe to
      name - the name used to identify this subscription
      messageSelector - only messages with properties matching the message selector expression are added to the durable subscription. A value of null or an empty string indicates that there is no message selector for the durable subscription.
      noLocal - if true then any messages published to the topic using this session's connection, or any other connection with the same client identifier, will not be added to the durable subscription.
      Returns:
      An unshared durable subscription on the specified topic.
      Throws:
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      javax.jms.IllegalStateException - if the client identifier is unset
      javax.jms.JMSException -
      • if the session fails to create the unshared durable subscription and TopicSubscriber due to some internal error
      • if an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active
      • if a shared durable subscription already exists with the same name and client identifier
      Since:
      JMS 1.1
    • createDurableConsumer

      public javax.jms.MessageConsumer createDurableConsumer(javax.jms.Topic topic, String name) throws javax.jms.JMSException
      Creates an unshared durable subscription on the specified topic (if one does not already exist) and creates a consumer on that durable subscription. This method creates the durable subscription without a message selector and with a noLocal value of false.

      A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.

      A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method.

      This method may only be used with unshared durable subscriptions. Any durable subscription created using this method will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time. The term "consumer" here means a TopicSubscriber, MessageConsumer or JMSConsumer object in any client.

      An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier.

      If an unshared durable subscription already exists with the same name and client identifier, and the same topic, message selector and noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this method creates a MessageConsumer on the existing durable subscription.

      If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown.

      If an unshared durable subscription already exists with the same name and client identifier but a different topic, message selector or noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.

      A shared durable subscription and an unshared durable subscription may not have the same name and client identifier. If a shared durable subscription already exists with the same name and client identifier then a JMSException is thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate.

      This method is identical to the corresponding createDurableSubscriber method except that it returns a MessageConsumer rather than a TopicSubscriber to represent the consumer.

      Specified by:
      createDurableConsumer in interface javax.jms.Session
      Parameters:
      topic - the non-temporary Topic to subscribe to
      name - the name used to identify this subscription
      Returns:
      An unshared durable subscription on the specified topic.
      Throws:
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.IllegalStateException - if the client identifier is unset
      javax.jms.JMSException -
      • if the session fails to create the unshared durable subscription and MessageConsumer due to some internal error
      • if an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active
      • if a shared durable subscription already exists with the same name and client identifier
      Since:
      JMS 2.0
    • createDurableConsumer

      public PulsarMessageConsumer createDurableConsumer(javax.jms.Topic topic, String name, String messageSelector, boolean noLocal) throws javax.jms.JMSException
      Creates an unshared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription.

      A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.

      A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method.

      This method may only be used with unshared durable subscriptions. Any durable subscription created using this method will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time. The term "consumer" here means a TopicSubscriber, MessageConsumer or JMSConsumer object in any client.

      An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier.

      If an unshared durable subscription already exists with the same name and client identifier, and the same topic, message selector and noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this method creates a MessageConsumer on the existing durable subscription.

      If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown.

      If an unshared durable subscription already exists with the same name and client identifier but a different topic, message selector or noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.

      If noLocal is set to true then any messages published to the topic using this session's connection, or any other connection with the same client identifier, will not be added to the durable subscription.

      A shared durable subscription and an unshared durable subscription may not have the same name and client identifier. If a shared durable subscription already exists with the same name and client identifier then a JMSException is thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate.

      This method is identical to the corresponding createDurableSubscriber method except that it returns a MessageConsumer rather than a TopicSubscriber to represent the consumer.

      Specified by:
      createDurableConsumer in interface javax.jms.Session
      Parameters:
      topic - the non-temporary Topic to subscribe to
      name - the name used to identify this subscription
      messageSelector - only messages with properties matching the message selector expression are added to the durable subscription. A value of null or an empty string indicates that there is no message selector for the durable subscription.
      noLocal - if true then any messages published to the topic using this session's connection, or any other connection with the same client identifier, will not be added to the durable subscription.
      Returns:
      An unshared durable subscription on the specified topic.
      Throws:
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      javax.jms.IllegalStateException - if the client identifier is unset
      javax.jms.JMSException -
      • if the session fails to create the unshared durable subscription and MessageConsumer due to some internal error
      • if an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active
      • if a shared durable subscription already exists with the same name and client identifier
      Since:
      JMS 2.0
    • createSharedDurableConsumer

      public javax.jms.MessageConsumer createSharedDurableConsumer(javax.jms.Topic topic, String name) throws javax.jms.JMSException
      Creates a shared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription. This method creates the durable subscription without a message selector.

      A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.

      A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method.

      This method may only be used with shared durable subscriptions. Any durable subscription created using this method will be shared. This means that multiple active (i.e. not closed) consumers on the subscription may exist at the same time. The term "consumer" here means a MessageConsumer or JMSConsumer object in any client.

      A shared durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared durable subscription must use the same client identifier.

      If a shared durable subscription already exists with the same name and client identifier (if set), and the same topic and message selector has been specified, then this method creates a MessageConsumer on the existing shared durable subscription.

      If a shared durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.

      If a shared durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown.

      A shared durable subscription and an unshared durable subscription may not have the same name and client identifier (if set). If an unshared durable subscription already exists with the same name and client identifier (if set) then a JMSException is thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.

      Specified by:
      createSharedDurableConsumer in interface javax.jms.Session
      Parameters:
      topic - the non-temporary Topic to subscribe to
      name - the name used to identify this subscription
      Returns:
      A shared durable subscription on the specified topic.
      Throws:
      javax.jms.JMSException -
      • if the session fails to create the shared durable subscription and MessageConsumer due to some internal error
      • if a shared durable subscription already exists with the same name and client identifier, but a different topic or message selector, and there is a consumer already active
      • if an unshared durable subscription already exists with the same name and client identifier
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      Since:
      JMS 2.0
    • createSharedDurableConsumer

      public PulsarMessageConsumer createSharedDurableConsumer(javax.jms.Topic topic, String name, String messageSelector) throws javax.jms.JMSException
      Creates a shared durable subscription on the specified topic (if one does not already exist), specifying a message selector, and creates a consumer on that durable subscription.

      A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.

      A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method.

      This method may only be used with shared durable subscriptions. Any durable subscription created using this method will be shared. This means that multiple active (i.e. not closed) consumers on the subscription may exist at the same time. The term "consumer" here means a MessageConsumer or JMSConsumer object in any client.

      A shared durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared durable subscription must use the same client identifier.

      If a shared durable subscription already exists with the same name and client identifier (if set), and the same topic and message selector has been specified, then this method creates a MessageConsumer on the existing shared durable subscription.

      If a shared durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.

      If a shared durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown.

      A shared durable subscription and an unshared durable subscription may not have the same name and client identifier (if set). If an unshared durable subscription already exists with the same name and client identifier (if set) then a JMSException is thrown.

      There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.

      Specified by:
      createSharedDurableConsumer in interface javax.jms.Session
      Parameters:
      topic - the non-temporary Topic to subscribe to
      name - the name used to identify this subscription
      messageSelector - only messages with properties matching the message selector expression are added to the durable subscription. A value of null or an empty string indicates that there is no message selector for the durable subscription.
      Returns:
      A shared durable subscription on the specified topic.
      Throws:
      javax.jms.JMSException -
      • if the session fails to create the shared durable subscription and MessageConsumer due to some internal error
      • if a shared durable subscription already exists with the same name and client identifier, but a different topic or message selector, and there is a consumer already active
      • if an unshared durable subscription already exists with the same name and client identifier
      javax.jms.InvalidDestinationException - if an invalid topic is specified.
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      Since:
      JMS 2.0
    • createBrowser

      public javax.jms.QueueBrowser createBrowser(javax.jms.Queue queue) throws javax.jms.JMSException
      Creates a QueueBrowser object to peek at the messages on the specified queue.
      Specified by:
      createBrowser in interface javax.jms.QueueSession
      Specified by:
      createBrowser in interface javax.jms.Session
      Parameters:
      queue - the queue to access
      Returns:
      A QueueBrowser object to peek at the messages on the specified queue.
      Throws:
      javax.jms.JMSException - if the session fails to create a browser due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid destination is specified
      Since:
      JMS 1.1
    • createBrowser

      public javax.jms.QueueBrowser createBrowser(javax.jms.Queue queue, String messageSelector) throws javax.jms.JMSException
      Creates a QueueBrowser object to peek at the messages on the specified queue using a message selector.
      Specified by:
      createBrowser in interface javax.jms.QueueSession
      Specified by:
      createBrowser in interface javax.jms.Session
      Parameters:
      queue - the queue to access
      messageSelector - only messages with properties matching the message selector expression are delivered. A value of null or an empty string indicates that there is no message selector for the message consumer.
      Returns:
      A QueueBrowser object to peek at the messages on the specified queue.
      Throws:
      javax.jms.JMSException - if the session fails to create a browser due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid destination is specified
      javax.jms.InvalidSelectorException - if the message selector is invalid.
      Since:
      JMS 1.1
    • createTemporaryQueue

      public javax.jms.TemporaryQueue createTemporaryQueue() throws javax.jms.JMSException
      Creates a TemporaryQueue object. Its lifetime will be that of the Connection unless it is deleted earlier.
      Specified by:
      createTemporaryQueue in interface javax.jms.QueueSession
      Specified by:
      createTemporaryQueue in interface javax.jms.Session
      Returns:
      a temporary queue identity
      Throws:
      javax.jms.JMSException - if the session fails to create a temporary queue due to some internal error.
      Since:
      JMS 1.1
    • createTemporaryTopic

      public javax.jms.TemporaryTopic createTemporaryTopic() throws javax.jms.JMSException
      Creates a TemporaryTopic object. Its lifetime will be that of the Connection unless it is deleted earlier.
      Specified by:
      createTemporaryTopic in interface javax.jms.Session
      Specified by:
      createTemporaryTopic in interface javax.jms.TopicSession
      Returns:
      a temporary topic identity
      Throws:
      javax.jms.JMSException - if the session fails to create a temporary topic due to some internal error.
      Since:
      JMS 1.1
    • unsubscribe

      public void unsubscribe(String name) throws javax.jms.JMSException
      Unsubscribes a durable subscription that has been created by a client.

      This method deletes the state being maintained on behalf of the subscriber by its provider.

      A durable subscription is identified by a name specified by the client and by the client identifier if set. If the client identifier was set when the durable subscription was created then a client which subsequently wishes to use this method to delete a durable subscription must use the same client identifier.

      It is erroneous for a client to delete a durable subscription while there is an active (not closed) consumer for the subscription, or while a consumed message is part of a pending transaction or has not been acknowledged in the session.

      Specified by:
      unsubscribe in interface javax.jms.Session
      Specified by:
      unsubscribe in interface javax.jms.TopicSession
      Parameters:
      name - the name used to identify this subscription
      Throws:
      javax.jms.JMSException - if the session fails to unsubscribe to the durable subscription due to some internal error.
      javax.jms.InvalidDestinationException - if an invalid subscription name is specified.
      Since:
      JMS 1.1
    • onError

      public void onError(Throwable err)
    • registerConsumer

      public void registerConsumer(PulsarMessageConsumer consumer)
    • isJms20

      public boolean isJms20()
    • setJms20

      public void setJms20(boolean jms20)
    • getConnection

      public PulsarConnection getConnection()
    • isTransactionStarted

      public boolean isTransactionStarted()
    • createReceiver

      public javax.jms.QueueReceiver createReceiver(javax.jms.Queue queue) throws javax.jms.JMSException
      Specified by:
      createReceiver in interface javax.jms.QueueSession
      Throws:
      javax.jms.JMSException
    • createReceiver

      public javax.jms.QueueReceiver createReceiver(javax.jms.Queue queue, String s) throws javax.jms.JMSException
      Specified by:
      createReceiver in interface javax.jms.QueueSession
      Throws:
      javax.jms.JMSException
    • createSender

      public javax.jms.QueueSender createSender(javax.jms.Queue queue) throws javax.jms.JMSException
      Specified by:
      createSender in interface javax.jms.QueueSession
      Throws:
      javax.jms.JMSException
    • createSubscriber

      public javax.jms.TopicSubscriber createSubscriber(javax.jms.Topic topic) throws javax.jms.JMSException
      Specified by:
      createSubscriber in interface javax.jms.TopicSession
      Throws:
      javax.jms.JMSException
    • createSubscriber

      public javax.jms.TopicSubscriber createSubscriber(javax.jms.Topic topic, String s, boolean b) throws javax.jms.JMSException
      Specified by:
      createSubscriber in interface javax.jms.TopicSession
      Throws:
      javax.jms.JMSException
    • createPublisher

      public javax.jms.TopicPublisher createPublisher(javax.jms.Topic topic) throws javax.jms.JMSException
      Specified by:
      createPublisher in interface javax.jms.TopicSession
      Throws:
      javax.jms.JMSException
    • checkNotClosed

      public void checkNotClosed() throws javax.jms.JMSException
      Throws:
      javax.jms.JMSException
    • isClosed

      public boolean isClosed()