Results 1 to 6 of 6

Thread: Maximum memory limit for HTML java instances for web server

  1. #1
    New Member
    Join Date
    Mar 2009
    Posts
    7

    Maximum memory limit for HTML java instances for web server

    Hi all,

    Long time lurker, been in JDE consulting for almost 14 years now!

    Currently I have a bit of situation,

    my customer is having performance issues on month end closings, there are very suspicious areas for it :least to say hardware is old and version. patch updates are not very good condition.

    that being said we would like to consider increasing memory allocated to web server since in last incidents we clearly saw memory issues for web server.

    JDE version 9.0, tool release 9.1.1.4

    currently the web server runs with:
    - Win2008 R2 (64 bit)
    - Oracle Jrockit Java 28.2.5 (1.6.0_37 64 bit)
    - WebLogic 10.3.6 (11g R1)

    and we have 8 gb memory for this server of which 4 is allocated to web logic.

    The thing is even if we want to increase it, we have conflicting views on increasing it for more than 4 GB , as CNC doesn't think it is good and alternative will be opening a second instance and use log on balance or smt .
    But i have concerns over doing it with second instance and logon balancer since we have only 2 weeks to year end closing and i don't want to change too many things.
    what is your take on this? does anyone know about max cap for memory limits for the HTML java instances

  2. #2
    As you mentioned, the versions are very old and adding more memory to the JVM is unlikely to yield much benefit. GC is going to be the main problem with more memory. You'll get a lot more benefit adding a second WebLogic instance and throwing in a LB.
    Russell Codlin
    www.rinami.com
    Capital Asset Management & Manufacturing Specialists
    REST Integration, IoT, Mobile Applications and Job Scheduling for all E1 releases from 9.2 back to 8.11SP1

  3. #3
    one way to make this less complicated would be to forget the load balancer for now. Create the second jvm and give only your financial users the url to the new jvm. Once you get them through year end, put a load balancer in place.
    Current: E1 9.2, TR 9.2.2.5, Win2012 R2, SQL Server 2014 R2, Weblogic, OneView, Embedded BIP
    Upgrade: E1 9.1, TR 9.1.4.4, Win2008 R2, SQL Server 2008 R2, WebLogic, OneView, Embedded BIP
    Original: E1 8.0, SP 24.1.2, Win2003, SQL Server 2005 SP3, all fat client

  4. #4
    Is there any danger of something going wrong while the load balancer is not in place?

  5. #5
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,267
    No - you just have a different URL for the Finance server
    Larry Jones
    E1 9.2 - TR 9.2.2.6 on Win 2016 R2. SQL Server 2016
    Wintel, BI Publisher

  6. #6
    Member Tom_Davidson's Avatar
    Join Date
    Nov 2000
    Location
    Wisconsin, USA
    Posts
    780
    It is less risky than what you have now, except that if you lose either one, you can give the users the other URL.
    Cleindori Consulting
    8.12/8.98.4.14, 9.1/9.1.5.3, 9.2/9.2.0.5/6
    IBM i, WebLogic on Windows, DBCS, Global installations.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.