它侦听端口563 (NNTPS)，并等待连接。
如果您已经添加自定义侦听端口，则可能不需要这些。
If you've added custom listener ports, these might not be needed.
如果给定的服务不是必需的，则可以禁用其侦听端口。
If a given service is not required, then you can disable its listening ports. Looking at this list, potential candidates for disabling are.
在主机上，服务器进程在请求进入时会侦听端口，并将那些消息发送到对象。
On the host machine, the server process listens at the port for requests and, when they come in, sends those messages to the object.
包含TCPIPClient Input节点的消息流将侦听端口，等待服务器应用程序的连接尝试。
A message flow that contains a TCPIPClient Input node listens on a port, waiting for a server application to try to connect.
包含TCPIPServer Input节点的消息流将侦听端口，等待客户端应用程序的连接尝试。
A message flow that contains a TCPIPServer Input node listens on a port, waiting for a client application to try to connect.
WebSphereMQ提供名为runmqlsr 的可执行文件，在缺省情况下，它侦听端口 1414。
WebSphere MQ provides an executable called runmqlsr which, by default, listens on port 1414.
如果您现在尝试重新启动MDBListener1，则在重新启动之前，必须等待其他侦听端口之一停止。
If you now try to restart MDBListener1, it will have to wait for one of our other listener ports to be stopped before it can restart.
随后可以编辑build . properties文件并将host - port值修改为TCPMon的侦听端口。
You can then edit the build.properties file and change the host-port value to the listening port for TCPMon.
客户机连接到端口 10000后，被转发到远程主机的PostgreSQL服务器，后者正在侦听端口 5432：ssh-L 10000:localhost:5432192.168.2.100。
The client, upon connecting to port 10000, is forwarded to the remote host's PostgreSQL server, which is listening on port 5432: ssh -L 10000:localhost:5432 192.168.2.100.
在一个远程主机192.168.2.100上，您连接到您的本地主机的PostgreSQL服务器，后者已经在侦听端口5432：ps ql- h 192.168.2.64- p 5432- Upostgres postgres。
On a remote host, 192.168.2.100, you connect into your local host's PostgreSQL server, which is already listening on port 5432: PSQL -h 192.168.2.64 -p 5432 -u postgres postgres.
它们各自位于侦听不同端口的不同JVM中，不应该彼此存在连接。
They are in different JVMs listening to different ports and shouldn't interfere with each other.
侦听器端口将始终使用连接池中的一个连接运行。
The listener port will always use one connection from the connection pool for running.
在这之前，侦听器端口使用的会话对其他任何应用程序都不可用。
Until that time, the session used by the listener port will not be available to any other application.
管理控制台提供该选项来启动和停止侦听器端口。
The administration console provided the options to start and stop the listener ports.
这个信息所不能告诉您的是，这些主机正在侦听哪些端口。
What this information doesn't tell you is what ports these hosts are potentially listening for connections on.
nc-l-p 2300命令侦听TCP端口 2300。
消息侦听器端口必须在服务器范围配置。
Message listener ports have to be configured at server scope.
通过此属性，我们可以设置消息侦听器服务用于运行侦听器端口的最大和最小线程数。
With this property, we can set the maximum and minimum number of threads used by the message listener service to run the listener ports.
此连接将存在于侦听器端口的整个生命周期。
This connection will exist for the entire life of the listener port.
侦听器端口线程使用的会话将在完成消息处理(执行或回滚)后释放。
Sessions used by the listener port thread will be released after they have processed a message (it commits or rolls back).
这包括所生成的侦听器端口、它的运行时状态及侦听器服务设置。
This includes the generated listener port, its runtime state, and the listener service Settings.
如果迁移多个消息侦听器端口配置，请注意避免JNDI名称冲突。
Take care to avoid JNDI name clashes if multiple message listener port configurations are migrated.
如果MDB配置为使用该侦听器端口，则它将立即开始处理队列中的任何消息。
If a MDB has been configured to use the listener port, it will start processing any messages on the queue immediately.
一次只有一个进程能侦听特定端口。
会话池应该大到能包含使用连接的任何侦听器端口的最大会话。
The session pool should be large enough to cover the Maximum Sessions value for any listener ports using the connection.
J2C激活规范而非MQJMS绑定上侦听器端口的使用。
Use of J2C activation specifications instead of listener ports on MQJMS bindings.
添加操作所得的侦听器端口条目如图6所示。
The resulting Add Listener Port entries are shown in Figure 6.
此连接只有在侦听器端口停止后才释放。
This connection will only be released after the listener port has been stopped.
侦听器端口需要通过使用管理控制台配置，如图2所示。
The listener ports need to be configured using the administration console as shown in figure 2.
应用推荐