WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage message-driven beans > Manage message listener resources for message-driven beans > Administer listener portsStopping a listener port
Use this task to stop a listener port on an application server, to prevent the listeners for message-driven beans associated with the port from retrieving messages. A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. For more information, see Message-driven beans - listener port components.
If a message-driven bean fails to process a message several times, the listener port is automatically stopped by the application server. We can also stop a listener port manually. When a listener port is stopped, the listener manager stops the listeners for all message-driven beans associated with the port. Consequently, the associated message-driven beans can no longer process messages.
- Start the dmgr console.
- In the navigation pane, click Servers > Server Types > WebSphere application servers->server_name > [Communications] Messaging > Message listener service > [Additional Properties] Listener Ports > listener_port
The Message listener port page panel is displayed.
- Select the check box for the listener port to stop.
- Click Stop.
- Save your changes to the master configuration.
- To have the changed configuration take effect, stop then restart the application server.
Related concepts:
Message-driven beans - listener port components
Related
Start a listener port
Migrating a listener port to an activation specification for use with the WebSphere MQ messaging provider
Manage message listener resources for message-driven beans