Bug 474387 - SocketExceptions in client.log during nightly tests
Summary: SocketExceptions in client.log during nightly tests
Status: CLOSED FIXED
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 4.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 468428
  Show dependency tree
 
Reported: 2015-08-06 04:38 EDT by Marvin Mueller CLA
Modified: 2016-05-19 03:39 EDT (History)
1 user (show)

See Also:

Attachments
reoccuring exception (2.80 KB, application/octet-stream)
2015-08-06 04:38 EDT, Marvin Mueller CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marvin Mueller CLA 2015-08-06 04:38:37 EDT 
Created attachment 255662 [details]
reoccuring exception

In our nightly test we have a lot "java.net.SocketException: Connection reset by peer: socket write error". Either this is really a problem or this is a expected behavior, but it is logged unnecessarily.
Comment 1 Marvin Mueller CLA 2015-08-14 07:25:25 EDT 
I have changed to logging in these place to debug and the callers of the send method are no responsible for logging this if necessary.

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=7136444e8b27c3a587516f4e2d536ed808d70e0b
Comment 2 Markus Tiede CLA 2015-08-18 06:25:09 EDT 
Did not re-occure - checked within the most recent ITE regression environment and by code inspection.