[
https://issues.apache.org/jira/browse/QPIDJMS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754106#comment-16754106
]
ASF subversion and git services commented on QPIDJMS-442:
---------------------------------------------------------
Commit 0597ab62f79618cf1339e165e61d84ae7e55f056 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=0597ab6 ]
QPIDJMS-442: transport options to configure local address and/or port used in
connect
Based on PR from [email protected], but with changes and more tests from me.
This closes #27.
> 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: [email protected]
For additional commands, e-mail: [email protected]
