10 Replies Latest reply on Oct 10, 2011 1:38 PM by 893476

    Standalone mode Error

    AndyPol
      Hi

      When I start first time apex listener I could go to Application Express Admin Page, after restart I have this error:


      C:\oracle\product\apex_listener.1.1.2.131.15.23>java -Dapex.port=6565 -Dapex.hom
      e=c:\apex_listener -jar apex.war
      INFO: Starting: C:\oracle\product\apex_listener.1.1.2.131.15.23\apex.war
      See: 'java -jar apex.war --help' for full range of configuration options
      INFO: Extracting to: c:\apex_listener
      INFO: Using classpath: file:/c:/apex_listener/apex/____embedded/start.jar:file:/
      c:/apex_listener/apex/WEB-INF/lib/apex.jar:file:/c:/apex_listener/apex/WEB-INF/l
      ib/commons-fileupload-1.2.1.jar:file:/c:/apex_listener/apex/WEB-INF/lib/je-4.0.1
      03.jar:file:/c:/apex_listener/apex/WEB-INF/lib/ojdbc6.jar:file:/c:/apex_listener
      /apex/WEB-INF/lib/ojmisc.jar:file:/c:/apex_listener/apex/WEB-INF/lib/poi-3.6-200
      91214.jar:file:/c:/apex_listener/apex/WEB-INF/lib/ucp.jar:file:/c:/apex_listener
      /apex/WEB-INF/lib/xdb-11.2.0.jar:file:/c:/apex_listener/apex/WEB-INF/lib/xmlpars
      erv2-11.2.0.jar:
      INFO: Starting Embedded Web Container in: c:\apex_listener
      2011-06-30 14:40:07 ____bootstrap.Deployer deploy
      INFO: Will deploy application path=c:\apex_listener\apex\WEB-INF\web.xml
      2011-06-30 14:40:08 ____bootstrap.Deployer deploy
      INFO: deployed application path=c:\apex_listener\apex\WEB-INF\web.xml
      2011-06-30 14:40:09 com.sun.grizzly.http.servlet.ServletContextImpl initListener
      s
      SEVERE:
      oracle.dbtools.rt.x3p.impl.X3PParseException: ParseError at [row,col]:[1,3]
      Message: The markup declarations contained or pointed to by the document type de
      claration must be well-formed.
      at oracle.dbtools.rt.x3p.impl.StAXEventIterator.wrap(StAXEventIterator.j
      ava:94)
      at oracle.dbtools.rt.x3p.impl.StAXEventIterator.access$000(StAXEventIter
      ator.java:27)
      at oracle.dbtools.rt.x3p.impl.StAXEventIterator$XMLEventIterator.advance
      (StAXEventIterator.java:116)
      at oracle.dbtools.rt.x3p.impl.StAXEventIterator$XMLEventIterator.advance
      (StAXEventIterator.java:97)
      at oracle.dbtools.rt.util.AbstractIterator.next(AbstractIterator.java:28
      )
      at oracle.dbtools.rt.util.M2NIterator.srcNext(M2NIterator.java:58)
      at oracle.dbtools.rt.util.M2NIterator.process(M2NIterator.java:39)
      at oracle.dbtools.rt.util.VariableIterator.advance(VariableIterator.java
      :25)
      at oracle.dbtools.rt.util.AbstractIterator.start(AbstractIterator.java:4
      7)
      at oracle.dbtools.rt.util.AbstractIterator.hasNext(AbstractIterator.java
      :20)
      at oracle.dbtools.rt.x3p.impl.Chain$EventIterator.advance(Chain.java:100
      )
      at oracle.dbtools.rt.x3p.impl.Chain$EventIterator.advance(Chain.java:75)

      at oracle.dbtools.rt.util.AbstractIterator.start(AbstractIterator.java:4
      7)
      at oracle.dbtools.rt.util.AbstractIterator.hasNext(AbstractIterator.java
      :20)
      at oracle.dbtools.rt.x3p.impl.X3PReaderAdaptor.next(X3PReaderAdaptor.jav
      a:29)
      at oracle.dbtools.apex.config.ApexConfigSerializer.read(ApexConfigSerial
      izer.java:46)
      at oracle.dbtools.apex.config.ApexConfig.init(ApexConfig.java:158)
      at oracle.dbtools.rt.web.SCListener.contextInitialized(SCListener.java:3
      3)
      at com.sun.grizzly.http.servlet.ServletContextImpl.initListeners(Servlet
      ContextImpl.java:152)
      at ____bootstrap.MimeTypesServletContext.initListeners(MimeTypesServletC
      ontext.java:28)
      at com.sun.grizzly.http.servlet.ServletAdapter.configureServletEnv(Servl
      etAdapter.java:465)
      at com.sun.grizzly.http.servlet.ServletAdapter.start(ServletAdapter.java
      :281)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapterChain.start(GrizzlyAdapterCh
      ain.java:118)
      at com.sun.grizzly.http.SelectorThread.initEndpoint(SelectorThread.java:
      1126)
      at com.sun.grizzly.http.SelectorThread.listen(SelectorThread.java:1177)
      at com.sun.grizzly.http.embed.GrizzlyWebServer.start(GrizzlyWebServer.ja
      va:585)
      at ____bootstrap.Deployer.start(Deployer.java:276)
      at ____bootstrap.____Bootstrap._start(____Bootstrap.java:41)
      at ____bootstrap.____Bootstrap.start(____Bootstrap.java:163)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at ____embedded.____EntryPoint.invoke(____EntryPoint.java:299)
      at ____embedded.____EntryPoint.main(____EntryPoint.java:95)
      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,3]
      Message: The markup declarations contained or pointed to by the document type de
      claration must be well-formed.
      at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(Unkn
      own Source)
      at com.sun.xml.internal.stream.XMLEventReaderImpl.nextEvent(Unknown Sour
      ce)
      at oracle.dbtools.rt.x3p.impl.StAXEventIterator$XMLEventIterator.advance
      (StAXEventIterator.java:108)
      ... 32 more
      2011-06-30 14:40:09 com.sun.grizzly.Controller logVersion
      INFO: Starting Grizzly Framework 1.9.18-o - Thu Jun 30 14:40:09 CEST 2011
      INFO: http://localhost:6565/apex started.


      I tried without it -Dapex.port=6565 and -Dapex.home=c:\apex_listener but error still appear.

      Windows XP Prof.
      JDK 1.6.0_26
        • 1. Re: Standalone mode Error
          872509
          I have the same problem.
          apex_listener.1.1.2.131.15.23
          Windows Server 2008 x64
          JDK 1.6.0_26
          • 2. Re: Standalone mode Error
            Udo
            Hi Andy,

            I think this error was raised due to an outage of the Oracle servers that hold the schema definition for validation.
            Both URLs http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd were temporarily down today but showed a splash screen, so the schema validation failed.
            Currently the system seems to be up again. Could you check if it's working again?

            -Udo

            P.S.: Similar problem: {thread:id=2246333}
            • 3. Re: Standalone mode Error
              872509
              Hi Udo,
              I've just checked it out. It's working fine again.
              Thanks for your answer!
              • 4. Re: Standalone mode Error
                AndyPol
                Now is OK : )
                • 5. Re: Standalone mode Error
                  MortenBraten
                  I think this error was raised due to an outage of the Oracle servers that hold the schema definition for validation.
                  Both URLs http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd were temporarily down today but showed a splash screen, so the schema validation failed.
                  Currently the system seems to be up again. Could you check if it's working again?
                  I had the same problem yesterday. Wasted precious time trying to figure out what was wrong, before giving up. It's working again now.

                  Not sure I like this external dependency, though... does this mean that the "standalone" Listener can't be used without an Internet connection? Since I used the Listener on a laptop on an airplane just the day before yesterday, I know that it works without a connection... so exactly when does this external validation (or "phoning home" if you will) take place?

                  - Morten

                  http://ora-00001.blogspot.com
                  • 6. Re: Standalone mode Error
                    Udo
                    Hi Morten,

                    this validation is done by (almost) every JEE server for (almost) every web application. I think, it would be skipped if the validation source was actually unreachable. The problem in that case was that Oracle has changed the behaviour of the former Sun site to behave according to Oracle standards and provide some custom splash screen on a server error/maintenance outage/... This splash screen obviously provides a non-usable validation resource. This should be handled better - both by the web server providing the validation and by the Container not to throw that error but behave like in case the resource is not reachable.

                    -Udo
                    • 7. Re: Standalone mode Error
                      Colm Divilly-Oracle
                      Just to clarify a couple of things about this problem:

                      - In the stack trace above the external validation is happening when the apex-config.xml file is being read, it's actually http://java.sun.com/dtd/properties.dtd that it's trying to access
                      - java.sun.com did experience downtime, which led to the problems noted above.
                      - The external validation should not be happening in the first place, this is a defect/regression. I've yet to determine why the XML parser was not behaving as expected in this case. This will be addressed in the next release.
                      • 8. Re: Standalone mode Error
                        Udo
                        Hi Colm,

                        you're right, seems I've overlooked the difference in the location. Yet, I experienced a similar problem with the web.xml that day - which of course had the same cause... But I'm currently not sure if it was on the Standalone version or some other container. However, it's good to know that there'll be a solution for the APEX Listener's validation, though I'm not sure if this would help with the validation of the web.xml. But as I said before, this would be a container problem ...

                        -Udo
                        • 9. Re: Standalone mode Error
                          893476
                          I am facing problem today. i created new file as .xsd and pointed in web.xml, but didnt work for me. pls let me know what is the right solution for this.
                          • 10. Re: Standalone mode Error
                            893476
                            HI Guys,

                            I found one temporary solution for this. I am not sure how good it is but I tried to run my standalone apex listener
                            I removed the line - code <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> from apex-config.xml file.

                            Once Oracle outage/splash up try to get this file as well web-xsd file for future reference, but till now you can remove line to search for dtd file .

                            I hope this will help for everybody..!