Announcement

Collapse
No announcement yet.

Compiler warnings after Java 7_40 update.

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

  • #31
    Nick, quick questions about this workaround.

    Is the global map reset upon appliance restart/MC service restart?
    Is the filter addition in your workaround reset upon appliance restart?

    Depending on the answer to those questions, it might be necessary to provide instructions on how to remove the log filter or somehow check to see if the filter is already in place.
    Thanks in advance!

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    edit: I am testing to get the answers to my questions. Will report back.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    edit #2: After testing I found the answers to my questions:
    Is the global map reset upon appliance restart/MC service restart?
    Yes, it resets up on Mirth Connect service restart.
    Is the filter addition in your workaround reset upon appliance restart?
    Yes, it resets upon Mirth Connect service restart, not just Mirth Appliance restart.

    Therefore, I'm very happy with the filter workaround that Nick provided above. It will run once when the first channel is deployed and if you need to take it out, you can simply remove the script code from the global deploy script and restart Mirth Connect.

    Thanks!
    Last edited by akathol; 04-01-2015, 08:22 AM.

    Comment


    • #32
      SAXParserImpl Warnings

      Should I be worried about these errors/ warnings:

      Code:
      [2015-04-09 19:03:26,242]  ERROR (Server:146):   WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
      [2015-04-09 19:03:26,242]  ERROR (Server:146): Compiler warnings:
      [2015-04-09 19:03:26,131]  ERROR (Server:146): Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.

      Comment


      • #33
        Search the forums first please...

        Merging this with the existing thread. Note that we have an open issue for it that should be addressed in the next version: MIRTH-3548
        Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

        Nicholas Rupley
        Work: 949-237-6069
        Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


        - How do I foo?
        - You just bar.

        Comment

        Working...
        X