Bug 70 - connection handler debugging output indicates a problem (?)
Summary: connection handler debugging output indicates a problem (?)
Status: CLOSED
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 0.4.1
Hardware: x86 Linux
: P3 minor
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 1999-07-13 11:17 CDT by Ossama Othman
Modified: 1999-07-13 12:49 CDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ossama Othman 1999-07-13 11:17:48 CDT 
The debugging output from the server side connection handler indicates a
possible problem with the IIOP and UIOP transport implementations.

The debugging output is:
TAO (22370|1024) - TAO_GIOP::handle_input, read_header: No such file or
directory
TAO (22370|1024) - TAO_UIOP_Server_Connection_Handler::handle_input,
handle_input: No such file or directory

The above debugging messages can be reproduced by running the InterOp-Naming
test as follows:

*** Server ***
./INS_test_server -i object_name -o test.ior -ORBEndpoint uiop://foobar
-ORBdebuglevel 1

*** Client ***
./INS_test_client object_name -ORBDefaultInitRef "uiop://foobar"

This isn't the only way to get the unexpected error/warning messages shown
above.  The messages have been reported by several users running different
applications.
Comment 1 Ossama Othman 1999-07-13 12:42:59 CDT 
Okay, I was being paranoid.  The debugging message is expected.
Comment 2 Carlos O'Ryan 1999-07-13 12:49:59 CDT 
Ossama is right, the debugging message is simply stating that the connection was
closed, usually simply because the client is going down.