Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 7 Release Notes

Message Service and Message-Driven Beans

This section describes the known issues in Java Message Service (JMS), Sun Java System Message Queue, and message-driven beans issues and the associated solutions.

ID 

Summary 

6184426

ConnectException errors on HP-UX11.11during stress tests.

Configuration of the HP-UX TCP-IP parameter at the OS level or at the IMQ level is required. 

Solution

At the IMQ level, make the following changes: 

imq.portmapper.backlog=1000

imq.authentication.client.response.timeout=360

imq.jms.tcp.backlog=3000

imq.jms.max_threads=5000

4683029

The -javahome flag in all MQ Solaris scripts does not work if the value has a space.

The command-line utilities in Sun ONE Message Queue have a -javahome option that allows you to specify an alternate Java runtime. Using this option exposes a limitation where the path of the specified alternate Java runtime must not contain spaces. Examples of paths that have spaces are:

/work/java 1.4

This problem occurs at Application Server instance startup. When a Sun ONE Application Server instance is started, by default its corresponding Sun ONE Message Queue broker instance is also started. The broker always starts using the -javahome command-line option to ensure that it uses the same Java runtime used by the Application Server. If the Java runtime that is configured for use by the Application Server (and therefore passed on for use by the broker) is located at a path that contains spaces, broker startup fails, which also causes the Application Server instance startup to fail.

Solution

Make sure that the Java runtime used by the Application Server is located at a path that does not contain spaces.