Issue 22: Components should reset pubsub status on disconnect
Project Member Reported by Moeh...@gmail.com, Jun 4, 2008
Reproduce:
- start openfire and all kinti processes
- stop openfire
- wait at least 15 seconds
- touch your nose using a finger on your left hand
- start openfire

The runner process should, just like all other processes, reset the pubsub
status. At this moment, after having followed the steps above, the runner
does not re-request the configuration and therefore, the sessionid it has
will not be updated. This results in the inability of the runner to publish
results.

Jun 4, 2008
Project Member #1 Moeh...@gmail.com
reminder!
Jun 4, 2008
Project Member #2 c...@novemberborn.net
Also applies to buckets?