•  
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
The following fields are now included in the Message Browser quick search:…
The following fields are now included in the Message Browser quick search:

Message ID

Connector Name

Custom meta-data columns (string-type only)

Issue: MIRTH-2528

    • -3
    • +11
    ./dbconf/postgres/postgres-message.xml
    • -3
    • +11
    ./dbconf/sqlserver/sqlserver-message.xml
  1. … 1 more file in changeset.
MIRTH-2563: Optimized transformWithoutSerializing for both HL7 v2.x and NCPDP. ER7Serializer now stores a string array of delimiters (the full inbound delimiter string split by "|"), and iterates thro…
MIRTH-2563: Optimized transformWithoutSerializing for both HL7 v2.x and NCPDP. ER7Serializer now stores a string array of delimiters (the full inbound delimiter string split by "|"), and iterates through the array, checking where each one is contained in the message. If any of them happen to be contained, then the matcher.replaceAll result is returned. In NCPDPSerializer, the inbound delimiter is always singular, so we just do a replace(String, String) call instead.
MIRTH-2561: Optimized the pre/postprocessors so that they don't instantiate and execute a Callable every time. Instead, a check is done in JavaScriptUtil to determine whether or not the script needs t…
MIRTH-2561: Optimized the pre/postprocessors so that they don't instantiate and execute a Callable every time. Instead, a check is done in JavaScriptUtil to determine whether or not the script needs to run. Only if it is needed will it submit the JavaScriptTask. The postprocessor methods in JSU have been de-normalized to mimic the preprocessor. Also, the scope is no longer always created; now it's created "as needed" for both the global and channel script portions.
MIRTH-2567, MIRTH-2568: Modified TcpReceiver so that it wraps the response output stream in a BufferedOutputStream once, at the same time the stream handler is being created. Also moved the remoteSide…
MIRTH-2567, MIRTH-2568: Modified TcpReceiver so that it wraps the response output stream in a BufferedOutputStream once, at the same time the stream handler is being created. Also moved the remoteSideHasClosed check to the catch clause in sendResponse, so it doesn't have to do the check every time.
MIRTH-2459: Paused channels now remain paused after a "Remove All Messages" task runs. The PAUSED and PAUSING states are now also used by the channel itself. Before, the Paused status was inferred by …
MIRTH-2459: Paused channels now remain paused after a "Remove All Messages" task runs. The PAUSED and PAUSING states are now also used by the channel itself. Before, the Paused status was inferred by looking at each connector status individually. However now the engine controller just uses the status directly from the channel. The PauseTask and ResumeTask now correctly update the channel status, including setting the state to PAUSING before attempting to stop the source connector. This means that a pausing channel can be halted, just like starting or stopping channels.

The StartTask now also takes a boolean in the constructor, indicating whether or not to start the source connector. DonkeyMessageController then uses the prior state of a channel to determine this. If a channel is being restarted and the prior state was PAUSED or PAUSING, the channel will be started except for the source connector. Recovery will still occur in this case.

  1. … 6 more files in changeset.
Replaced use of the "string_agg" aggregate function in the message browser in Postgres with the "array_agg" function, which is supported by Postgres >= 8.4. The former is only available in >= 9.0.…
Replaced use of the "string_agg" aggregate function in the message browser in Postgres with the "array_agg" function, which is supported by Postgres >= 8.4. The former is only available in >= 9.0.

Tested and verified that there are no other obvious problems that occur when using Postgres 8.4.

Mirth Connect 3.0 now supports Postgres >= 8.4

Issue: MIRTH-2341

    • -1
    • +1
    ./dbconf/postgres/postgres-message.xml
Fixed exception that occurred when the pruner was not running…
Fixed exception that occurred when the pruner was not running

Issue: MIRTH-2539

MIRTH-2566: Fixed bug that caused a question mark to always get appended to HTTP requests, even if no query parameters are specified.
MIRTH-2566: Fixed bug that caused a question mark to always get appended to HTTP requests, even if no query parameters are specified.
Allow the "!=" operator for custom String metadata searches…
Allow the "!=" operator for custom String metadata searches

String metadata searches now use "=" operator instead of the text version "EQUALS". This produced unnecessary complexity.

Removed TEXT_EQUALS conditions from the message queries.

Fixed a potential NullPointerException when using Timestamp custom metadata if the timestamp value for a message was null.

Issue: MIRTH-2522

    • -3
    • +0
    ./dbconf/postgres/postgres-message.xml
    • -3
    • +0
    ./dbconf/sqlserver/sqlserver-message.xml
  1. … 2 more files in changeset.
MIRTH-2278: Updated mirth-vocab.jar to reflect the changes to ORC.4.
MIRTH-2278: Updated mirth-vocab.jar to reflect the changes to ORC.4.
Added call to channelController.removeDeployedChannelFromCache(channelId) to undeployChannel() in DonkeyEngineController.…
Added call to channelController.removeDeployedChannelFromCache(channelId) to undeployChannel() in DonkeyEngineController.

Issue: MIRTH-2505

Changed length of VARCHAR columns PERSON_PASSWORD.PASSWORD and ALERT.NAME from 256 to 255. We received a report that VARCHAR(256) caused an error when creating the database schema in MySQL.…
Changed length of VARCHAR columns PERSON_PASSWORD.PASSWORD and ALERT.NAME from 256 to 255. We received a report that VARCHAR(256) caused an error when creating the database schema in MySQL.

Issue: MIRTH-2541

    • -2
    • +2
    ./dbconf/sqlserver/sqlserver-database.sql
    • -2
    • +2
    ./dbconf/postgres/postgres-database.sql
Modified FtpConnection.writeFile() to check the reply code after a write to verify if the write was successful and throw an exception if it wasn't (IE> Permission denied).…
Modified FtpConnection.writeFile() to check the reply code after a write to verify if the write was successful and throw an exception if it wasn't (IE> Permission denied).

Issue: MIRTH-2461

MIRTH-2555: Fixed bug that caused temp files created by multipart HTTP Senders to not be cleaned up correctly. Also refactored the send() method so that only a single catch clause is used.
MIRTH-2555: Fixed bug that caused temp files created by multipart HTTP Senders to not be cleaned up correctly. Also refactored the send() method so that only a single catch clause is used.
MIRTH-2366: Updated references from "messageObject" to "connectorMessage", and removed "message" from transformer scopes since it is no longer used.
MIRTH-2366: Updated references from "messageObject" to "connectorMessage", and removed "message" from transformer scopes since it is no longer used.
  1. … 3 more files in changeset.
Implemented alerting for using the new event framework…
Implemented alerting for using the new event framework

Events are now dispatched for connector state changes and message statistic updates.

Events are now dispatched for filter/transformer and response transformer errors.

Channel selection for an alert has been drastically improved. Users can now filter on the channel list, multi-select/update channels, and set whether new channels created after the alert will trigger the alert. Furthermore, it is now possible to select whether individual connectors will trigger an alert.

It is now possible to route an alert message to a channel in addition to sending an email.

There is now a separate alert dashboard panel that lists all alerts, instead of combining it with the edit options.

The alert dashboard now retrieves an AlertStatus rather than the AlertModel itself.

Updated connector monitoring to use the new event framework. This should also improve the performance of various connectors.

The old ConnectorStatusPlugin has been removed completely.

Various methods of the AlertWorker have been moved to the EventListener class where it logically fits better.

MIRTH-2553

MIRTH-2554

    • -8
    • +22
    ./src/com/mirth/connect/server/alert/Alert.java
  1. … 73 more files in changeset.
MIRTH-2134: Manually set entity resolver for PDF document parsing. The FSEntityResolver will use internal resources for common doctypes, and only grab them from the network if necessary.
MIRTH-2134: Manually set entity resolver for PDF document parsing. The FSEntityResolver will use internal resources for common doctypes, and only grab them from the network if necessary.
Removed old references to mule and the mule license.…
Removed old references to mule and the mule license.

Issue: MIRTH-2507

MIRTH-2550: Switched out SerializationUtils for a custom semi-shallow cloning implementation. QueueConnectorPropertiesInterface is now gone, and has been replaced with DispatcherConnectorPropertiesInt…
MIRTH-2550: Switched out SerializationUtils for a custom semi-shallow cloning implementation. QueueConnectorPropertiesInterface is now gone, and has been replaced with DispatcherConnectorPropertiesInterface, which supplies the getter for the queue properties, and also a clone() method. The getReplacedConnectorProperties method on DestinationConnector has been changed to replaceConnectorProperties, and instead of returning an object, an already-cloned ConnectorProperties object is passed in. Each dispatcher and their properties have been updated with the changes. In some cases not all fields are shallowly cloned; maps and lists that will be iterated through and will have replacement run them are cloned via new Map(oldMap), etc.
  1. … 23 more files in changeset.
Moved channel tags from the Channel object to the ChannelProperties object. Also removed the associated table and queries, since this change removes the need for those. The DefaultChannelController …
Moved channel tags from the Channel object to the ChannelProperties object. Also removed the associated table and queries, since this change removes the need for those. The DefaultChannelController now gets the tags directly from the channels, which are pulled from the channel cache.

