<?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 Re: &amp;quot;Process killed due to Stack growth failure&amp;quot; in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442907#M8253</link>
    <description>Increase the kernel parameter maxssiz as I'm sure java will be a 32bit application. The default is 8MB.&lt;BR /&gt;&lt;BR /&gt;There is also maxssiz_64bit which you may want to look at.</description>
    <pubDate>Wed, 06 Sep 2000 10:28:53 GMT</pubDate>
    <dc:creator>Andy Monks</dc:creator>
    <dc:date>2000-09-06T10:28:53Z</dc:date>
    <item>
      <title>"Process killed due to Stack growth failure"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442906#M8252</link>
      <description>Dear all&lt;BR /&gt;&lt;BR /&gt;I am having HPUX 11.00 installed on L-1000&lt;BR /&gt;running radius for ISP Service.&lt;BR /&gt;now we have upgraded the Java SDK from 1.2&lt;BR /&gt;to 1.2.2.05.00  ( Java 2 SDK for HP-UX (700/800)).Dependent recommended patches also&lt;BR /&gt;installed.&lt;BR /&gt;After this my radius daemon is getting killed&lt;BR /&gt;automatically and I am getting the following error.&lt;BR /&gt;&lt;BR /&gt;""PID xxxx ws killed due to stack growth failure.&lt;BR /&gt;Possible cause: Insufficient memory or swap,or stack size exceeded maxssize."".&lt;BR /&gt;&lt;BR /&gt;If I restart again also it is getting killed.&lt;BR /&gt;Can anybody can help me , it is very urgent.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;V.Selvaraj</description>
      <pubDate>Wed, 06 Sep 2000 10:18:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442906#M8252</guid>
      <dc:creator>vselvaraj</dc:creator>
      <dc:date>2000-09-06T10:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: "Process killed due to Stack growth failure"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442907#M8253</link>
      <description>Increase the kernel parameter maxssiz as I'm sure java will be a 32bit application. The default is 8MB.&lt;BR /&gt;&lt;BR /&gt;There is also maxssiz_64bit which you may want to look at.</description>
      <pubDate>Wed, 06 Sep 2000 10:28:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442907#M8253</guid>
      <dc:creator>Andy Monks</dc:creator>
      <dc:date>2000-09-06T10:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: "Process killed due to Stack growth failure"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442908#M8254</link>
      <description>This is probably either due to insufficient swap space or you application requiring to extend its stack size larger than that allowed by the 'maxssiz' kernel parameter.&lt;BR /&gt;&lt;BR /&gt;Check your swap usage with 'swapinfo -mt', paying particular attention to the PCT Used value in the total. If this is nowhere near 100% then it is likely that 'maxssiz' is set too low. The default is 8Mb. If you have 'glance' then you could monitor the offending process and check its stack size.&lt;BR /&gt;&lt;BR /&gt;Does the application provider give any indication of required kernel settings?&lt;BR /&gt;&lt;BR /&gt;If not then try increasing 'maxssiz' to 16Mb with 'sam' -&amp;gt; kernel configuration -&amp;gt; configurable parameters.&lt;BR /&gt;This will require a reboot.&lt;BR /&gt;&lt;BR /&gt;Note that most applications don't normally need a huge stack size. Exceeding 'maxssiz' is normally the result of a software problem.</description>
      <pubDate>Wed, 06 Sep 2000 10:30:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442908#M8254</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2000-09-06T10:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: "Process killed due to Stack growth failure"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442909#M8255</link>
      <description>Increase maxssiz to 40mb to accomodate for future expansion.</description>
      <pubDate>Wed, 06 Sep 2000 11:44:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442909#M8255</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-09-06T11:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: "Process killed due to Stack growth failure"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442910#M8256</link>
      <description>Increase maxssiz to 40mb to accomodate for future expansion.</description>
      <pubDate>Wed, 06 Sep 2000 11:44:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-process-killed-due-to-stack-growth-failure-quot/m-p/2442910#M8256</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-09-06T11:44:47Z</dc:date>
    </item>
  </channel>
</rss>

