Troubleshooting Common Agent Container Problems in the Solaris OS

This section addresses problems that you might encounter with the Common Agent Container shared component. Starting with the Solaris Express 4/06 release, the Common Agent Container Java program is included in the Solaris OS. The program implements a container for Java management applications. Typically, the Common Agent Container is not visible. The following are potential problems:

Port Number Conflicts

The Common Agent Container, version 2.0, inside the Java Enterprise Server (Java ES), occupies the following port numbers by default:

  • JMX port (TCP) = 11162

  • SNMPAdaptor port (UDP) = 11161

  • SNMPAdaptor port for traps (UDP) = 11162

  • Commandstream Adaptor port (TCP) = 11163

  • RMI connector port (TCP) = 11164

Note

If you are troubleshooting an installation of Sun Cluster, the port assignments are different. For more information, see the Sun Java Enterprise System 2006Q3 Installation Guide for UNIX at .

If your installation already reserves any of these port numbers, change the port numbers that are occupied by the Common Agent Container, as described in the following procedure.

How to Check Port Numbering

This procedure shows you how to verify the Solaris port.

  1. Become superuser or assume an equivalent role.

    Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services .

  2. Stop the Common Agent Container management daemon.

    # //usr/sbin/cacaoadm stop
    
  3. Change the port number using the following syntax:

    # /usr/sbin/cacaoadm set-param param=value
    
    

    For example, to change the port occupied by the SNMPAdaptor from the default of 11161 to 11165, type:

    # /usr/sbin/cacaoadm set-param snmp-adaptor-port=11165 
  4. Restart the Common Agent Container management daemon.

    # /usr/sbin/cacaoadm start
    

Compromised Security for Superuser Password

It might be necessary to regenerate security keys on a host that is running the Java ES. For example, if there is a risk that a superuser password has been exposed or compromised, you should regenerate the security keys. The keys that are used by the Common Agent Container services are stored in /etc/opt/SUNWcacao/security directory. The following task shows you how to generate security keys for the Solaris OS.

How to Generate Security Keys for the Solaris OS

  1. Become superuser or assume an equivalent role.

    Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services .

  2. Stop the Common Agent Container management daemon.

    # /opt/SUNWcacao/bin/cacaoadm stop
    
  3. Regenerate the security keys.

    # /opt/SUNWcacao/bin/cacaoadm create-keys --force
    
  4. Restart the Common Agent Container management daemon.

    # /opt/SUNWcacao/bin/cacaoadm start
    

    Note

    For the Sun Cluster software, you must propagate this change across all nodes in the cluster. For further instructions, see the Sun Java Enterprise System 2006Q3 Installation Guide for UNIX at .