[jbosstools-issues] [JBoss JIRA] (JBTIS-186) ModeShape sometimes doesn't publish all models of Teiid VDB

[Randall Hauch (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12813424#comment-12813424 ] 

Randall Hauch commented on JBTIS-186:
-------------------------------------

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.

                
> ModeShape sometimes doesn't publish all models of Teiid VDB
> -----------------------------------------------------------
>
>                 Key: JBTIS-186
>                 URL: https://issues.jboss.org/browse/JBTIS-186
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: modeshape
>    Affects Versions: 4.1.3
>         Environment: Ubuntu 12.04, JBTIS 4.1.3.Beta4, DV 6.0.0.ER2, sun jdk 1.6
>            Reporter: Lucie Fabrikova
>         Attachments: BooksMode.vdb
>
>
> If I publish a teiid VDB with relational models .xmi in given environment, sometimes some (or all) of the models are not published. 

--
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