3 Replies Latest reply: Jul 2, 2013 4:47 AM by Christian Erlinger RSS

    FRM-41214 by long running Report




      Forms/Reports 10g on OC4J:

      I get a Forms error FRM-41214 by trying a long running Report after 14 min,

      Iin the Reports log we find a 'end of connection..' .


      Is there a config parameter of Forms to handle this worst case?


      Many thanks


        • 1. Re: FRM-41214 by long running Report
          Christian Erlinger

          How are you running your reports? With run_reports_object?



          • 2. Re: FRM-41214 by long running Report

            Hi Christian,


            I am using the rp2rro-package (modified) :





                 IF id_null (mparamlist_id)  THEN





                 END IF;



            I am trying also the asynchron Reports mode and get the same break (on the same side 1257 from about 2500 sides) ::


            [2013/7/1 0:11:59:282] Info 56013 (ConnectionManager:release): Connection 87771 is released
            [2013/7/1 0:11:59:291] Info 56013 (ConnectionManager:release): Connection 87772 is released
            [2013/7/1 0:11:59:306] Info 56013 (ConnectionManager:release): Connection 87773 is released
            [2013/7/1 0:11:59:316] State 56016 (JobManager:updateJobStatus): Job 1643 status is: Bericht Seite 1257 wird formatiert wird ausgef??hrt
            [2013/7/1 0:11:59:316] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 1643
            [2013/7/1 0:11:59:317] Info 56013 (ConnectionManager:release): Connection 87774 is released
            [2013/7/1 0:11:59:327] Info 56013 (ConnectionManager:release): Connection 87775 is released

            [2013/7/1 0:14:6:923] Info 56013 (ConnectionManager:release): Connection 98871 is released
            [2013/7/1 0:14:6:934] Exception 50125 (org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 completed: Maybe
            at com.sun.corba.se.internal.iiop.IIOPConnection.purge_calls(IIOPConnection.java:438)
            at com.sun.corba.se.internal.iiop.ReaderThread.run(ReaderThread.java:70)
            ): Interner Fehler org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 completed: Maybe
            [2013/7/1 0:14:6:934] Info 56029 (EngineManager:shutdownEngine): Shutting down engine rwEng-0
            [2013/7/1 0:14:6:935] Exception 50125 (org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
            at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:148)
            at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:65)
            at com.sun.corba.se.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:67)
            at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:652)
            at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:594)
            at com.sun.corba.se.internal.corba.ClientDelegate.request(ClientDelegate.java:886)
            at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:431)
            at oracle.reports.engine._EngineClassStub.shutdown(_EngineClassStub.java:173)
            at oracle.reports.server.EngineManager.shutdownEngine(EngineManager.java:1473)
            at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:1033)
            at oracle.reports.server.ExecAsynchJobThread.run(ExecAsynchJobThread.java:54)
            ): Interner Fehler org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
            [2013/7/1 0:14:6:935] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Shutdown
            [2013/7/1 0:14:6:935] Info 56047 (EngineManager:remove): Reports Server shut down engine rwEng-0
            [2013/7/1 0:14:6:936] State 56016 (JobManager:updateJobStatus): Job 1643 status is: Mit Fehler beendet:
            REP-56048: Engine rwEng-0 ausgefallen, job Id: 1643



            • 3. Re: FRM-41214 by long running Report
              Christian Erlinger

              Allright, the reports engine crashed, so you can rule your forms code out. There are a lot of reasons why this might happen; I remember having engine crashes in the base release ( with big report outputs and ref cursors with a very same behaviour; there were some other problems as well so if you are not on the latest patch level ( you should go ahead and patch your system. The next thing I can remember was some problem with the java heap with big reports; you could increase your java heap size in the reports server config; e.g.:


              <engine id="rwEng" jvmOptions="-Xmx512m" [...]


              Another thing causing somehow erratic behaviour I encountered where the REPORTS_TEMP / REPORTS_TMP / TEMP / TMP environment / registry variables which by default on windows contain blanks which also sometimes causes crashes. Simply point them to directories without blanks (C:\temp or something).


              And as a tip: when searching for problems with the reports server remove everything not necessary from the reports server config (e.g. the job status repository). Sometimes this also worked.


              In any case as said your forms code is most certainly not causing this problem but some misconfiguration/misbehaviour of the reports server is, so if the above does not solve your problem you might be better off in the reports forum.