[jitsi-dev] Copy edits to download page


#1

Download
https://jitsi.org/index.php/Main/Download

page reads: " Latest nightlis are also quite usable"
page should read: " Latest *nightlies* are also quite usable"

page reads: "If you are using our stable build line, you can switch nightly builds"
page should read: "If you are using our stable build line, you can switch *to* nightly builds"

David


#2

currently can't connect to neither jit.si nor jabber. is that only on my part?


#3

Done, thanks!

Ingo

···

-----Original Message-----
From: David Bolton [mailto:davidkbolton@gmail.com]
Sent: Donnerstag, 10. Januar 2013 05:26
To: Jitsi Developers
Subject: [jitsi-dev] Copy edits to download page
Download
https://jitsi.org/index.php/Main/Download

page reads: " Latest nightlis are also quite usable"
page should read: " Latest *nightlies* are also quite usable"

page reads: "If you are using our stable build line, you can switch
nightly builds"
page should read: "If you are using our stable build line, you can
switch *to* nightly builds"

David


#4

Hi,

using latest nightly I'm connected to jit.si and successfully
connect/disconnect my jit.si account.
Any exception in logs?

Cheers
damencho

···

On Thu, Jan 10, 2013 at 1:35 PM, Steve <stevebell@gulli.com> wrote:

currently can't connect to neither jit.si nor jabber. is that only on my part?


#5

Steve:

currently can't connect to neither jit.si nor jabber. is that only on my part?

I also can not connect to jabber.org, but no problem connecting with
jit.si and other XMPP servers.

jabber.org does not seem be very reliable recently.

Cheers,
Andreas

···

---

     [java] 14:43:31.150 Schwerwiegend:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVRecords().843
Error connecting to hermes6.jabber.org./2605:da00:5222:5269:0:0:2:1:5222
for domain:jabber.org serviceName:jabber.org
     [java] XMPPError connecting to 2605:da00:5222:5269:0:0:2:1:5222.:
remote-server-error(502) XMPPError connecting to
2605:da00:5222:5269:0:0:2:1:5222.
     [java] -- caused by: java.net.SocketException: Das Netzwerk ist
nicht erreichbar
     [java] at
org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:540)
     [java] at
org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:977)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1185)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:896)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVRecords(ProtocolProviderServiceJabberImpl.java:837)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:649)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:454)
     [java] at
net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator$ReconnectTask.run(ReconnectPluginActivator.java:883)
     [java] at java.lang.Thread.run(Thread.java:722)
     [java] Nested Exception:
     [java] java.net.SocketException: Das Netzwerk ist nicht erreichbar
     [java] at java.net.PlainSocketImpl.socketConnect(Native Method)
     [java] at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
     [java] at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
     [java] at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
     [java] at java.net.Socket.connect(Socket.java:579)
     [java] at java.net.Socket.connect(Socket.java:528)
     [java] at
org.jivesoftware.smack.proxy.DirectSocketFactory.createSocket(DirectSocketFactory.java:28)
     [java] at
org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:528)
     [java] at
org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:977)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1185)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:896)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVRecords(ProtocolProviderServiceJabberImpl.java:837)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:649)
     [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:454)
     [java] at
net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator$ReconnectTask.run(ReconnectPluginActivator.java:883)
     [java] at java.lang.Thread.run(Thread.java:722)


#6

Hm not sure what was going on yesterday. Jabber resolved itself a couple of hours after I wrote. Jitsi remained unreachable the whole day.
But today jit.si is working again as well.

I check the console but didn't find anything related.

Anyways, working again.
best, steve

···

Am 10.01.2013 um 15:12 schrieb Andreas Kuckartz <A.Kuckartz@ping.de>:

Steve:

currently can't connect to neither jit.si nor jabber. is that only on my part?

I also can not connect to jabber.org, but no problem connecting with
jit.si and other XMPP servers.

jabber.org does not seem be very reliable recently.

Cheers,
Andreas

---

    [java] 14:43:31.150 Schwerwiegend:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVRecords().843
Error connecting to hermes6.jabber.org./2605:da00:5222:5269:0:0:2:1:5222
for domain:jabber.org serviceName:jabber.org
    [java] XMPPError connecting to 2605:da00:5222:5269:0:0:2:1:5222.:
