Installation seems OK, but the followings:
00:26:26,113 INFO [org.rhq.enterprise.server.installer.InstallerServiceImpl]
App server has been successfully asked to reload its configuration
00:26:26,155 ERROR [org.jboss.remoting.remote.connection] JBREM000200: Remote
connection failed: java.io.IOException: JBREM000202: Abrupt close on
Remoting connection 38dcf88e to localhost/ 127.0.0.1:6999
00:26:27,253 INFO [org.rhq.enterprise.server.installer.InstallerServiceImpl]
Installing RHQ EAR subsystem
That error is not really an error :) Its to be expected. What is happening is after the
installer successfully sends all the remote commands to the app server to configure it to
run RHQ, it asks the app server to reload its internal components (that is, the app server
internals will do something like a shutdown, reload its config, and start back up again -
thus picking up all changes the installer did.) Since some of the config changes the
installer asked to make are not hot-loaded at runtime, we have to ask the app server to
essentially recycle its internals so the changes are picked up. When this happens, the
remote connection is disconnected and sometimes you get that error message (though I
can't say I remember seeing that in my latest builds, but maybe I just haven't
looked for it).
"rhqctl install" stops everything at the end. It
doesn't really seems to be
an error, so I have restarted it again
Yes, this "feature" of stopping after the install was something that people
explicitly asked for. We were asked to ensure "install" doesn't also do a
"start" - as apparently, some customers don't expect an install to leave the
software running once the install is done. So, now, when you install, the components are
shutdown at the end.
If you want to keep the components started after the install, just pass in
"--start" on the command line when doing the install - e.g. "rhqctl install
--start".