Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Andy Armstrong
Andy Armstrong wrote: UK time here. Still trying to get Ethereal to trace local (intra machine) traffic. I'm not around tomorrow so it may be Monday before there's anything to dissect. Monday came and went. Is anyone else interested in the detail of what follows (analysis of packet dumps) or

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Henri Gomez
Andy Armstrong wrote: Andy Armstrong wrote: UK time here. Still trying to get Ethereal to trace local (intra machine) traffic. I'm not around tomorrow so it may be Monday before there's anything to dissect. Monday came and went. Is anyone else interested in the detail of what follows

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Andy Armstrong
Henri Gomez wrote: That's as far as I've got and I'm just wondering whether it'd be nice to write an Ethereal packet dissector for AJP 1.3 or whether that would count as displacement activity. Is there anything specific I should be looking for Henri? There is allready an ajp13 disector for

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Henri Gomez
Andy Armstrong wrote: Henri Gomez wrote: That's as far as I've got and I'm just wondering whether it'd be nice to write an Ethereal packet dissector for AJP 1.3 or whether that would count as displacement activity. Is there anything specific I should be looking for Henri? There is allready

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Andy Armstrong
Henri Gomez wrote: The ajp13 disector was introduced in ethereal some months ago And I now have a copy of it rather than last year's model :) Anyway, the conversation looks like this in summary and a (naive) analysis of the contents of the packets doesn't yield anything obvious. - FORWARD

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Henri Gomez
Andy Armstrong wrote: Henri Gomez wrote: The ajp13 disector was introduced in ethereal some months ago And I now have a copy of it rather than last year's model :) Anyway, the conversation looks like this in summary and a (naive) analysis of the contents of the packets doesn't yield anything

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Andy Armstrong
Henri Gomez wrote: - FORWARD REQUEST - SEND HEADERS - SEND BODY CHUNK - END RESPONSE (REUSEP:1) OK, that's enough of a difference to explain what I'm seeing... May be something to do with chunk encoding which has been modified in ajp13/jk (after your works on domino I think) Well so far I've

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Henri Gomez
Andy Armstrong wrote: Henri Gomez wrote: - FORWARD REQUEST - SEND HEADERS - SEND BODY CHUNK - END RESPONSE (REUSEP:1) OK, that's enough of a difference to explain what I'm seeing... May be something to do with chunk encoding which has been modified in ajp13/jk (after your works on domino I

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Henri Gomez
Andy Armstrong wrote: Henri Gomez wrote: - FORWARD REQUEST - SEND HEADERS - SEND BODY CHUNK - END RESPONSE (REUSEP:1) OK, that's enough of a difference to explain what I'm seeing... May be something to do with chunk encoding which has been modified in ajp13/jk (after your works on domino I

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Andy Armstrong
Henri Gomez wrote: Nope, there was works on the chunked and header len in ajp13 java side which are probably not in old domino code... Take a look at what is on IIS which should be at right level OK, thanks :) -- Andy Armstrong, Tagish

Re: JK/ajp13 connection reuse problem

2003-10-21 Thread Andy Armstrong
Henri Gomez wrote: Well so far I've taken the old Domino Connector source and built it against the latest version of ajp13/jk (as of last week). Should that not 'just work'? BTW, we're now focusing on jk2, so what about working on jk2 for domino. The requirement will be having apr for your box

JK/ajp13 connection reuse problem

2003-10-16 Thread Andy Armstrong
I'm trying to bring the Domino connector up to date with the latest codebase and I'm running into a problem with connection reuse. The characteristic is that with connection reuse working normally the first message from Domino to Tomcat round trips without any problem but a second message

Re: JK/ajp13 connection reuse problem

2003-10-16 Thread Henri Gomez
Andy Armstrong wrote: I'm trying to bring the Domino connector up to date with the latest codebase and I'm running into a problem with connection reuse. The characteristic is that with connection reuse working normally the first message from Domino to Tomcat round trips without any problem but

Re: JK/ajp13 connection reuse problem

2003-10-16 Thread Andy Armstrong
Henri Gomez wrote: mod_jk 1.2.5 ? 1.2.6 - the latest code from the CVS yesterday. -- Andy Armstrong, Tagish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: JK/ajp13 connection reuse problem

2003-10-16 Thread Henri Gomez
Andy Armstrong wrote: I'm trying to bring the Domino connector up to date with the latest codebase and I'm running into a problem with connection reuse. The characteristic is that with connection reuse working normally the first message from Domino to Tomcat round trips without any problem but

Re: JK/ajp13 connection reuse problem

2003-10-16 Thread Andy Armstrong
Henri Gomez wrote: Could you get an ethereal dump ? That mail coincided exactly with my trying to remember whether I had a network tracing tool installed on this PC - and fortunately I do :) Ethereal dump coming up. -- Andy Armstrong, Tagish

Re: JK/ajp13 connection reuse problem

2003-10-16 Thread Henri Gomez
Andy Armstrong wrote: Henri Gomez wrote: Could you get an ethereal dump ? That mail coincided exactly with my trying to remember whether I had a network tracing tool installed on this PC - and fortunately I do :) Ethereal dump coming up. In such case ethereal is allways your friend. I'll

Re: JK/ajp13 connection reuse problem

2003-10-16 Thread Andy Armstrong
Henri Gomez wrote: I'll have to leave (Europe GMT end of day). UK time here. Still trying to get Ethereal to trace local (intra machine) traffic. I'm not around tomorrow so it may be Monday before there's anything to dissect. -- Andy Armstrong, Tagish