[gatein-issues] [JBoss JIRA] (GTNWSRP-340) WS ports link to individual nodes' URL instead of loadbalancer
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Thu Jan 24 12:27:47 EST 2013
[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750322#comment-12750322 ]
RH Bugzilla Integration commented on GTNWSRP-340:
-------------------------------------------------
claprun at redhat.com made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729]
It is possible to fix this issue by changing the configuration of JBoss WS in standalone.xml (and standalone-ha.xml, of course) by changing:
<wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
to
<wsdl-host>jbossws.undefined.host</wsdl-host>
as explained in https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide#AdvancedUserGuide-Dynamicrewrite.
There doesn't seem to be any need to use <modify-wsdl-address>true</modify-wsdl-address>, though. Alessio said that using jbossws.undefined.host probably forces the dynamic rewrite and that he needs to update the docs.
> WS ports link to individual nodes' URL instead of loadbalancer
> --------------------------------------------------------------
>
> Key: GTNWSRP-340
> URL: https://issues.jboss.org/browse/GTNWSRP-340
> Project: GateIn WSRP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Consumer, Producer
> Affects Versions: 2.2.0.Final
> Reporter: Chris Laprun
> Assignee: Chris Laprun
> Fix For: 2.2.1.Final
>
>
> This results in failover problems when a producer node is taken down since the port on the consumer side might refer to the node URL that is down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the gatein-issues
mailing list