6.20

7.0

The connection factories are bound in the root context – that is, TopicConnectionFactory.

The connection factories are bound in the jmsfactory/INSTANCE_NAME sub-context –that is, jmsfactory/default/TopicConnectionFactory.

The queues are bound in the jmsContext sub-context – that is, jmsContext/MyQueue.

The queues are bound in the jmsqueues/INSTANCE_NAME sub-context – that is, jmsqueues/default/MyQueue.

The topics are bound in the jmsContext sub-context – that is, jmsContext/MyTopic.

The topics are bound in the jmstopics/INSTANCE_NAME sub-context – that is, jmstopics/default/MyTopic.

Solution:

Use the new lookup names. See JMS Overview.

Change reason:

The JMS Provider service in 7.0 supports multiple instances so each application can use a different instance. There is a default JMS instance configured at the very fist start-up of the J2EE Engine, named “default”.

6.20

7.0

There is no security implementation in the JMS Service in 6.20 – that is,

conn_factory.createConnection();

conn_factory.createConnection(X, Y);

will create a connection for any string values for X and Y.

If the createConnection() method is used, the connection will be created with the user specified when the connection factory was created using the Visual Administrator tool. If the createConnection(X, Y) method is used, then X/Y should be a valid user/password, with which you can log on to the J2EE Engine.

Solution:

Make sure that X/Y is a valid user/password combination.

Change reason:

Compliance with the J2EE standards.

6.20

7.0

Directly manage the topics and queues using the Visual Administrator.

Manage the topics and queues of a specific instance using the Visual Administrator.

Solution:

See JMS Administration in the Administration Manual.