<div dir="ltr"><div><div><div><div><div>I tried the example with directly connection to 5222 and the performance improved vastly. </div>I am running into another issue now. </div>I have setup ejabberd and opened port 5222. </div>I have setup nginx as a reverse proxy for ejabberd server. The nginx configuration is as follows. stream{ upstream ejabberd-servers{ server ejabberd:5222; } server{ listen 5222; proxy_pass ejabberd-servers; } } </div>ejabberd point to the ejabberd server and I am using a docker container to reverse proxy. </div>The smack code I am using to connect is as shown below. <pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo"">public void createConnectionObject(){ AbstractXMPPConnection conn = null; try { XMPPTCPConnectionConfiguration.Builder builderConfig = XMPPTCPConnectionConfiguration.builder(); SmackConfiguration.DEBUG = true; builderConfig.setConnectTimeout(60000); builderConfig.setHost(xmppHost); builderConfig.setPort(xmppPort); builderConfig.setServiceName(xmppDomain); builderConfig.setDebuggerEnabled(true); builderConfig.setSecurityMode(ConnectionConfiguration.SecurityMode.required); /*System.setProperty("javax.net.ssl.trustStore", "classpath:hereimkeystore.jks");*/ builderConfig.setKeystoreType("jks"); builderConfig.setKeystorePath("classpath:mykeystore.jks"); ProxyInfo proxyInfo = getProxyInfo(); builderConfig.setProxyInfo(proxyInfo); conn = new XMPPTCPConnection(builderConfig.build()); conn.setPacketReplyTimeout(100000); conn.connect(); }catch(SmackException se){ System.out.println("Smack Exception thrown"); }catch(IOException io){ System.out.println("IO Exception thrown"); }catch(XMPPException xmppEx){ System.out.println("XMPP Exception thrown"); } this.connection = conn; } private ProxyInfo getProxyInfo(){ ProxyInfo proxyInfo = ProxyInfo.forHttpProxy(xmppHost, 443, null, null); return proxyInfo; } </pre><pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo"">But when I try to make the connection, I get the error "java.net.SocketException: Unconnected sockets not implemented" </pre><pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo"">I understand nginx will only serve as a tcp proxy, so any pointers on how to get this work? </pre><pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo"">Regards </pre><pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo"">Vaibhav </pre><pre style="background-color:rgb(255,255,255);color:rgb(0,0,0);font-family:"Menlo""></pre> </div><div class="gmail_extra"> <div class="gmail_quote">On Sat, Jul 2, 2016 at 3:35 PM, Marcel Waldvogel <<a href="mailto:marcel.waldvogel@uni-konstanz.de" target="_blank">marcel.waldvogel@uni-konstanz.de</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>With BOSH you can do the same things as with direct c2s XMPP (and even more, because guessing an RID is enough). So what should be the security concerns of using 5222 directly instead of 5280? <a href="https://me.uni.kn/marcel.waldvogel" target="_blank"></a><a href="https://me.uni.kn/marcel.waldvogel" target="_blank">-Marcel Waldvogel</a> -----Original Message----- From: Vaibhav Ranglani <<a href="mailto:ranglani.vaibhav@gmail.com" target="_blank">ranglani.vaibhav@gmail.com</a>> To: Jabber/XMPP software development list <<a href="mailto:jdev@jabber.org" target="_blank">jdev@jabber.org</a>> Sent: Sa., 02 Juli 2016 11:57 Subject: Re: [jdev] Message sending performance XEP-0124 </div><div class="HOEnZb"><div class="h5"><div dir="ltr"><div><div><div>Thanks for the inputs Florian. </div>This question is then related to the deployment side. Should I proxy the nginx server to ejabberd port 5222? If yes, then can somebody point to a post where this has been explained? </div><div>Also wouldn't directly exposing port 5222 to the internet cause security concerns? </div><div> </div>Thanks </div>Vaibhav </div><div class="gmail_extra"> <div class="gmail_quote">On Sat, Jul 2, 2016 at 3:18 PM, Florian Schmaus <<a href="mailto:flo@geekplace.eu" target="_blank">flo@geekplace.eu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01.07.2016 16:22, Marcel Waldvogel wrote: > For reliability requirements over wireless connections: don't use BOSH; > do use Stream Management (XEP-0198) Exactly. And if you want the BOSH advantage over XMPP's TCP binding, i.e., using standard HTTP(S) ports, then use XMPP's WebSocket binding (RFC 7395) + Stream Management. Some background to this thread: <a href="https://community.igniterealtime.org/message/258562#comment-258562" rel="noreferrer" target="_blank">https://community.igniterealtime.org/message/258562#comment-258562</a> I have not much experience with BOSH as I don't/seldom use it. I've merged Smack's BOSH branch when I took over Smack and fixed a few things, but the code should be considered unmaintained. I wonder if BOSH is suitable for mobile environments. In my experience those environments require being able to check the underlying TCP connection for liveness, which is not trivial when using BOSH I imagine. Using the BOSH Technique in mobile environments could cause serious UX issues if the first connection hangs in the long-polling state because the TCP connection broke down silently. WebSocket doesn't have this issues, and provides the same feature set as BOSH when used with Stream Management. I think it is the future and that there is no real reason, besides implementation availability, to use BOSH any more. Sadly there is no support for XMPP over WebSocket in Smack (yet). - Florian _______________________________________________ JDev mailing list Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev" rel="noreferrer" target="_blank">http://mail.jabber.org/mailman/listinfo/jdev</a> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org" target="_blank">JDev-unsubscribe@jabber.org</a> _______________________________________________ </blockquote></div> </div> </div></div> _______________________________________________ JDev mailing list Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev" rel="noreferrer" target="_blank">http://mail.jabber.org/mailman/listinfo/jdev</a> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a> _______________________________________________ </blockquote></div> </div>