You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gregg Saffell (JIRA)" <ji...@apache.org> on 2010/02/08 21:11:32 UTC
[jira] Created: (AMQ-2598) Configuring HTTP with
proxyHost, proxyPort results in "Invalid connect parameters:
{proxyPort=nn)}" error
Configuring HTTP <networkConnector> with proxyHost, proxyPort results in "Invalid connect parameters: {proxyPort=nn)}" error
----------------------------------------------------------------------------------------------------------------------------
Key: AMQ-2598
URL: https://issues.apache.org/activemq/browse/AMQ-2598
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.3.0
Environment: Windows XP
Reporter: Gregg Saffell
Priority: Minor
I'm trying to set up a forwarding bridge that will connect through an http proxy (where the proxy happens to be running on the same machine as the destination ApacheMQ instance). Per AMQ-1099, the following should work:
<networkConnector name="gstest-252" uri="static://(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)" networkTTL="5"/>
But it results in the following error at start up:
INFO | Establishing network connection from vm://localhost to http://gstest-252
:61617?proxyHost=gstest-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80)
WARN | Could not connect to remote URI: http://gstest-252:61617?proxyHost=gstes
t-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80): Invalid connect parameter
s: {proxyPort=80)}
INFO | Network Connector gstest-252 Started
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2598) Configuring HTTP
with proxyHost, proxyPort results in "Invalid connect parameters:
{proxyPort=nn)}" error
Posted by "Gregg Saffell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61213#action_61213 ]
Gregg Saffell commented on AMQ-2598:
------------------------------------
Thanks, we will update our activemq.xml files accordingly. I actually got that from the examples on http://activemq.apache.org/networks-of-brokers.html. You'll note that the first couple of examples show it the way you suggest but the examples further down have "static://.
> Configuring HTTP <networkConnector> with proxyHost, proxyPort results in "Invalid connect parameters: {proxyPort=nn)}" error
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2598
> URL: https://issues.apache.org/activemq/browse/AMQ-2598
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.3.0
> Environment: Windows XP
> Reporter: Gregg Saffell
> Assignee: Dejan Bosanac
> Priority: Minor
> Fix For: 5.4.1
>
>
> I'm trying to set up a forwarding bridge that will connect through an http proxy (where the proxy happens to be running on the same machine as the destination ApacheMQ instance). Per AMQ-1099, the following should work:
> <networkConnector name="gstest-252" uri="static://(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)" networkTTL="5"/>
> But it results in the following error at start up:
> INFO | Establishing network connection from vm://localhost to http://gstest-252
> :61617?proxyHost=gstest-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80)
> WARN | Could not connect to remote URI: http://gstest-252:61617?proxyHost=gstes
> t-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80): Invalid connect parameter
> s: {proxyPort=80)}
> INFO | Network Connector gstest-252 Started
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-2598) Configuring HTTP
with proxyHost, proxyPort results in "Invalid connect parameters:
{proxyPort=nn)}" error
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac reassigned AMQ-2598:
----------------------------------
Assignee: Dejan Bosanac
> Configuring HTTP <networkConnector> with proxyHost, proxyPort results in "Invalid connect parameters: {proxyPort=nn)}" error
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2598
> URL: https://issues.apache.org/activemq/browse/AMQ-2598
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.3.0
> Environment: Windows XP
> Reporter: Gregg Saffell
> Assignee: Dejan Bosanac
> Priority: Minor
> Fix For: 5.4.1
>
>
> I'm trying to set up a forwarding bridge that will connect through an http proxy (where the proxy happens to be running on the same machine as the destination ApacheMQ instance). Per AMQ-1099, the following should work:
> <networkConnector name="gstest-252" uri="static://(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)" networkTTL="5"/>
> But it results in the following error at start up:
> INFO | Establishing network connection from vm://localhost to http://gstest-252
> :61617?proxyHost=gstest-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80)
> WARN | Could not connect to remote URI: http://gstest-252:61617?proxyHost=gstes
> t-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80): Invalid connect parameter
> s: {proxyPort=80)}
> INFO | Network Connector gstest-252 Started
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2598) Configuring HTTP
with proxyHost, proxyPort results in "Invalid connect parameters:
{proxyPort=nn)}" error
Posted by "Gregg Saffell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57508#action_57508 ]
Gregg Saffell commented on AMQ-2598:
------------------------------------
I did some debugging and the problem seems to be caused by org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd() method where it calls "connectUri = URISupport.applyParameters(connectUri, parameters);"
Note in the output included in the description of this issue, the "INFO | Establishing network connection" reports the query parameters twice and inccludes ")" at the end. That duplication and the addition of the ")" to the end of the last parameter is caused by the applyParameters() call. I found that if I comment that call out, every thing works fine. (Commenting out that code is probably not the correct solution. Maybe the problem is with what ever code populated the "parameters" HashMap that is being passed to the applyParameters() method? At any rate, I just wanted to note what I've found so far.)
> Configuring HTTP <networkConnector> with proxyHost, proxyPort results in "Invalid connect parameters: {proxyPort=nn)}" error
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2598
> URL: https://issues.apache.org/activemq/browse/AMQ-2598
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.3.0
> Environment: Windows XP
> Reporter: Gregg Saffell
> Priority: Minor
>
> I'm trying to set up a forwarding bridge that will connect through an http proxy (where the proxy happens to be running on the same machine as the destination ApacheMQ instance). Per AMQ-1099, the following should work:
> <networkConnector name="gstest-252" uri="static://(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)" networkTTL="5"/>
> But it results in the following error at start up:
> INFO | Establishing network connection from vm://localhost to http://gstest-252
> :61617?proxyHost=gstest-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80)
> WARN | Could not connect to remote URI: http://gstest-252:61617?proxyHost=gstes
> t-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80): Invalid connect parameter
> s: {proxyPort=80)}
> INFO | Network Connector gstest-252 Started
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2598) Configuring HTTP
with proxyHost, proxyPort results in "Invalid connect parameters:
{proxyPort=nn)}" error
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-2598.
--------------------------------
Resolution: Fixed
Fixed with svn revision 984826
Just a note that it won't work with the url you're using
static://(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)
You need to use
static:(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)
which is a properly formatted composite url.
> Configuring HTTP <networkConnector> with proxyHost, proxyPort results in "Invalid connect parameters: {proxyPort=nn)}" error
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2598
> URL: https://issues.apache.org/activemq/browse/AMQ-2598
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.3.0
> Environment: Windows XP
> Reporter: Gregg Saffell
> Assignee: Dejan Bosanac
> Priority: Minor
> Fix For: 5.4.1
>
>
> I'm trying to set up a forwarding bridge that will connect through an http proxy (where the proxy happens to be running on the same machine as the destination ApacheMQ instance). Per AMQ-1099, the following should work:
> <networkConnector name="gstest-252" uri="static://(http://gstest-252:61617?proxyHost=gstest-252&proxyPort=80)" networkTTL="5"/>
> But it results in the following error at start up:
> INFO | Establishing network connection from vm://localhost to http://gstest-252
> :61617?proxyHost=gstest-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80)
> WARN | Could not connect to remote URI: http://gstest-252:61617?proxyHost=gstes
> t-252&proxyPort=80&proxyHost=gstest-252&proxyPort=80): Invalid connect parameter
> s: {proxyPort=80)}
> INFO | Network Connector gstest-252 Started
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.