<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic could not allocate code space in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488043#M3897</link>
    <description>We are running a java applications under Oracle 9iAs rel. 9.0.2.3 on a DS40 tru64 5.1B native java 1.3.1.3.&lt;BR /&gt;Pretty often the java container crash giving the error:&lt;BR /&gt;&lt;BR /&gt;could not allocate code space: No such file or directory, file /sys/alpha/md.c, line 134&lt;BR /&gt;&lt;BR /&gt;When this errors happens the Java container crash and restart.&lt;BR /&gt;&lt;BR /&gt;The starting  Java parameter are:&lt;BR /&gt;&lt;BR /&gt;java -fast64 -Xms3072m -Xmx3072m -Xgc:compacting -Xnoprecompiledsys&lt;BR /&gt;&lt;BR /&gt;Do you have any suggestion?&lt;BR /&gt;Below the memory allocation and kernel parameter.&lt;BR /&gt;Regards&lt;BR /&gt;Donatella&lt;BR /&gt;&lt;BR /&gt;Below the Memory allocation&lt;BR /&gt;levante1.uniroma1.it&amp;gt; vmstat -P&lt;BR /&gt;&lt;BR /&gt;Total Physical Memory =  6144.00 M&lt;BR /&gt;                      =   786432 pages&lt;BR /&gt;&lt;BR /&gt;Physical Memory Clusters:&lt;BR /&gt;&lt;BR /&gt;start_pfn     end_pfn        type  size_pages / size_bytes&lt;BR /&gt;         0         256         pal         256 /    2.00M&lt;BR /&gt;       256      130970          os      130714 / 1021.20M&lt;BR /&gt;    130970      131072         pal         102 /  816.00k&lt;BR /&gt;    131072      786422          os      655350 / 5119.92M&lt;BR /&gt;    786422      786432         pal          10 /   80.00k&lt;BR /&gt;&lt;BR /&gt;Physical Memory Use:&lt;BR /&gt;&lt;BR /&gt; start_pfn     end_pfn        type  size_pages / size_bytes&lt;BR /&gt;       256         289    scavenge          33 /  264.00k&lt;BR /&gt;       289        1124        text         835 /    6.52M&lt;BR /&gt;      1124        1295        data         171 /    1.34M&lt;BR /&gt;      1295        1530         bss         235 /    1.84M&lt;BR /&gt;      1530        1739      kdebug         209 /    1.63M&lt;BR /&gt;      1739        1746     cfgmgmt           7 /   56.00k&lt;BR /&gt;      1746        1748       locks           2 /   16.00k&lt;BR /&gt;      1748        1762        pmap          14 /  112.00k&lt;BR /&gt;      1762        4123   unixtable        2361 /   18.45M&lt;BR /&gt;      4123        4267        logs         144 /    1.12M&lt;BR /&gt;      4267        7673    vmtables        3406 /   26.61M&lt;BR /&gt;      7673      131072     managed      123399 /  964.05M&lt;BR /&gt;    131072      146080    vmtables       15008 /  117.25M&lt;BR /&gt;    146080      786422     managed      640342 / 5002.67M&lt;BR /&gt;                             ============================&lt;BR /&gt;         Total Physical Memory Use:     786166 / 6141.92M&lt;BR /&gt;&lt;BR /&gt;Managed Pages Break Down:&lt;BR /&gt;&lt;BR /&gt;       free pages = 100758&lt;BR /&gt;     active pages = 455786&lt;BR /&gt;   inactive pages = 63571&lt;BR /&gt;      wired pages = 44778&lt;BR /&gt;        ubc pages = 98778&lt;BR /&gt;        ==================&lt;BR /&gt;            Total = 763671&lt;BR /&gt;&lt;BR /&gt;WIRED Pages Break Down:&lt;BR /&gt;&lt;BR /&gt;   vm wired pages = 5702&lt;BR /&gt;  ubc wired pages = 10&lt;BR /&gt;  meta data pages = 23539&lt;BR /&gt;     malloc pages = 11724&lt;BR /&gt;     contig pages = 1467&lt;BR /&gt;    user ptepages = 1518&lt;BR /&gt;  kernel ptepages = 808&lt;BR /&gt;    free ptepages = 10&lt;BR /&gt;        ==================&lt;BR /&gt;            Total = 44778&lt;BR /&gt;&lt;BR /&gt;Kernel Parameter&lt;BR /&gt;&lt;BR /&gt;proc:&lt;BR /&gt;        per_proc_stack_size=134217728&lt;BR /&gt;        per_proc_data_size=4294967296&lt;BR /&gt;&lt;BR /&gt;        max_per_proc_stack_size=4294967296&lt;BR /&gt;        max_threads_per_user=4096&lt;BR /&gt;        max_proc_per_user=2048&lt;BR /&gt;        max_per_proc_data_size=4294967296&lt;BR /&gt;        max_per_proc_address_space=4294967296&lt;BR /&gt;        per_proc_address_space=4294967296&lt;BR /&gt;        maxusers=4096&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 17 Feb 2005 11:24:14 GMT</pubDate>
    <dc:creator>Donatella_2</dc:creator>
    <dc:date>2005-02-17T11:24:14Z</dc:date>
    <item>
      <title>could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488043#M3897</link>
      <description>We are running a java applications under Oracle 9iAs rel. 9.0.2.3 on a DS40 tru64 5.1B native java 1.3.1.3.&lt;BR /&gt;Pretty often the java container crash giving the error:&lt;BR /&gt;&lt;BR /&gt;could not allocate code space: No such file or directory, file /sys/alpha/md.c, line 134&lt;BR /&gt;&lt;BR /&gt;When this errors happens the Java container crash and restart.&lt;BR /&gt;&lt;BR /&gt;The starting  Java parameter are:&lt;BR /&gt;&lt;BR /&gt;java -fast64 -Xms3072m -Xmx3072m -Xgc:compacting -Xnoprecompiledsys&lt;BR /&gt;&lt;BR /&gt;Do you have any suggestion?&lt;BR /&gt;Below the memory allocation and kernel parameter.&lt;BR /&gt;Regards&lt;BR /&gt;Donatella&lt;BR /&gt;&lt;BR /&gt;Below the Memory allocation&lt;BR /&gt;levante1.uniroma1.it&amp;gt; vmstat -P&lt;BR /&gt;&lt;BR /&gt;Total Physical Memory =  6144.00 M&lt;BR /&gt;                      =   786432 pages&lt;BR /&gt;&lt;BR /&gt;Physical Memory Clusters:&lt;BR /&gt;&lt;BR /&gt;start_pfn     end_pfn        type  size_pages / size_bytes&lt;BR /&gt;         0         256         pal         256 /    2.00M&lt;BR /&gt;       256      130970          os      130714 / 1021.20M&lt;BR /&gt;    130970      131072         pal         102 /  816.00k&lt;BR /&gt;    131072      786422          os      655350 / 5119.92M&lt;BR /&gt;    786422      786432         pal          10 /   80.00k&lt;BR /&gt;&lt;BR /&gt;Physical Memory Use:&lt;BR /&gt;&lt;BR /&gt; start_pfn     end_pfn        type  size_pages / size_bytes&lt;BR /&gt;       256         289    scavenge          33 /  264.00k&lt;BR /&gt;       289        1124        text         835 /    6.52M&lt;BR /&gt;      1124        1295        data         171 /    1.34M&lt;BR /&gt;      1295        1530         bss         235 /    1.84M&lt;BR /&gt;      1530        1739      kdebug         209 /    1.63M&lt;BR /&gt;      1739        1746     cfgmgmt           7 /   56.00k&lt;BR /&gt;      1746        1748       locks           2 /   16.00k&lt;BR /&gt;      1748        1762        pmap          14 /  112.00k&lt;BR /&gt;      1762        4123   unixtable        2361 /   18.45M&lt;BR /&gt;      4123        4267        logs         144 /    1.12M&lt;BR /&gt;      4267        7673    vmtables        3406 /   26.61M&lt;BR /&gt;      7673      131072     managed      123399 /  964.05M&lt;BR /&gt;    131072      146080    vmtables       15008 /  117.25M&lt;BR /&gt;    146080      786422     managed      640342 / 5002.67M&lt;BR /&gt;                             ============================&lt;BR /&gt;         Total Physical Memory Use:     786166 / 6141.92M&lt;BR /&gt;&lt;BR /&gt;Managed Pages Break Down:&lt;BR /&gt;&lt;BR /&gt;       free pages = 100758&lt;BR /&gt;     active pages = 455786&lt;BR /&gt;   inactive pages = 63571&lt;BR /&gt;      wired pages = 44778&lt;BR /&gt;        ubc pages = 98778&lt;BR /&gt;        ==================&lt;BR /&gt;            Total = 763671&lt;BR /&gt;&lt;BR /&gt;WIRED Pages Break Down:&lt;BR /&gt;&lt;BR /&gt;   vm wired pages = 5702&lt;BR /&gt;  ubc wired pages = 10&lt;BR /&gt;  meta data pages = 23539&lt;BR /&gt;     malloc pages = 11724&lt;BR /&gt;     contig pages = 1467&lt;BR /&gt;    user ptepages = 1518&lt;BR /&gt;  kernel ptepages = 808&lt;BR /&gt;    free ptepages = 10&lt;BR /&gt;        ==================&lt;BR /&gt;            Total = 44778&lt;BR /&gt;&lt;BR /&gt;Kernel Parameter&lt;BR /&gt;&lt;BR /&gt;proc:&lt;BR /&gt;        per_proc_stack_size=134217728&lt;BR /&gt;        per_proc_data_size=4294967296&lt;BR /&gt;&lt;BR /&gt;        max_per_proc_stack_size=4294967296&lt;BR /&gt;        max_threads_per_user=4096&lt;BR /&gt;        max_proc_per_user=2048&lt;BR /&gt;        max_per_proc_data_size=4294967296&lt;BR /&gt;        max_per_proc_address_space=4294967296&lt;BR /&gt;        per_proc_address_space=4294967296&lt;BR /&gt;        maxusers=4096&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Feb 2005 11:24:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488043#M3897</guid>
      <dc:creator>Donatella_2</dc:creator>
      <dc:date>2005-02-17T11:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488044#M3898</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I assume you have installed the latest patch? Did you follow the instructions concerning java?&lt;BR /&gt;Isn't 3gb a little too much for startup?&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Feb 2005 12:58:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488044#M3898</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-02-17T12:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488045#M3899</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;witch latest patches are you talking about?&lt;BR /&gt;Yes we followed all the instructions.&lt;BR /&gt;Any how this system is completely dedicated to the applications, anything else is running, and as you can check it has a 6Gb RAM, why i could not dedicate 3Gb to the applications?&lt;BR /&gt;Another question, why the Xmx option does not work? In any case even the maximum allocated by Jvm is always equal to the Xms value.&lt;BR /&gt;Regards&lt;BR /&gt;Donatella</description>
      <pubDate>Fri, 18 Feb 2005 03:37:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488045#M3899</guid>
      <dc:creator>Donatella_2</dc:creator>
      <dc:date>2005-02-18T03:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488046#M3900</link>
      <description>Donatella,&lt;BR /&gt;&lt;BR /&gt;I am talking about the patch kit 4 for the unix and there is an instruction:&lt;BR /&gt;SPECIAL INSTRUCTIONS for Patch 1414.00 &lt;BR /&gt;Prior to setting the executable_data tunable to a non-zero&lt;BR /&gt;value, you MUST run the following script:&lt;BR /&gt;/usr/sbin/javaexecutedata&lt;BR /&gt;&lt;BR /&gt;Is this container only running once?&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Feb 2005 04:55:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488046#M3900</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-02-18T04:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488047#M3901</link>
      <description>hello Michael,&lt;BR /&gt;&lt;BR /&gt;is it one of the latest patch kit?&lt;BR /&gt;if yes it is not installed,i cant' find it running setld -i.&lt;BR /&gt;What do you mean for " Is this container running once ?"&lt;BR /&gt;The Oracle 9iAS has a named OC4J container.&lt;BR /&gt;This container is the one that "contains" the applications, and it is supposed to be up and running.&lt;BR /&gt;When Java crashes i read the message on the log file and the container automatically restart after the crash.&lt;BR /&gt;Of course it is a problem being a transactional application and if it crashes all the transactions running at that moment are lost.&lt;BR /&gt;I cannot upgrade the JVM because once i tried to put on the 1.3.1-6 and we had problem in deploying the applications, in any case this is a production system, so i have to try all the modification on a test system first.&lt;BR /&gt;&lt;BR /&gt;Greetings&lt;BR /&gt;Donatella</description>
      <pubDate>Fri, 18 Feb 2005 06:29:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488047#M3901</guid>
      <dc:creator>Donatella_2</dc:creator>
      <dc:date>2005-02-18T06:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488048#M3902</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you can see the installed patch kit with &lt;BR /&gt;dupatch -track -type kit&lt;BR /&gt;The output for the last kit is&lt;BR /&gt;T64V51BB25AS0004-20040616 OSF540&lt;BR /&gt;&lt;BR /&gt;This java command is that only started once?&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Feb 2005 06:48:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488048#M3902</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-02-18T06:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: could not allocate code space</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488049#M3903</link>
      <description>That patch is not installed, these are the patch kit installed:&lt;BR /&gt;&lt;BR /&gt;       Patches installed on the system came from following patch kits:&lt;BR /&gt;        --------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;        - T64V51BB22AS0002-20030415 OSF540&lt;BR /&gt;        - T64V51BB22AS0002-20030415 TCR540&lt;BR /&gt;&lt;BR /&gt;Yes the Java is started once and together with Apache are the only user process running on the system.&lt;BR /&gt;Regards&lt;BR /&gt;Donatella</description>
      <pubDate>Fri, 18 Feb 2005 08:11:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/could-not-allocate-code-space/m-p/3488049#M3903</guid>
      <dc:creator>Donatella_2</dc:creator>
      <dc:date>2005-02-18T08:11:37Z</dc:date>
    </item>
  </channel>
</rss>

