Closed
Bug 298930
Opened 20 years ago
Closed 19 years ago
Create JSS client/server test program to test secure file transfer
Categories
(JSS Graveyard :: Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
4.1
People
(Reporter: Sandeep.Konchady, Assigned: Sandeep.Konchady)
Details
Attachments
(1 file, 1 obsolete file)
|
25.03 KB,
patch
|
glenbeasley
:
superreview+
|
Details | Diff | Splinter Review |
Older release of JSS had an issue with gradually slowing socket read time when transfering large files (> 10MB). In order to test this in current and future release, there needs to be a test client that can read a file and transfer it to a server (remote or local) via JSS socket. The server should report the number of bytes read and the time it took to read these bytes. There should not no degradation in read time if there is no leak of any sort.
| Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•19 years ago
|
||
This is not part of all.pl, but is a client/server that uses JSS to transfer files securely. The main purpose of this test would be to test the performance of large file transfer using JSS.
Attachment #189245 -
Flags: superreview?(glen.beasley)
Comment 2•19 years ago
|
||
Comment on attachment 189245 [details] [diff] [review] JSS_FileUploadClient and JSS_FileUploadServer program to test secure file transfer using JSS you should put a System.exit(0) at the exits of the the two programs, and also change error case where you call System.exit to a nonzero status code to indicate abnormal termination. Also, provide a note in this bug on your findings regarding BufferedStream.mark(Interger.MaxValue) you might even want to put a comment in the code to warn others.
Attachment #189245 -
Flags: superreview?(glen.beasley) → superreview+
| Assignee | ||
Comment 3•19 years ago
|
||
Updated the source with Glen's suggestions to place System.exit() calls appropriately. NOTE: If bufferedStream.mark(Integer.MAX_VALUE); method is invoked then fill method of BufferedInputStream class copies lot of data using System.arraycopy (which in-turn use memcpy). This causes very high CPU usage. This is one of the reasons secure large file transfer can become slow over time.
Attachment #189245 -
Attachment is obsolete: true
Attachment #192301 -
Flags: superreview?(glen.beasley)
Comment 4•19 years ago
|
||
Comment on attachment 192301 [details] [diff] [review] Modified JSS_FileUploadServer.java and JSS_FileUploadClient.java with critical notes you could add: For JSS_FileUploadServer usage last parameter [testInetAddress: true|false] instead of just [true|false] For the client you could pass in the file name rather than " Default file to upload is foo.in located locally"
Attachment #192301 -
Flags: superreview?(glen.beasley) → superreview+
| Assignee | ||
Comment 5•19 years ago
|
||
Commited the files JSS_FileUploadServer.java and JSS_FileUploadClient.java with changes suggested by Glen.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 6•19 years ago
|
||
Could you set the target milestone? Thanks.
| Assignee | ||
Updated•19 years ago
|
Target Milestone: --- → 4.1
You need to log in
before you can comment on or make changes to this bug.
Description
•