Re: [opennms-devel] OpenNMS && JBoss 4.2.2

Tilman Kastner <[email protected]>
Newsgroups gmane.network.opennms.bugs
Message-ID <200806062204.55515.kastner__36880.964987404$1212782801$gmane$org@devicen.de>
Mark,

I ran into this too. For me, it was a configuration issue. I had to add 
the "collection" parameter in collectd-configuration.xml

See:
http://bugzilla.opennms.org/show_bug.cgi?id=2446

Jonathan added a page at the wiki, too:
http://www.opennms.org/index.php/JMX_Collector

Am Freitag, 6. Juni 2008 schrieb Mark Spenser:
> Hi all, I'm trying to make OpenNMS and JBoss friends and spent on this task
> some days already.
>
> Generally, to make capsd working with JBoss 4.2.2, you need to update jboss
> libraries, log4j and apply opennms-1.5.91-jboss-capsd.patch
> After that, capabilities check works.
>
> But with JMX data collection, I still can't make a solution. I'm a sysadm,
> not a programmer, so I'm not able to figure out what is wrong.
> With default configuration, I'm getting exceptions like:
> org.opennms.netmgt.rrd.RrdException: An error occured creating
> rrdfile /usr/local/OpenNMS/share/rrd/snmp/1/jsr160/CurThreadCpuTime.jrb:
> org.jrobin.core.RrdException: Invalid heartbeat, must be positive: -2
>         at org.opennms.netmgt.rrd.RrdUtils.createRRD(RrdUtils.java:198)
> (http://paste.lisp.org/display/61779)
>
> I tried to hardcode that heartbeat (opennms-1.5.91-jboss-jrobin.patch), but
> now it is NPE in another part:
>
> 2008-06-06 12:53:52,497 ERROR [CollectdScheduler-50 Pool-fiber0] RrdUtils:
> createRRD: An error occured creating
> rrdfile /opt/opennms/share/rrd/jmx/2/jboss/
> TotalMemory.jrb: java.lang.NullPointerException
> java.lang.NullPointerException
>         at
> org.opennms.netmgt.rrd.jrobin.JRobinRrdStrategy.createDefinition(JRobinRrdS
>trategy.java:112) at
> org.opennms.netmgt.rrd.QueuingRrdStrategy.createDefinition(QueuingRrdStrate
>gy.java:734) at org.opennms.netmgt.rrd.RrdUtils.createRRD(RrdUtils.java:195)
> at
> org.opennms.netmgt.collectd.PersistOperationBuilder.commit(PersistOperation
>Builder.java:113) at
> org.opennms.netmgt.collectd.BasePersister.commitBuilder(BasePersister.java:
>72) at
> org.opennms.netmgt.collectd.OneToOnePersister.completeAttribute(OneToOnePer
>sister.java:57) at
> org.opennms.netmgt.collectd.AbstractCollectionAttribute.visit(AbstractColle
>ctionAttribute.java:65) at
> org.opennms.netmgt.collectd.AttributeGroup.visit(AttributeGroup.java:75)
>         at
> org.opennms.netmgt.collectd.AbstractCollectionResource.visit(AbstractCollec
>tionResource.java:103) at
> org.opennms.netmgt.collectd.JMXCollector$JMXCollectionSet.visit(JMXCollecto
>r.java:913) at
> org.opennms.netmgt.collectd.CollectableService.doCollection(CollectableServ
>ice.java:354) at
> org.opennms.netmgt.collectd.CollectableService.run(CollectableService.java:
>296) at
> org.opennms.netmgt.scheduler.LegacyScheduler$1.run(LegacyScheduler.java:292
>) at
> org.opennms.core.concurrent.RunnableConsumerThreadPool$FiberThreadImpl.run(
>RunnableConsumerThreadPool.java:422) at
> java.lang.Thread.run(Thread.java:595)
>
>
> What can I do for JMX parameters collection?



-- 
Tilman Kastner            abian GmbH
Tel.: (05 11) 9 29 99 66  Deisterstrasse 81
Fax:  (05 11) 9 29 99 99  30449 Hannover
Mail: [email protected]  Germany
Registergericht:          Hannover HRB 60127
Geschäftsführer:          Matthias Lange
St.-Nr.:                  25/204/33889

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.