[sip-comm-dev] Errors when terminating SC - some problems with SIP listeners?


#1

All,

yet some other error messages. The SIP error messages occurred
after updating the SIP to single stack as far as I can remember.

Because I managed to get a SER (openSER indeed) up and running my
SC now uses an account that registers as well as an account without
registrar. The following messages contain the address of the
registered account (100@172.....). This happens regardless if
I just start/exit SC without performing a call or if I placed one or
more calls.

Regards,
Werner

Console log:

      [java] 19:40:58.803 INFO: impl.protocol.zeroconf.ZeroconfActivator.stop().115 Zeroconf protocol implementation [STOPPED].
      [java] 19:40:58.928 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.getListenerFor().897 no listener found for local party: <sip:100@172.16.231.1>
      [java] 19:40:58.929 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processResponse().541 couldn't find a ProtocolProviderServiceSipImpl to dispatch to
      [java] 19:41:03.910 SCHWERWIEGEND: impl.gui.main.login.LoginManager.registrationStateChanged().271 null
      [java] ERROR: Error stopping bundle. (java.util.ConcurrentModificationException)
      [java] java.util.ConcurrentModificationException
      [java] at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
      [java] at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.stopListening(SipStackSharing.java:335)
      [java] at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.removeSipListener(SipStackSharing.java:142)
      [java] at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.unregister(ProtocolProviderServiceSipImpl.java:338)
      [java] at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl$ShutdownThread.run(ProtocolProviderServiceSipImpl.java:856)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.shutdown(ProtocolProviderServiceSipImpl.java:831)
      [java] at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.stop(ProtocolProviderFactory.java:788)
      [java] at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.stop(ProtocolProviderFactory.java:765)
      [java] at net.java.sip.communicator.impl.protocol.sip.SipActivator.stop(SipActivator.java:213)
      [java] at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:611)
      [java] at org.apache.felix.framework.Felix._stopBundle(Felix.java:1914)
      [java] at org.apache.felix.framework.Felix.stopBundle(Felix.java:1871)
      [java] at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1081)
      [java] at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] java.lang.IllegalStateException: Invalid BundleContext.
      [java] at org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:460)
      [java] at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:376)
      [java] at net.java.sip.communicator.impl.protocol.sip.UriHandlerSipImpl.serviceChanged(UriHandlerSipImpl.java:359)
      [java] at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:765)
      [java] at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:623)
      [java] at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:554)
      [java] at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3525)
      [java] at org.apache.felix.framework.Felix.access$000(Felix.java:36)
      [java] at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:593)
      [java] at org.apache.felix.framework.ServiceRegistry.fireServiceChanged(ServiceRegistry.java:435)
      [java] at org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:86)
      [java] at org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:99)
      [java] at org.apache.felix.framework.ServiceRegistry.unregisterServices(ServiceRegistry.java:119)
      [java] at org.apache.felix.framework.Felix._stopBundle(Felix.java:1951)
      [java] at org.apache.felix.framework.Felix.stopBundle(Felix.java:1871)
      [java] at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1081)
      [java] at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] java.lang.IllegalStateException: Invalid BundleContext.
      [java] at org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:460)
      [java] at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:376)
      [java] at net.java.sip.communicator.impl.protocol.sip.UriHandlerSipImpl.serviceChanged(UriHandlerSipImpl.java:359)
      [java] at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:765)
      [java] at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:623)
      [java] at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:554)
      [java] at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3525)
      [java] at org.apache.felix.framework.Felix.access$000(Felix.java:36)
      [java] at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:593)
      [java] at org.apache.felix.framework.ServiceRegistry.fireServiceChanged(ServiceRegistry.java:435)
      [java] at org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:86)
      [java] at org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:99)
      [java] at org.apache.felix.framework.ServiceRegistry.unregisterServices(ServiceRegistry.java:119)
      [java] at org.apache.felix.framework.Felix._stopBundle(Felix.java:1951)
      [java] at org.apache.felix.framework.Felix.stopBundle(Felix.java:1871)
      [java] at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1081)
      [java] at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] java.lang.IllegalStateException: Invalid BundleContext.
      [java] at org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:460)
      [java] at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:376)
      [java] at net.java.sip.communicator.impl.protocol.sip.UriHandlerSipImpl.serviceChanged(UriHandlerSipImpl.java:359)
      [java] at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:765)
      [java] at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:623)
      [java] at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:554)
      [java] at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3525)
      [java] at org.apache.felix.framework.Felix.access$000(Felix.java:36)
      [java] at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:593)
      [java] at org.apache.felix.framework.ServiceRegistry.fireServiceChanged(ServiceRegistry.java:435)
      [java] at org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:86)
      [java] at org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:99)
      [java] at org.apache.felix.framework.ServiceRegistry.unregisterServices(ServiceRegistry.java:119)
      [java] at org.apache.felix.framework.Felix._stopBundle(Felix.java:1951)
      [java] at org.apache.felix.framework.Felix.stopBundle(Felix.java:1871)
      [java] at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1081)
      [java] at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] java.util.ConcurrentModificationException
      [java] at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
      [java] at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.stopListening(SipStackSharing.java:335)
      [java] at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.removeSipListener(SipStackSharing.java:142)
      [java] at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.unregister(ProtocolProviderServiceSipImpl.java:338)
      [java] at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl$ShutdownThread.run(ProtocolProviderServiceSipImpl.java:856)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.shutdown(ProtocolProviderServiceSipImpl.java:831)
      [java] at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.stop(ProtocolProviderFactory.java:788)
      [java] at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.stop(ProtocolProviderFactory.java:765)
      [java] at net.java.sip.communicator.impl.protocol.sip.SipActivator.stop(SipActivator.java:213)
      [java] at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:611)
      [java] at org.apache.felix.framework.Felix._stopBundle(Felix.java:1914)
      [java] at org.apache.felix.framework.Felix.stopBundle(Felix.java:1871)
      [java] at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1081)
      [java] at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
      [java] at java.lang.Thread.run(Thread.java:619)
      [java] ERROR: EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: Invalid BundleContext.)
      [java] ERROR: Error stopping reference:file:sc-bundles/protocol-sip.jar (org.osgi.framework.BundleException: Activator stop error.)

