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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.