Bug 807942 - [AS7] server cannot be started using RHQ
Summary: [AS7] server cannot be started using RHQ
Keywords:
Status: CLOSED DUPLICATE of bug 804102
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-29 08:02 UTC by Libor Zoubek
Modified: 2015-11-02 00:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-02 14:36:53 UTC
Embargoed:

Attachments (Terms of Use)

Description Libor Zoubek 2012-03-29 08:02:23 UTC 
Description of problem:It seems that some recent change causes that starting script path is no longer derived from EAP's home directory


Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: 559098b

How reproducible:always


Steps to Reproduce:
1.inventory EAP6 Beta1 or AS 7.1.1
2.restart using RHQ
  
Actual results:

java.lang.Exception: Start failed with error code 127:
/bin/sh: /home/hudson/jbas-instances/jboss-eap6-standalone1/standalone/bin/standalone.sh: No such file or directory

	at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)


Expected results: 


Additional info:
Server's HOME is detected correctly to /home/hudson/jbas-instances/jboss-eap6-standalone1/

applies for both domain and standalone
Comment 1 Charles Crouch 2012-04-02 14:36:53 UTC 

*** This bug has been marked as a duplicate of bug 804102 ***
Note You need to log in before you can comment on or make changes to this bug.