locked
Available memory in APPV environment? RRS feed

  • Question

  • Hi there,

    I'm having issues running a java app in appv. I have sequenced the java runtime together with the app.

    At strartup, the app notifies that only 240MB of free memory is available when it is being run virtualized. Could this be an issue with the appv client?

    /Bart.

    Monday, June 20, 2016 10:01 AM

Answers

All replies

  • Which App-V Version are you running?

    Simon Dettling | msitproblog.com | @SimonDettling

    Monday, June 20, 2016 12:17 PM
    Moderator
  • That would be 5.1 with HF3.

    /Bart.

    Monday, June 20, 2016 12:38 PM
  • Have you tried assigning more memory to the JAR file?

    Before 5.1 HF3 i was only able to assign a maximum of 734M, but now I got apps virtualized with as much as 1500Mb of virtual memory.

    A sample commandline would be:
    Java.exe -jar <file> -xmx1024M
    (that would assign 1GB of virtual java memory)

    ---- Snippet from configuration.xml ---

    <Extension Category="AppV.Shortcut">
              <Shortcut>
                <File>[{Common Programs}]\HDFView 2.11.lnk</File>
                <Target>[{Common AppData}]\Oracle\Java\javapath\javaw.exe</Target>
                <Icon>[{AppVPackageRoot}]\HDFView-2_103.ico</Icon>
                <Arguments>-jar "[{AppVPackageRoot}]\lib\jhdfview.jar" -xmx1024M -dJava.Library.path="[{AppVPackageRoot}]\lib;[{AppVPackageRoot}]\bin" -Dhdfview.root="[{AppVPackageRoot}]\"</Arguments>
                <WorkingDirectory>[{AppVPackageRoot}]</WorkingDirectory>
                <ShowCommand>1</ShowCommand>
                <ApplicationId>[{Common AppData}]\Oracle\Java\javapath\javaw.exe"</ApplicationId>
              </Shortcut>
            </Extension>

    Regards, Frans.



    • Edited by Frans K. _ Tuesday, June 21, 2016 6:53 PM
    Tuesday, June 21, 2016 6:52 PM
  • Hi Frans,

    Yes, I tried playing with the -XMX settings.

    If I allocate -xmx1024M the app doesn't start (even no error msg). If I lower max memory eg -xmx750M the app starts, but it complains that not enough memory might be available (it's a check that's done within the app).

    /Bart.

    Tuesday, June 21, 2016 7:43 PM
  • Ok, this issue has been fixed in the 06/2016 mdop servicing release

    https://support.microsoft.com/en-us/kb/3155806)

    • Marked as answer by BartPe Tuesday, July 19, 2016 1:31 PM
    Tuesday, July 19, 2016 1:31 PM