BUILD SUCCESSFUL
Total time: 1 minute 15 seconds
wd@linux-black:~/devhome/sip-communicator>

···

---------------------------------------------------------------------
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 Werner,

yet some other error messages. The SIP error messages occurred
after updating the SIP to single stack as far as I can remember.

Thanks for the feedback.

Because I managed to get a SER (openSER indeed) up and running my
SC now uses an account that registers as well as an account without
registrar. The following messages contain the address of the
registered account (100@172.....). This happens regardless if
I just start/exit SC without performing a call or if I placed one or
more calls.

I've OpenSIPS (a fork of OpenSER) on my laptop. I'll test and report back.

Console log:

<snip>

     [java] 19:40:58.928 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.getListenerFor().897 no listener found for local party: <sip:100@172.16.231.1>
     [java] 19:40:58.929 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processResponse().541 couldn't find a ProtocolProviderServiceSipImpl to dispatch to

This is clearly a bug. Is it always reproducible? SC is probably
receiving a response to a SIP request it issued before unregistering the
account.

     [java] 19:41:03.910 SCHWERWIEGEND: impl.gui.main.login.LoginManager.registrationStateChanged().271 null

Don't know about this.

     [java] ERROR: Error stopping bundle. (java.util.ConcurrentModificationException)
     [java] java.util.ConcurrentModificationException

I'm to blame for this one and I'll commit a fix, see:
https://sip-communicator.dev.java.net/servlets/ReadMsg?list=dev&msgNo=5029

Cheers,

···

Le 11 Dec 2008 à 19:48, Werner Dittmann a écrit :

--
Sébastien Mazy

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


#3

Sébastien,

the login manager problem is an old one - need to look at it separately.

I've updated to the latest SVN. At least during shutdown there may be
some problems also with registarless accounts. Tomorrow I'll do some
more tests and send the results. Thanks for your fast response.

Regards,
Werner

Sébastien Mazy schrieb:

···

Hi Werner,

Le 11 Dec 2008 à 19:48, Werner Dittmann a écrit :

yet some other error messages. The SIP error messages occurred
after updating the SIP to single stack as far as I can remember.

Thanks for the feedback.

Because I managed to get a SER (openSER indeed) up and running my
SC now uses an account that registers as well as an account without
registrar. The following messages contain the address of the
registered account (100@172.....). This happens regardless if
I just start/exit SC without performing a call or if I placed one or
more calls.

I've OpenSIPS (a fork of OpenSER) on my laptop. I'll test and report back.

Console log:

<snip>

     [java] 19:40:58.928 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.getListenerFor().897 no listener found for local party: <sip:100@172.16.231.1>
     [java] 19:40:58.929 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processResponse().541 couldn't find a ProtocolProviderServiceSipImpl to dispatch to

This is clearly a bug. Is it always reproducible? SC is probably
receiving a response to a SIP request it issued before unregistering the
account.

     [java] 19:41:03.910 SCHWERWIEGEND: impl.gui.main.login.LoginManager.registrationStateChanged().271 null

