Reports 11g on 64-bit: In-process Reports Server Hangs and Standalone Works OK on Brand New Installation
(Doc ID 1359969.1)
Last updated on FEBRUARY 12, 2018
Applies to:Oracle Reports Developer - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Checked for relevance 04-Nov-2015
The issues related to incorrect JDK or re-installation of WLS or FMW 11g are handled by Fusion Middleware team, not by Reports Team.
When attempting to access the in-process Reports Server deployed in WLS_REPORTS (for example, "getserverinfo" or "showenv" from URL), the web browser hangs.
"Stuck Threads" Error
However, the standalone Reports Server works fine:
Also, per rwdiag.sh -findAll output, the standalone Reports Server is up and running:
The problem is only with the in-process Reports Server.
NOTE: The rwdiag.sh displays warnings on 64bit platforms, but these may not be critical by themselves:
Environment:getEnvironmentStrings java.lang.UnsatisfiedLinkError: /opt/oracle/Middleware/PFRD1/lib/librwu.so: ld.so.1: java: fatal: /opt/oracle/Middleware/PFRD1/lib/librwu.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch)
These are per known <Bug 9720237> : RWDIAG.SH ERRORS WITH /LIB/LIBRWU.SO: WRONG ELF CLASS: ELFCLASS64
Edit rwdiag.sh and add -d64 to line as below and retry:
That warning from rwdiag.sh is not critical.
This is a new Fusion Middleware 11g Rel 1 installation on 64-bit platform.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!