IBM Support

PI63752: RIT DOES NOT APPLY THE HTTP PROXY SETTING IN LIBRARY MANAGER FORREADING FROM RTCP

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In the case of there is a HTTP proxy between RIT and RTCP, and
    the proxy is set in Library Manager, RIT does not really use the
    proxy for accessing the RTCP. Although RIT showed it can reach
    RTCP by displaying a green check mark, but failed to read out
    domain information from RTCP.
    
    When recording database traffics via a JDBC proxy, RIT gives
    below exception:
    com.ghc.ghTester.proxy.JDBCProxyHelper$UnableToContactGHServerEx
    ception: [CRRIT8368E] RTCP is not reachable
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.getRules(JDBCProxyHelper.
    java:647)
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.getRules(JDBCProxyHelper.
    java:589)
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.getFirstRule(JDBCProxyHel
    per.java:130)
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.setMode(JDBCProxyHelper.j
    ava:234)
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.setMode(JDBCProxyHelper.j
    ava:214)
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.setMode(JDBCProxyHelper.j
    ava:198)
    at
    com.ghc.ghTester.recordingstudio.model.DatabaseMonitorableStateC
    ontroller.startDatabaseRecording(DatabaseMonitorableStateControl
    ler.java:201)
    at
    com.ghc.ghTester.recordingstudio.model.RecordingStudioJob.X_star
    tRecording(RecordingStudioJob.java:401)
    at
    com.ghc.ghTester.recordingstudio.model.RecordingStudioJob.startR
    ecording(RecordingStudioJob.java:215)
    at
    com.ghc.ghTester.recordingstudio.ui.monitorview.RecordAction$Sta
    rtRecordingAllSelectedMonitorsJob.run(RecordAction.java:123)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    Caused by: java.net.ConnectException: Connection timed out:
    connect
    at
    java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketIm
    pl.java:370)
    at
    java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainS
    ocketImpl.java:231)
    at
    java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl
    .java:213)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:404)
    at java.net.Socket.connect(Socket.java:643)
    at java.net.Socket.connect(Socket.java:590)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:193)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:462)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:557)
    at sun.net.www.http.HttpClient.(HttpClient.java:226)
    at sun.net.www.http.HttpClient.New(HttpClient.java:329)
    at sun.net.www.http.HttpClient.New(HttpClient.java:347)
    at
    sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Htt
    pURLConnection.java:1011)
    at
    sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURL
    Connection.java:990)
    at
    sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConne
    ction.java:865)
    at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpU
    RLConnection.java:1314)
    at
    java.net.HttpURLConnection.getResponseCode(HttpURLConnection.jav
    a:480)
    at
    com.greenhat.vie.comms.util.ObjectCommunicatorImpl.get(ObjectCom
    municatorImpl.java:216)
    at
    com.greenhat.vie.comms.util.ObjectCommunicatorImpl.get(ObjectCom
    municatorImpl.java:245)
    at
    com.ghc.ghTester.proxy.JDBCProxyHelper.getRules(JDBCProxyHelper.
    java:623)
    ... 10 more
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of Rational Integration Tester connecting to       *
    * Rational Test Control Panel via an HTTP proxy.               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Rational Integration Tester was not honoring the proxy       *
    * configuration when establishing a connection to Rational     *
    * Test Control Panel which may cause connectivity issues.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in version 9.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI63752

  • Reported component name

    RATL INTEGRA TE

  • Reported component ID

    5725G79IT

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-08

  • Closed date

    2016-12-12

  • Last modified date

    2016-12-12

  • 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 INTEGRA TE

  • Fixed component ID

    5725G79IT

Applicable component levels

  • R800 PSN

       UP

  • R801 PSN

       UP

  • R850 PSN

       UP

  • R851 PSN

       UP

  • R860 PSN

       UP

  • R870 PSN

       UP

  • R871 PSN

       UP

  • R900 PSN

       UP

  • R901 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSBLQQ","label":"IBM Rational Test Workbench"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 December 2016