Bug #62378 for jmx4perl: alternate port for j4p

Fri Oct 22 12:20:51 2010 isaac.hollander [...] seleritycorp.com - Ticket created

Subject:	alternate port for j4p
Date:	Fri, 22 Oct 2010 12:20:18 -0400
To:	bug-jmx4perl [...] rt.cpan.org
From:	Isaac Hollander <isaac.hollander [...] seleritycorp.com>

I'm trying to monitor a Glassfish instance with jmx4perl, but I've already got another container running on port 8080. Is it possible to force j4p.war to run on a different port? Thanks Isaac -- Isaac Hollander Senior Systems Engineer Selerity http://www.seleritycorp.com O: (201) 377 2095

Mon Dec 13 02:26:23 2010 roland [...] cpan.org - Correspondence added

On Fri Oct 22 12:20:51 2010, isaac.hollander@seleritycorp.com wrote:
Show quoted text

> I'm trying to monitor a Glassfish instance with jmx4perl, but I've
> already got another container running on port 8080. Is it possible to
> force j4p.war to run on a different port?

Yes, this is possible by adding another container to the Glassfish server.
I haven't done this yet for Glassfish, but for Tomcat you can find a
howto at http://labs.consol.de/blog/nagios/putting-jmx4perl-on-the-fast-lane-for-tomcat/

Probably I will look for a similar Glassfish setup soon and post it on our blog.
....roland

Mon Dec 13 02:26:24 2010 The RT System itself - Status changed from 'new' to 'open'

Mon Dec 13 02:26:27 2010 roland [...] cpan.org - Taken

Mon Aug 22 05:42:29 2011 roland [...] cpan.org - Correspondence added

Sorry, no blog post yet, but no bug either, so I close this ticket now.

Mon Aug 22 05:42:30 2011 roland [...] cpan.org - Status changed from 'open' to 'resolved'