connection problems after queued
 

I recently installed PHEX3.2 after a full uninstall of PHEX3.0.

All seems to work great with one exception. Downloads seem to work fine until I get "Queued" by the host. After waiting 60 seconds for my turn in the Que Phex tries to connect and then says "connection failed". This seems to happen with every host that places me in the Que. I can download from the host all day long until I get "Queued". Then I get connection failures every time from that host.

I included a screen capture of the network data that ultimately resulted in the "connection failed" response. I also included a partial video capture (AVI) to illustrate the problem. To save time...jump to the beginning of each attempted download.

Note that all downloads in the video are from the same host however the problem continues regardless of hosts.
ix
Looking for a solution.

BTW...in this example I first "Browsed Host" to obtain all files from a single host and configured to download only 1 file at a time to illustrate the problem.

Thanks
Dave

Follow-up to above post
 

Just a quick followup to my post above.

I reinstalled Phex 3.0. Configured it the same as above, and browsed the same host as before.

All downloads worked and "queued" properly. (Although its a very slow host with lots of traffic).

In addition....when I previously browsed the host with Phex 3.2 It only returned 90 files. I knew the host had approx 400 files but every time I browsed it returned exactly 90. When I browsed other hosts with 3.2 I would get some files but the GUI on the left would also say "connection error"

When I returnd to Phex 3.0...the browse worked properly returning 421 files.

Im not sure if this is a bug, or just something on my end.
Thanks

I found something regarding the host browsing. Once a file with blocked URN (malware) is in the browsing result the connection gets aborted.
I changed this in SVN to just skip the bad file.

I had no problems with queuing though...
To help debug this better try to add the following line to your phexCorePrefs.properties:

Download.CandidateLogBufferSize = 1000000

This gives about 1MB of extra memory for holding a candidate download log. You will see a Log button on the candidate toolbar. Pressing it shows the log of the candidate. The log shows the exchanged dialog and also includes status changes and errors. This log might give us an idea where and why something could go wrong.

Ill give it a try. Thanks

I tried using my Phex 3.2 again and had the same problem as posted above. Here is that log that you suggested Gregor.

I would get put in the "Que", the download would start when it was my turn, and then I would get a "connection failed" message each time.


071011 10:35:55,0812::phex.download.RemotelyQueuedExcepti on
071011 10:35:55,0812::Setting status to Queued on position: 5. Waiting 0:00. and raise timeout from 1192113355812 to 1192113438312(82500) Reason:null. OldStatus: REQUESTING
071011 10:37:18,0312::Setting status to Requesting... and raise timeout from 1192113438312 to 1192113438312(0) Reason:null. OldStatus: REMOTLY_QUEUED
071011 10:37:18,0312::HTTP Request:
GET /uri-res/N2X?urn:sha1:Z3RFEYQPDCENDWXUXRINCHUY????5YFJ HTTP/1.1
User-Agent: Phex 3.2.0.102
Host: 66.66.???.94:15088
X-Queue: 0.1
Connection: Keep-Alive


071011 10:37:18,0843::HTTP Response:
HTTP/1.1 200 OK
Server: LimeWire/4.12.11
X-Gnutella-Content-URN: urn:sha1:Z3RFEYQPDCENDWXU????CHUYBK5K5YFJ
Content-Length: 528
Content-Type: application/dime


071011 10:37:18,0843::Setting status to Downloading... and raise timeout from 1192113438843 to 1192113438843(0) Reason:null. OldStatus: REQUESTING
071011 10:37:20,0000::Is accepting next segment: false
071011 10:37:20,0000::Download failed.
071011 10:37:20,0000::java.net.MalformedURLException
071011 10:37:20,0000::Moving candidate to medium list.
071011 10:37:20,0000::Setting status to Connection failed (1). and raise timeout from 1192113440000 to 1192113560000(120000) Reason:null. OldStatus: DOWNLOADING
071011 10:37:20,0015::Allocating as good candidate.
071011 10:37:20,0015::Wait for connect slot 66.66.???.94:15088
071011 10:37:20,0015::Connecting to 66.66.???.94:15088
071011 10:37:20,0015::Setting status to Connecting... and raise timeout from 1192113440015 to 1192113440015(0) Reason:null. OldStatus: WAITING
071011 10:37:20,0437::Connected successfully to 66.66.???.94:15088.
071011 10:37:20,0437::Start download.
071011 10:37:20,0437::Setting status to Requesting... and raise timeout from 1192113440437 to 1192113440437(0) Reason:null. OldStatus: CONNECTING
071011 10:37:20,0437::HTTP Request:
GET /uri-res/N2R?urn:sha1:HBTV4WVOO6O63PSLS5ZQ2?????CU HTTP/1.1
User-Agent: Phex 3.2.0.102
Host: 66.66.???.94:15088
Range: bytes=0-15495
X-Queue: 0.1
Connection: Keep-Alive
X-Node: 66.?7.???.77:42949
Chat: 64.77.???.77:42949


071011 10:37:21,0312::HTTP Response:
HTTP/1.1 503 Service Unavailable
Server: LimeWire/4.12.11
X-Queue: position=10, pollMin=45, pollMax=120
X-Gnutella-Content-URN: urn:sha1:HBTV4WVOO6O63PSLS5Z????7BIJ7QECU
X-Features: fwalt/0.1, chat/0.1, browse/1.0


071011 10:37:21,0312::phex.download.RemotelyQueuedExcepti on
071011 10:37:21,0328::Setting status to Queued on position: 10. Waiting 0:00. and raise timeout from 1192113441312 to 1192113523812(82500) Reason:null. OldStatus: REQUESTING
071011 10:37:21,0328::Accept queued candidate (0/1)

Thanks for the log. Unfortunately I'm still not very sure where this problem comes from.
Arne had the same problem a while ago and there is a bug entry of it already:
SourceForge.net: Detail: 1802488 - Download from a Phex breaks repeatedly

I added some more debugging in SVN (in case you are using it) and hope to find the origin of the problem soon.

Gregor

i get a queuing problem when downloading torrents. i can only download 2 at a time, the rest get queued(wierd to type) any way to change that? its not my max download btw, or any other obvious things

@SINIK: Since Phex has no option to download torrents, you seem to be using LimeWire. Please post in the LimeWire Forums.