General Issues

This section covers general issues in Message Queue 4.0. Some of these were introduced with previous Message Queue versions.

The following issues affect both editions of the Message Queue 4.0 product.

• SOAP clients. Previously the SAAJ 1.2 implementation jar used to refer to mail.jar and mail.jar did not need to be in CLASSPATH. In SAAJ 1.3 this reference was removed; thus, Message Queue clients must put mail.jar explicitly in CLASSPATH.

• In Message Queue 4.0, the example broker configuration for using an LDAP server as a user repository is provided in the comment area in the config.properties file, and the LDAP user repository example in the default.properties file has been commented out.

  If you previously relied on any property value in the example LDAP user repository properties specified in the default.properties file, your JMS application client will receive a security exception when attempting to create a JMS connection. This will happen after you upgrade to Message Queue 4.0.

  When your JMS client tries to make a connection to the Message Queue 4.0 broker, you will get a error in the broker log and your JMS client will receive the following exception:

  SecurityException.
  20/Aug/2004:11:16:41 PDT] ERROR [B4064]: Ldap repository ldap property
  .uidattr not defined for authentication type 
  basic:com.sun.messaging.jmq.auth.LoginException: 
  [B4064]: Ldap repository ldap property .uidattr not defined 
  for authentication type basic

  Workaround Set the broker property imq.user_repository.ldap.uidattr following the instructions in Chapter 8 in Sun Java System Message Queue 3 2005Q4 Administration Guide.