The following issues pertain to administration and configuration of Message Queue
On Windows platforms, the built-in Windows Firewall, which is enabled by default, must be manually configured with a firewall rule that allows the broker to accept incoming connections from clients. (Bug 6675595)
Double-click on Windows Firewall in the Control Panel
You will have to click Continue on the User Account Control dialog for the Windows Firewall Settings dialog to open.
In the Windows Firewall Settings dialog, click the Exceptions tab.
Click Add program.
In the Add a Program dialog, select java.exe and click Browse.
Windows identifies the broker process as a Java Platform SE binary. Therefore, locate the java.exe used by the broker (usually at jdk1.5.0_15\jre\bin\java.exe).
Click Change scope.
In the Change Scope dialog, select “Any computer (including those on the Internet.”
In the Add a Program dialog, click OK.
In the Windows Firewall Settings dialog, click OK.
On Windows platforms, the imqadmin and imqobjmgr commands throw an error when the CLASSPATH contains double quotes. (Bug 5060769)
Workaround: Open a command prompt window and unset the CLASSPATH:
Then run the desired command the same command prompt window, for example:
The -javahome option in all Solaris and Windows scripts does not work if the value provided contains a space. (Bug 4683029)
The javahome option is used by Message Queue commands and utilities to specify an alternate Java 2 compatible runtime to use. However, the path name to the alternate Java runtime must not contain spaces. The following are examples of paths that include spaces.
Windows: C:\jdk 1.4
Solaris: /work/java 1.4
Workaround: Install the Java runtime at a location or path that does not contain spaces.
The imqQueueBrowserMaxMessagesPerRetrieve attribute specifies the maximum number of messages that the client runtime retrieves at one time when browsing the contents of a queue. The attribute affects how the queued messages are batched, to be delivered to the client runtime, but it does not affect the total number of messages browsed. The attribute only affects the browsing mechanism, it does not affect queue message delivery. (Bug 6387631)