[ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.... ] Randall Hauch edited comment on JBTIS-186 at 10/11/13 9:51 AM: --------------------------------------------------------------- Please verify whether the above stack trace is even related. I suspect the stack trace occurred _when the server was shutdown while ModeShape was actively running the sequencer_. If that's the case, then the sequencing operation would have stopped immediately without saving any content, resulting in "missing information". (ModeShape runs all sequencing activities in the background, and each one is given its own session with which the sequencer reads and writes to the repository. This session is not available to any other components, meaning the session cannot be closed except by the sequencer. But as one might expect shutting down a repository must necessarily close all open sessions, and this includes any sessions being used by sequencing operations running in the background.) Regarding the exception, my guess is that the user too quickly shutdown the server. To fix, simply re-publish the file. If the exception is unrelated, then you might not just be waiting long enough. The sequencing operation is asynchronous (via an internal queue), which means that it may take a few minutes (or longer if the server is under load) for the sequencing output to appear in the repository. To test this out, simply perform your procedure and then repeat step 4 multiple times to see if additional rows show up in the query results. was (Author: rhauch): Please verify whether the above stack trace is even related. I suspect the stack trace occurred _when the server was shutdown while ModeShape was actively running the sequencer_. If that's the case, then the sequencing operation would have stopped immediately without saving any content, resulting in "missing information". (ModeShape runs all sequencing activities in the background, and each one is given its own session with which the sequencer reads and writes to the repository. This session is not available to any other components, meaning the session cannot be closed except by the sequencer. But as one might expect shutting down a repository must necessarily close all open sessions, and this includes any sessions being used by sequencing operations running in the background.) My guess is that the user too quickly shutdown the server. To fix, simply re-publish the file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira