Closed Bug 144261 Opened 22 years ago Closed 22 years ago

can't publish document with more than 40 images, must be cancelled.

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
mozilla1.0

People

(Reporter: sujay, Assigned: Brade)

References

Details

(Whiteboard: publish) 

this bug came in from the mozilla community.

Apparently user had a document with 40 images in it.

He tried to publish and had to cancel.
This is a limitation of the number of network connections we can open.
What was publishing method: FTP or HTTP?

I tested publishing a page with 30 images by FTP and after 10 connections were
opened, I got a non-zero status error. I tested again today and instead got an
assertion in nsSocketTransportService::ProcessWorkQ():
"ASSERTION: reached max open connections..." This happens when we attempt to
open more than MAX_OPEN_CONNECTIONS (currently 50) connections.


I'm betting that Brade won't want me to dup this to bug 138659, but it is 
obvious that serializing FTP transfer of images also fixes this problem.
I confirmed this with the patch on but 138659.
Assignee: cmanske → brade
Depends on: 138659
Whiteboard: publish
Keywords: nsbeta1
Target Milestone: --- → mozilla1.0
The FTP serialization issue has been moved to bug 138662
Depends on: 138662
No longer depends on: 138659
this is now fixed on the trunk
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.