Mirth Connect 3.1.1
Oracle 11.0.1
I'm having trouble resolving an issue we recently encountered after an upgrade to 3.1.1 from 3.0.3. It seems to occur with longer HL7 messages containing many OBX segments. An exception is logged (below), but the message stays in a Received state though source queue is off.
We thought perhaps the upgrade was not completed successfully, so we restarted the service on a clean schema and re-imported our channels. This allowed the problem message to process successfully, however, the next day we received the error again.
After the channel fails on this message, subsequent processing continues to log ArrayOutOfBoundsExceptions (farther below).
Initial exception encountered with long HL7:
Caused by: com.mirth.connect.donkey.server.data.DonkeyDaoExce ption: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. insertContent(JdbcDao.java:255)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. updateMap(JdbcDao.java:819)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. updateSourceMap(JdbcDao.java:834)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. insertConnectorMessage(JdbcDao.java:606)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.executeTasks(BufferedDao.java:97)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.commit(BufferedDao.java:74)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.commit(BufferedDao.java:61)
at com.mirth.connect.donkey.server.channel.Channel.di spatchRawMessage(Channel.java:1129)
... 8 more
Subsequent errors output to the server log:
[2014-12-04 13:41:53,172] ERROR (com.mirth.connect.donkey.server.channel.Channel:1 194): Error processing message in channel My_Channel_Name (acc14337-5e1d-4613-b3fd-cd5f652d3c80).
com.mirth.connect.donkey.server.channel.ChannelExc eption: java.lang.ArrayIndexOutOfBoundsException
at com.mirth.connect.donkey.server.channel.Channel.di spatchRawMessage(Channel.java:1153)
at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:196)
at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:174)
at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe ader.call(TcpReceiver.java:642)
at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe ader.call(TcpReceiver.java:477)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
at java.lang.Thread.run(Unknown Source)Caused by: java.lang.ArrayIndexOutOfBoundsException
Oracle 11.0.1
I'm having trouble resolving an issue we recently encountered after an upgrade to 3.1.1 from 3.0.3. It seems to occur with longer HL7 messages containing many OBX segments. An exception is logged (below), but the message stays in a Received state though source queue is off.
We thought perhaps the upgrade was not completed successfully, so we restarted the service on a clean schema and re-imported our channels. This allowed the problem message to process successfully, however, the next day we received the error again.
After the channel fails on this message, subsequent processing continues to log ArrayOutOfBoundsExceptions (farther below).
Initial exception encountered with long HL7:
Caused by: com.mirth.connect.donkey.server.data.DonkeyDaoExce ption: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. insertContent(JdbcDao.java:255)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. updateMap(JdbcDao.java:819)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. updateSourceMap(JdbcDao.java:834)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. insertConnectorMessage(JdbcDao.java:606)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.executeTasks(BufferedDao.java:97)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.commit(BufferedDao.java:74)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.commit(BufferedDao.java:61)
at com.mirth.connect.donkey.server.channel.Channel.di spatchRawMessage(Channel.java:1129)
... 8 more
Subsequent errors output to the server log:
[2014-12-04 13:41:53,172] ERROR (com.mirth.connect.donkey.server.channel.Channel:1 194): Error processing message in channel My_Channel_Name (acc14337-5e1d-4613-b3fd-cd5f652d3c80).
com.mirth.connect.donkey.server.channel.ChannelExc eption: java.lang.ArrayIndexOutOfBoundsException
at com.mirth.connect.donkey.server.channel.Channel.di spatchRawMessage(Channel.java:1153)
at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:196)
at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:174)
at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe ader.call(TcpReceiver.java:642)
at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe ader.call(TcpReceiver.java:477)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
at java.lang.Thread.run(Unknown Source)Caused by: java.lang.ArrayIndexOutOfBoundsException
DonkeyDaoException with Mirth Connect 3.1.1
0 commentaires:
Enregistrer un commentaire