PQ74699: DUPLICATE SESSIONTABLENAME ENTRIES IN SERVER.XML, CAUSING AN SQL EXCEPTION WITH SESSION IN DB2. | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Users of WebSphere Application Server Version 5.0 who have configured HttpSession persistence to use DB2 are instructed to enter the database table name within which HttpSessions will be stored: (<Application Servers -> <server name> -> Webcontainer -> Custom Properties) After entering the database table name, an unreported error occurs such that the database table name is not correctly updated. Subsequent attempts by the HttpSession Manager to access the desired database table will result in an SQL exception that will appear in the log as: error message: BBOO0223I Exception is: com.ibm.db2.jcc.DB2SQLException: DB2JDBCSection Received Error in Method prepare:SQLCODE==> -204 SQLSTATE ==> 42704 Error Tokens ==> <<DB2 7.1 SQLJ/JDBC>> <IBMUSER.SESSION> In this example, <IBMUSER.SESSION> is an example and may differ on the user's system. This problem occurs because one or more duplicate entries for the SessionTableName exist within the server.xml configuration file for this server.Local fix The local fix for this problem is to manually edit the server.xml file to remove the duplicate entries. After the duplicate entries are removed the web admin user interface may be used to successfully update the SessionTableName. In order to edit the server.xml file, the Application Server must be stopped, the file editted and then the server must be restarted. When the Application Server is started, a message similar to the following message will be logged: Using the above example, the server.xml file exists in the directory: /WebSphere/V5R0M0/AppServer/config/cells/SY1/nodes/SY1/ servers/server1 The data within the file is in the ASCII codepage. If editing the file on z/OS, the file will have to be converted to EBCDIC, edited, and then converted to ASCII. While editing the file, search for all occurrences of "SessionTableName". More than one occurrance will be found. The following is an example SessionTableName stanza within the server.xml file: <properties xmi:id="Property_21" name="SessionTableName" value="SESSION" description="Relational table name for session state." required="true" /> The stanza begins with "<properties xmi:id=" and ends with " />". The entry may be written entirely on one line or on serveral lines (as in the above example). Delete all duplicate stanzas such that only one SessionTableName stanza remains. It is important that one SessionTableName stanza remain in the file after editing is complete. Note that the entire stanza must be deleted, i.e. starting with <properties xmi:id= and ending with />. After editing is complete, start the Application Server. The user may now return to the admin user interface and update the SessionTableName to the desired value and save the configuration.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Duplicate sessiontablename entries in * * server.xml, causing an sql exception * * with session in DB2. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the server.xml, there is a duplicate entry for the SessionTableName property. This duplicate entry caused the the following exception: error message: BBOO0223I Exception is: com.ibm.db2.jcc. DB2SQLException: DB2JDBCSection Received Error in Method prepare:SQLCODE==>-204 SQLSTATE ==> 42704 Error Tokens ==> <<DB2 7.1 SQLJ/JDBC>> IBMUSER.SESSION where IBMUSER is the Administration userid in use.Problem conclusion Post installer scripts will be provided to remove the duplicate entry from the server.xml in the templates directory. ++Hold for action will be provided to tell the user to remove duplicate entry from the server.xml under the server's directory. Once the duplicate entry is removed, the reported exception will not occur. APAR PQ74699 is associated with SERVICE LEVEL W501001 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ74699.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ74699
IBM Group: Software Group
Modified date: Feb 28, 2006
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.