Starting a listener port
Use this task to start a listener port on an application server, to enable the listeners for message-driven beans associated with the port to retrieve 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.
A listener is active, that is able to receive messages from a destination, if the deployed message-driven bean, listener port, and message listener service are all started. Although we can start these components in any order, they must all be in a started state before the listener can retrieve messages.
If we set the initial state of a listener port to Started, the listener port is started automatically when a message-driven bean associated with that port is installed. We can also start a listener port manually.
When a listener port is started, the listener manager tries to start the listeners for each message-driven bean associated with the port. If a message-driven bean is stopped, the port is started but the listener is not started, and remains stopped. If we start a message-driven bean, the related listener is started.
- Start the console.
- The listener for a deployed message-driven bean to be able to receive messages at the port, check that the message-driven bean has been started.
- 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 collection panel is displayed.
- Select the check box for the listener port to start.
- Click Start.
- Save the changes to the master configuration.
Related concepts
Message-driven beans - listener port components
Related tasks
Stopping a listener port Migrate a listener port to an activation specification for use with the WebSphere MQ messaging provider Manage message listener resources for message-driven beans