Ticket #285 (closed Bugs: worksforme)

Opened 7 years ago

Last modified 6 years ago

Unhandled Exception when closing active connections.

Reported by: doni49 Owned by: octo
Priority: major Milestone: 2.0
Component: LogicMail Version: 2.0.0
Keywords: unhandled exception Cc:
Blocked By: Blocking:

Description

I'm on a Tour 9630 with OS 5.0.0.732 (VZW) and I've currently got LM 2.0.0.258 (Beta) installed.

I leave LM open most of the day. Occasionally I get an Unhandled Exception error when I close LM and click yes on the dialog that asks if I want to close all open connections.

My event log is in the attached file. The unhandled exception message occurred at approximately 10:10 (the latest entry in the log is at 10:07).

Attachments

EventLog.txt Download (4.0 KB) - added by doni49 7 years ago.

Change History

Changed 7 years ago by doni49

comment:1 Changed 7 years ago by octo

  • Status changed from new to assigned
  • Owner set to octo

The attached log file provides absolutely no useful information. It just has the usual log messages during idling. Unhandled exceptions are often logged separately as bold entries on the event log screen, and tend to be hidden if the logger is filtered to just show LogicMail messages.

However, there are several long-standing issues with connection closing on shutdown, this possibly being one of them, so I'll use this ticket to cover a task to resolve them. In my experience, these issues include:

  1. Dead socket that LogicMail thinks is still open (probably the issue you experienced)
  2. Extremely poor or stalled connection, that causes LogicMail to be slow to exit
  3. Extremely poor or stalled connection, that causes LogicMail to act as if its totally frozen when trying to exit

One of the major challenges in testing these situations is a lack of good and usable test tools in a development environment.  Sysinternals TCPview is useful for quickly killing a connection, but does not simulate lag. All the tools I've found that can simulate lag and severe packet loss on a still-open connection are either hard-to-find buggy abandonware, only work for HTTP, overly complex and expensive "enterprise network simulator" tools, or simply not designed to be interactively used by a developer testing their software.

My normal test environment consists of the BlackBerry simulator running on a Windows desktop, along with a  VirtualBox instance containing a full  OpenBSD installation with a half-dozen different E-Mail server packages. Right now my only easy ways to simulate network issues are with TCPview, or by disabling the network interface inside the test server VM.

comment:2 Changed 6 years ago by octo

  • Status changed from assigned to closed
  • Resolution set to worksforme

Closing because issue has gone stale.

Note: See TracTickets for help on using tickets.