Server starts up perfectly fine on Solaris -- it launches and apparently drops user back at prompt. Once users exits out of terminal session, however, the server goes down. Steps to repro. 1. telnet (!) to Solaris box. 2. install jon server and/or launch `bin/rhq-server.sh start`. Note that server starts and user is returned to prompt 3. in your web browser, navigate to the $server:7080 URL 4. Log out of session. 5. Reload browser page Expected results Server continues to run Current result: Server goes down. `ps` confirms this: # ps -u root| grep java #
for the record, this does NOT happen on other UNIXs like Linux.
I'm not seeing this. I'm running the latest trunk/HEAD code on a solaris box: $ uname -a SunOS <hostname> 5.9 Generic_118558-25 sun4u sparc SUNW,Sun-Fire-V210 Solaris It started and stopped fine even after logging out and logging back in. Note however, that I used ssh, not telnet (unsure if it makes a difference). This solaris box doesn't allow telnet access so I can't test that explicitly. But since this works on my Solaris (albeit via ssh), then it must be something with either the shell or login that is causing this behavior (or it could be something in the HEAD of trunk fixed something). I think the end result might be that if this happens to people that will have to use "nohup" in their specific command to start the server. Wait until the next QA cycle to see if this is corrected by the code in trunk).
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1356
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Per triage this is moved to ONQA w/ the expectation that it is fixed. If not, please reopen, otherwise close
Verified on jon-2.4.0.GA Used telnet to access the solaris box and followed the repro steps. The server does not go down. It continues to run.