Announcement

Collapse
No announcement yet.

Compiler warnings after Java 7_40 update.

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

  • Compiler warnings after Java 7_40 update.

    Hello,

    I just updated a few cusotmer's Java install from Java 7_25 to Java 7_40 and am now receiving the following ERROR warnings upon channel deploy.

    Using Mirth v2.2.1

    [2013-09-30 11:51:53,215] ERROR (Server:146): WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
    [2013-09-30 11:51:53,215] ERROR (Server:146): Compiler warnings:

    Has anyone seen this? I have not yet seen any side effects but I never like to see these types of things and want to find a solution.

    Thanks,

    Mark

  • #2
    Compiler warnings after Java 7_40 update.

    I have seen that Warning as well. I like you don't know if there is a bad side effect. I have searched the forum and have found no resolution.

    Comment


    • #3
      I had the same issues with Java 7_40.
      I found no solution so far but found related bug report outside forum
      http://bugs.sun.com/bugdatabase/view...bug_id=8016153
      Hope this will be resolved soon even if there was no critical issue with my channel.
      Any idea somebody?

      Comment


      • #4
        v3.0 warning

        ERROR (Server:146) WARNING: 'org.apache.xerces.jaxp.SAXParserImpl:Property 'http://avax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'

        I just upgraded a 2.2.2 instance and received this after updating a deprecated command and redeployed the channel.

        Comment


        • #5
          Just doing a quick Google search:

          http://bugs.sun.com/bugdatabase/view...bug_id=8016153

          It looks like it was fixed but I'm not sure in what version. It's a bit confusing because the affects and fix versions are the same.
          Last edited by narupley; 10-25-2013, 05:43 AM.
          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


          • #6
            Mirth 3.0 starting Warnings

            Hello,

            When my mirth server start, I get this warnings :

            - WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'

            - Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser : Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.


            What I have to do?
            All channels work fine in other mirth server.

            Thanks,


            benyssen

            Comment


            • #7
              Originally posted by benyssen View Post
              Hello,

              When my mirth server start, I get this warnings :

              - WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'

              - Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser : Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.


              What I have to do?
              All channels work fine in other mirth server.

              Thanks,


              benyssen
              Search the forums first: http://www.mirthcorp.com/community/f...ead.php?t=9356

              EDIT: Merged this thread with the existing one.
              Last edited by narupley; 10-25-2013, 05:47 AM.
              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


              • #8
                Same warnings

                Sorry,

                but I use :
                "2013-10-25 16:02:22,260] INFO (com.mirth.connect.server.Mirth:587): Running Java HotSpot(TM) 64-Bit Server VM 1.7.0_45 on Linux (2.6.39-400.17.1.el6uek.x86_64, amd64), postgres, with charset UTF-8."

                this version should solve this problem, no?

                Comment


                • #9
                  Originally posted by benyssen View Post
                  Sorry,

                  but I use :
                  "2013-10-25 16:02:22,260] INFO (com.mirth.connect.server.Mirth:587): Running Java HotSpot(TM) 64-Bit Server VM 1.7.0_45 on Linux (2.6.39-400.17.1.el6uek.x86_64, amd64), postgres, with charset UTF-8."

                  this version should solve this problem, no?
                  It looks like the issue occurred in 7u40, and Oracle only has plans to fix it in 8 currently. We'll still continue to look for a workaround or a way to suppress the warning...
                  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


                  • #10
                    nope, u45 does NOT solve the problem:

                    [2013-12-13 15:30:29,115] INFO (com.mirth.connect.server.Mirth:477): Running Java HotSpot(TM) Client VM 1.7.0_45 on Windows 7 (6.1, x86), derby, with charset windows-1252.
                    [2013-12-13 15:31:36,512] ERROR (Server:146): Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser : Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.
                    [2013-12-13 15:31:36,730] ERROR (Server:146): WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'

                    =(

                    Comment


                    • #11
                      Java version 1.7.0_51 solves this issue

                      Code:
                      [2014-01-16 09:53:09,448]  INFO  (com.mirth.connect.server.Mirth:615): Running Java HotSpot(TM) 64-Bit Server VM 1.7.0_51 on Windows Server 2008 R2 (6.1, amd64), derby, with charset windows-1252.
                      [2014-01-16 09:53:09,448]  INFO  (com.mirth.connect.server.Mirth:614): This product was developed by Mirth Corporation (http://www.mirthcorp.com) and its contributors (c)2005-2014.
                      [2014-01-16 09:53:09,446]  INFO  (com.mirth.connect.server.Mirth:613): Mirth Connect 3.0.1.7051 (Built on December 6, 2013) server successfully started.
                      Mirth Connect Server 3.4.1.8057
                      Java version: 1.8.0_101

                      on Debian 8.5 and various Winboxes

                      Comment


                      • #12
                        Hmmm ... weird. After sending a sending a msg via SOAP the 2 warnings appear again
                        Mirth Connect Server 3.4.1.8057
                        Java version: 1.8.0_101

                        on Debian 8.5 and various Winboxes

                        Comment


                        • #13
                          I think I read that it wont be fixed till Java 8

                          Comment


                          • #14
                            Do we know yet whether this actually causes any mal-effect?

                            Comment


                            • #15
                              Originally posted by dgtombs View Post
                              Do we know yet whether this actually causes any mal-effect?
                              unfortunately I just ran into an issue and I think it miight be related.
                              I cannot do any logger operations anymore.

                              INFO (com.mirth.connect.server.Mirth:615): Running Java HotSpot(TM) Client VM 1.7.0_51 on Windows 7 (6.1, x86), sqlserver, with charset windows-1252.

                              ERROR (Server:146): Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser : Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.

                              ERROR (Server:146): Compiler warnings:

                              ERROR (Server:146): WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
                              When I clear my server log, nnothing will happen again anymore. It might be related.

                              Comment

                              Working...
                              X