[jmanage-tracker] [ jmanage-Support Requests-1588025 ] Using JManage with CruiseControl on Linux

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Support Requests item #1588025, was opened at 2006-10-31 10:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=659058&aid=1588025&group_id=111374

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: John Brugge (jbrugge)
Assigned to: Nobody/Anonymous (nobody)
Summary: Using JManage with CruiseControl on Linux

Initial Comment:
I have Cruisecontrol v2.5 running on my Linux
workstation (Fedora Core 5), and am trying to use
JManage 1.0.4 as an alternative to the built-in JMX
console that CC provides.

I am running JDK 1.5, and have been able to
successfully start up JManage, and can navigate to all
screens. However I have not been able to get JManage to
show any managed beans for CC.

CC is started with the option "-rmiport 8099", and I am
able to connect to it from another application that
uses RMI (cc-config).

I have tried adding CC as a JSR160 application, with
the following (using instructions from the JManage doc
page on MX4J applications):
     URL = service:jmx:rmi://localhost/jndi/jrmp
     user = blank
     password = blank
     java.naming.factory.initial =
com.sun.jndi.rmi.registry.RegistryContextFactory
     java.naming.provider.url = rmi://localhost:8099

I save the settings, and when I click it in the list of
applications, the page comes up saying "There are no
configured objects."

I have read Jerome Lacoste's article on setting up
JManage and CC, and the settings look the same, albeit
with some updates to JManage to make the
java.naming.factory.initial setting available in the
webapp interface.

I do not see any information in the console log or in
Cruisecontrol's log indicating what might be wrong. I'm
wondering if there are other diagnostics I could look
at, or other suggestions for ways to troubleshoot this.

Thanks,
John

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=659058&aid=1588025&group_id=111374