JMS CONTAINER INVOKER proxy-factory-config

<proxy-factory-config>
   <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
   <ServerSessionPoolFactoryJNDI>stdjmspool</ServerSessionPoolFactoryJNDI>
   <MinimumSize>1</MinimumSize>
   <MaximumSize>15</Maximumsize>
   <KeepAliveMills>30000</keepAliveMills>
   <MaxMessages>10</MaxMessages> 
   <MDBConfig>
            <ReconnectIntervalSec>10</ReconnectIntervalSec>
            <DLQConfig>
                <DestinationQueue>queue/DLQ</DestinationQueue>
                 <MaxTimesRedelivered>10</MaxTimesRedelivered>
                 <TimeToLive>0</TimeToLive> 
            <DLQConfig>
   </MDBConfig>
  </proxy-factory-config>

  MinimuSize :This specifies the minimum pool size for MDBS processig ,this defaluts to 1
  Maximusize :this specified the upper limit to the number of concurrent MDBS that will be
  allowed for the JMS destination ,this default to 15.
  MaxMessages:It is the maximum number of messages that can be assigned to a server session at one time. This defaults to 1. This
  value should not be modified from the default unless your JMS provider indicates this is supported. 
  KeepAliveMillis:This specifies the keep alive time interval in milliseconds for sessions in the session pool.
The default is 30000 .i think if it is not consumed ,then i will store in file or DB,not stay in pool(Memory)
MDBConfig:Configuration for the MDB JMS connection behavior.

  ReconnectIntervalSec:he time to wait (in seconds) before trying to recover the connection to the JMS
server.

  DeliveryActive: Whether or not the MDB is active at startup. The default is true.

DLQConfig: Configuration for an MDB's dead letter queue, used when messages are redelivered too many
times.

EJB container-pool-conf element

 MinimumSize:The MaximumSize specifies the maximum number of pool instances that are allowed.
MaximumSize:The MaximumSize specifies the maximum number of pool instances that are allowed.
strictMaximumSize:When there are MaximumSize active instances, any subsequent requests will be blocked
until an instance is freed back to the pool. The default value for strictMaximumSize is false.

strictTimeout:A value less than or equal to 0 will mean not to wait at
all. When a request times out waiting for an instance a java.rmi.ServerException is generated and the call
aborted.   

these all from JBOSS.DTD