Issue with configuring the initial and maximum capacity for the EJB pool using EJB 3.0 annotations? What are supported properties for ActivationConfigProperty? (Doc ID 979972.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle Weblogic Server - Version 10.3 and later
Information in this document applies to any platform.
***Checked for relevance on 8-Aug-2013***

Symptoms

On trying to configure initial and maximum capacity for the EJB pool you will face issues, since the changes are not implemented when using EJB 3.0 annotations on WLS EJB Container. Below is a simple illustration:

 @MessageDriven(
name="SampleMDB",
mappedName = "oracle.sample.queue",
activationConfig = {
  @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
  @ActivationConfigProperty(propertyName = "initialBeansInFreePool", propertyValue = "10"),
  @ActivationConfigProperty(propertyName = "maxBeansInFreePool",
propertyValue = "10"),
  @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "oracle.sample.connectionFactory"),
  @ActivationConfigProperty(propertyName = "initialContextFactory", propertyValue = "weblogic.jndi.WLInitialContextFactory"),
  @ActivationConfigProperty(propertyName = "providerUrl", propertyValue = "t3://localhost:7001"),
  @ActivationConfigProperty(propertyName = "transactionType", propertyValue = "CONTAINER"),
  @ActivationConfigProperty(propertyName = "defaultTransaction", propertyValue = "NOT_SUPPORTED"),
 @ActivationConfigProperty(propertyName = "durable", propertyValue = "FALSE") })

Changes

Using annotations to configure initial and maximum capacity for the EJB pool.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms