Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Unable to access Enterprise Manager after Fusion Middleware Install with OAS 2025 on RHEL9

Accepted answer
180
Views
12
Comments
Chad Williams
Chad Williams Rank 5 - Community Champion
in Oracle Analytics Cloud and Server

Hello,

I installed FMW (12.2.1.4) and OAS2025 on RHEL9. I can hit the web page for both the EM and the Console for WLS (http://server:9500/em and http://server:9500/console), and when I login for the first time (as weblogic user), the page just spins and spins and eventually times out. Trying to parse AdminServer.log but it's pretty big. I've tried 3 different browsers, clearing cache, and so on, and get the same result each time.

Incidentally, I'm able log in to the OAS 2025 Application as the weblogic user (http://server:9502/dv) with no issues. Am going to double check firewalls, but am wondering if anyone else has ran into this issue recently? Running on a 100GB disk with 32GB RAM so don't think that is an issue.

I've tried both with and without patching and have the same issue either way. Currently running JDK version 1.8_421.

Thanks in advance for any Insight you might be able to provide. Have never encountered this in previous installations.

Regards,

Chad Williams

Tagged:

Best Answers

  • Chad Williams
    Chad Williams Rank 5 - Community Champion
    Answer ✓

    I was looking at that same document. I will give it a shot!

«1

Answers

  • Chad Williams
    Chad Williams Rank 5 - Community Champion

    Well, I guess it got in eventually. It's giving me this warning.

    Login is taking more time than usual. Total login time is 1240406 ms, discovery time is 1229629 ms. Consider enabling discovery cache and/or improving application server performance.

  • Chad Williams
    Chad Williams Rank 5 - Community Champion
    edited Mar 24, 2025 9:17PM

    ExecuteRequest failed
    java.lang.OutOfMemoryError: GC overhead limit exceeded.
    java.lang.OutOfMemoryError: GC overhead limit exceeded

    Seeing some info like this in AdminServer.log

  • Chad Williams
    Chad Williams Rank 5 - Community Champion

    Thanks as always for your help @Gianni Ceresa !

  • Chad Williams
    Chad Williams Rank 5 - Community Champion

    I am seeing this error in the log, so will pursue it

    <Info> <ServletContext-/em> <AdminServer> <[ACTIVE] ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <9f067b2c-6495-4c58-a4a4-20100d3376a4-00000153> <1742848549921> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <JspServlet error: Servlet unable to dispatch to the following requested page: The following exception occurred:java.lang.OutOfMemoryError: GC overhead limit exceeded>

  • Chad Williams
    Chad Williams Rank 5 - Community Champion

    Seeing some stuff like this in the AdminServer.log

    ####<Mar 24, 2025 4:37:39,398 PM EDT> <Error> <Kernel> <oit-app-ld030.oit.ohio.edu> <AdminServer> <[ACTIVE] ExecuteThread: '34' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9f067b2c-6495-4c58-a4a4-20100d3376a4-0000015c> <1742848659398> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000802> <ExecuteRequest failed
    java.lang.OutOfMemoryError: GC overhead limit exceeded.
    java.lang.OutOfMemoryError: GC overhead limit exceeded

  • Gianni Ceresa
    Gianni Ceresa Mod

    If EM works for what you need (you shouldn't be spending much time in there anyway), I wouldn't bother much…

    If you really want to try to get rid of that, you could try giving more memory to java. MOS should have some documents on how to do that for WebLogic or FMW (/em is not "inside" OAS itself, it'a FMW thing). It's probably a file to edit to add a -Xms and/or -Xmx in the java call.

  • SteveF-Oracle
    SteveF-Oracle Mod

    In addition to java memory tuning (AdminServer in this case for FMWControl (EM)), low file descriptors can cause issues such as  java.lang.OutOfMemoryError: GC overhead limit exceeded.

    There is a MOS tuning guide for OAS that can guide you to increase the soft and hard limits.
    Doc ID 2866848.2

  • Chad Williams
    Chad Williams Rank 5 - Community Champion

    Thanks for the additional feedback. I do have some additional tuning steps that support provided to me on our last few installs, but for some reason, I just couldn't get into EM at all with this particular install. I spent 3 hours fussing with trying to get into EM to make the bare minimum needed configuration changes and it was very frustrating. I even regretfully did a rebuild to make sure it wasn't a result of patching or Java compatibility. Editing the emoms.properties file was super easy and definitely the way to go here. I probably won't need to do any more tuning as the performance is more than adequate now. Will probably also make this change in FMW for our 2022 environment.