Bug 607932 - Autodiscovery: fails to detect multiple instances of JBossAS
Summary: Autodiscovery: fails to detect multiple instances of JBossAS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Communications Subsystem
Version: 3.0.0
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: JON24 602538
TreeView+ depends on / blocked
 
Reported: 2010-06-25 08:34 UTC by Sudhir D
Modified: 2010-08-12 16:47 UTC (History)
1 user (show)

Fixed In Version: 2.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-12 16:47:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Sudhir D 2010-06-25 08:34:48 UTC
Description of problem:
Autodiscovery fail to detect multiple instances of JBossAS running on the single server.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Configure Agent on a Linux box. Ensure that the JBossAS5 plugin is present.
2. Install JBoss AS 5.1 on the agent box and check the dashboard to see if this is autodiscovered.
3. Install JBoss AS 5.0 on the same agent box on a different port. Check the autodiscovery queue for this newly installed JBoss AS 5.0. 
  
Actual results:
The second instance is not auto discovered.

Expected results:
Second instance should be auto disovered.

Additional info:
Manual addition of JBoss get added however, the service does not report up. When I try to start, I get the java home exception, where as Java Home is mentioned in the Connections properties.

java.lang.IllegalStateException: The 'javaHome' connection property must be set in order to start the application server or to stop it via script.
        at org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.initProcessExecution(ApplicationServerOperationsDelegate.java:284)
        at org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.start(ApplicationServerOperationsDelegate.java:230)
        at org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.invoke(ApplicationServerOperationsDelegate.java:142)
        at org.rhq.plugins.jbossas5.ApplicationServerComponent.invokeOperation(ApplicationServerComponent.java:495)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        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)

Comment 1 Rajan Timaniya 2010-07-01 11:58:47 UTC
Verified on JON 2.4 GA_QA (tag-jon-release build #46)
Revision: 10759

Steps
1) Configured Agent on a Linux box. Ensure that the JBossAS5 plugin is present.
2) Installed JBoss AS 5.1 on the agent box.
3. Installed JBoss AS 5.0 on the same agent box on a different port.

JBossAS 5.0 and JBossAS 5.1 both are auto discovered.

Comment 2 Corey Welton 2010-08-12 16:47:32 UTC
Mass-closure of verified bugs against JON.


Note You need to log in before you can comment on or make changes to this bug.