PM05816: Eclipse workflow integration is unstable.

APAR status

• Closed as program error.

Error description

• Rhapsody 7.5.1 and previous: Customers often run into a situatio
  n where the LocateInRhapsody from Eclipse does no longer work.
  Rhapsody seems to receive some signal: The window moves to backg
  round, instead of getting the focus.
  Moving it back to foreground manually then sometimes shows that
  the Locate has worked, sometimes it has not.
  This is the most frequent problem that customer has.
  Sometimes there are other instability symptoms to observe, e.g.
  occasional messages that the project was not be connected though
   it is. All this is not reproducible.
  
  Below is email conversation between customer and PD:
  
  From:       Yura Zharkovsky/Haifa/IBM
  
  Sent:       Montag, 18. Januar 2010 08:01
  
  To:         Torsten Schoefbeck
  
  Cc:         Sasha Rekhter; Ubaidu Peediakkal
  
  Subject:    Re: Eclipse Interface
  
  Hi Torsten,
  
  I spend some time with the Eclipse interface to check the workfl
  ow
  integration. Sometimes at Draeger we see instabilities (loss of
  
  communication, locate only works in one direction, no focus swit
  ch,...)
  It's very hard to track it down as it's not really reproduceable
  .
  I hope we are able to send clearer information later. But do you
   have
  information for this already?
  
  Communication issue is probably caused by ports binding problem
  (ports
  remain bound after you close Rhapsody or Eclipse). The simplest
  
  workaround is just to switch port in both Eclipse and Rhapsody.
  We know
  about this issue but it's very hard to reproduce.
  
  Honestly, I was never able to reproduce it.
  
  However. if you believe that this problem is critical please log
   a
  defect (User should be notified to switch port when we a binding
  
  problem is found)
  
  .
  
  Business impact ( BusImpact )
  
  We really want to use the Eclipse workflow integration. Unfortun
  ately
  it is very unstable. The proposed workaround takes much time and
   maybe
  does not help in all cases.
  
  .
  

Local fix

Problem summary

• Eclipse workflow integration is unstable.
  

Problem conclusion

• Fixed in 7.5.2
  

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:

Fix information

• Fixed component name

  TLOGIC RHAPSODY

• Fixed component ID

  5724V74RP

Applicable component levels

• R751 PSN

     UP