apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Spinetti <m.spine...@pisa.iol.it>
Subject Re: RedHat Linux 7.1 Problem apr
Date Fri, 09 Jan 2004 16:56:45 GMT
I'll report all the information I have written in my three previous 
messages:

I have developed my application using spr and pthreads. I developed it 
in a red hat linux 9.0 and all is ok.

Then I tried my application on Red Hat linux 7.1 (glibc-2.2.4-33, gcc 
2.96, apr 0.9.4) and I have noticed that when I call apr_socket_recv, 
this method return immediately and  the return status is  70014.

I don't know what it means but I tried the application on two different 
machines (both with RedHat 7.1) and the behaviour is the same.

I ran the test inside test directory and I noticed this two error:

 > ./testall -v testsockets
Partial APR Tests:
   Socket Creation:          ..FFF.

6 tests run:  3 passed, 3 failed, 0 not implemented.

Failed tests in Socket Creation:
1) tcp6_socket: expected <0> but was <97>
2) udp6_socket: expected <0> but was <97>
3) sendto_receivefrom: expected <0> but was <97>

 > ./testall -v testtime
Partial APR Tests:
   Time:                     ..F....F....

12 tests run:  10 passed, 2 failed, 0 not implemented.

Failed tests in Time:
1) test_localstr: expected
---->
2002-08-14 12:05:36.186711 -25200 [257 Sat] DST
<----
but saw
---->
2002-08-14 21:05:36.186711 +7200 [257 Sat] DST
<----
2) test_ctime: expected
---->
Sat Sep 14 12:05:36 2002
<----
but saw
---->
Sat Sep 14 21:05:36 2002
<----


50% of testsockets fails!!!!!

This is the output of the program testsock in the test directory.

I have enclose between ** what it seems starnge to me.


 >./testsock
Initializing.........OK
Creating context.......OK
This test relies on the process test working.  Please
run that test first, and only run this test when it
completes successfully.  Alternatively, you could run
server and client by yourself.
Creating children to run network tests.......
server: Initializing............................ OK
server: Creating context........................ OK
server: Preparing getopt........................ OK
server: Creating new socket..................... OK
server: Setting option APR_SO_NONBLOCK.......... OK
server: Setting option APR_SO_REUSEADDR......... OK
server: Binding socket to port.................. OK
server: Listening to socket..................... OK
server: Setting up for polling.................. OK
Initializing.........OK
Creating context.......OK
       Client:  Making socket address...............OK
       Client:  Creating new socket.......OK
       Client:  Setting socket timeout.......OK
       Client:  Connecting to socket.......OK
       Client socket: 127.0.0.1:43847 -> 127.0.0.1:8021
       Client:  Trying to send data over socket.......OK
       Client:  Trying to receive data over socket.......server: Polling 
for socket...................... OK
server: Accepting a connection.................. OK
Server socket: 127.0.0.1:8021 -> 127.0.0.1:43847
server: Receiving data from socket.............. OK
OK
       Client:  Shutting down socket.......OK
       Client:  Closing down socket.......OK
server: Sending data over socket................ OK
server: Shutting down accepted socket........... OK
server: Closing duplicate socket................ OK
server: Closing original socket................. OK
Network test completed.
Creating children to run network tests.......
Waiting for a client to connect...
Creating a test file...
Sending the file...
Processing a client...
apr_socket_sendfile() updated offset with 0
apr_socket_sendfile() updated len with 370049
bytes really sent: 370049
After apr_socket_sendfile(), the kernel file pointer is at offset 0.
server: apr_socket_sendfile() worked as expected!
client: apr_socket_sendfile() worked as expected!
Network test completed.
Creating children to run network tests.......
Waiting for a client to connect...
Creating a test file...
Sending the file...
Calling apr_socket_sendfile()...
Headers (3):
       15 bytes (1)
       5 bytes (E)
       80000 bytes (^)
File: 200000 bytes from offset 0
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 65532 bytes
Calling apr_socket_sendfile()...
Headers (1):
       14488 bytes (^)
File: 200000 bytes from offset 0
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 81921 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 132567 bytes from offset 67433
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->11, sent 0 bytes
Processing a client...
Calling apr_socket_sendfile()...
Headers (0):
File: 132567 bytes from offset 67433
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 83415 bytes from offset 116585
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->11, sent 0 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 83415 bytes from offset 116585
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 34263 bytes from offset 165737
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->11, sent 0 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 34263 bytes from offset 165737
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 0 bytes from offset 0
Trailers (1):
       75140 bytes
apr_socket_sendfile()->11, sent 0 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 0 bytes from offset 0
Trailers (1):
       75140 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 0 bytes from offset 0
Trailers (1):
       25988 bytes
apr_socket_sendfile()->11, sent 0 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 0 bytes from offset 0
Trailers (1):
       25988 bytes
apr_socket_sendfile()->0, sent 25988 bytes
After apr_socket_sendfile(), the kernel file pointer is at offset 0.
***********apr_socket_recv()->11/Resource temporarily unavailable 
(expected APR_EOF)*******************
Network test completed.
Creating children to run network tests.......
Waiting for a client to connect...
Creating a test file...
Sending the file...
Calling apr_socket_sendfile()...
Headers (3):
       15 bytes (1)
       5 bytes (E)
       80000 bytes (^)
File: 200000 bytes from offset 0
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 65532 bytes
Calling apr_socket_sendfile()...
Headers (1):
       14488 bytes (^)
File: 200000 bytes from offset 0
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 81921 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 132567 bytes from offset 67433
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
Processing a client...
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 83415 bytes from offset 116585
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 34263 bytes from offset 165737
Trailers (3):
       19 bytes
       10 bytes
       90000 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 0 bytes from offset 0
Trailers (1):
       75140 bytes
apr_socket_sendfile()->0, sent 49152 bytes
Calling apr_socket_sendfile()...
Headers (0):
File: 0 bytes from offset 0
Trailers (1):
       25988 bytes
apr_socket_sendfile()->0, sent 25988 bytes
After apr_socket_sendfile(), the kernel file pointer is at offset 0.
server: apr_socket_sendfile() worked as expected!
client: apr_socket_sendfile() worked as expected!
Network test completed.



Can you explain me what is happening?


What Am I missing?


Thnaks for any support


--Marco




kfogel@collab.net wrote:

>Marco Spinetti <m.spinetti@pisa.iol.it> writes:
>  
>
>>Has anyone some information/advice about my problem?
>>
>>I'm waiting.....
>>    
>>
>
>A little more context is usually helpful.  Not everyone saves old
>messages.  What is your problem?
>
>  
>



Mime
View raw message