Q7

OutOfMemoryError instead of something more meaningful

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1
  • Fix Version/s: 1.1.3
  • Component/s: Runtime
  • Labels:
    None

Activity

Hide
ystrot added a comment - 01/Dec/11 8:08 PM

Finally I've added negative values check and in case of OutOfMemoryError include data size to error message.

Fixed in the Synergy.

Show
ystrot added a comment - 01/Dec/11 8:08 PM Finally I've added negative values check and in case of OutOfMemoryError include data size to error message. Fixed in the Synergy.
Hide
komaz added a comment - 01/Dec/11 6:14 PM

If not, problem is not in firewall

Show
komaz added a comment - 01/Dec/11 6:14 PM If not, problem is not in firewall
Hide
komaz added a comment - 01/Dec/11 6:13 PM

Can we check what happens when windows firewall blocks connection to port? Can we get the same out of memory error in this case?

Show
komaz added a comment - 01/Dec/11 6:13 PM Can we check what happens when windows firewall blocks connection to port? Can we get the same out of memory error in this case?
Hide
ystrot added a comment - 01/Dec/11 6:02 PM

I see two quick fix for this issue:

  • Handle OutOfMemoryError on the client side. It's not correct to limit client data on server side, because in this case we can skip real OutOfMemory in case client collect and send too much data. However server response is always very small, so we can find appropriate limit.
  • Use some "identification" data. Like send "42" at the beginning to make sure client connect to the right host.

As for original issue, I'm not sure how it can happen. So I think we need to provide some optional logging on both client and server side or transfer all data to file as well.

Show
ystrot added a comment - 01/Dec/11 6:02 PM I see two quick fix for this issue:
  • Handle OutOfMemoryError on the client side. It's not correct to limit client data on server side, because in this case we can skip real OutOfMemory in case client collect and send too much data. However server response is always very small, so we can find appropriate limit.
  • Use some "identification" data. Like send "42" at the beginning to make sure client connect to the right host.
As for original issue, I'm not sure how it can happen. So I think we need to provide some optional logging on both client and server side or transfer all data to file as well.

People

  • Assignee:
    ystrot
    Reporter:
    komaz
Vote (0)
Watch (0)

Dates

  • Created:
    01/Dec/11 4:22 PM
    Updated:
    01/Dec/11 8:08 PM
    Resolved:
    01/Dec/11 8:08 PM