Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1946 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1946.

Report 1946 Actions

    Problem Report Number 1946
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0973
    Raised 1995-11-02 08:00
    Updated 2003-03-13 08:00
    Published 1995-11-07 08:00
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.3
    Test Identification XTI.os/cots/T.connect 2 5 6 10 22
    Problem Summary TSDT4.011 The master test program performs a synchronous t_connect() and, almost immediately, aborts the connection with t_close(). Since a TCP transport provider is being used, the connection is automatically ...
    Problem Text
    The master test program performs a synchronous t_connect() and, almost
    immediately, aborts the connection with t_close(). Since a TCP transport
    provider is being used, the connection is automatically accepted by the
    slave system. In some instances, before the slave can call t_accept(),
    the disconnect indication arrives, and t_accept() fails with a TLOOK error.
    examination of the XTI call trace below indicates a t_look() code of
    T_DISCONNECT (0x10).

    The tester for TCP is already built with the auto-accept flag enabled,
    but this doesn't affect the operation of this test case. This should
    be considered a test suite defect, because a timer delay could be used
    between the t_connect() and t_close() calls.

    Master trace:
    ============
    Thu Sep 28 16:37:15 1995 -> t_connect()
    > fd = 7
    > sndcall->addr.len = 16
    > sndcall->addr.buf = (16/16)
    00 02 4E 23 0F 0D 88 25 00 00 00 00 00 00 00 00 ..N#...%........
    > sndcall->opt.len = 0
    > sndcall->udata.len = 0
    > sndcall->udata.buf = (0/0)
    > rcvcall = 0x0
    Thu Sep 28 16:37:15 1995 <- t_connect() = 0

    Thu Sep 28 16:37:15 1995 -> t_getstate()
    > fd = 7
    Thu Sep 28 16:37:15 1995 <- t_getstate() = 5

    Thu Sep 28 16:37:15 1995 -> t_look()
    > fd = 7
    Thu Sep 28 16:37:15 1995 <- t_look() = 0x0

    Thu Sep 28 16:37:15 1995 -> t_close()
    > fd = 7
    Thu Sep 28 16:37:15 1995 <- t_close() = 0


    Slave trace:
    ===========
    Thu Sep 28 16:37:15 1995 -> t_accept()
    > fd = 6
    > resfd = 6
    > call->addr.len = 16
    > call->addr.buf = (16/16)
    00 02 27 12 0F 0D 88 25 00 00 00 00 00 00 00 00 ..'....%........
    > call->opt.len = 0
    > call->udata.len = 0
    > call->udata.buf = (0/0)
    > call->sequence = 1
    Thu Sep 28 16:37:15 1995 -> t_look()
    > fd = 6
    Thu Sep 28 16:37:15 1995 <- t_look() = 0x10
    Thu Sep 28 16:37:15 1995 <- t_accept() = -1; t_errno = TLOOK


    The above data was sumitted in a previous interpretation request (hp_xti_07),
    which was refused due to the fact that the test suite was run using
    loopback connections. The following formatted report shows the same
    problem occuring in a two-node test run in test connect 2, 6, and 10.
    Since this is an intermittent, timing related problem, it may also show
    up in T.connect test numbers 5 and 22, as shown above.

    ************************************************************************
    /tset/XTI.os/cots/connect/T.connect 2 Unresolved

    Test Description:
    If the implementation supports a connection-oriented transport
    service:
    When rcvcall is NULL, and O_NONBLOCK is clear, then a successful
    call to t_connect( fd, sndcall, rcvcall ) establishes a connection
    on fd, changes the state of the endpoint to T_DATAXFER, and
    returns a value of (int)0.

    Test Information:

    Test Information From Slave:
    t_accept() on TCP endpoint
    RETURN VALUES: expected: 0, observed: -1
    TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    t_look() 16
    ************************************************************************

    ************************************************************************
    /tset/XTI.os/cots/connect/T.connect 6 Unresolved

    Test Description:
    If the implementation supports a connection-oriented transport
    service:
    When sndcall->opt includes one or more options that specify an
    unknown option name, then a successful call to t_connect( fd,
    sndcall, rcvcall ) discards those options and does not return them
    in rcvcall->opt.

    Test Information:

    Test Information From Slave:
    t_accept() on TCP endpoint
    RETURN VALUES: expected: 0, observed: -1
    TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    ************************************************************************

    ************************************************************************
    /tset/XTI.os/cots/connect/T.connect 10 Unresolved

    Test Description:
    If the implementation supports a connection-oriented transport
    service:
    When sndcall->udata.len is zero, then a successful call to
    t_connect( fd, sndcall, rcvcall ) does not send any user data to
    the destination transport user.

    Test Information:

    Test Information From Slave:
    t_accept() on TCP endpoint
    RETURN VALUES: expected: 0, observed: -1
    TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    ************************************************************************
    Test Output
    400|19 2 1 13:43:10|IC Start
    200|19 2 13:43:10|TP Start
    520|19 2 00101523 1 1|t_accept() on TCP endpoint
    520|19 2 00101523 1 2|RETURN VALUES: expected: 0, observed: -1
    520|19 2 00101523 1 3|TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    220|19 2 2 13:43:10|UNRESOLVED
    410|19 2 1 13:43:10|IC End

    400|19 5 1 13:43:35|IC Start
    200|19 5 13:43:35|TP Start
    520|19 5 00101523 1 1|t_accept() on TCP endpoint
    520|19 5 00101523 1 2|RETURN VALUES: expected: 0, observed: -1
    520|19 5 00101523 1 3|TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    220|19 5 2 13:43:35|UNRESOLVED
    410|19 5 1 13:43:35|IC End

    400|19 6 1 13:43:35|IC Start
    200|19 6 13:43:35|TP Start
    520|19 6 00101523 1 1|t_accept() on TCP endpoint
    520|19 6 00101523 1 2|RETURN VALUES: expected: 0, observed: -1
    520|19 6 00101523 1 3|TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    220|19 6 2 13:43:35|UNRESOLVED
    410|19 6 1 13:43:36|IC End

    400|19 10 1 13:43:36|IC Start
    200|19 10 13:43:36|TP Start
    520|19 10 00101523 1 1|t_accept() on TCP endpoint
    520|19 10 00101523 1 2|RETURN VALUES: expected: 0, observed: -1
    520|19 10 00101523 1 3|TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    220|19 10 2 13:43:36|UNRESOLVED
    410|19 10 1 13:43:36|IC End

    400|19 22 1 13:43:38|IC Start
    200|19 22 13:43:38|TP Start
    520|19 22 00101523 1 1|t_accept() on TCP endpoint
    520|19 22 00101523 1 2|RETURN VALUES: expected: 0, observed: -1
    520|19 22 00101523 1 3|TERRNO VALUES: expected: 0 (NO ERROR), observed: 9 (TLOOK)
    220|19 22 2 13:43:38|UNRESOLVED
    410|19 22 1 13:43:38|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    While we expected that this problem would disappear once the test suite was
    executed between two nodes, this hasn't happened in this case. I recommend
    that this is treated as a test suite fault and that a waiver is granted on
    these grounds.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority