When preparing a deployment from a DEV or TEST installation for TEST resp. PROD, you might export a corrupted xml file for your channel but might not be alerted when importing it. Here is the scenario :
Start developing your channel :
Log into Mirth (say DEV)
Create a channel, say TEST, set a MLLP Listener, save it and then log off
You're now ready to deploy on your TEST installation
Log in your DEV box and go to channel editor, open your channel
From Summary tab, export your channel to file system (say test.xml).
Take a look at the xml, you'll see that most inbound connector properties where lost, as well as the queue size and max processing threads params (they were set to 0)
5a Your channel doesn't exist : import and save it => you'll get an error "error in the form for connector TCP Listener"
5b your channel already exists : import it, replace current version, deploy it: channel will deploy without warning, channel's connection status on the dashboard shows "Idle (0)", and server log may show an error next time it refreshes : "Address is invalid on local machine, or port is not valide on remote machine"
Bug only occurs if your very first action is to export that channel from its Summary tab.
Imported Issue. Original Details:
Jira Issue Key: MIRTH-4306
Reporter: atom
Created: 2018-07-20T05:16:12.000-0700
This one affected me recently.
When preparing a deployment from a DEV or TEST installation for TEST resp. PROD, you might export a corrupted xml file for your channel but might not be alerted when importing it. Here is the scenario :
Start developing your channel :
You're now ready to deploy on your TEST installation
Take a look at the xml, you'll see that most inbound connector properties where lost, as well as the queue size and max processing threads params (they were set to 0)
5a Your channel doesn't exist : import and save it => you'll get an error "error in the form for connector TCP Listener" 5b your channel already exists : import it, replace current version, deploy it: channel will deploy without warning, channel's connection status on the dashboard shows "Idle (0)", and server log may show an error next time it refreshes : "Address is invalid on local machine, or port is not valide on remote machine"
Bug only occurs if your very first action is to export that channel from its Summary tab.
Imported Issue. Original Details: Jira Issue Key: MIRTH-4306 Reporter: atom Created: 2018-07-20T05:16:12.000-0700