Appendix B: Frequently Asked Questions

JBoss Enterprise Application Server

Q: What do I do if I receive the following error message?

‘java.lang.OutOfMemoryError: PermGen space’

A: PermGen space represents the Permanent Generation space used by JVM to store classes and metadata. Increasing the MaxPermSize parameter when starting the JBoss Enterprise Application Server should resolve the problem

For example, to set this parameter to 128MB, add the option ‘-XX:MaxPermSize=128m’ to the ‘JAVA_OPTS=’ line in the $JBOSS_HOME/bin/run.conf file.

where:

Q: How do I open specific ports without disabling the firewall?

A: RHEL by default prevents external systems from connecting to any of the reserved port numbers (0 to 1023). To open a specific port, update the firewall rules by opening the specified port number by using the following commands:

For an ipchains-based firewall:

# ipchains -I input -s 0/0 -d 0/0 <port number> -p tcp \

-y -j ACCEPT

# service ipchains save

# service ipchains restart

Example:

# ipchains -I input -s 0/0 -d 0/0 389 -p tcp -y -j ACCEPT
# service ipchains save
# service ipchains restart

For an iptables-based firewall:

# iptables -I INPUT -s 0/0 -d 0/0 -p tcp \

--dport <port number> --syn -j ACCEPT

# service iptables save

# service iptables restart

Example:

# iptables -I INPUT -s 0/0 -d 0/0 -p tcp \
 --dport 389 --syn -j ACCEPT 
# service iptables save 
# service iptables restart 

Q: How do I disable firewall settings?

A: By default, RHEL has a firewall enabled. This prevents external systems from accessing ports below 1024. Run the following command to open the firewall configuration dialog and disable the firewall:

# system-config-securitylevel

	CAUTION: Disabling the firewall is not advisable. If any external applications need to communicate with the system, open only those specific ports for outside access rather than fully disabling the firewall. For details on how to open a specific port for external programs, see the following question and answers.

Figure 34 Firewall Configuration

HP OpenView Operations

Q: What should I do if I receive one of the following error messages:

A: You are having issues with nodeId, to correct these issues, perform the following steps:

Q: When I try to start or shutdown the JBoss Server or when I try to start or stop the Log Monitor for JBoss Server Logs in the OVO console, I encounter the following error message

sudo: sorry, you must have a tty to run sudo.

What do I do?

A: On the OVO agent machine, edit the /etc/sudoers file and comment out the line as follows:

#Defaults requiretty

Q: What to do if I want to use a different JBoss server configuration and monitor the corresponding log files?

A: On the OVO agent machine, edit the /var/opt/OV/bin/instrumentation/APSSPI/conf/apsspi_jboss.cfg file and add the following line:

configuration=<jboss_server_configuration_name>

The server configuration name can be all, defaults, minimal, etc.

Systems Insight Manager Agents

Q: What can I do if the following error messages appeared while installing SIM?

Warning: group hpsmh does not exist – using root 
…
Chown: ’root:hpsmh’:invalid group
…

A: This error message occurred because the groupid is currently being used by another application. In this environment, the application is the OpenView Operation (OVO) Agent.

To correct this error, perform the following steps:

Hibernate

Q: When deploying a Hibernate Web application on the JBoss Enterprise Application Server, what do I do if I receive the following handler exception?

‘log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by…..’

A: Edit the $JBOSS_HOME/erver/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml file and change the following section:

	NOTE: Alternatively, you can also delete the files commons-logging.jar and log4j.jar from your application library and then redeploy the application.