RS01142: SYNCHRONIZATION: CONNECTION FROM RULE DESIGNER FAILS WHEN THE USER NAME HAS A '@' CHARACTER

WebSphere Operational Decision Management V7.5.0.3 Fix Pack

APAR status

• Closed as program error.

Error description

• In Rule Designer, when the connection to Decision Center is
  defined with a user name that contains a '@' (for instance
  lolo.coco@lolo.com), and you perform a synchronization for a
  rule project, using right-click + "Decision Center > Synchronize
  with Decision Center ...", there is an error dialog with the
  following message: Protocol error when contacting
  "lolo.com@http://localhost:9083/teamserver"
  
  This does not occur if connecting from the "Decision Center
  configuration" wizard. Also it does not occur right after
  configuring the connection information (possibly because a
  connection is already opened). However, it will occur if Rule
  Designer is restarted and an attempt to synchronize is made from
  the right-click menu.
  
  The workspace log yields a related exception and stack trace:
  
  !ENTRY org.eclipse.team.core 4 0 2012-10-17 10:13:16.062
  !MESSAGE Protocol error when contacting
  "lolo.com@http://localhost:9083/teamserver".
  !STACK 0
  ilog.rules.model.dataaccess.DataAccessException: Protocol error
  when contacting "lolo.com@http://localhost:9083/teamserver".
    at
  ilog.rules.synchronization.endpoint.remote.client.RTSHttpRemoteA
  ccessProvider.connect(RTSHttpRemoteAccessProvider.java:51)
    at
  ilog.rules.synchronization.endpoint.remote.client.RemoteRuleMode
  lDataAccess.connect(RemoteRuleModelDataAccess.java:141)
    at
  ilog.rules.synchronization.subscriber.service.SynchronizationSer
  vice.connectTarget(SynchronizationService.java:58)
    at
  ilog.rules.dataaccess.rs4j.synchronization.RuleStudioSynchroniza
  tionService.connectTarget(RuleStudioSynchronizationService.java:
  110)
    at
  ilog.rules.synchronization.subscriber.client.AbstractSynchroniza
  tionClient.connectTarget(AbstractSynchronizationClient.java:53)
    at
  ilog.rules.synchronization.eclipseui.subscriber.EclipseWrapperSu
  bscriber.refresh(Unknown Source)
    at
  org.eclipse.team.internal.ui.synchronize.RefreshSubscriberPartic
  ipantJob.doRefresh(RefreshSubscriberParticipantJob.java:116)
    at
  org.eclipse.team.internal.ui.synchronize.RefreshParticipantJob.r
  un(RefreshParticipantJob.java:309)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
  Caused by:
  ilog.rules.synchronization.endpoint.remote.ConnectionException:
  Protocol error when contacting
  "lolo.com@http://localhost:9083/teamserver".
    ... 9 more
  Caused by: java.net.MalformedURLException: no protocol:
  lolo.com@http://localhost:9083/teamserver
    at java.lang.Throwable.<init>(Throwable.java:67)
    at java.net.URL.<init>(URL.java:501)
    at java.net.URL.<init>(URL.java:476)
    at java.net.URL.<init>(URL.java:425)
    at
  ilog.rules.synchronization.endpoint.remote.client.RTSHttpRemoteA
  ccessProvider.buildHttpClient(RTSHttpRemoteAccessProvider.java:1
  90)
    at
  ilog.rules.synchronization.endpoint.remote.client.RTSHttpRemoteA
  ccessProvider.connect(RTSHttpRemoteAccessProvider.java:46)
    ... 8 more
  

Local fix

• Use a user id which does not contain a '@' character
  

Problem summary

• the @ symbol is used internally as a delimiter in the code
  establishing the connection and it does not anticipate that
  this character could appear in the string
  

Problem conclusion

• the code is modified so that the internal processing does not
  depend on the characters included in the user name
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• None
  999
  

Fix information

• Fixed component name

  WDS FOR RULES

• Fixed component ID

  5725B6903

Applicable component levels

• R750 PSY

     UP