[wildfly-dev] Issue with HTTP upgrade for remote naming on OpenShift?

[Jason T. Greene]

Thanks for looking into it.

We should start a discussion with the openshift team on that. 

> On Mar 5, 2014, at 4:31 AM, Jeff Mesnil <jmesnil at redhat.com> wrote:
> 
> I’ve spent some time running WildFly on OpenShift and playing with it.
> 
> * I’ve added a quickstart using WebSocket API[1] and it works fine on OpenShift. 
> => note however that OpenShift requires to use a different port for WebSocket (8000) than for HTTP (80) even though both are mapped to WildFly’s 8080 internal port.
> 
> * OpenShift does not support custom protocols for HTTP upgrade beside web socket[2][3]
> => all the quick starts using remote naming, EJB, JMS from external clients will not work unless port-forwarding is enabled.
> 
> jeff
> 
> [1] https://github.com/wildfly/quickstart/tree/master/helloworld-websocket
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1071862
> [3] https://trello.com/c/swGjabeH
> 
> jeff
> 
>> On 19 Feb 2014, at 09:15, Jeff Mesnil <jmesnil at redhat.com> wrote:
>> 
>> 
>>> On 18 Feb 2014, at 22:19, Farah Juma <fjuma at redhat.com> wrote:
>>> 
>>> I'm looking into this as well to see if there's a way to make this work. When using port forwarding, I'm finding that an error still occurs:
>> 
>> At this stage, port forwarding works. Thanks Farah.
>> 
>> The remaining issue is the way HornetQ configures its connectors.
>> 
>> HornetQ connectors are the bits that are retrieved using JNDI and contains the informations to connect to the HornetQ server (embedded with WildFly in our case).
>> The ugly ugly part of it is that the connector must know the host of the server to connect to.
>> In WildFly, we resolve the socket-binding (http in this case) to get this address[1]. When using OpenShift, the HornetQ connectors will use the OpenShift server address (127.5.118.129).
>> If I use port forwarding, the remote naming will work and I will retrieve a connector that wants to connect to 127.5.118.129 from my local machine and this does not work.
>> 
>> The HornetQ team has some features planned for the cloud. I’ll let them know about this.
>> 
>> [1] https://github.com/wildfly/wildfly/blob/master/messaging/src/main/java/org/jboss/as/messaging/HornetQService.java#L181
>> 
>> -- 
>> Jeff Mesnil
>> JBoss, a division of Red Hat
>> http://jmesnil.net/
>> 
>> 
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> 
> -- 
> Jeff Mesnil
> JBoss, a division of Red Hat
> http://jmesnil.net/
> 
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev