![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| HP-UX HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Shared memory for shared library | otheus | High Level Programming | 0 | 09-03-2008 03:55 AM |
| Shared memory in shared library | DreamWarrior | High Level Programming | 12 | 05-30-2007 04:33 PM |
| memory sharing - not shared memory - | elzalem | High Level Programming | 9 | 05-02-2007 07:45 AM |
| Shared memory shortage but lots of unused memory | cjcamaro | UNIX for Advanced & Expert Users | 1 | 10-13-2004 05:10 PM |
| Memory Fault with Lawson Install | dnardi212 | HP-UX | 2 | 03-05-2004 04:31 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
WAS 6.1 ND/Lawson ERP/HP-UX 11.23 PA-RISC - unable to attach shared memory segment
I'm not an HP-UX Admin professional, but rather a Lawson ERP installer. I'm looking for clues on how to troubleshoot this issue. I have WAS 6.1 ND running on HP-UX 11.23 PA-RISC with the Lawson ERP application . When I start the Lawson application, no errors arise. When I start WAS app server, an error appears in the Lawson ladb.log "Unable to attach shared memory segment" and many Lawson web components do not work. I used to be able to get around this error by removing all values from WAS JVM min/max heap sizes and letting it default to set values. But not on this install. Any input or help would be greatly appreciated!
|
|
||||
|
max proc /threads or shmmax
Thank you for the advice. We have reviewed these settings. Here's the kicker, however - another installation, same OS level and patches, same memory, identical kernel params exhibits no errors. So, could this error be a symptom of shared memory? I found an article on HP's site regarding shared memory fragmentation and the inability of a 32-bit app to secure the segment it needs. Could this be my culprit? If not, I'll lookt into increasing max proc /threads and shmmax. Thanks again!
|
|
|||||
|
I would concentrate on finding the difference between the two systems. And be sure you have checked all of the shared memory kernel settings. Especially shmmni(5) which is a system-wide limitation.
Run ipcs -mb on both systems to see how much shared memeory is currently in use. Has something used it all up? And what about free memory? You need free memory to make shared memory. Run vmstat 1 5 to see how that looks. |
| Sponsored Links | ||
|
|