Embedded messaging fails to install on Solaris Operating System
 Technote (troubleshooting)
 
Problem(Abstract)
Debugging embedded messaging installation failure on Solaris Operating System™.
 
Resolving the problem
If the installation fails:
  • Review Install_Root/logs/mq_install.log. If it does not exist, look for /tmp/mq_prereq.
  • Verify that the groups and users needed to install embedded messaging have been successfully created:
    • Verify that groups mqm and mqbrkrs exist.
    • Verify that the users that the JMS server runs on are members of the mqm group. This is normally mqm and root.
    • Verify that root is a member of the mqmbrkrs group.
    • Verify that a system log out was performed to set the permissions.

  • Ensure that the Solaris Operating System kernel values are correct for all the embedded messaging components to operate. If there are insufficient kernel resources, there will be a First Failure Support Technology (FFST) file in the /var/mqm/errors directory.

    If necessary, you can change these kernel parameters by editing the /etc/system file and rebooting the system:

    set shmsys:shminfo_shmmax = 4294967295
    set shmsys:shminfo_shmseg = 1024
    set shmsys:shminfo_shmmni = 1024
    set semsys:seminfo_semaem = 16384
    set semsys:seminfo_semmni = 1024                      
    set semsys:seminfo_semmap = 1026
    set semsys:seminfo_semmns = 16384
    set semsys:seminfo_semmsl = 100
    set semsys:seminfo_semopm = 100
    set semsys:seminfo_semmnu = 2048
    set semsys:seminfo_semume = 256
    set msgsys:msginfo_msgmap = 1026
    set msgsys:msginfo_msgmax = 4096
    set rlim_fd_cur=1024
    After you alter the /etc/system file and reboot, verify that the settings have taken effect. Issue the following command:

    sysdef -i >sysdef.txt

    This dumps information about the system, including the kernel parameters, to a text file. Review this text file, find each of the kernel parameters that were set, and ensure that the values have taken effect.

    If the values have not taken effect, there might be a problem with the information in the /etc/system file. Review the information logged in /var/adm/messages during boot time, and look for error messages that indicate problems in interpreting the /etc/system file. If errors are present, carefully review the file and ensure that the parameters have been set exactly as stated above.
  • Run pkginfo | grep wemps to show the packages for the IBM® WebSphere® Application Server embedded messaging publish and subscribe feature. Remove these packages using the pkgrm command or the Solaris admintool.

  • Run pkginfo | grep mqm to show packages for the embedded messaging queue manager or the IBM WebSphere MQ product. Do not remove these packages.

To reinstall:
  1. Run pkginfo | grep mqm and pkginfo | grep wemps and remove all packages.

  2. Remove the /wemps and /mqm directories. These directories should be under the /opt directory.

  3. Make sure that /tmp and /opt have sufficient space (df -k).

  4. Install any needed patches. Be sure to check the prereq section for any errors.

  5. Check the mq_install log in the /opt/WebSphere/AppServer/logs directory for any errors.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Solaris
Software version: 5.0.2.8
Software edition:
Reference #: 1152973
IBM Group: Software Group
Modified date: May 21, 2008