If you start multiple servers on the same machine using the -b switch, the snmp-adaptor service will have a port conflict:

java.net.BindException: Address already in use: Cannot bind
at java.net.PlainDatagramSocketImpl.bind(Native Method)
at java.net.DatagramSocket.bind(DatagramSocket.java:368)
at java.net.DatagramSocket.<init>(DatagramSocket.java:210)
at java.net.DatagramSocket.<init>(DatagramSocket.java:261)
at org.opennms.protocols.snmp.SnmpPortal.<init>(SnmpPortal.java:256)
at org.opennms.protocols.snmp.SnmpPortal.<init>(SnmpPortal.java:204)
at org.opennms.protocols.snmp.SnmpAgentSession.<init>(SnmpAgentSession.java:357)
at org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService.startAgent(SnmpAgentService.java:577)

The JBoss code is handling the jboss.bind.address properly; the problem is in the org.opennms code. SnmpAgentSession does not pass the address through to SnmpPortal, so SnmpPortal opens a port bound to all addresses.

This definitely sucks, as it prevents a very effective demonstration of the ease of JBoss clustering – unzip JBoss, make a copy of "all", open two windows and run two JBoss instances with the -b switch.

Dimitris, I assigned this over to you because your name was in the SnmpAgentService author tags