PK73248: Clicking Apply and Save on the "New application specific bindings" panel causes a duplicate binding name error.

Fixes are available

APAR status

Closed as program error.

Error description

Using the WebSphere Application Server administrative console:
Configure a bus member and message engine:
1. Navigate to Service Integration > Buses
2. Click New
3. Name the bus TestBus
4. Click Next all the way to Finish
5. Under Buses -> TestBus -> Bus members, click Add
6. Using defaults, click Next until the Finish
button appears,then Save.

Install a web service client application ( such as the one
contained in the Sample JaxWSServicesSamples.ear )

Configure the web service client application policy set and
bindings
1. Navigate to WebSphere enterprise applications
> <service client app> > Service client policy sets and
bindings
2. Select the client service -> click "Attach client policy
set"
3. Select "WSReliableMessaging persistent" (if its missing in
the dropdown, Import the policy set from the Default
repository )
4. Select the client service again, click "Assign binding"
5. Select "New Application Specific Binding" option
6. Use the Binding configuration name: testRM
7. Add the "WS-ReliablingMessaging" policy type
8. For Bus name and the Messaging engine select the ones
previously created
9. Click Apply and Save


The following message is displayed on the console:
"A duplicate name exists. You must use a unique name."

The WS-ReliableMessaging policy type just added does
not show up on the panel.

If the Client policy set and bindings panel is accessed,
the binding has actually been created.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V7.0           *
*                  administrative console users that create    *
*                  new application specific bindings           *
****************************************************************
* PROBLEM DESCRIPTION: Creating a new application specific     *
*                      binding and clicking Apply and then     *
*                      Save can cause a duplicate binding      *
*                      name error to be displayed.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A flag used to indicate when a New binding name should be
checked for duplicate name entries was not being set to false
in the BindingsDetailAction class.

Problem conclusion

The flag to check for duplicate name entries is now properly
set.
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

Temporary fix

Comments

APAR Information

APAR number
PK73248
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-03
Closed date
2008-10-28
Last modified date
2008-10-28

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

R700 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

PK73248: Clicking Apply and Save on the "New application specific bindings" panel causes a duplicate binding name error.

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

R700 PSY

Document Information

Share your feedback

Need support?