November 1999

 

Magic Broker Version 8.3-3 

 

 


Dear Developer,

We are happy to introduce Magic Broker Version 8.3-3.

Magic Broker 8.3-3 is a bug-fix version for the modules that were supplied in Magic 8.30 Service Pack 1.

We hope that the improved Magic Broker modules will make your work easier and more enjoyable. 

 

General information

Bugs fixed in Magic Broker 8.3-3

New Features in Magic Broker 8.3-3

Bugs fixed in Magic Broker 8.3-2

New Features in Magic Broker 8.3-2

 

Bugs fixed in Magic Broker 8.3-3 (Top)

  • Bug 120516 - The Magic Broker closed without any warning when an illegal port number was set in the MRB.INI file.

    Now, the Magic Broker displays the error message,
    Invalid Port Number.
  • Bug 241742 - When a Magic application server was loaded with the Start Program setting, the application server connected to the messaging server only after the Start Program finished.
  • Bug 768573 - Date fields transferred from an HTML form in the format of d/m/yyyy corrupted the next variable.
  • Bug 446527 – If the Request Broker could not connect to a server application, the server was removed from the pool but not disconnected.

    Now, an application server is removed from the Request Broker's pool only after the Broker successfully connects to the server and returns a termination message.
  • Bug 711133 – The partitioning modules failed to operate after 49 days of continuous operation.
  • Bug 757967 – The Magic Broker provided an incorrect status for an application server. This caused the start-up application to open in Toolkit mode.

    Any application server toolkit engine that has a start-up application now opens in Runtime mode for Magic Broker 8.3-3 and the Magic Engine modules provided in Service Pack 2.
  • Bug 787444 - When a pending request was cleared from the Request Broker's queue, the next request number fetched was wrong.

 

New Features in Magic Broker 8.3-3 (Top)

  • Automatic reload of the Magic Broker

    The Magic Broker can now automatically reload when an abnormal termination occurs.

    This is achieved by providing a new process that spawns the process of the Magic Broker. The new process is entirely responsible for monitoring and administrating the main process of the Magic Broker.
  • Automatic termination of the application server

    If the Magic Broker terminates and restarts, normally or abnormally, the application server connected to the Broker session will terminate after 60 seconds or less. This applies only to an application server running in background mode.
  • Re-connecting to a recovered Broker

    The Alternate Messaging Server allows the requester to reconnect to the main Broker after a designated time interval.

    A new setting in the requesters ini file (MGREQ.INI),
    RetryMainTime=10, is used to set the time intervals by which the requester reconnects to the main Broker. The number used in this setting is the number of minutes.

    If no value is set, the default retry time interval is 5 minutes.
  • Broker Availability

    The Magic Broker accepts requests only after the startup sequence is complete.
  •  

    Bugs fixed in Magic Broker 8.3-2 (Top)

  • Bug 773812 – Loading the Magic Broker with a background engine disrupted the Microsoft Windows operating system.
  • Bug 983892 - The Magic Broker crashed when connecting from a telnet terminal.
  • Bug 754955 - The Magic Broker stayed in 'Busy request' status even after an application running in background mode closed at the end of the request.
  • Bug 877 – If an application server connection was aborted and the Broker did not get a connection-reset message, due to a timing problem, the requester would not notify the Broker of the status of the application server even after it failed to connect. 
  •  

    New Features in Magic Broker 8.3-2 (Top)

  • Mgreq.ini

    In previous versions of Magic, the Magic Broker would search for the Mgreq.ini file used by the Internet requester in the Web Server default directory or in the directory specified in the registry, HKEY_LOCAL_MACHINE/SOFTWARE/MAGIC/MGREQ.

    For Magic 8.30 Service Pack 1, the Magic Broker now searches for the Mgreq.ini file in the directory of the Generic Messaging layer module (mgrqgnrc.dll) 
  • Broker events log

    The new Broker Events log,
    mrb_events.log, is created and appended each time the Magic Broker is opened.

    This log only displays major events: startup and shutdown of the Magic Broker and engines, and error messages.
  • Reload

    For Magic 8.30, the Reload feature was added to the Magic Broker.
    The Reload feature was enhanced by automatically assigning a messaging server to an engine that was automatically loaded by the Magic Broker.

    This Automatic Assignment generated a password that was used by the application server to connect from the engine entry name in Mgrb.ini to the actual password of the Broker in the following format <!$MG_exe_entry>password.

    For Magic 8.30 Service Pack 1, the format was changed, ++exe_entry++password, to be accessible to the UNIX server.
  •  

     

     

    Thank you,

    The Magic Version 8 Team