When I ran it the second time, it succeeded. However, now when I try to access the RQH Web Console using the following URL, the page is blank (for a half of second it says that the RHQ is initializing and then goes blank):

http://<rhq-host>:7080

At the same time, there lots of errors in the server log, i.e:

12:49:57,070 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-remoting-servlet-invoker].[ServerInvokerServlet]] (http-/0.0.0.0:7080-1) JBWEB000235: Allocate exception for servlet ServerInvokerServlet: javax.servlet.ServletException: Could not find the remoting servlet invoker: jboss.remoting:service=invoker,rhq.communications.connector.rhqtype=server,* - need to wait for remoting to be initialized later

Hi Stefan,

Thanks for your response and clarifications.

Regarding the Oracle JDBC driver issue, it has been explained well here:

http://www.usn-it.de/index.php/2009/02/20/oracle-11g-jdbc-driver-hangs-blocked-by-devrandom-entropy-pool-empty/

Basically, by default JDBC driver uses a blocking device (/dev/random) as a source of random number generator. However, on a server system, since there is not enough entropy - unless someone installs a microphone inside a chasis , the device will block so will the JDBC driver, causing timeouts or connection reset errors. Fortunately, there is an easy fix, at the expense of the quality of random data when using a non-blocking device (/dev/urandom):

-Djava.security.egd=file:///dev/urandom

Regarding my original issue, I will provide more details shortly.

Thanks,

Lukasz

Hi Stefan,

I ended up reinstalling everything as documented all the steps along the way - and it worked this time! Well, at least I can access RHQ web Console. I hope below instructions can be of use to others trying to setup RHQ with Oracle database.

Thanks,

Lukasz

Preparation:

1. Extracted RHQ archive to <RHQ-HOME>

2. Edited database (Oracle) and SMTP settings under <RHQ-HOME>/bin/rhq-server.properties

3. Edited rhq.agent.basedir under <RHQ-HOME>/bin/rhqctl.properties to point to <RHQ-HOME>/rhq-agent directory

4. Set RHQ_CONTROL_ADDITIONAL_JAVA_OPTS variable in <RHQ-HOME>/bin/rhqctl

RHQ_CONTROL_ADDITIONAL_JAVA_OPTS="-Djava.security.egd=file:///dev/urandom"

5. Added the following JVM argument to <RHQ-HOME>/bin/wrapper/rhq-server-wrapper.conf

wrapper.java.additional.23=-Djava.security.egd=file:///dev/urandom

6. Added the following JVM argument to <RHQ-HOME>/bin/wrapper/rhq-storage-wrapper.conf

wrapper.java.additional.18=-Djava.security.egd=file:///dev/urandom

7. Installed Oracle JDBC driver jar under <RHQ-HOME>/modules/org/rhq/oracle/main

8. Edited JDBC driver's path in <RHQ-HOME>/modules/org/rhq/oracle/main/modules.xml

Installation:

$ cd <RHQ-HOME>/bin

$ ./rhqctl install --storage-data-root-dir <RHQ-HOME>/data

All went fine except below error was reported (not sure if it is harmless or not):

22:05:22,961 ERROR [org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: JBREM000202: Abrupt close on Remoting connection 6b19ae3e to localhost.localdomain/127.0.0.1:6999

$ ./rhqctl status

22:09:28,944 INFO  [org.jboss.modules] JBoss Modules version 1.2.0.CR1

RHQ Storage Node               (pid 10400  ) IS running

RHQ Server                     (pid 10779  ) IS running

JBossAS Java VM child process  (pid 10779  ) IS running

RHQ Agent                      (pid 12016  ) IS running

Notes:

- there are repeated XA recovery errors in the <RHQ-HOME>/logs/server.log (these could be related to the fact that I reused the database schema from previous installation attempts):

22:12:04,079 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException

        at oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:709)

        at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:358)

        at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.recover(XAResourceWrapperImpl.java:165)

        at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryEnd(XARecoveryModule.java:683) [jbossjts-jacorb-4.17.3.Final.jar:4.17.3.Final (revision: 74343b48951c0fdab92316e56bfcaed605d620f6)]

        at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:490) [jbossjts-jacorb-4.17.3.Final.jar:4.17.3.Final (revision: 74343b48951c0fdab92316e56bfcaed605d620f6)]

        at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:378) [jbossjts-jacorb-4.17.3.Final.jar:4.17.3.Final (revision: 74343b48951c0fdab92316e56bfcaed605d620f6)]

        at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:166) [jbossjts-jacorb-4.17.3.Final.jar:4.17.3.Final (revision: 74343b48951c0fdab92316e56bfcaed605d620f6)]

        at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-jacorb-4.17.3.Final.jar:4.17.3.Final (revision: 74343b48951c0fdab92316e56bfcaed605d620f6)]

        at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.3.Final.jar:4.17.3.Final (revision: 74343b48951c0fdab92316e56bfcaed605d620f6)]

- no errors in <RHQ-HOME>/logs/rhq-storage.log

- no errors in <RHQ-HOME>/rhq-agent/logs/agent.log (except initial problems regarding missing plugins, before these were automatically downloaded)