.... I believe mission control is payware. On 13 May 2016 8:35 p.m., "Simone Bordet" <[email protected]> wrote:
> Hi, > > On Fri, May 13, 2016 at 9:43 AM, JingYuan Chen <[email protected]> wrote: > > It is simple and flexible to configure. > > > > I use it to create two instances with different initial parameters. One > is > > Production and the other is Sandbox. Sandbox is not only for test purpose > > but also dealing with background jobs. Both of them connect to the same > > database. Jetty helps me to achieve that easily. I just created 2 > > sub-directories for different instance. It is very convenient. > > > > However, there is one thing that I haven't achieved. My JMX is enabled > but I > > can not connect it with Jconsole. > > Don't use JConsole, you can use Java Mission Control (JMC) that is now > shipped with the JDK, it's a much more powerful tool. > > To be able to connect with JMC (or JConsole) to a remote Jetty server, > you need to enable the "jmx-remote" module in the Jetty server. > That will allow you to connect from remote. > > -- > Simone Bordet > ---- > http://cometd.org > http://webtide.com > Developer advice, training, services and support > from the Jetty & CometD experts. > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
