Taylor
March 14, 2009, 6:48am
1
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:
Contact logging in; I can run iChat + Openfire with two different users just fine, until I try to have them interact.
Trying to buddy someone: If the two users talk to eachother, the messages successfully go through and then the SparkWeb user gets booted.
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:30:29 Could not route packet
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]
Taylor
March 14, 2009, 6:54am
2
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:30:29 Could not route packet
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]
Taylor
March 14, 2009, 7:01am
3
The answer was here.
The user was being logged out because the server was not requesting polling.
To fix: Openfire admin ->System Properties add a new property at the bottom of the page: xmpp.httpbind.client.requests.polling set the value to 0