[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4190) New JBR Gateway wizard does not create "host" property on jbr-provider xml tag

[Aaron Pestel (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12472171#action_12472171 ] 

Aaron Pestel commented on JBIDE-4190:
-------------------------------------

I don't think the JBR gateway uses the -b setting.  I think the only way to set the bind host for the JBR/HTTP gateway is via the host attribute in jboss-esb.xml.  If I'm wrong, this Jira can be closed.  I'm pretty sure though that we tried just using the -b with the customer and that made things like the admin console work, but not the JBR/HTTP gateway.

> New JBR Gateway wizard does not create "host" property on jbr-provider xml tag
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-4190
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4190
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>         Environment: Version: 2.0.0.CR1
> Build id: R200812221144
> Build date: 12/22/2008 11:54
>            Reporter: Aaron Pestel
>            Assignee: Viacheslav Kabanovich
>            Priority: Minor
>             Fix For: 3.1.0.M3
>
>
> In the JBoss ESB Editor, when I right-click on Providers and select "New | JBR Provider", the wizard should have an option for "host" in addition to "Name" and "Protocol".  Technically, that's probably a feature request rather than a bug, but here is why it's a problem.
> The <jbr-provider> that gets generated does not include the "host" attribute, which apparently defaults to 127.0.0.1.  As can be seen in the log:
> ---------------------------------------------------
> 14:37:49,588 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-7979
> 14:37:49,588 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-7979
> 14:37:49,589 INFO  [JBossRemotingGatewayListener] JBoss Remoting Gateway listener 'listener' started.
> ---------------------------------------------------
> So, what happens is that it starts the JBR listener bound to a local interface and then when remote clients contact it, they get connection refused errors.  Without having the property there, it's difficult for folks to figure out what is going on and how to fix it.  Please see the comments at the bottom of this wiki:  http://www.jboss.org/community/docs/DOC-13352

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira