AnsweredAssumed Answered

SparkWeb crashes on activity

Question asked by editor17 on Mar 13, 2009
Latest reply on Mar 14, 2009 by editor17

I am tantalizingly close to having SparkWeb + Openfire intergrated into a web application.

 

I can log into SparkWeb and authenticate through Openfire just fine. If I don't do anything, I can sit in SparkWeb, buty if I trigger some kind of server response then the page refreshes and makes me log back in again.

 

Example actions that cause problems:

1. Contact logging in; I can run iChat + Openfire with two different users just fine, until I try to have them interact.

2. Trying to buddy someone: If the two users talk to eachother, the messages successfully go through and then the SparkWeb user gets booted.

3. Sending a message: Once it logs you out for trying to buddy, you log back in and can see the invitation to chat. If you accept this, crash.

 

I took a look at the HTTP headers, and there isn't anything that suggest foul play. I figure the page must be unloading, throwing an error, or forcing the user to log out.

 

Has anyone head of this before? Right now SparkWeb kind of works like a poor man's email system. I'd really love to get it doing what it does best.

 

From /opt/openfire/logs/warn.log, after I tried to search for other users:

 


2009.03.13 23:04:00 Client provided invalid session: 1efeb210. [99.8.XX.XX]
2009.03.13 23:04:00 Client provided invalid session: 1efeb210. [99.8.XX.XX]
2009.03.13 23:06:03 Client provided invalid session: a621f973. [99.8.XX.XX]
2009.03.13 23:06:03 Client provided invalid session: a621f973. [99.8.XX.XX]
2009.03.13 23:07:25 Client provided invalid session: d3fa8ad9. [99.8.XX.XX]
2009.03.13 23:07:25 Client provided invalid session: d3fa8ad9. [99.8.XX.XX]
2009.03.13 23:09:37 Client provided invalid session: 9db4714e. [99.8.XX.XX]
2009.03.13 23:09:37 Client provided invalid session: 9db4714e. [99.8.XX.XX]
2009.03.13 23:10:25 Client provided invalid session: 411c7494. [99.8.XX.XX]
2009.03.13 23:10:25 Client provided invalid session: 411c7494. [99.8.XX.XX]
2009.03.13 23:11:37 Client provided invalid session: 5f1070ae. [99.8.XX.XX]
2009.03.13 23:11:37 Client provided invalid session: 5f1070ae. [99.8.XX.XX]
2009.03.13 23:14:29 Client provided invalid session: 58d077c7. [99.8.XX.XX]
2009.03.13 23:14:30 Client provided invalid session: 58d077c7. [99.8.XX.XX]
2009.03.13 23:16:46 Client provided invalid session: 814f9ba9. [99.8.XX.XX]
2009.03.13 23:16:46 Client provided invalid session: 814f9ba9. [99.8.XX.XX]
2009.03.13 23:17:24 Client provided invalid session: 8ff130e2. [99.8.XX.XX]
2009.03.13 23:17:24 Client provided invalid session: 8ff130e2. [99.8.XX.XX]
2009.03.13 23:19:10 Client provided invalid session: ea0ca1ef. [99.8.XX.XX]
2009.03.13 23:19:37 Client provided invalid session: e58bb35c. [99.8.XX.XX]
2009.03.13 23:19:37 Client provided invalid session: e58bb35c. [99.8.XX.XX]
2009.03.13 23:21:41 Client provided invalid session: 731fcaec. [99.8.XX.XX]
2009.03.13 23:21:41 Client provided invalid session: 731fcaec. [99.8.XX.XX]
2009.03.13 23:28:16 Client provided invalid session: 7cd55679. [99.8.XX.XX]
2009.03.13 23:28:16 Client provided invalid session: 7cd55679. [99.8.XX.XX]
2009.03.13 23:30:29 Could not route packe

 


<iq type="result" id="iq_17" from="proxy.mydomain.com" to="myhandle@mydomain.com/sparkweb">
  <query xmlns="http://jabber.org/protocol/disco#info">
    <identity category="proxy" name="SOCKS5 Bytestreams Service" type="bytestreams"/>
    <feature var="http://jabber.org/protocol/bytestreams"/>
    <feature var="http://jabber.org/protocol/disco#info"/>
  </query>
</iq>
2009.03.13 23:30:29 Could not route packet

 


<iq type="result" id="iq_18" from="search.mydomain.com" to="myhandle@mydomain.com/sparkweb">
  <query xmlns="http://jabber.org/protocol/disco#info">
    <identity category="directory" type="user" name="User Search"/>
    <feature var="jabber:iq:search"/>
  </query>
</iq>
2009.03.13 23:30:29 Client provided invalid session: 242328ba. [99.8.XX.XX]
2009.03.13 23:30:29 Client provided invalid session: 242328ba. [99.8.XX.XX]
2009.03.13 23:34:06 Client provided invalid session: 216fe644. [99.8.XX.XX]
2009.03.13 23:34:06 Client provided invalid session: 216fe644. [99.8.XX.XX]
2009.03.13 23:37:00 Client provided invalid session: 63ae495b. [99.8.XX.XX]
2009.03.13 23:37:00 Client provided invalid session: 63ae495b. [99.8.XX.XX]
2009.03.13 23:39:18 Client provided invalid session: bd84587f. [99.8.XX.XX]
2009.03.13 23:39:18 Client provided invalid session: bd84587f. [99.8.XX.XX]

Outcomes