REP-56048 Engine Crash when Connecting to the Database (Doc ID 747045.1)

Last updated on AUGUST 02, 2016

Applies to:

Oracle Reports Developer - Version 10.1.2.0.2 to 10.1.2.3 [Release Oracle10g to 10gr2]
Information in this document applies to any platform.
"Checked for relevance on 02-Oct-2013"
"Checked for relevance on 04-Mar-2015"
"Checked for relevance on 02-Aug-2016"

Symptoms

Reports Engine crashing with REP-56048 error when connecting to the Database.

Browser error

REP-56048: Engine rwEng-0 crashed, job Id: XXX

Error in rwserver.trc file

[2008/10/28 8:27:22:302] Debug 50103 (EngineManager:updateEngineState): Engine rwEng-0 status is 3
[2008/10/28 8:27:22:302] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Running
[2008/10/28 8:27:22:974] 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)
): Internal error org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 208 completed: Maybe
[2008/10/28 8:27:22:974] Info 56029 (EngineManager:shutdownEngine): Shutting down engine rwEng-0
[2008/10/28 8:27:23:286] (ConnectionImpl:getServerRunningInfo) enter...
[2008/10/28 8:27:23:286] (ConnectionImpl:getServerRunningInfo) ...exit
[2008/10/28 8:27:23:286] Info 56013 (ConnectionManager:release): Connection 8 is released
[2008/10/28 8:27:23:865] 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.JobManager.runJobLocal(JobManager.java:1912)
at oracle.reports.server.JobManager.dispatch(JobManager.java:1152)
at oracle.reports.server.ConnectionImpl.runJob(ConnectionImpl.java:1285)
at oracle.reports.server._ConnectionImplBase._invoke(_ConnectionImplBase.java:401)
at com.sun.corba.se.internal.corba.ServerDelegate.dispatch(ServerDelegate.java:355)
at com.sun.corba.se.internal.iiop.ORB.process(ORB.java:280)
at com.sun.corba.se.internal.iiop.RequestProcessor.process(RequestProcessor.java:81)
at com.sun.corba.se.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:106)
): Internal error org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
[2008/10/28 8:27:23:865] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Shutdown
[2008/10/28 8:27:23:865] Info 56047 (EngineManager:remove): Reports Server shut down engine rwEng-0
[2008/10/28 8:27:23:865] State 56016 (JobManager:updateJobStatus): Job XXX status is: Terminated with error:
REP-56048: Engine rwEng-0 crashed, job Id: XXX

How to determine if engine crash is happening when connecting to the database?

Error in Reports Engine trace file (rw-Engx.trc) [no more trace information is generated and last line in trace file is "(C Engine) "]

[2008/10/28 8:27:22:302] Debug 50103 (EngineImpl:run): Running Jobid=XXX
[2008/10/28 8:27:22:802] (C Engine) LOG :

[2008/10/28 8:27:22:802] (C Engine) Logged onto server: <server name>

[2008/10/28 8:27:22:818] (C Engine) Username: <USERNAME>

[2008/10/28 8:27:22:818] (C Engine)

To double check if this error is happening during the database connection process it is recommended to enable engine diagnostics for advanced tracing <Note:360302.1>

Engine diagnostic trace information will look as follows:

[2008/10/01 09:55:59] Diagnosis (rwsjni:CInitEngine): Diagnosis system is initialized...
[2008/10/01 09:55:59] Diagnosis (rwsjni:CInitEngine): Before calling rwsjnist_Startup()
[2008/10/01 09:55:59] Diagnosis (rwsjni:CInitEngine): After calling rwsjnist_Startup()
[2008/10/01 09:55:59] Diagnosis (rwsjni:CInitEngine): Before calling uiprg() to create printer
[2008/10/01 09:55:59] Diagnosis (rwsjni:CInitEngine): After calling uiprg()
[2008/10/01 09:55:59] Diagnosis (rwsjni:CInitEngine): Exit
[2008/10/01 09:56:11] Diagnosis (rwsjni:CRunReport): Enter
[2008/10/01 09:56:11] Diagnosis (rxsjni:CRunReport): Run Reports ...
[2008/10/01 09:56:11] Diagnosis (rxsjni:CRunReport): Before calling CheckDirectories
[2008/10/01 09:56:11] Diagnosis (rxsjni:CRunReport): After calling CheckDirectories
[2008/10/01 09:56:11] Diagnosis (rwsjni:CRunReport): Before calling riulgf() & riulgo()
[2008/10/01 09:56:11] Diagnosis (riul:riulgf): Enter
[2008/10/01 09:56:11] Diagnosis (riul:riulgo): Enter
[2008/10/01 09:56:11] Diagnosis (riul:riulgo): Before calling rolgin()

Last line in diagnostic trace file will be "Diagnosis (riul:riulgo): Before calling rolgin() "

A normal engine database connection will look as follows:

[2008/10/01 09:58:59] Diagnosis (rwsjni:CInitEngine): Diagnosis system is initialized...
[2008/10/01 09:58:59] Diagnosis (rwsjni:CInitEngine): Before calling rwsjnist_Startup()
[2008/10/01 09:58:59] Diagnosis (rwsjni:CInitEngine): After calling rwsjnist_Startup()
[2008/10/01 09:58:59] Diagnosis (rwsjni:CInitEngine): Before calling uiprg() to create printer
[2008/10/01 09:58:59] Diagnosis (rwsjni:CInitEngine): After calling uiprg()
[2008/10/01 09:58:59] Diagnosis (rwsjni:CInitEngine): Exit
[2008/10/01 10:00:20] Diagnosis (rwsjni:CRunReport): Enter
[2008/10/01 10:00:20] Diagnosis (rxsjni:CRunReport): Run Reports ...
[2008/10/01 10:00:20] Diagnosis (rxsjni:CRunReport): Before calling CheckDirectories
[2008/10/01 10:00:20] Diagnosis (rxsjni:CRunReport): After calling CheckDirectories
[2008/10/01 10:00:20] Diagnosis (rwsjni:CRunReport): Before calling riulgf() & riulgo()
[2008/10/01 10:00:20] Diagnosis (riul:riulgf): Enter
[2008/10/01 10:00:20] Diagnosis (riul:riulgo): Enter
[2008/10/01 10:00:20] Diagnosis (riul:riulgo): Before calling rolgin()
[2008/10/01 10:00:21] Diagnosis (riul:riulgo): After calling rolgin(), succeed in logging on

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms