-->
edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Create JMS session

Create JMS session pools


A JMS session pool enables an application to process messages concurrently. Once you have defined a JMS server, optionally, you can configure one or more session pools for each JMS server:

Note: Session pools are now used rarely, as they are not a required part of the J2EE specification, do not support JTA user transactions, and are largely superseded by message-driven beans (MDBs), which are a required part of the J2EE specification.

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

  2. In the Administration Console, expand Services > Messaging and select JMS Servers.

  3. On the Summary of JMS Servers page, click the JMS server you want to configure with a session pool.

  4. Click the Session Pools tab.

  5. On the JMS Session Pools page, click New.

    Note: Once you create a JMS session pool, you cannot rename it. Instead, delete it and create another one that uses the new name.

  6. On the Create a New JMS Session Pool page, define the general session pool options:

    1. In Name, enter a name for the JMS session pool.

    2. In Listener Class, enter the listener class that will be used by the JMS session pool, which is used to receive and process messages concurrently.

    3. Click OK.

    For more information about these session pool attributes, see Configuration Options.

  7. On the JMS Session Pools page, click the new session pool to open it.

  8. On the JMS Session Pool: Configuration page:

    1. In Connection Factory, enter the JNDI name of the connection factory for the session pool.

    2. In Acknowledge Mode, select the acknowledge mode used by non-transacted sessions within the session pool.

    3. In Sessions Maximum, enter the maximum number of concurrent sessions allowed for the session pool.

    4. In Transacted, select whether the session pool creates transacted sessions.

    For more information about these session pool attributes, see Configuration Options.

  9. Click Save.

  10. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).
} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i