Download
Abstract
contextId has the deployment parameter which expects an associated application name. This causes a NoSuchElementException.
Download Description
PK71796 resolves the following problem:
ERROR DESCRIPTION:?
1. Navigate to "Service integration > buses"
2. Create a bus through the new bus wizard
3. Navigate to the new buses detail panel, click on the "Bus members" link and create a new bus member
4. Save to master configuration
5. Navigate to "Service integration > WS-Notification > Services"
6. Create a new WS-Notification service item using the wizard. Be sure to create a service point at step 4 of this wizard.
7. Navigate to "Services > Service clients"
8. Select a service (OutboundNotificationService was used in this scenario)
9. The result is an error on the page instead of displaying the correct service client detail panel.
Details of the Java exception occurring on the page:
An error occurred while processing request
/ibm/console/secure/layouts/configboxLayout.jsp
Message: java.util.NoSuchElementException
java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(Unknown Source)
at com.ibm.ws.console.core.ConfigFileHelper.parseContextId
(ConfigFileHelper.java:1204)
LOCAL FIX:?
PROBLEM SUMMARY:?
USERS AFFECTED:
Customers using WS-Notification get an exception when accessing "Services > Service clients" link
PROBLEM DESCRIPTION:
contextId has the deployment parameter which expects an associated application name. This causes a NoSuchElementException.
RECOMMENDATION:
Apply iFix PK71796
Accessing the "Services > Service clients" link for the WS-Notification service client results in an exception on the console.
Details of java exception:
An error occurred while processing request:
/ibm/console/secure/layouts/configboxLayout.jsp
Message: java.util.NoSuchElementException
java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(Unknown Source)
at com.ibm.ws.console.core.ConfigFileHelper.parseContextId(ConfigFileHelper.java:1204)
An if statement was introduced to check for the application name value in the contextId string, if it is an empty string the tokenizer is prevented from being advanced to the missing element.
PROBLEM CONCLUSION:?
The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.1.
Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Prerequisites
WebSphere Application Server version 7.0.0.0
Installation Instructions
Please review the readme.txt for detailed installation instructions.
Download Package
Download package
What is Fix Central (FC)?
What is DD?
Download | RELEASE DATE | LANGUAGE | SIZE(Bytes) | Download Options | ||
---|---|---|---|---|---|---|
7.0-WS-WAS-IFPK71796 | 09-18-2008 | US English | 20922 | FC | FTP | DD |
Technical Support
Contact IBM Support using SR (http://www-306.ibm.com/software/support/probsub.html), visit the WebSphere Application Server Support Web site (http://www.ibm.com/software/webservers/appserv/was/support/), or contact 1-800-IBM-SERV(U.S. only).
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg24020612