Prev
Next
Forums S3 Systems Administration

Websphere Heap Sizes And Shared Memory Segments, SSO smoke tests won't run

Sort:
You are not authorized to post a reply.
Author
Messages
mrvitas
Basic Member
Posts: 16
Basic Member
9/22/2008 12:28 PM

     

    When installing WAS on HP-UX server, Lawson recommended initial and max heap sizes of 512/1024 produced error messages in ladb.log when WAS started - couldn't attach shared memory segment. SSO smoke tests failed.

    When initial and max heap sizes were left blank, no errors in ladb.log and SSO smoke tests completed OK.

    New HP-UX server and trying to leave heap sizes blank again, but shared memory segment errors appearing in ladb.log nonetheless. SSO smoke tests failing.

    Anyone see or find an IBM tuning process on how to best set-up the initial and max heap sizes? Anyone else see this on their OS systems? Any help would be great! Thanks!

    mrvitas

    John Henley
    Senior Member
    Posts: 3348
    Senior Member
    9/22/2008 12:36 PM
      Re: Websphere Heap Sizes And Shared Memory Segments, SSO smoke tests won't run (159595f9-eac7-4521-97c3-c9aba203b714) <!-- Converted from text/plain format -->

      You probably need to check/increase kernel parameters.
      John Henley

      Thanks for using the LawsonGuru.com forums!
      John
      mrvitas
      Basic Member
      Posts: 16
      Basic Member
      9/22/2008 12:47 PM
        Hi John - thanks for the swift feedback. I guess I can start by increasing HP-UX kernel parameters related to shared memory? Although configured per Lawson's suggestions, I'll try and bump SHMMAX, SHMMNI and SHMSEG. Any other ideas?
        John Henley
        Senior Member
        Posts: 3348
        Senior Member
        9/22/2008 1:58 PM
          Re: Websphere Heap Sizes And Shared Memory Segments, SSO smoke tests won't run (159595f9-eac7-4521-97c3-c9aba203b714) <!-- Converted from text/plain format -->

          Also max_thread_proc
          John Henley

          Thanks for using the LawsonGuru.com forums!
          John
          mrvitas
          Basic Member
          Posts: 16
          Basic Member
          9/23/2008 12:45 PM

            Hi John,

            I found an IBM document about installing WebSphere on HP-UX. IT had kernel parameter settings which exceeded Lawson's recommended settings, including max_thread_proc. These were changed but the same issue/error persists - when WebSphere application server for Lawson starts, "can't attach shared memory segment" error appears in $LAWDIR/system/ladb.log.

            Ay other ideas?    Thanks again for your help on this!

             

            Roger French
            Veteran Member
            Posts: 545
            Veteran Member
            9/24/2008 8:51 PM

              This may or may not help.

              Do you really know the problem lies with the heap size? How do you know it's not the WebSphere install and/or configuration?

              Have you checked websphere? Is the Application Server and the Applications running on websphere? What SSO Smoketests are not running... all of them?

              There is also a LID smoke test... does that work?

              Check also the environment/os service in ssoconfig.

              -Roger

               

               

              mrvitas
              Basic Member
              Posts: 16
              Basic Member
              10/15/2008 5:37 PM
                Hi Roger - it's been a while, but I'm still wrestling with this issue. Here's the scenario, briefly. Installed LSF9 core technology, portal is not yest installed. Executing post LSF9 core technology smoke tests. /servlet/Profile?_PATh=TEST and pfserv test testGroupIOS are both failing with ""java.UnsatisfiedLinkError: jniTsDBConnect errors. I find this inthe wuerr log file and ios.log. Lawson KB 939906 talks about access to the shared libraries but it all checks out, in WebSphere and in lawson.env.

                I think it's related to WebSphere heap sizes because I fixed this very same issue before at another client by leaving these values blank. Here, it doesn't work. I also advised a Topica user to do the same and she got around her "shared memory segment error" by manipulating the heap sizes.

                What do you think?
                John Henley
                Senior Member
                Posts: 3348
                Senior Member
                10/15/2008 6:31 PM
                  This is HP-UX, right? What do you have for the max_thread_proc kernel setting?
                  Thanks for using the LawsonGuru.com forums!
                  John
                  mrvitas
                  Basic Member
                  Posts: 16
                  Basic Member
                  11/3/2008 8:45 PM
                    Hi John - Sorry that I haven't responded in a while. max_thread_proc kernel setting for this server is the same as for another HP-UX 11.23 PA-RISC server running LSF9 - 256. Seems to work OK on 1 server, but not another. In the meantime, just for laughs, we restored the working LSF9 environment to the server where we are having a problem and it came up working OK, no issues. But Lawson wouldn't let us reconfigure it to run as our development server. They told us it was an HP-UX issue, so, we are re-installing in the hopes we don't encounter the error again. We are also trying to engage HP-UX to assist, in the event we see it again.

                    In the meantime, another Lawson user is having this problem on AIX (... on Topica) They turned on verbose setting in WebSphere Java Virtual Machine and found issues with the JNI method. Lawson is evaluating.

                    Thanks again for all the help!

                    Vitas
                    You are not authorized to post a reply.