Connection Factories

Two default connection factories have been deprecated. The JNDI names for these factories are:

• javax.jms.QueueConnectionFactory

• javax.jms.TopicConnectionFactory

For backwards compatibility, the JNDI names for these two connection factories are still defined and supported.

WebLogic JMS 6.x or later defines one connection factory, by default: weblogic.jms.ConnectionFactory

You can also specify user-defined connection factories using the Administration Console.

Note: Using the default connection factory, you have no control over the WebLogic server on which the connection factory may be deployed. If you would like to target a particular WebLogic Server, create a new connection factory and specify the appropriate WebLogic Server target(s).

It is recommended that existing code that use the deprecated classes be modified to use a new default or user-defined connection factory class.

For example, if your code specified the following constant using the default queue connection factory:

public final static String JMS_FACTORY="javax.jms.QueueConnectionFactory"

You should modify the constant to use a new user-defined connection factory, for example:

public final static String JMS_FACTORY="weblogic.jms.QueueConnectionFactory"

For true backwards compatibility with previous releases, you should ensure that you select the Allow Close In onMessage and User Transactions Enabled check boxes when configuring the connection factory.

For more information about defining connection factories, see "JMS Connection Factories" in the Administration Console Online Help.

In order to instantiate the default connection factory on a particular WebLogic Server, you must select the Enable Default JMS Connection Factories check box when configuring the WebLogic Server.

None required. This is a configuration requirement. For more information, see "Server" in the Administration Console Online Help.

Connections

When closing a connection, the call blocks until outstanding synchronous calls and asynchronous listeners have completed.

None required.

Sessions

When closing a session, the call blocks until outstanding synchronous calls and asynchronous listeners have completed.

None required.

Message Consumers

If multiple topic subscribers are defined in the same session for the same topic, each consumer will receive its own copy of a message.

None required.

When closing a message consumer, the call blocks until the method call completes and any outstanding synchronous applications are cancelled.

None required.

In order to comply with the JMS specification, if the close() method is called from within an onMessage() method, the application will hang unless the Allow Close In OnMessage check box is selected when configuring the connection factory. If the acknowledge mode is AUTO_ACKNOWLEDGE, the current message will still be automatically acknowledged.

None required. This is a configuration requirement. For more information, see "JMS Connection Factories" in the Administration Console Online Help.

Message Header Field

The JMSMessageID header field format has changed.

If you wish to access existing messages using the JMSMessageID, you may need to run one of the following weblogic.jms.extensions.JMSHelper methods to convert between WebLogic pre-JMS 5.1 and JMS 6.x JMSMessageID formats.

To convert from pre-5.1 to 6.x JMSMessageID format:

public void oldJMSMessageIDToNew(
String id,
long timeStamp
) throws JMSException

To convert from 6.1 to pre- 6.1 JMSMessageID format:

public void newJMSMessageIDToOld(
String id,
long timeStamp
) throws JMSException

Destinations

The createQueue() and createTopic() methods do not create destinations dynamically, only references to destinations that already exist given the vendor-specific destination name.

Update any portion of code that uses createQueue() or createTopic() to dynamically create destinations using the following JMSHelper class methods, respectively: createPermanentQueueAsync() and createPermanentTopicAsync().

For example, if your code used the following method to dynamically create a queue:

queue=qsession.createQueue(queueName);

You should modify the code to dynamically create a queue, as described in the sample findQueue() method in Using the JMSHelper Class Methods.

For more information on the JMSHelper classes, see Creating Destinations Dynamically.

When creating temporary destinations, you must specify a temporary template.

None required. This is a configuration requirement. For more information, see "JMS Templates" in the Administration Console Online Help.

You must be the owner of the connection in order to create a message consumer for that temporary destination.

When creating a message consumer on a temporary destination, ensure that you are the owner of the connection.

Durable Subscribers

You no longer need to manually create JDBC tables for durable subscribers. They are created automatically.

None required.

There is no limit on the number of durable subscribers that can be created.

None required.

When defining a client ID programatically, it must be defined immediately after creating a connection. Otherwise, an exception will be thrown and you will be unable to make any other JMS calls on that connection.

Ensure that the setClientID() method is issued immediately after creating the connection. For more information, refer to Defining the Client ID.

Session Pools

Session pool factories, session pools, referenced connection factories, referenced destinations, and associated connection consumers must all be targeted on the same JMS server.

Ensure that all objects are targeted on the same JMS server.

The SessionPoolManager and ConnectionConsumerManager interfaces that were published as part of the WebLogic JMS version 5.1 Javadoc have been removed from the version 6.x and later Javadoc, as they are system interfaces and should not be used within client applications.

If used, remove any references to these objects from the client application.

Transactions

To combine JMS and EJB database calls within the same transaction, a two-phase commit (2PC) license is required. In previous releases of WebLogic Server, it was possible to combine them by using the same database connection pool.

None required.

Recovering or rolling back received queue messages makes them available to all consumers on the queue. In previous releases of WebLogic Server, rolled back messages were only available to the session that rolled back the message, until that session was closed.

None required.

Connection Factories

For the Acknowledge Policy attribute in the Administration Console, the new default value of All is a work-around to accommodate a change in the JMS Specification. This new default setting represents a change from prior versions of JMS, which internally defaulted to Previous, and which did not appear as an option in the Administration Console.

As the message acknowledge policy for the connection factory, the Acknowledge Policy attribute only applies to implementations that use the CLIENT_ACKNOWLEDGE mode for a non-transacted session.

• All — acknowledge all messages ever received by a given session, regardless of which message calls the acknowledge method.

• Previous — acknowledge all messages received by a given session, but only up to and including the message that calls the acknowledge method.

For more information on message acknowledge modes, refer to Non-transacted Session.

Note: For connection factories used by MDBs (message-driven beans), always set the Acknowledge Policy field to Previous. Although the default MDB connection factory already does this, foreign connection factories may not.

If you want to acknowledge only previously received messages, up to and including the message that calls the acknowledge method, change the default Acknowledge Policy setting from All to Previous via the JMS Connection Factories tab in the Administration Console.

Destinations

In WLS 6.0, the JMS documentation correctly specifies values of default, true, and false for the StoreEnabled attribute of the JMSDestinationMBean, even though the software allowed for mixed case characters. version 6.1 or later, however, requires all lowercase characters for the StoreEnabled settings.

None required. This is a configuration requirement. For more information, see "JMS Templates" in the Administration Console Online Help.