Fixes are available
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
When using WebSphere PFBC to make changes to the session pool configuration of a JMS Connection Factory (Queue or Topic), the requested changes are not made. To recreate the problem, do the following: (1) Create a JMS [Queue|Topic] Connection Factory using the Admin Console or AdminConfig wsadmin commands (2) Use the extractConfigProperties command to extract the configuration for the server: AdminTask.extractConfigProperties('-propertiesFileName my_test.props -configData Server=server1 -options [[PortablePropertiesFile true]]') (3) Modify the sessionPool subsection to include the desired values (4) Use the apply command to apply it back to the configuration: AdminTask.applyConfigProperties('[-propertiesFileName modified_my_test.props -reportFileName my_test_report.txt]') AdminConfig.save() The result is that the session pool is not updated with the desired values. This can be seen upon review of the session pool values in the resources.xml file or in the WebSphere Admin Console.
Local fix
1) Use AdminConfig.modify() commands or the Administrative Console to make the necessary changes to the session pool values. 2) Limited usage: Another workaround for session pool configuration attribute updates would be to extract a MQQueueConnectionFactory object using the AdminTask.extractConfigProperties() command without specifying "PortablePropertiesFile true" (by default, it is set to false). Then, modify the attribute(s) and apply the property file back to the SAME object of the same server using the AdminTask.applyConfigProperties() command. The limitation is that this approach is not portable, which means that you can not apply the modified property file to a different MQQueueConnectionFactory configuration object within a server or to a MQQueueConnectionFactory configuration object on a different server.
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V8.0 and * * V8.5.5 users of Property File Based * * Configuration (PFBC) commands. * **************************************************************** * PROBLEM DESCRIPTION: AdminTask.applyConfigProperties * * command * * does not update the session pool * * section of a JMS connection fatory. * **************************************************************** * RECOMMENDATION: Install a fix pack containing this APAR. * **************************************************************** The session pool section of a JMS connection factory is not updated or created using AdminTask.applyConfigProperties command as the configuration object instance in this case is not uniquely identified.
Problem conclusion
Added the logic to uniquely identify a connection pool configuration object instance in the AdminTask.applyConfigProperties command implementation. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.10. and 8.5.5.3. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI13983
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-18
Closed date
2014-04-03
Last modified date
2014-04-09
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022