remote-server-error(502) XMPPError connecting to
2605:da00:5222:5269:0:0:2:1:5222.
    [java] -- caused by: java.net.SocketException: Das Netzwerk ist
nicht erreichbar
    [java] at
org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:540)
    [java] at
org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:977)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1185)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:896)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVRecords(ProtocolProviderServiceJabberImpl.java:837)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:649)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:454)
    [java] at
net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator$ReconnectTask.run(ReconnectPluginActivator.java:883)
    [java] at java.lang.Thread.run(Thread.java:722)
    [java] Nested Exception:
    [java] java.net.SocketException: Das Netzwerk ist nicht erreichbar
    [java] at java.net.PlainSocketImpl.socketConnect(Native Method)
    [java] at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
    [java] at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
    [java] at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
    [java] at java.net.Socket.connect(Socket.java:579)
    [java] at java.net.Socket.connect(Socket.java:528)
    [java] at
org.jivesoftware.smack.proxy.DirectSocketFactory.createSocket(DirectSocketFactory.java:28)
    [java] at
org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:528)
    [java] at
org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:977)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1185)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:896)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVRecords(ProtocolProviderServiceJabberImpl.java:837)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:649)
    [java] at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:454)
    [java] at
net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator$ReconnectTask.run(ReconnectPluginActivator.java:883)
    [java] at java.lang.Thread.run(Thread.java:722)


#7

jabber.org does not seem be very reliable recently.

We're in the process of getting a new server ready to put into
production. That should help a lot.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


#8

Hello. Startinf with version 1.1.4398.10264, Jitsi starts to misbehave -
eats 330MB (usually it uses ~110MB) of memory then starts using 100% CPU
and the UI becomes almost unresponsive.

Log errors:

12:41:22.719 SEVERE: util.UtilActivator.uncaughtException().103 An
uncaught exception occurred in
thread=Thread[UDPMessageProcessorThread,10,main] and message was: Java
heap space
java.lang.OutOfMemoryError: Java heap space
  at
gov.nist.javax.sip.stack.UDPMessageProcessor.run(UDPMessageProcessor.java:221)
  at java.lang.Thread.run(Thread.java:679)
12:43:45.227 SEVERE:
impl.protocol.sip.ProtocolProviderServiceSipImpl.registerUsingNextAddress().2502
Cannot send register!
java.lang.OutOfMemoryError: Java heap space
12:44:24.161 SEVERE:
impl.protocol.sip.ServerStoredContactListSipImpl.init().656 Error while
connecting to XCAP server. Contact list won't be saved
java.lang.OutOfMemoryError: Java heap space
12:44:40.394 WARNING: sun.awt.X11.XToolkit.processException() Exception
on Toolkit thread
java.lang.OutOfMemoryError: Java heap space
12:45:37.177 SEVERE:
service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged().160
An error occurred while executing
RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of
net.java.sip.communicator.impl.protocol.sip.OperationSetPresenceSipImpl@1efb699
java.lang.OutOfMemoryError: Java heap space

Downgrading ro 1.1.4397.10262 seems to solve this problem. I have a
google talk, a SIP, a yahoo and a facebook account configured.

Debian Testing 32-bit/ Xfce 4.10,

java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-1)
OpenJDK Server VM (build 20.0-b12, mixed mode)

···

--
O zi buna,

Kertesz Laszlo


#9

Hey

Are you sure that 1.1.4397.10262 is okay? The only change between 10262 and 10264 was the removal of two println() statements.
If you can reproduce the situation, could please send us your complete logs and if possible a Java-threaddump?

Ingo

···

-----Original Message-----
From: Kertesz Laszlo [mailto:laszlo.kertesz@gmail.com]
Sent: Sonntag, 13. Januar 2013 11:54
To: dev@jitsi.java.net
Subject: [jitsi-dev] Jitsi starts using 100% CPU and uses 330MB memory
Hello. Startinf with version 1.1.4398.10264, Jitsi starts to misbehave -
eats 330MB (usually it uses ~110MB) of memory then starts using 100% CPU
and the UI becomes almost unresponsive.

Log errors:

