… handling and error logging ... server errors will be dealt with using separate (to be written) logic (checkpoint)

…MTests tests .... added several more tests and fixed some bugs in GemServer class>>gemServerTransaction:onError: and friends

…on support

…te tests for internal server errors ... interactiveMode added so that exceptions are passed so that debugger can be used

… GemServer, i.e., in interactiveMode exceptions are handled, logged then passed so that developer can bring up a debugger in a development environment ... for those cases when server-side code is being written ...

…: as non-transactional veriants for handling server errors, breakpoints and halts (should satisfy Issue #12)...refactor GemServer>>gemServerTransaction:onError:  to use GemServer>>gemServer:onError: ... add GemServer>>handleGemServerException: to isolate server error and interactiveMoe logic ... GemServer>>serverError:titled:inTransactionDo: allows for performing optional work in the same transaction as the continuation ... if one is already in transaction a commit is expected to come from the caller ... started work on an example server as the GemServerTestServer has been sacrificed to being able to test various error conditions and is no longer a clean example ...

…oflictBlock ... GemServer>>doComplexTransaction:onConflict: conflict handling is WHY you use doComplexTransaction:. Allow for exceptionSet customization in gemServer:... gemServerTransaction:... calls and of course add onConflict customization to gemServerTransaction:... calls...GemServerTestServer>>startBasicServerOn: now uses both flavors of gemServer api calls: gemServer:... and gemServerTransaction:...

…mServerRemoteServerExample and it is passing

…ss leak ... added GemServerRemoteServerExampleTests>>test100Tasks to put a little bit of stress on the server ... error logging in GemServerRemoteServerExampleTests>>testSimple (test errors on travis?)

…ests

…ing: exception implements exceptionHandlingForGemServer: to route appropriate message to server. Add AlmostOutOfMemory and AlmostOutOfStack support to GemServer ... add GemServerRemoteServerExampleTests tests for internal server errors, Warning, AlmostOutOfMemory and AlmostOutOfStack

…s when running GemServerRemoteServerExampleTests>>test100Tasks

…o lineup (is 3.2.3-specific problem?) ... add example script in support of interactive debugging

…vironment

…tatus...

…o delay from continuation .... an abort is causing the process to forget the waiters ... bug will be finxed in 23.2.4? ... causing failure in GemServerRemoteServerExampleTests>>test100Tasks

… gem has crashed and take action...

…s we don't catch a socket on the stack ...

…s again ...

…nuations for all GemServerRemoteServerExampleTests ... run baseline tests

…lly produce continuations anyway...

…c delay

…mount)

…implemented

…lide during 100task test ... why? ...

…ci.org/GsDevKit/gsApplicationTools/builds/45173024) turn continuations for all tests

…ion dispatching to v30 package

…saction most of the time allowing for concurrent request handling ... transaction model B runs in transaction, synced on transaction mutex, ala Seaside transaction model ... still some fine tuning to do ...

…xception passing .... fix handling of AlmostOutOfMemory exception with temp stack references in GemServerRemoteServerExample

…ive tests needs to be able to customize the exception set used and it stands to reason that developers will as well ...

…k in shape...

…t ...

…on: ... comment fiddling

…ption: ... changed comment so the same mistake won't be made again...

…nsaction:, and GemServer>>doTransaction:onConflict: to replace GemServer>>doSimpleTransaction: and GemServer>>doComplexTransaction:onConflict: ... ongoing docs work

…o issue_10

…of onError:

…AExample>>taskServiceThreadBlock: ... restored

… and *TransactionModelB* classes to *SerialProcessing*

…mserver stack

…test failures ...

…BasicServerOn: ... bad boy ... don't automatically go into interactiveMode when running GemServer>>interactiveStartServiceOn:transactionMode: ... interactiveMode setting for server should be independently controlled, since it is convenient to use interactiveStart... to run tests without debugging exceptions ... to verify that bug is really fixed ... fix logic in GemServer>>doTransaction:onConflict:

…tiveVMTests test failures

…ServerError failures

…s>>#testInternalServerError failure ... tweak GemServerRemoteTaskExample class>>reset to avoid potential commit conflicts

…fMemoryTempMethod