PK72294: Problems administering WebSphere MQ as an messaging provider.

Fixes are available

APAR status

Closed as program error.

Error description

Problems using the administrative console to create and edit
WebSphere MQ messaging resources.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server 7.0,  *
*                  using WebSphere MQ as a messaging provider. *
****************************************************************
* PROBLEM DESCRIPTION: Problems editing WebSphere MQ           *
*                      connection factories, activation        *
*                      specifications and topics via the       *
*                      administrative console.                 *
*                      The default for the "message            *
*                      retention" option for a WebSphere MQ    *
*                      activation specification is             *
*                      also incorrect.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A java.lang.ArrayIndexOutOfBoundsException may be thrown when
adding a container authentication alias to a WebSphere MQ
connection factory.

When modifying a WebSphere MQ JMS Activation Specification
Authentication alias or WebSphere MQ connection factory
Container authentication alias back to the (none) value from
another value in the administrative console does not unset the
authentication alias in the configuration files and remains at
its previous value.

When selecting "OK" on the MQ Config panel:
(Resources > Queues > [MQ QUEUE] > WebSphere MQ connection
properties)
The following error is displayed:
"Invalid path
/com.ibm.ws.console.resources.jms.mqseries.forwardCmd was
requested"

When using the "Test connection" button on step 3 of the
wizard for creating MQ (queue/topic) connection factories and
activation specifications the test was always connected via
"bindings" regardless of whether "binding", "client" or
"bindings then client" had been selected as the transport type.

WebSphere MQ JMS Topics cannot be created at cluster scope.
When creating an MQ JMS Topic at cluster scope the error
message "ADMG0007E: The configuration data type Cluster is not
valid." is displayed when the OK button is clicked.

The default setting of the "message retention" option for a
WebSphere MQ activation specification is false, rather than
true. This means that messages which do not match the selection
criteria of an MDB consuming from that destination will be
either moved to the dead letter queue, or discarded (if
MQRO_DISCARD_MSG is set in the reporting options of the
message).

Problem conclusion

```
This APAR fixes these problems.
```

Temporary fix

Comments

APAR Information

APAR number
PK72294
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-17
Closed date
2008-11-14
Last modified date
2008-11-14

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
PLAT MSG COM
Fixed component ID
620800101

Applicable component levels

R300 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK72294: Problems administering WebSphere MQ as an messaging provider.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R300 PSY

Document Information

Share your feedback

Need support?