You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rahul B (JIRA)" <ji...@apache.org> on 2019/01/18 09:28:00 UTC
[jira] [Updated] (QPIDJMS-442) Ability to bind local address and
port while connecting to Broker
[ https://issues.apache.org/jira/browse/QPIDJMS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul B updated QPIDJMS-442:
----------------------------
Description:
When qpid-jms-client connect to broker it picks available local port randomly(actually Netty libraries do this). I would like to control from which port qpid-jms-client make the connection.
Looking at the qpid-jms-client this can be achieved by configuring the io.netty.bootstrap.Bootstrap class. But this class is being instantiated inside org.apache.qpid.jms.transports.netty.NettyTcpTransport and only configured with Channel Options.
PS this is the first time I'm posting an issue, so let me know if I need to provide some more information.
was:
When qpid-jms-client connect to broker it picks available local port randomly(actually Netty libraries do this). I would like to control from which port qpid-jms-client make the connection.
Looking at the qpid-jms-client this can be achieved by configuring the io.netty.bootstrap.Bootstrap class. But this class is being instantiated inside org.apache.qpid.jms.transports.netty.NettyTcpTransport and only configured with Channel Options.
PS this is the first time I m posting a issue so let me know if I need to supply some more information.
> Ability to bind local address and port while connecting to Broker
> -----------------------------------------------------------------
>
> Key: QPIDJMS-442
> URL: https://issues.apache.org/jira/browse/QPIDJMS-442
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.40.0
> Reporter: Rahul B
> Priority: Major
>
> When qpid-jms-client connect to broker it picks available local port randomly(actually Netty libraries do this). I would like to control from which port qpid-jms-client make the connection.
>
> Looking at the qpid-jms-client this can be achieved by configuring the io.netty.bootstrap.Bootstrap class. But this class is being instantiated inside org.apache.qpid.jms.transports.netty.NettyTcpTransport and only configured with Channel Options.
> PS this is the first time I'm posting an issue, so let me know if I need to provide some more information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org