OK. I'll do this tomorrow. D.
On Wed, Nov 18, 2009 at 9:02 PM, Andy the destroyer <[email protected]> wrote: > We just need to remove the following lines ( 25-29 ) in > > org.apache.esme.lib.ESMEStatsMBean.scala > > def apply(packageName: String, mbeanServer: jmx.MBeanServer): Unit = { > mbeanServer.registerMBean(new ESMEStatsMBean(), new > jmx.ObjectName(packageName + ":type=Stats")) > > 25-> val adaptor = new HtmlAdaptorServer > 26-> adaptor.setPort(9092) > 27-> val adaptorName = new > jmx.ObjectName("StatsAgent:name=htmlAdaptor,port=9092") > 28-> mbeanServer.registerMBean(adaptor, adaptorName) > 29-> adaptor.start > > } > > also remove the import > > 6 -> import com.sun.jdmk.comm._ > > and remove the maven dependency > > -Andy > > On Wed, Nov 18, 2009 at 11:52 AM, Richard Hirsch <[email protected]>wrote: > >> OK. Markus is right. I just talked to someone else and he had same problem. >> >> @Andy - can we remove the openDMK reference or will the build break without >> it? >> >> D. >> >> On Wed, Nov 18, 2009 at 7:45 PM, Richard Hirsch <[email protected]> >> wrote: >> > @Andy: >> > >> > Sounds great. >> > >> > I can't wait to combine your JMX code with Markus' performance tests. >> > Then we will definitely get some interesting results. >> > >> > Just ping me when you are ready and I'll integrate everything. >> > >> > D. >> > >> > On Wed, Nov 18, 2009 at 7:42 PM, Andy the destroyer >> > <[email protected]> wrote: >> >> We actually don't need openDMK anymore. It was used as an HTTP agent for >> >> accessing the Stats mBean. However, the Stax environment won't allow the >> >> agent to bind to any ports so it won't work in Stax which is where most >> of >> >> the testing is done. >> >> >> >> I have written a JMX REST api to replace it. I haven't uploaded it to >> JIRA >> >> yet because I still need to find the time to finish the piece that >> allows >> >> you to invoke operations on MBeans, but the reading of attributes works. >> >> >> >> I think it is a good idea to leave agents out of the codebase and leave >> it >> >> up to whoever is deploying esme to write their own instrumentation >> agents >> >> and launch them through the java -javaagent argument. >> >> >> >> -Andy >> >> >> >> On Wed, Nov 18, 2009 at 9:41 AM, Ethan Jewett <[email protected]> >> wrote: >> >> >> >>> I could swear that this exact same thing happened to me, where it was >> >>> only the one thing that failed to download. If you send the actual >> >>> Maven error, I'll recognize it. In any case, maybe it was actually the >> >>> server, not the firewall... >> >>> >> >>> Ethan >> >>> >> >>> On Wed, Nov 18, 2009 at 12:01 PM, Markus Kohler < >> [email protected]> >> >>> wrote: >> >>> > No difference. >> >>> > I suspect the file is just not on the server anymore. I guess it >> should >> >>> be >> >>> > on maven.tigase.org. >> >>> > >> >>> > On Wed, Nov 18, 2009 at 5:52 PM, Markus Kohler < >> [email protected] >> >>> >wrote: >> >>> > >> >>> >> Yes, it does not find the jar file. >> >>> >> Yes I'm behind an http proxy. But downloading everything else >> worked. >> >>> >> I will try without the proxy server. >> >>> >> >> >>> >> Regards, >> >>> >> Markus >> >>> >> >> >>> >> >> >>> >> On Wed, Nov 18, 2009 at 5:47 PM, Ethan Jewett <[email protected]> >> >>> wrote: >> >>> >> >> >>> >>> Hi Markus, >> >>> >>> >> >>> >>> The build works fine for me (mvn clean test). I think I had an >> issue >> >>> >>> with OpenDMK once when I was behind a firewall. Is it possible that >> >>> >>> Maven is just failing to download the artifact? >> >>> >>> >> >>> >>> Ethan >> >>> >>> >> >>> >>> On Wed, Nov 18, 2009 at 11:25 AM, Markus Kohler < >> >>> [email protected]> >> >>> >>> wrote: >> >>> >>> > Hudson build run through, but it doesn't seem to do anything >> useful. >> >>> >>> > - downloaded jetty util jar files several times. >> >>> >>> > - 0 tests executed because of exception, but no failure shown in >> the >> >>> >>> > overview >> >>> >>> > >> >>> >>> > Can you force a clean build, maybe? >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > Regards, >> >>> >>> > Markus >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > On Wed, Nov 18, 2009 at 1:36 PM, Richard Hirsch < >> >>> [email protected] >> >>> >>> >wrote: >> >>> >>> > >> >>> >>> >> trying a build on hudson to see if the problem occurs there as >> well >> >>> >>> >> >> >>> >>> >> On Wed, Nov 18, 2009 at 1:05 PM, Markus Kohler < >> >>> >>> [email protected]> >> >>> >>> >> wrote: >> >>> >>> >> > Hi all, >> >>> >>> >> > Anyone has the same problem? >> >>> >>> >> > >> >>> >>> >> > Regards, >> >>> >>> >> > Markus >> >>> >>> >> > >> >>> >>> >> >> >>> >>> > >> >>> >>> >> >>> >> >> >>> >> >> >>> > >> >>> >> >> >> > >> >
