[
http://jira.nuxeo.org/browse/NXP-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat closed NXP-1545.
--------------------------------
Resolution: Fixed
Not more SFSB in webapp in 5.1 branch
> could not find stateful bean errors (passivation issues)
> --------------------------------------------------------
>
> Key: NXP-1545
> URL: http://jira.nuxeo.org/browse/NXP-1545
> Project: Nuxeo Enterprise Platform 5
> Issue Type: Bug
> Components: Web Foundations, Web UI
> Affects Versions: 5.1.0.GA
> Reporter: Olivier Grisel
> Assignee: Thierry Delprat
> Fix For: 5.1.3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The current state of platform has still issues with a number of a Stateful
> bean that fail to get restored after passivation. Here is a procedure to hunt
> them:
> - set up the threshold of the logs for appender File (
> server/default/conf/log/log4j.xml ) to level DEBUG after having used the
> current version of "ant patch" to enable the logging of DEBUG level EJB3
> serializer:
> <category name="org.jboss.ejb3"><priority value="INFO"/></category>
> <category
> name="org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager"><priority
> value="DEBUG"/></category>
> - adjust the serializer to passivate beans more often than on a real
> production setup using the idleTimeoutSeconds parameter of the file
> server/default/deploy/ejb3-interceptors-aop.xml, for instance :
> <annotation
> expr="!class(@org.jboss.annotation.ejb.cache.simple.CacheConfig) AND
> !class(@org.jboss.annotation.ejb.Clustered)">
> @org.jboss.annotation.ejb.cache.simple.CacheConfig (maxSize=100000,
> idleTimeoutSeconds=300)
> </annotation>
> Then run the application with and play around for a couple of minutes (import
> files, use the clipboard, the workflow, ...), then wait a couple of minute
> and then play again. You should get a couple of 404 errors though most
> passivation errors are logged silently without user level crash screen.
> Then run the find_passivation_errors.py python script to analyse the log
> automatically:
> https://svn.nuxeo.org/nuxeo/tools/jboss/find_passivation_errors.py
> Here is the output of the script after a 10min test run with 2 users playing
> around:
> BreadcrumbActionsBean
> ClipboardActionsBean
> DocumentTemplatesActionsBean
> DomainActionsBean
> NavigationContextBean
> QueryModelActionsBean
> ResultsProvidersCacheBean
> SearchActionsBean
> SearchColumnsBean
> TreeManagerBean
> WebActionsBean
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
