试图通过Smack连接XMPP服务器并获取错误

Question

我有一个要求使用Java API Smack连接XMPP服务器并进一步发送消息/接收消息。

我试着用Smack API（4.1.8），我得到错误（在下面找到错误）。

注意：主机和端口都打开。

Code:`public class Sender { 
public static void main(String a[]) throws NoResponseException,XMPPException, 
InterruptedException, SmackException, IOException 
{ 
    // Create the configuration for this new connection 
    XMPPTCPConnectionConfiguration.Builder configBuilder = XMPPTCPConnectionConfiguration.builder(); 
    configBuilder.setUsernameAndPassword("user", "******"); 
    configBuilder.setResource("work"); 
    configBuilder.setServiceName("HOstname"); 
    configBuilder.setSocketFactory(SSLSocketFactory.getDefault()); 
    configBuilder.setSecurityMode(SecurityMode.required); 

    configBuilder.setCompressionEnabled(true); 
    configBuilder.setHost("thingsociety.im"); 
    configBuilder.setDebuggerEnabled(true); 
    configBuilder.setPort(5222); 
    System.out.println("Connected1.............."); 

    XMPPTCPConnection connection = new XMPPTCPConnection(configBuilder.build()); 
    // Connect to the server 
    try { 
     System.out.println("Connected2.............."); 
     connection.setPacketReplyTimeout(100000); 
     connection.connect(); 
     System.out.println("Connected3.............."); 
     // Log into the server 
     connection.isConnected(); 
     connection.login(); 
     System.out.println("Connected4.............."); 
    } 

    catch (XMPPException | SmackException | IOException e) { 
     // TODO Auto-generated catch block 
     e.printStackTrace(); 
     System.out.println(e.getMessage()); 
     } 
    } 
} 

Error: No response received within reply timeout. Timeout was 100000ms (~100s). Used filter: No filter used or filter was 'null'. org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 100000ms (~100s). Used filter: No filter used or filter was 'null'

Answer 1

所以basicly东西（本地防火墙或网关上）阻止outgouing通信或configBuilder.setServiceName("HOstname");服务名（又名XMPP域）是错误的，也许是拼写错误的 - 特别是具有资本O看起来像拼错给我。

我刚刚探讨thingsociety.im:5222，它是开放的，所以很可能它是一个防火墙问题。

另一个可能是unhandeld，服务器端的低级错误。