RE: ComponentFactory decommissioning instance
> > But if it does not implement Poolable - what does it mean then ? > Nothing bad :) > > It just means that everytime your action is used a new instance of your > action class is created. > Now if you make your action implement Poolable (which is just a marker > interface) then cocoon will manage a pool of action instances for you, > and everytime your action is used it will take one from the pool instead > of creating a new instance. Works like a charm Thank you! LG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ComponentFactory decommissioning instance
Leszek Gawron wrote: Does your action implement the Poolable interface? If it doesn't then there is no point setting the pool parameters (at least in 2.0.4 it doesn't) because Action inherits straight from Component. It does not implement Poolable interface. Searching for the solution I just copied the declaration of another action. Usually the message below indicates that the pool size for this component is too small - the component instance is not returned to the pool but instead destroyed. But if it does not implement Poolable - what does it mean then ? Nothing bad :) It just means that everytime your action is used a new instance of your action class is created. Now if you make your action implement Poolable (which is just a marker interface) then cocoon will manage a pool of action instances for you, and everytime your action is used it will take one from the pool instead of creating a new instance. Jorg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ComponentFactory decommissioning instance
> Does your action implement the Poolable interface? If it doesn't then > there is no point setting the pool parameters (at least in 2.0.4 it > doesn't) because Action inherits straight from Component. It does not implement Poolable interface. Searching for the solution I just copied the declaration of another action. > > Usually the message below indicates that the pool size for this > component is too small - the component instance is not returned to the > pool but instead destroyed. But if it does not implement Poolable - what does it mean then ? -- Leszek Gawron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ComponentFactory decommissioning instance
Leszek Gawron wrote: DEBUG (2004-02-02) 15:55.06:770 [sitemap] (/test/report-save) PoolThread-9/DefaultComponentFactory: ComponentFactory decommissioning instance of com.***.ReportAcceptor. Does your action implement the Poolable interface? If it doesn't then there is no point setting the pool parameters (at least in 2.0.4 it doesn't) because Action inherits straight from Component. Usually the message below indicates that the pool size for this component is too small - the component instance is not returned to the pool but instead destroyed. I keep getting those messages in my sitemap.xmap. What does it really mean and how can I get rid of it. The action is quite simple. It does some request parameters processing and inserts data into the database. The sitemap snippets follow. try setting here pool-max to a higher number HTH Jorg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
