Setting JAVA_MAX_MEM in bin/setenv does not work when a container is launched using bin/admin

Solution Verified - Updated -

Issue

The script bin/setenv contains various memory settings that can be applied to a Fuse JVM. These settings are processed when starting the container using the bin/fuse script, but when starting a container using bin/admin they appear to be ignored, and default values are used.

Environment

  • Red Hat JBoss Fuse
    • 6.1
    • 6.2f

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content