Issue: MIRTH-2548

    • -6
    • +0
    ./dbconf/sqlserver/sqlserver-database.sql
    • -29
    • +8
    ./dbconf/postgres/postgres-channel.xml
    • -6
    • +0
    ./dbconf/postgres/postgres-database.sql
    • -31
    • +2
    ./dbconf/sqlserver/sqlserver-channel.xml
    • -10
    • +0
    ./src/com/mirth/connect/model/Channel.java
  1. … 4 more files in changeset.
Replaced the channel cache with one that is lazy loaded and updated from the database every time it is called.…
Replaced the channel cache with one that is lazy loaded and updated from the database every time it is called.

Moved the ChannelCache and DeployedChannelCache into inner classes in the DefaultChannelController to separate their logic.

Fixed memory leak where channels with changed names weren't removed from the channnelCacheByName map.

Changed ChannelController API to allow getting single, multiple, or all channels at the same time through the API. The controller simply pulls the appropriate channels from the refreshed channel cache and does not directly ever do a database call to get channel from the database. One caveat is that the channel cache is always refreshed when the API is used, which requires at least one database call to get the latest channel revisions numbers. Because of this, the number of calls to get channels from the ChannelController was optimized.

Issue: MIRTH-2536

    • -1
    • +0
    ./src/com/mirth/connect/server/Mirth.java
  1. … 4 more files in changeset.
Removed old Quartz Scheduler jar file…
Removed old Quartz Scheduler jar file

Issue: MIRTH-2544

Fixed problem resulting from recent commit that prevented the message pruner tests from running.…
Fixed problem resulting from recent commit that prevented the message pruner tests from running.

Issue: MIRTH-2539

MIRTH-2537

- Prevent potential deadlocks by ensuring that only one pruner process can execute at one time (additional requests to start the pruner will be ignored if the pruner is already running)

MIRTH-2496

- Refactored/optimized/cleaned up much of the pruner code (it is now contained in a single MessagePruner class, rather than separate With/WithoutArchiver classes)

MIRTH-2539

- Added the ability to manually start and stop the pruner from the pruner settings pane (archiver settings can now be specified when the pruner schedule is disabled)

- Added panel above the pruner schedule that displays various status information about the pruner (current state, start/elapsed time, info on last process, next scheduled time)

MIRTH-2544

- Updated the Quartz Scheduler library to version 2.1.7 and updated the code in MessagePrunerService to use the new API.

    • -0
    • +7
    ./src/com/mirth/connect/model/Event.java
    • -2
    • +2
    ./dbconf/sqlserver/sqlserver-message.xml
    • -2
    • +13
    ./src/com/mirth/connect/util/MessageExporter.java
    • binary
    ./lib/quartz-all-2.1.7.jar
  1. … 3 more files in changeset.
Replaced the static message import/export methods in the MessageUtils class with MessageImporter and MessageExporter classes, so that new features such as tracking the import/export status can be adde…
Replaced the static message import/export methods in the MessageUtils class with MessageImporter and MessageExporter classes, so that new features such as tracking the import/export status can be added in the future (possibly in MIRTH-2539).

Original issue: MIRTH-1699

    • -0
    • +100
    ./src/com/mirth/connect/util/MessageExporter.java
    • -259
    • +0
    ./src/com/mirth/connect/util/MessageUtils.java
    • -0
    • +175
    ./src/com/mirth/connect/util/MessageImporter.java
  1. … 3 more files in changeset.
Updated Derby's message archiver query so that it is consistent with the pruning query, which checks the received_date on the d_m table rather than the d_mm table. In the future, we may update Derby t…
Updated Derby's message archiver query so that it is consistent with the pruning query, which checks the received_date on the d_m table rather than the d_mm table. In the future, we may update Derby to check on d_mm.received_date as the other databases do (MIRTH-2471).

Issue: MIRTH-1699

Removing SQL Server 2000 files since we are now only supporting version 2005 and above.…
Removing SQL Server 2000 files since we are now only supporting version 2005 and above.

Issue: MIRTH-2496

Fixed error in the alert SQL code for Derby.…
Fixed error in the alert SQL code for Derby.

Removed old alert tables in derby-database.sql.

Issue: MIRTH-2530

Removed old alert tables in sqlserver-database.sql…
Removed old alert tables in sqlserver-database.sql

Issue: MIRTH-2496

    • -14
    • +0
    ./dbconf/sqlserver/sqlserver-database.sql
MIRTH-2497

MIRTH-2530

Fixed errors with the message pruner/archiver when using MySQL.

Removed old alert tables in mysql-database.sql.

Issue: MIRTH-2497

    • -27
    • +47
    ./dbconf/mysql/mysql-message.xml