Hi Ladd,
I cannot reproduce the behavior. Even after killing (-15) one of the
agents, the second
still works like a charm with the SNMP4J using Oracle JRE 1.7.0_55 on
Windows 7 SP 1.
Best regards,
Frank
Am 04.06.2014 23:16, schrieb Frank Fock:
Am 04.06.2014 00:54, schrieb Ladd:
Frank Fock <fock@...> writes:
Hi Ladd,
The exception is logged but catched and does not have a side effect
on other
connections (as promised by the Java API). I would suspect a JRE or OS
bug here
(although I cannot exempt an error in SNMP4J at this point).
What JRE version and operating system (incl. version) are you using?
Best regards,
Frank
I appreciate the support Frank! I'm seeing this with:
java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing)
running on:
Windows 7 Professional
Service Pack 1
- Ladd
Hi Ladd,
This seems to be very common combination. I will try to reproduce this...
Best regards,
Frank
_______________________________________________
SNMP4J mailing list
SNMP4J@agentpp.org
https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
SNMP4J@agentpp.org
https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j
