[sip-comm-dev] Re: [Issue 476] SC fails to connect to jabber servers from a specific network


#1

Hey Seb,

Just had a look and it appears that the exception is cause by a missing
class in the dns4java lib which is a bit weird. Are you using the trunk
version of SIP Communicator or have you modified things in build.xml or
the libs?

Also, it would also help to add more details such as a tcpdump trace for
example and your complete logs. It would be a bit difficult to address
the problem with what's in there currently :wink:

Oh and btw, not a big deal really but it is generally a good thing to
try and discuss such problems on dev before entering them in the issue
tracker:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues#issuesubmit

The point is to get them confirmed by a developer and make sure that we
have all necessary information logged in the issue entry.

Cheers
Emil

smazy@dev.java.net 薪邪锌懈褋邪:

路路路

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=476
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Issue #|476
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Summary>SC fails to connect to jabber servers from a specific
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽>network
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Component>sip-communicator
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Version>current
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Platform>All
聽聽聽聽聽聽聽聽聽聽聽聽聽聽OS/Version|All
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽URL>
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Status>NEW
聽聽聽聽聽聽聽Status whiteboard|
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Keywords>
聽聽聽聽聽聽聽聽聽聽聽聽聽聽Resolution>
聽聽聽聽聽聽聽聽聽聽聽聽聽聽Issue type|DEFECT
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽Priority>P3
聽聽聽聽聽聽聽聽聽聽聽聽Subcomponent>development
聽聽聽聽聽聽聽聽聽聽聽聽聽Assigned to|smazy
聽聽聽聽聽聽聽聽聽聽聽聽聽Reported by|smazy

------- Additional comments from smazy@dev.java.net Wed Oct 22 22:42:45 +0000 2008 -------
SIP Communicator fails to connect to any jabber server from my dorm network
(other jabber clients connect just fine though).

I haven't investigated the issue yet but here is the stack trace:

[java] 00:32:39.603 SEVERE: impl.gui.main.login.LoginManager.run().504 Failed to
register protocol provider.
[java] java.lang.NoClassDefFoundError: Could not initialize class
org.xbill.DNS.Lookup
[java] at
net.java.sip.communicator.util.NetworkUtils.getSRVRecords(NetworkUtils.java:243)
[java] at
net.java.sip.communicator.util.NetworkUtils.getSRVRecord(NetworkUtils.java:317)
[java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:315)
[java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:145)
[java] at
net.java.sip.communicator.impl.gui.main.login.LoginManager$RegisterProvider.run(LoginManager.java:418)
[java] 00:32:39.625 SEVERE: impl.gui.main.login.LoginManager.run().504 Failed to
register protocol provider.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: issues-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi all,

OK, it turned out that the issue was caused by an escape character in
my resolv.conf. The weird thing is that it only affected SC (and maybe
other Java apps I would guess), not the other jabber clients. I closed
the issue. Pardon the unnecessary noise and loss of time.

Oh and btw, not a big deal really but it is generally a good thing to
try and discuss such problems on dev before entering them in the issue
tracker:

http://www.sip-communicator.org/index.php/Development/BugsAndIssues#issuesubmit

The point is to get them confirmed by a developer and make sure that we
have all necessary information logged in the issue entry.

My Bad. Should have RTFMed.

Cheers,

路路路

--
S茅bastien