What is the access log? How to check it?
Pid Ster wrote:
>
> On 08/03/2010 04:37, Shirely wrote:
>>
>> No error log.
>> This is the return packet
>>
>> No. Time Source Destination Protocol
>> Info
>> 3749 202.714770 118.142.22.3 192.168.1.109 HTTP
>> HTTP/1.1 200 OK
>
> Sure, but that does the access log say, does it also say zero bytes sent?
>
> What happens if the line:
>
> Utility.writeToFile("/WP.txt",str +"\n");
>
> throws an exception?
> The only line which writes output to the response is after that line, so
> if something stops the page before or at that line, then the response
> body will be empty.
>
> Admittedly, I can't think of a way for the page to stop there as a
> result of an exception and still send a 200 status, but it's worth
> exploring.
>
> Your JSP seems simple, but I can't tell exactly where it's writing the
> WP.txt file to, so this may also be causing a problem.
>
>
> p
>
>
>
>
>> Frame 3749 (170 bytes on wire, 170 bytes captured)
>> Ethernet II, Src: Tp-LinkT_d2:89:3a (00:25:86:d2:89:3a), Dst:
>> Tp-LinkT_b8:40:30 (00:27:19:b8:40:30)
>> Internet Protocol, Src: 118.142.22.3 (118.142.22.3), Dst: 192.168.1.109
>> (192.168.1.109)
>> Version: 4
>> Header length: 20 bytes
>> Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
>> Total Length: 156
>> Identification: 0x112b (4395)
>> Flags: 0x02 (Don't Fragment)
>> Fragment offset: 0
>> Time to live: 119
>> Protocol: TCP (0x06)
>> Header checksum: 0xa38a [correct]
>> Source: 118.142.22.3 (118.142.22.3)
>> Destination: 192.168.1.109 (192.168.1.109)
>> Transmission Control Protocol, Src Port: http (80), Dst Port: 52568
>> (52568),
>> Seq: 1, Ack: 379, Len: 116
>> Source port: http (80)
>> Destination port: 52568 (52568)
>> [Stream index: 71]
>> Sequence number: 1 (relative sequence number)
>> [Next sequence number: 117 (relative sequence number)]
>> Acknowledgement number: 379 (relative ack number)
>> Header length: 20 bytes
>> Flags: 0x18 (PSH, ACK)
>> Window size: 65536 (scaled)
>> Checksum: 0xa7be [validation disabled]
>> [Good Checksum: False]
>> [Bad Checksum: False]
>> [SEQ/ACK analysis]
>> Hypertext Transfer Protocol
>> HTTP/1.1 200 OK\r\n
>> [Expert Info (Chat/Sequence): HTTP/1.1 200 OK\r\n]
>> Request Version: HTTP/1.1
>> Response Code: 200
>> Server: Apache-Coyote/1.1\r\n
>> Transfer-Encoding: chunked\r\n
>> Date: Mon, 08 Mar 2010 04:21:06 GMT\r\n
>> \r\n
>> HTTP chunked response
>> End of chunked encoding
>> Chunk size: 0 octets
>> Chunk boundary
>>
>> 0000 00 27 19 b8 40 30 00 25 86 d2 89 3a 08 00 45 00 .'....@0.%...:..E.
>> 0010 00 9c 11 2b 40 00 77 06 a3 8a 76 8e 16 03 c0 a8 ....@.w...v.....
>> 0020 01 6d 00 50 cd 58 78 1e 12 3a 3e 9b 5f d4 50 18 .m.P.Xx..:>._.P.
>> 0030 01 00 a7 be 00 00 48 54 54 50 2f 31 2e 31 20 32 ......HTTP/1.1 2
>> 0040 30 30 20 4f 4b 0d 0a 53 65 72 76 65 72 3a 20 41 00 OK..Server: A
>> 0050 70 61 63 68 65 2d 43 6f 79 6f 74 65 2f 31 2e 31 pache-Coyote/1.1
>> 0060 0d 0a 54 72 61 6e 73 66 65 72 2d 45 6e 63 6f 64 ..Transfer-Encod
>> 0070 69 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a 44 61 ing: chunked..Da
>> 0080 74 65 3a 20 4d 6f 6e 2c 20 30 38 20 4d 61 72 20 te: Mon, 08 Mar
>> 0090 32 30 31 30 20 30 34 3a 32 31 3a 30 36 20 47 4d 2010 04:21:06 GM
>> 00a0 54 0d 0a 0d 0a 30 0d 0a 0d 0a T....0....
>>
>>
>>
>> Pid Ster wrote:
>>>
>>> On 06/03/2010 18:36, Shirely wrote:
>>>>
>>>> I already monitor it by network packet level, I found that server side
>>>> have
>>>> receive the reqeust. and it have response it by sending out a packet.
>>>> but
>>>> the response packet only have a "0" at the body part.
>>>
>>> How many bytes does the access log say it sent?
>>> Is there any error in any other log?
>>>
>>>
>>> p
>>>
>>>> Shirley
>>>>
>>>>
>>>> n828cl wrote:
>>>>>
>>>>>> From: Shirely [mailto:shir...@powerelab.com]
>>>>>> Subject: Re: Tomcat response Blank Page
>>>>>>
>>>>>> Then, I found that when it display blank page, it will not update the
>>>>>> session counter and also didn't read to text file.
>>>>>
>>>>> Sounds like something in between is responding to the request, rather
>>>>> than
>>>>> it reaching the server. Try running Wireshark on each end and see if
>>>>> you
>>>>> can catch the failure.
>>>>>
>>>>> - Chuck
>>>>>
>>>>>
>>>>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
>>>>> PROPRIETARY
>>>>> MATERIAL and is thus for use only by the intended recipient. If you
>>>>> received this in error, please contact the sender and delete the
>>>>> e-mail
>>>>> and its attachments from all computers.
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/Tomcat-response-Blank-Page-tp27792029p27831337.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
