Issue Details (XML | Word | Printable)

Key: GLASSFISH-18803
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: oleksiys
Reporter: yavuzs
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

no response for a chunked package

Created: 13/Jun/12 12:04 PM   Updated: 14/Dec/12 05:43 PM
Component/s: grizzly-kernel
Affects Version/s: 3.1.2_b23
Fix Version/s: None

Time Tracking:
Original Estimate: 1 day
Original Estimate - 1 day
Remaining Estimate: 1 day
Remaining Estimate - 1 day
Time Spent: Not Specified
Time Spent - Not Specified

File Attachments: 1. File seac808012.cap (920 kB) 13/Jun/12 12:04 PM - yavuzs

Environment:

SunOs, x86, 64bit


Tags: http http-listener
Participants: oleksiys and yavuzs


 Description  « Hide

there is a server that sends us chunked requests (by POST), our application on glassfish takes these packages and process them. but somehow, some of the packages are not processed by the application, also there is no log activity about these packages. but when we capture the network activity we can see that the request has come to the server.
we tried "-Dcom.sun.enterprise.web.connector.grizzly.enableSnoop=true" parameter. with this parameter, for the lost request there is no log.
here is a lost request:
Host: 192.168.100.10:49205
Transfer-Encoding: chunked

185
<?xml version='1.0' encoding='UTF-8'?>
<env:Envelope xmlns:env='http://www.w3.org/2003/05/soap-envelope' xmlns:seadac='http://www.schange.com/2004/SeaDAC/triggers'>
<env:Header><seadac:transaction transaction-id='{20321632-B758-442a-ADFE-6E4607343AE3}' origination-time='2012-06-12T08:29:04Z' env:role='http://www.w3.org/2003/05/soap-envelope/ultimateReceiver'/></env:Header>
<env:Body>
80
<seadac:subscription-notification subscription-id='{1942B6B8-158F-4279-B9E9-0429671BEC67}' current-request='3' next-request='4'>
c7
<seadac:hierarchy-changed hierarchy-uid='539401'><seadac:node-added hierarchy-uid='539710' asset-uid='528673'/></seadac:hierarchy-changed></seadac:subscription-notification></env:Body></env:Envelope>
0

you can find the capture attached.
frame 7824 and 7825 are the same request that the server sends to all subscribed clients. for this example there are two client subscribed. the gf application and the tomcat application. as you see, at the frame 7824 tomcat responded the request but at the frame 7825 fg did not respond the request.
regards,



yavuzs added a comment - 19/Jun/12 11:02 AM

any response?


shreedhar_ganapathy made changes - 13/Dec/12 08:45 PM
Field Original Value New Value
Assignee shreedhar_ganapathy [ shreedhar_ganapathy ] oleksiys [ oleksiys ]
Component/s grizzly-kernel [ 10632 ]
oleksiys added a comment - 14/Dec/12 01:08 PM

sorry for the late response.
is it still the case w/ Glassfish 3.1.2.2?

thanks.


yavuzs added a comment - 14/Dec/12 01:12 PM

the version is : GlassFish Server Open Source Edition 3.1.2 (build 23)


oleksiys added a comment - 14/Dec/12 01:38 PM

yes, I understand, but there is a newer version (patch release) where this issue might have been fixed.
are you able to reproduce the issue consistently, or it happens sporadically?


yavuzs added a comment - 14/Dec/12 05:43 PM

it happens sporadically. we didn't try new patch yet.