tag:blogger.com,1999:blog-535871139796137802.post2116449845140795201..comments2022-12-05T05:19:05.534+02:00Comments on Chris Ritchies Java Blog: Configure WildFly, Apache and websocket connections on Ubuntu 14.04Chrishttp://www.blogger.com/profile/17099003228715114731noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-535871139796137802.post-63524241253097820452016-07-05T11:09:31.156+02:002016-07-05T11:09:31.156+02:00Thx for this scripts, it's very useful, I thin...Thx for this scripts, it's very useful, I thinking abot using it in my dissertation work, if y don't mind.<br />Best regards<br />Toby, <a href="https://www.idealsvdr.com/" rel="nofollow">data room solutions</a>Anonymoushttps://www.blogger.com/profile/15542362115702942216noreply@blogger.comtag:blogger.com,1999:blog-535871139796137802.post-65438865444611859632016-05-05T12:05:22.077+02:002016-05-05T12:05:22.077+02:00At the time of this answer AJP [which is the defau...At the time of this answer AJP [which is the default one] does not support HTTP upgrade and hence not websocket.<br /><br />If you switch to HTTP websocket will work.<br /><br />Following changes you need to do to switch to AJP<br /><br />Change<br /><br />LoadModule proxy_ajp_module modules/mod_proxy_ajp.so<br />#LoadModule proxy_http_module modules/mod_proxy_http.so<br /><br />To<br /><br />#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so<br />LoadModule proxy_http_module modules/mod_proxy_http.so<br /><br />[comment out proxy_ajp_module and added proxy_http_module]<br /><br />In modcluster sub-system<br /><br />Change<br /><br /><br /><br /><br /><br /><br /><br /><br /><br />To<br /><br /><br /><br /><br /><br /><br /><br /><br /><br />[“default” is the name of the http listener]<br /><br />Also you need to load mod_proxy_wstunnel in your httpd<br />Anonymoushttps://www.blogger.com/profile/02960703722073467502noreply@blogger.comtag:blogger.com,1999:blog-535871139796137802.post-25719644737822918542015-10-24T00:40:59.593+02:002015-10-24T00:40:59.593+02:00Hi Chris...
My environment is Wildfly 8.2 and Apac...Hi Chris...<br />My environment is Wildfly 8.2 and Apache 2.2.21<br /><br />I did the following things and I couldnt get this work...<br />1)I enabled proxy_wstunnel_module (shared)<br />2)I disabled mod_proxy_ajp.so due to AJP is not compatible with websocket according to documentation<br />3)I am using Atmosphere Websocket with wildfly...<br /><br />My web.xml config is:<br /> <br /> Push Servlet<br /> org.primefaces.push.PushServlet<br /> <br /> org.atmosphere.cpr.broadcasterCacheClass<br /> org.atmosphere.cache.UUIDBroadcasterCache<br /> <br /> 0<br /> true<br /> <br /> <br /><br /> <br /> Push Servlet<br /> /primepush/*<br /> <br /><br />About my EndPoint is @PushEndpoint("/{primepush}/{user}")<br /><br />4) I changed my subsystem wildfly config from AJP to HTTP<br />5)I created my reverse proxies:<br /><br />ProxyPass /company http://app.tiedocs.com/company<br /> ProxyPassReverse /company http://asubdomain.website.com/company<br /> ProxyPass /company/primepush/ ws://subdomain.website.com/company/primepush/<br /> ProxyPassReverse /company/primepush/ ws://subdomain.website.com/company/primepush/<br /><br />ProxyPass /company http://localhost:8080/company<br /> ProxyPassReverse /company http://localhost:8080/company<br /> ProxyPass /company/primepush/ ws://localhost:8080/company/primepush/<br /> ProxyPassReverse /company/primepush/ ws://localhost:8080/company/primepush/<br /><br />But ever, I'm still getting the same error UT000077: The underlying transport does not support HTTP upgrade..<br /><br />I dont know exactly what I'm doing wrong.Dannyhttps://www.blogger.com/profile/17397690621506804598noreply@blogger.comtag:blogger.com,1999:blog-535871139796137802.post-29208820133893220002015-06-05T10:35:03.440+02:002015-06-05T10:35:03.440+02:00Hi Maurice, thanks for the message.
I find HTTP ...Hi Maurice, thanks for the message. <br /><br />I find HTTP easier to set up and configure. AJP is designed to communicate between the web server and the application server, so in theory, should be better performing. Also, if you use mod_proxy_http the host headers will be stripped out where as the headers will be preserved with AJP. (For example you will loose your HTTP Upgrade)<br /><br />To keep the headers with HTTP you need to use 'ProxyPreserveHost On' in you Apache config.<br /><br />With regards to your SSL question. I have always installed my SSL certs in Apache and let Apache deal with the encryption. I then forward the traffic to WildFly using HTTP. I have favoured this approach as I can quickly configure Apache SSL. Also when I upgrade my JBoss/WildFly server I have less to configure. I suppose it comes down to personal preference.Chrishttps://www.blogger.com/profile/17099003228715114731noreply@blogger.comtag:blogger.com,1999:blog-535871139796137802.post-50741022267763512122015-06-02T14:14:00.364+02:002015-06-02T14:14:00.364+02:00Hi Chris,
I wonder what your take is on a couple ...Hi Chris,<br /><br />I wonder what your take is on a couple of issues I faced regarding this topic:<br /><br />- Would you consider using AJP instead of HTTP between Apache and Wildfly? My understanding is that AJP offers better performance.<br />- When securing the outside traffic (using SSL/TLS, always a good idea IMHO), would you have Apache offload the encryption (i.e. end encryption at Apache and connect unencrypted to Wildfly) or carry the encryption up to Wildfly?<br /><br />Thanks,<br />MauriceAnonymoushttps://www.blogger.com/profile/02241252853726862350noreply@blogger.com