Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

DB DESTINATION_CONNECTORS size limit reached !

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DB DESTINATION_CONNECTORS size limit reached !

    Hi !

    I got a big problem !

    Code:
    com.webreach.mirth.client.core.ClientException: method failed: HTTP/1.1 500 com.ibatis.common.jdbc.exception.NestedSQLException:   
    --- The error occurred in mysql/mysql-channel.xml.  
    --- The error occurred while applying a parameter map.  
    --- Check the updateChannel-InlineParameterMap.  
    --- Check the statement (update failed).  
    --- Cause: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (1130915 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.
    Caused by: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (1130915 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.
    com.webreach.mirth.client.core.ServerConnection.executePostMethod(ServerConnection.java:99)
    com.webreach.mirth.client.core.Client.updateChannel(Client.java:182)
    com.webreach.mirth.client.ui.Frame.updateChannel(Frame.java:1095)
    com.webreach.mirth.client.ui.ChannelSetup.saveChanges(ChannelSetup.java:861)
    com.webreach.mirth.client.ui.Frame$24.doInBackground(Frame.java:2209)
    com.webreach.mirth.client.ui.Frame$24.doInBackground(Frame.java:2221)
    org.jdesktop.swingworker.SwingWorker$1.call(Unknown Source)
    java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    java.util.concurrent.FutureTask.run(Unknown Source)
    org.jdesktop.swingworker.SwingWorker.run(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    java.lang.Thread.run(Unknown Source)

    I've reached the size limit of my channel ...
    I'know that it's a longtext type but ... i need more space !

    Can i convert the channel.DESTINATION_CONNECTORS table (actually as longtext) into BLOB or LONGBLOB ....

    Is it dangerous ? (=> data crashing ????)

    Does Mirth could read this columns as a BLOB ????

    Thanks for your replies

    Antaris

    Post edited by: Antaris, at: 01/24/2008 08:52
Working...
X