IPv4 instead of IPv6 is used to communicate between server and database server

Technote (troubleshooting)


Problem(Abstract)

Attempts to connect to the database using IBM Collaborative Lifecycle Management (CLM) products when IP address in database connection string is in version 6 causes using IPv4.

Symptom

Steps to reproduce:

  1. Set up connection string in CLM application such as IBM Jazz Team Server (JTS), IBM Rational Team Concert (RTC) or IBM Rational Quality Manager (RQM) to use IPv6. Here is example connection string:

    //[::1]:50000/JTS:user=db2inst1;password={password};
  2. Start Wireshark tool to overhear connection between CLM and database server.

    Expected result:
    The connection goes through IPv6.

    Actual result:
    The connection goes through IPv4.

Cause

CLM Applications are Java applications. In Java applications the communication goes through IPv4 as default.

Environment

IBM WebSphere Application Server (WAS) as an application server.

Resolving the problem

Procedure:

  1. Log in to WAS console.

  2. Click Servers > Server Types > WebSphere application servers > Server1.

  3. Click Java and Process Management > Process definition.

  4. Click Java Virtual Machine under Additional Properties.

  5. Add following line in the Generic JVM arguments field:
    -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true

  6. Restart WAS profile.

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational Quality Manager Web App Server Linux, Windows 4.0.0.1, 4.0.0.2, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 5.0 Standard

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Team Concert
Repository

Software version:

4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 5.0

Operating system(s):

Linux, Windows

Reference #:

1662521

Modified date:

2014-07-17

Translate my page

Machine Translation

Content navigation