12:41:22.719 SEVERE: util.UtilActivator.uncaughtException().103 An
uncaught exception occurred in
thread=Thread[UDPMessageProcessorThread,10,main] and message was: Java
heap space java.lang.OutOfMemoryError: Java heap space at
gov.nist.javax.sip.stack.UDPMessageProcessor.run(UDPMessageProcessor.java
:221 ) at java.lang.Thread.run(Thread.java:679) 12:43:45.227 SEVERE:
impl.protocol.sip.ProtocolProviderServiceSipImpl.registerUsingNextAddress
().2 502 Cannot send register! java.lang.OutOfMemoryError: Java heap
space 12:44:24.161 SEVERE:
impl.protocol.sip.ServerStoredContactListSipImpl.init().656 Error while
connecting to XCAP server. Contact list won't be saved
java.lang.OutOfMemoryError: Java heap space 12:44:40.394 WARNING:
sun.awt.X11.XToolkit.processException() Exception on Toolkit thread
java.lang.OutOfMemoryError: Java heap space 12:45:37.177 SEVERE:
service.protocol.AbstractProtocolProviderService.fireRegistrationStateCha
nged ().160 An error occurred while executing
RegistrationStateChangeListener#registrationStateChanged(RegistrationStat
eCha ngeEvent) of
net.java.sip.communicator.impl.protocol.sip.OperationSetPresenceSipImpl@1
efb6 99 java.lang.OutOfMemoryError: Java heap space

Downgrading ro 1.1.4397.10262 seems to solve this problem. I have a
google talk, a SIP, a yahoo and a facebook account configured.

Debian Testing 32-bit/ Xfce 4.10,

java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-1)
OpenJDK Server VM (build 20.0-b12, mixed mode)


#10

Personally, I've been seeing this situation for quite a while and it
mostly happens after I suspend to ram and wake up, change networks or both.

Kertesz, can you confirm that the same thing happened to you?

Emil

···

On 13.01.13, 14:37, Ingo Bauersachs wrote:

Hey

Are you sure that 1.1.4397.10262 is okay? The only change between 10262 and 10264 was the removal of two println() statements.
If you can reproduce the situation, could please send us your complete logs and if possible a Java-threaddump?

Ingo

-----Original Message-----
From: Kertesz Laszlo [mailto:laszlo.kertesz@gmail.com]
Sent: Sonntag, 13. Januar 2013 11:54
To: dev@jitsi.java.net
Subject: [jitsi-dev] Jitsi starts using 100% CPU and uses 330MB memory
Hello. Startinf with version 1.1.4398.10264, Jitsi starts to misbehave -
eats 330MB (usually it uses ~110MB) of memory then starts using 100% CPU
and the UI becomes almost unresponsive.

Log errors:

12:41:22.719 SEVERE: util.UtilActivator.uncaughtException().103 An
uncaught exception occurred in
thread=Thread[UDPMessageProcessorThread,10,main] and message was: Java
heap space java.lang.OutOfMemoryError: Java heap space at
gov.nist.javax.sip.stack.UDPMessageProcessor.run(UDPMessageProcessor.java
:221 ) at java.lang.Thread.run(Thread.java:679) 12:43:45.227 SEVERE:
impl.protocol.sip.ProtocolProviderServiceSipImpl.registerUsingNextAddress
().2 502 Cannot send register! java.lang.OutOfMemoryError: Java heap
space 12:44:24.161 SEVERE:
impl.protocol.sip.ServerStoredContactListSipImpl.init().656 Error while
connecting to XCAP server. Contact list won't be saved
java.lang.OutOfMemoryError: Java heap space 12:44:40.394 WARNING:
sun.awt.X11.XToolkit.processException() Exception on Toolkit thread
java.lang.OutOfMemoryError: Java heap space 12:45:37.177 SEVERE:
service.protocol.AbstractProtocolProviderService.fireRegistrationStateCha
nged ().160 An error occurred while executing
RegistrationStateChangeListener#registrationStateChanged(RegistrationStat
eCha ngeEvent) of
net.java.sip.communicator.impl.protocol.sip.OperationSetPresenceSipImpl@1
efb6 99 java.lang.OutOfMemoryError: Java heap space

Downgrading ro 1.1.4397.10262 seems to solve this problem. I have a
google talk, a SIP, a yahoo and a facebook account configured.

Debian Testing 32-bit/ Xfce 4.10,

java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-1)
OpenJDK Server VM (build 20.0-b12, mixed mode)

--
https://jitsi.org