Ignite Realtime: Invalid SID issues

Skip navigation

Up to Discussions in Openfire Support

5522 Views 4 Replies Latest reply: Nov 25, 2011 7:38 PM by Paul Clapham

Dallas Gutauckis

33 posts since
Jul 26, 2007

Currently Being Moderated

Jan 23, 2008 1:12 PM

Invalid SID issues

Yesterday, our IM server was upgraded from 3.4.3 to 3.4.4, (a fresh install, actually) set up with clustering and moved to new machines. Now, our client is randomly experiencing times of "Invalid SID" as illustrated in the attached screenshot of Firebug.

It is totally possible that I am sending a bad request, so please, also look over what I am sending to verify it's correctness.

Also, when I was trying to resolve this issue earlier, I checked logs for any errors and found nothing of pertinence; however, I will go look again and reply if I find any possible leads.

Thanks,

Dallas

Attachments:

invalidSID.jpg (428.2 K)

Like (0)

Dallas Gutauckis
33 posts since
Jul 26, 2007

Currently Being Moderated

Jan 23, 2008 1:10 PM (in response to Dallas Gutauckis)
Re: Invalid SID issues

These may be related.

2008.01.23 14:46:36 org.jivesoftware.openfire.spi.PresenceManagerImpl.probePresence(PresenceManagerI mpl.java:427) Internal server error
com.tangosol.util.AssertionException: poll() is a blocking call and cannot be called on the Service thread
at com.tangosol.coherence.Component._assertFailed(Component.CDB:12)
at com.tangosol.coherence.Component._assert(Component.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.poll(Servic e.CDB:4)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.poll(Servic e.CDB:18)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.InvocationS ervice.query(InvocationService.CDB:17)
at com.tangosol.coherence.component.util.safeService.SafeInvocationService.query(S afeInvocationService.CDB:1)
at com.jivesoftware.util.cache.CoherenceClusteredCacheFactory.doSynchronousCluster Task(CoherenceClusteredCacheFactory.java:274)
at org.jivesoftware.util.cache.CacheFactory.doSynchronousClusterTask(CacheFactory. java:502)
at com.jivesoftware.openfire.session.RemoteSession.doSynchronousClusterTask(Remote Session.java:162)
at com.jivesoftware.openfire.session.RemoteClientSession.getPresence(RemoteClientS ession.java:113)
at org.jivesoftware.openfire.spi.PresenceManagerImpl.probePresence(PresenceManager Impl.java:370)
at org.jivesoftware.openfire.spi.PresenceManagerImpl.handleProbe(PresenceManagerIm pl.java:283)
at org.jivesoftware.openfire.PresenceRouter.handle(PresenceRouter.java:182)
at org.jivesoftware.openfire.PresenceRouter.route(PresenceRouter.java:69)
at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:75)
at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:56)
at org.jivesoftware.openfire.component.InternalComponentManager.sendPacket(Interna lComponentManager.java:192)
at org.jivesoftware.openfire.gateway.BaseTransport.sendPacket(BaseTransport.java:1 830)
at org.jivesoftware.openfire.gateway.BaseTransport.processPacket(BaseTransport.jav a:424)
at org.jivesoftware.openfire.gateway.BaseTransport.processPacket(BaseTransport.jav a:198)
at org.jivesoftware.openfire.component.InternalComponentManager$RoutableComponent. process(InternalComponentManager.java:497)
at org.jivesoftware.openfire.spi.RoutingTableImpl.routePacket(RoutingTableImpl.jav a:234)
at com.jivesoftware.util.cluster.RemotePacketExecution.run(RemotePacketExecution.j ava:49)
at com.jivesoftware.util.cache.CoherenceClusteredCacheFactory$1.run(CoherenceClust eredCacheFactory.java:321)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.InvocationS ervice.onInvocationMessage(InvocationService.CDB:6)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.InvocationS ervice$InvocationMessage.onReceived(InvocationService.CDB:32)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.onMessage(S ervice.CDB:9)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.onNotify(Se rvice.CDB:123)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:35)
at java.lang.Thread.run(Unknown Source)
I'm going to tail the logs to try and determine if the issue is happening at the same time and report back.

Report Abuse

Like (0)
- Dallas Gutauckis
  33 posts since
  Jul 26, 2007
  
  Currently Being Moderated
  
  Jan 23, 2008 1:49 PM (in response to Dallas Gutauckis)
  Re: Invalid SID issues
  
  It may also be worth noting that warn.log contains a LOT of these
  
  2008.01.23 11:41:04 Client provided invalid session: aa533c31. http://10.10.130.251
  2008.01.23 11:41:04 Client provided invalid session: dac531e2. http://10.10.130.251
  2008.01.23 11:41:04 Client provided invalid session: fd191bd5. http://10.10.130.251
  2008.01.23 11:41:04 Client provided invalid session: 7987d604. http://10.10.130.251
  2008.01.23 11:41:05 Client provided invalid session: 49b837c6. http://10.10.130.251
  2008.01.23 11:41:05 Client provided invalid session: e6bea5de. http://10.10.130.251
  2008.01.23 11:41:05 Client provided invalid session: 73f15c75. http://10.10.130.251
  2008.01.23 11:41:05 Client provided invalid session: c97a270f. http://10.10.130.251
  2008.01.23 11:41:06 Client provided invalid session: a5bd711. http://10.10.130.251
  2008.01.23 11:41:06 Client provided invalid session: 6dcd9795. http://10.10.130.251
  2008.01.23 11:41:06 Client provided invalid session: eac27acf. http://10.10.130.251
  2008.01.23 11:41:07 Client provided invalid session: 2331074f. http://10.10.130.251
  2008.01.23 11:41:07 Client provided invalid session: b19bffac. http://10.10.130.251
  2008.01.23 11:41:07 Client provided invalid session: 22a8d931. http://10.10.130.251
  2008.01.23 11:41:07 Client provided invalid session: e4992736. http://10.10.130.251
  2008.01.23 11:41:08 Client provided invalid session: 2d1dfb9. http://10.10.130.251
  2008.01.23 11:41:08 Client provided invalid session: ed3dc84e. http://10.10.130.251
  2008.01.23 11:41:08 Client provided invalid session: 67a18766. http://10.10.130.251
  2008.01.23 11:41:08 Client provided invalid session: 86585114. http://10.10.130.251
  2008.01.23 11:41:09 Client provided invalid session: fd6bf33d. http://10.10.130.251
  2008.01.23 11:41:09 Client provided invalid session: 77b5064e. http://10.10.130.251
  
  Report Abuse
  
  Like (0)
Dallas Gutauckis
33 posts since
Jul 26, 2007

Currently Being Moderated

Feb 13, 2008 10:53 AM (in response to Dallas Gutauckis)
Re: Invalid SID issues

The servers aren't aware of each other's sessions; therefore, one must always return to the same server when making BOSH requests.

Report Abuse

Like (0)
Paul Clapham
4 posts since
Nov 25, 2011

Currently Being Moderated

Nov 25, 2011 7:38 PM (in response to Dallas Gutauckis)
Invalid SID issues

I found i fixed this when my server name (in server properties) didn't match the host name the client was connecting with.

Report Abuse

Like (1)

Go to original post

Legend

Correct Answers - 10 points
Helpful Answers - 5 points

Jan 23, 2008 1:12 PM

Invalid SID issues

Actions

More Like This

Bookmarked By (0)

Legend