PM99612: CCRC fails with Null Pointer Exception due to CQ designer's unable to deal with MBCS in field name.

Fixes are available

APAR status

Closed as program error.

Error description

CCRC is failed with Null Pointer Exception when field names use
MBCS.

Reproducing step is as follws.
 1. Launch CCRC.
 2. Login CQ database. (DB Set: KK_ORG, Username: Admin,
<password field is kept blank.>)
 3. Select BUGDB, and query all the "Activity Management (in
Japanese)" table.
 4. List of Activity Managemet" records are shown.
 5. Select any record, then Null pointer exception is occurred.
    Error messages are as follows.
java.lang.NullPointerException
    at
com.ibm.rational.team.client.rpm.resourcepropertymanagement.regi
stries.PropertyManagement.isConnected(PropertyManagement.java:15
68)
    at
com.ibm.rational.team.client.rpm.resourcepropertymanagement.regi
stries.PropertyManagement.retrieveProps(PropertyManagement.java:
425)
    at
com.ibm.rational.team.client.rpm.resourcepropertymanagement.regi
stries.PropertyManagement.retrieveProps(PropertyManagement.java:
118)
    at
com.ibm.rational.team.client.rpm.resourcepropertymanagement.regi
stries.PropertyManagement.getPropertyValue(PropertyManagement.ja
va:1978)
    at
com.ibm.rational.team.client.ui.cq.model.objects.CQRowData.getAd
dressBarName(CQRowData.java:146)
    at
com.ibm.rational.team.client.ui.views.GIExplorerDetails.setConte
ntIntoAddressBar(GIExplorerDetails.java:469)
    at
com.ibm.rational.team.client.ui.views.GIExplorerDetails.selectio
nChanged(GIExplorerDetails.java:302)
    at
com.ibm.rational.team.client.ui.views.GIExplorerDetails.eventFir
ed(GIExplorerDetails.java:415)
    at
com.ibm.rational.team.client.rpm.events.GUIEventDispatcher.fireE
vent(GUIEventDispatcher.java:48)
    at
com.ibm.rational.team.client.ui.views.GIExplorerDetailsPart$1.se
lectionChanged(GIExplorerDetailsPart.java:794)
    at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
    at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.runtime.Platform.run(Platform.java:857)
    at
org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
    at
org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199)
    at
org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.jav
a:160)
    at
org.eclipse.jface.viewers.StructuredViewer.updateSelection(Struc
turedViewer.java:2047)
    at
org.eclipse.jface.viewers.StructuredViewer.handleSelect(Structur
edViewer.java:1138)
    at
org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(Stru
cturedViewer.java:1168)
    at
org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrat
egy.java:227)
    at
org.eclipse.jface.util.OpenStrategy.access$3(OpenStrategy.java:2
21)
    at
org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.j
ava:388)
    at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
    at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3
682)
    at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:329
3)
    at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:23
89)
    at
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
    at
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
    at
org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
    at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Rea
lm.java:289)
    at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbenc
h.java:461)
    at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
149)
    at
com.ibm.rational.clearcase.standalone.plugin.StandaloneApplicati
on.run(StandaloneApplication.java:50)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at
org.eclipse.equinox.internal.app.EclipseAppContainer.callMethod(
EclipseAppContainer.java:572)
    at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseApp
Handle.java:171)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.run
Application(EclipseAppLauncher.java:106)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.sta
rt(EclipseAppLauncher.java:76)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
er.java:363)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
er.java:176)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

--------------------------------
The root cause for the NULL pointer exception problem, that is:
    In CCRC CQ form, just as its display design, it will
translate the "Field Name" input in CQ designer to XML tags,
which restrict the content cannot contain any of the characters
!"#$%&'()*+,/;<=>?@[\]^`{|}~, nor a space character, and cannot
start with -, ., or a numeric digit.
    That means, in CQ designer,  when you input "Field Name"
content, you should not input below characters:
!"#$%&'()*+,/;<=>?@[\]^`{|}~, nor a space character, and cannot
start with -, ., or a numeric digit.
    Even though CQ does check !"#$%&'()*+,/;<=>?@[\]^`{|}~, but
it only check ANSI code, did not check i18n code.
    In this defect, the customer use Japanese character "/" in
"Field Name" in CQ designer, , but CQ does not check that
special character, even worse in CCRC CQ form, it will translate
that to XML tags, then translation error error, cause that
defect.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:                                              *
* CCRC users when field names use mult-byte characters.        *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* CCRC is failed with Null Pointer Exception when field names  *
* use MBCS.                                                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************

Problem conclusion

A fix is available in ClearCase versions 8.0.0.9 and 8.0.1.2

Temporary fix

Comments

APAR Information

APAR number
PM99612
Reported component name
CC&CC MSITE WIN
Reported component ID
5724G3300
Reported release
712
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-10-21
Closed date
2013-12-13
Last modified date
2013-12-13

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
CC&CC MSITE WIN
Fixed component ID
5724G3300

Applicable component levels

R800 PSY
UP
R801 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSSH3S","label":"Rational ClearCase MultiSite"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 November 2021

Tips

PM99612: CCRC fails with Null Pointer Exception due to CQ designer's unable to deal with MBCS in field name.

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

R800 PSY

R801 PSY

Document Information

Share your feedback

Need support?