Don't know about this.

     [java] ERROR: Error stopping bundle. (java.util.ConcurrentModificationException)
     [java] java.util.ConcurrentModificationException

I'm to blame for this one and I'll commit a fix, see:
https://sip-communicator.dev.java.net/servlets/ReadMsg?list=dev&msgNo=5029

Cheers,

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


#4

Hi back,

I've OpenSIPS (a fork of OpenSER) on my laptop. I'll test and report back.

I have the same issue as the one you reported, but it's actually not
related to OpenSIPS/CER (more below).

> Console log:
<snip>
> [java] 19:40:58.928 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.getListenerFor().897 no listener found for local party: <sip:100@172.16.231.1>
> [java] 19:40:58.929 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processResponse().541 couldn't find a ProtocolProviderServiceSipImpl to dispatch to

This is clearly a bug. Is it always reproducible? SC is probably
receiving a response to a SIP request it issued before unregistering the
account.

That was it. There was a major design flow in the single stack patch.
The SIP protocol provider wouldn't receive any message after *starting*
the unregistration process, thus the dispatching error for the registrar
accounts (due to the 200 OK answering the final REGISTER). I've made a
few modifications to let the protocol provider receive SIP messages from
SipStackSharing until it is really unregistered.

Could you please test the attached patch and report if it works with you?
(sorry this is a git diff, 'patch -p1')

the login manager problem is an old one - need to look at it separately.

OK.

I've updated to the latest SVN. At least during shutdown there may be
some problems also with registarless accounts. Tomorrow I'll do some
more tests and send the results. Thanks for your fast response.

Normally there shouldn't have been any problem with registrarless
accounts, as no message whatsoever are sent during the unregistration
process.

Cheers,

shutdown_sip_lps_later.diff (3.08 KB)

···

On Thu, Dec 11, 2008 at 09:06:46PM +0100, Sébastien Mazy wrote:
On Thu, Dec 11, 2008 at 11:40:10PM +0100, Werner Dittmann wrote:

--
Sébastien Mazy


#5

Hi Damian,

I notice that the DEB builds are at 1583, but that the WIN builds
are staying at 1564.

Regards, Earl

···

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


#6

S�bastien,

the patch is ok - no more nasty error messages :slight_smile: .

Now SC works with nearly no error message during SIP
calls and starting/stopping.

Can you commit this patch?

Regards,
Werner

S�bastien Mazy schrieb:

···

Hi back,

On Thu, Dec 11, 2008 at 09:06:46PM +0100, S�bastien Mazy wrote:

I've OpenSIPS (a fork of OpenSER) on my laptop. I'll test and report back.

I have the same issue as the one you reported, but it's actually not
related to OpenSIPS/CER (more below).

Console log:

<snip>

     [java] 19:40:58.928 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.getListenerFor().897 no listener found for local party: <sip:100@172.16.231.1>
     [java] 19:40:58.929 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processResponse().541 couldn't find a ProtocolProviderServiceSipImpl to dispatch to

This is clearly a bug. Is it always reproducible? SC is probably
receiving a response to a SIP request it issued before unregistering the
account.

That was it. There was a major design flow in the single stack patch.
The SIP protocol provider wouldn't receive any message after *starting*
the unregistration process, thus the dispatching error for the registrar
accounts (due to the 200 OK answering the final REGISTER). I've made a
few modifications to let the protocol provider receive SIP messages from
SipStackSharing until it is really unregistered.

Could you please test the attached patch and report if it works with you?
(sorry this is a git diff, 'patch -p1')

On Thu, Dec 11, 2008 at 11:40:10PM +0100, Werner Dittmann wrote:

the login manager problem is an old one - need to look at it separately.

OK.

I've updated to the latest SVN. At least during shutdown there may be
some problems also with registarless accounts. Tomorrow I'll do some
more tests and send the results. Thanks for your fast response.

Normally there shouldn't have been any problem with registrarless
accounts, as no message whatsoever are sent during the unregistration
process.

Cheers,

------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-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


#7

Hi Werner,

···

On Fri, Dec 12, 2008 at 06:44:13PM +0100, Werner Dittmann wrote:

the patch is ok - no more nasty error messages :slight_smile: .

Now SC works with nearly no error message during SIP
calls and starting/stopping.

Can you commit this patch?

Just commited r4845.

Cheers,

--
Sébastien Mazy

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


#8

Hey Earl,

Thanks for reporting this. It was once again an IPv6 tunnel problem.
Should be OK now.

Cheers
Emil

Earl wrote:

···

Hi Damian,

I notice that the DEB builds are at 1583, but that the WIN builds
are staying at 1564.

Regards, Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-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