APAR status
Closed as program error.
Error description
In WebSphere Application Server v5.0.2, the Administrative
Console does not update the resources.xml file when setting
Expiry for a WebSphere JMS Provider Queue Destination:
Administrative Console -> Resources -> WebSphere JMS Provider ->
WebSphere Queue Destinations -> <queue_destination_name> ->
Expiry
The resources.xml file will not have an entry for
"expiry=<expiry_value>"
Example excerpt from resources.xml file:
<resources.jms:JMSProvider xmi:id="builtin_jmsprovider"
name="WebSphere
JMS Provider" description="Built-in WebSphere JMS Provider"
externalInitialContextFactory="" externalProviderURL="">
<factories
xmi:type="resources.jms.internalmessaging:WASQueue"
xmi:id="WASQueue_1077123592887" name="myqueue"
jndiName="jms/myqueue"
persistence="PERSISTENT" priority="APPLICATION_DEFINED"
specifiedPriority="0"/>
</resources.jms:JMSProvider>
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server V5.x admin *
* console users *
****************************************************************
* PROBLEM DESCRIPTION: The admin console does not update *
* resources.xml file when setting Expiry *
* for WebSphere JMS Provider Queue *
* Destination *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The console code had a misplaced condition check that caused
the expiry entry not being updated correctly.
Problem conclusion
Modified the console code to correct the misplaced condition
check so the expiry entry will be set correctly in
resources.xml file
Temporary fix
change checked in, waiting to be picked up by a 5.0.2.x
service pack
Comments
APAR information |
APAR number |
PQ84999 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-02-20 |
Closed date |
2004-04-20 |
Last modified date |
2004-04-20 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|