[Design of POJO Server] - Re: VFS issues
by scott.stark@jboss.org
I have merged the nested jar capability into the org.jboss.virtual tree, and to support this added a notion of an options map to the VFSContext. This is curretnly parsed from the rootURL query string. It could be made an explicit map of options that does not require a String key and value.
I'm also working on the Serialization support, but the hiearchy in the abstract plugin classes is not consistent with the data that needs to be written out. The problem is that the AbstractVirtualFileHandler has the VFSContext reference, but it does not have the URL needed to recreate this. This exists in the AbstractURLHandler. Either the rootURL is needed at the AbstractVirtualFileHandler, or the handler url is pushed to this level, in which case I don't see much point to the AbstractURLHandler.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970363#3970363
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970363
19 years, 7 months
[Design of JCA on JBoss] - Re: StdServerSession/StdServerSessionPool -- JmsServerSessio
by weston.price@jboss.com
Also:
Driven by client request the following changes have been made the the StdServerSessionSession/Pool in the ASF implementation:
1) 3 new elements have been added to jboss.xml
| <LazyInitialization></LazyInitialization>
| <RecycleIdleSessions></RecycleIdleSessions>
| <IdleTimeOutMinutes></IdleTimeOutMinutes>
|
|
LazyInitialization being set to true requires that the StdServerSessionPool be lazily constructed with only the minimum pool size being created on startup.
RecycleIdleSesssion being set to true creates a JMS Reaper that functions in the same manner as our IdleRemover: removes idle JMS Sessions a configured interval (IdleTimeoutMinutes)
As a result, the StdServerSessionPool functions in a similar manner to the InternalManagedConnection pool. A semaphore has be implemented to managed acquiring session. Idle sessions are recycled with a PoolFiller maintaining the minimum pool size in the case that the session count falls below the minimum.
THis stuff is on a different branch at this point but my plan is to carry these features over to the JMS Inflow stuff as time permits.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970331#3970331
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970331
19 years, 7 months