Announcement

Collapse

NextGen (Mirth) Connect 3.10.0 Released!

NextGen (Mirth) Connect 3.10.0 is now available as an appliance update and on our GitHub page. This release includes better SQL Server database support, security improvements through fixes and library updates, and improvements for the Advanced Clustering plugin with a focus on improving performance of many of the tasks that are carried out on a frequent interval. 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

length of a document xml

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    length of a document xml

    Hello I'm testing xml documents. When I send to a channel a very long
    document, the channel can't procces it but when I reduce the size of the
    text (XML), the channel runs ok. Is possible that the channel can't procces
    a XML message if it's very long? In this case how many characters we can
    write?

    I atacched you the error that appears at the channel of Mirth. error.txt (2088 bytes)
    Tags: None
  • #2
    Re:length of a document xml

    Check your TCP buffer size. If the message is larger than the buffer, it might split it and cause the error you attached.
    Chris Lang

    Comment

    • #3
      Re:length of a document xml

      Hello I have changed the TCP buffer size but it continues returning the same
      error, the channel only process part of the XML message. How can I solve it?
      Thanks.

      Comment

      • #4
        Re:length of a document xml

        Export your channel and post it.
        Jon Bartels

        Zen is hiring!!!!
        http://consultzen.com/careers/
        Talented healthcare IT professionals wanted. Engineers to sales to management.
        Good benefits, great working environment, genuinely interesting work.

        Comment

        • #5
          Re:length of a document xml

          pruebaxml.xml (38562 bytes)

          Comment

          • #6
            Re:length of a document xml

            Could you please attach a sample message that you are sending this channel that does not work properly? I will try to get this issue fixed for 1.6 if it is indeed a problem. I will use your channel and sample message.

            Thanks,
            Jacob
            Jacob Brauer
            Director, Software Development
            NextGen Healthcare

            sigpic

            Comment

            • #7
              Re:length of a document xml

              this my message simsg.xml (10930 bytes)

              Comment

              • #8
                Re:length of a document xml

                I notice you have line breaks that cause empty lines in your message. I tried running it without those empty lines and the message went through fine. Could you try this and let me know if you get the same behavior?

                Also, could you paste where exactly your message is cutting off?

                Thanks,
                Jacob
                Jacob Brauer
                Director, Software Development
                NextGen Healthcare

                sigpic

                Comment

                • #9
                  Re:length of a document xml

                  Also, are you having a problem every time you process the message, or just some of the time? I have been able to reproduce the same error some of the time, but many of the messages also go through.

                  Jacob
                  Jacob Brauer
                  Director, Software Development
                  NextGen Healthcare

                  sigpic

                  Comment

                  • #10
                    Re:length of a document xml

                    Jacob have you tried to create a large number of LLP's and several destinations, when the mule.conf file - reaches sizes around 64K seems like the same is duplicated. Have anyone other than me had that problem. And if they did, could you give me some work around to test.

                    thanks,

                    Joao

                    Comment

                    • #11
                      Re:length of a document xml

                      Jacob have you tried to create a large number of LLP's and several destinations, when the mule.conf file - reaches sizes around 64K seems like the same is duplicated. Have anyone other than me had that problem. And if they did, could you give me some work around to test.

                      thanks,

                      Joao

                      Comment

                      • #12
                        Re:length of a document xml

                        We've never had that problem here. Can you give more of a description of what exactly is happening in your mule.conf?

                        Perhaps you can export all of your channels and your mule.conf and attach them.

                        Thanks,

                        Jacob
                        Jacob Brauer
                        Director, Software Development
                        NextGen Healthcare

                        sigpic

                        Comment

                        • #13
                          Re:length of a document xml

                          message is cutting in

                          <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
                          <simsg>
                          <header>
                          <msgId>2007-0510-1256-59309-004</msgId>
                          <msgType>A08</msgType>
                          <timestamp>2007-05-10T12:56:59.465+02:00</timestamp>
                          <destination>Fugado</destination>
                          <source>REA</source>
                          <acknowledge>none</acknowledge>
                          </header>
                          <body>
                          <patientData>
                          <patientIdentification notFoundAction="ignore">
                          <patientIdentifier identifierType="Code" isSearchKey="false">171006305</patientIdentifier>
                          <patientIdentifier identifierType="PatientNumber" isSearchKey="false">1604374</patientIdentifier>
                          <patientIdentifier identifierType="InternalPatientID" isSearchKey="true">72</patientIdentifier>
                          <caseID isSearchKey="false">72</caseID>
                          <lastname isSearchKey="false">PEREZ FERNANDEZ</lastname>
                          <firstname isSearchKey="false">ACRACIA</firstname>
                          <dob isSearchKey="false" useTime="true">1921-02-01T00:00:00+01:00</dob>
                          </patientIdentification>
                          <patient>
                          <address>
                          <street>PADRE 1º/ª ÁÍÓÚÉ Ü Ç ÑÑ FIN, 38 2</street>
                          <zip>46930</zip>
                          <country>ESPAÑA</country>
                          <phone type="unknown"/>
                          <phone type="unknown">961532464</phone>
                          <phone type="unknown"/>
                          <phone type="unknown">961533903</phone>
                          </address>
                          <demographics>
                          <sex>F</sex>
                          </demographics>
                          </patient>
                          <observation>
                          <identifier>Salida_REA</identifier>
                          <name>Salida REA</name>
                          <type>4</type>
                          <observationValue>
                          <value>2</value>
                          <valueTime>2007-05-10T12:56:14.840+02:00</valueTime>
                          </observationValue>
                          <dataType>1</dataType>
                          </observation>
                          <observation>
                          <identifier>Motivo_Ingreso</identifier>
                          <name>Motiv ingres</name>
                          <type>4</type>
                          <observationValue>
                          <value>Mujer que ingresa por sangrado de úlcera cutánea extensa, asociado a terapia anticoagulante (sintrom) procedente de Urgencias.</value>
                          <valueTime>2007-05-10T12:36:00+02:00</valueTime>
                          </observationValue>
                          <dataType>3</dataType>
                          </observation>
                          <observation>
                          <identifier>Antecedentes_Personales</identifier>
                          <name>Anteced pers</name>
                          <type>4</type>
                          <observationValue>
                          <value>Diabetes mellitus tipo II. Portador de bypass coronario (01/11/2003). Insuficiencia cardíaca (01/11/2003). HTA (01/11/2003). FA crónica HTA (01/11/2003). Anticoagulado con sintrom HTA (01/11/2003). Portador de válvula cardíaca. Insuficiencia renal crónica</value>
                          <valueTime>2007-05-10T12:36:00+02:00</valueTime>
                          </observationValue>
                          <dataType>3</dataType>
                          </observation>
                          <observation>
                          <identifier>Exploracion_Fisica</identifier>
                          <name>Explor fisic</name>
                          <type>4</type>
                          <observationValue>
                          <value>Consciente, orientada, palidez normohidratada. AC: Arrítmico. AR: hipoventilación en vases. TSA: no soplos. EESS: simétricas. Abdomen: muy globoso, no masas palpables. EEII: EID: normal. EIIulso femoral y poplíteo presentes; ausencia de distales; úlcera</value>
                          <valueTime>2007-05-10T12:36:00+02:00</valueTime>
                          </observationValue>
                          <dataType>3</dataType>
                          </observation>
                          <observation>
                          <identifier>Enfermedad_Actual</identifier>
                          <name>Enferm actua</name>
                          <type>4</type>
                          <observationValue>
                          <value>

                          Comment

                          Previous template Next
                          Working...
                          X

                          We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                          By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                          I Agree