PM86925: RTCP SHOWS "DEPLOYING" WHEN DEPLOYING A SECOND STUB TO AN AGENT ON NON-WINDOWS SYSTEMS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • STEPS TO REPRODUCE
    
    Install and run the Rational Integration Tester Agent
    (RIT-Agent) on a non-Windows system.
    
    Use Rational Test Control Panel (RTCP) VIE pages to deploy one
    stub to this Agent.
    
    Wait for the stub to show as ready.
    
    Use RTCP to deploy a second stub.
    
    EXPECTED RESULT
    
    The second stub should deploy and show"Ready" status in the
    RTCPdisplay.
    
    ACTUAL RESULT
    
    The RTCP status always displays "Deploying".
    
    The console of the RIT-Agent shows the following Java null
    pointer exception:
    
    SEVERE: Exception in callback processing received object
    java.lang.NullPointerException
    
    atcom.ghc.appfactory.ApplicationFactory.X_makeDynamicApplication
    (ApplicationFactory.java:275)
    
    atcom.ghc.appfactory.ApplicationFactory.makeNewApplication(Appli
    cationFactory.java:305)
    
    atcom.ghc.appfactory.rest.RESTApplicationFactorySPI$1.caseCreate
    NewInstance(RESTApplicationFactorySPI.java:138)
    
    atcom.greenhat.vie.comms1.agent.util.AgentSwitch.doSwitch(AgentS
    witch.java:195)
    
    atcom.greenhat.vie.comms1.agent.util.AgentSwitch.doSwitch(AgentS
    witch.java:98)
    
    atcom.greenhat.vie.comms1.agent.util.AgentSwitch.doSwitch(AgentS
    witch.java:86)
    
    atcom.ghc.appfactory.rest.RESTApplicationFactorySPI.processComma
    nd(RESTApplicationFactorySPI.java:189)
    
    atcom.ghc.appfactory.rest.RESTApplicationFactorySPI$CommandCallb
    ack.onReceived(RESTApplicationFactorySPI.java:119)
    
    atcom.ghc.appfactory.rest.RESTApplicationFactorySPI$CommandCallb
    ack.onReceived(RESTApplicationFactorySPI.java:1)
    
    atcom.greenhat.vie.comms.util.ObjectPoller$Poller.run(ObjectPoll
    er.java:131)
    
    atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.
    java:482)
    
    atjava.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTa
    sk.java:362)
    
    atjava.util.concurrent.FutureTask.runAndReset(FutureTask.java:18
    9)
    
    atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutu
    reTask.access$301(ScheduledThreadPoolExecutor.java:189)
    
    atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutu
    reTask.run(ScheduledThreadPoolExecutor.java:304)
    
    atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolEx
    ecutor.java:1121)
    
    atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE
    xecutor.java:614)
            atjava.lang.Thread.run(Thread.java:780)
    

Local fix

  • The problem is caused by an error in the installed version of
    the Agent.config file on Linux.
    
    Open the RIT-Agent /config/Agent.config file in an editor and
    check that the following XML stanza:
    
       <application type="VirtualApp" workingDirectory="."
    dataHome="@user.home/.rit8/cmd-workspace">
          <args>
             <arg value=".\RunTests.exe"/>
          </args>
          <instance name="instance1"/>
       </application>
    
    In 800 and 801 installs the <instance> element will be missing.
    The problem can be corrected by adding the <instance> tag
    exactly as shown above under the </args>.
    
    The agent must then be restarted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Linux users of RTVS                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An attempt to start a 2nd stub that requires the Agent to    *
    * load a separate test engine will result in the stub becoming *
    * stuck in the deploying state and an exception from the       *
    * agent.                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Correct the agent.config file on the RTVS server (RIT Agent) *
    * as per local workaround.                                     *
    ****************************************************************
    

Problem conclusion

  • This problem was corrected in release 8.5 of RTW.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM86925

  • Reported component name

    RATL TEST VIRT

  • Reported component ID

    5725G9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-12

  • Closed date

    2013-06-24

  • Last modified date

    2013-06-24

  • 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

    RATL TEST VIRT

  • Fixed component ID

    5725G9400

Applicable component levels

  • R800 PSY

       UP

  • R801 PSY

       UP

  • R850 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Test Virtualization Server

Software version:

8.0.1

Reference #:

PM86925

Modified date:

2013-06-24

Translate my page

Machine Translation

Content navigation