Yes frank, the object itself is not changed. What kind of problems do you think in JDK or in RHEL ? I searched in the net with this error and couldnt get anything of this sort ?
We use java 1.7.0_40 version and RHEL 5.10 Are you aware of any similar issues ? Regards Prathib Kumar. On Thu, Jan 16, 2014 at 2:34 AM, Frank Fock <[email protected]> wrote: > Hi, > > If the target object is not changed itself then it will be OK. > > Best regards, > Frank > > Am 15.01.2014 22:01, schrieb Prathib Kumar: > > Hi Frank, > > Thanks for your response. I corrected the alias name. > > We use target object as the class member variable in our code, after we > pass the target object to the snmp4j, it might be possible that targetObj > might be re-initialized with the different target object for a different > device. > > I think that shouldnt be a problem rite ? > > Regards > Prathib Kumar. > > > On Thu, Jan 16, 2014 at 1:28 AM, Frank Fock <[email protected]> wrote: > >> Hi Prathib, >> >> First of all, the email address of the SNMP4J mailing list is >> [email protected] >> >> This might be an issue with your JDK or operating system, if >> you do not modify the Target object while a request is being >> processed by SNMP4J. >> >> Best regards, >> Frank >> >> >> >>> We are using SNMP4J 1.11.2 in our product and our product runs on RHEL >>> 5.10. >>> >>> So far, we have supported only IPV4 and now we started supporting IPV6 >>> and we are getting the following exception only when we query the IPV6 and >>> IPV4 parallely. >>> >>> If we have only IPV4 devices in our product, then we dont see this >>> issue. If we have mix of both IPV4 and IPV6, then we hit upon this issue. >>> >>> >>> Hence I went thru the SNMP4J source code and got a question that >>> whether sendPDU() in Snmp is thread safe ? I read the FAQ and found that it >>> says its thread safe. >>> >>> Since ours is multithreaded environment, any idea what could have >>> caused this issue ? >>> >>> *Exception Trace :* >>> Caused by: org.snmp4j.MessageException:* Address family not supported >>> by protocol* >>> at >>> org.snmp4j.MessageDispatcherImpl.sendPdu(MessageDispatcherImpl.java:494) >>> at >>> org.snmp4j.util.MultiThreadedMessageDispatcher.sendPdu(MultiThreadedMessageDispatcher.java:146) >>> at org.snmp4j.Snmp.sendMessage(Snmp.java:1082) >>> at org.snmp4j.Snmp.send(Snmp.java:971) >>> at org.snmp4j.Snmp.send(Snmp.java:955) >>> at >>> com.cisco.xmp.snmp.sessionmgr.async.ResponseFuture.internalSend(ResponseFuture.java:103) >>> at >>> com.cisco.xmp.snmp.sessionmgr.async.ResponseFuture.start(ResponseFuture.java:140) >>> >>> Please let me know if you need any other info. >>> >>> >>> Regards >>> Prathib Kumar. >>> >> >> >> >> -- >> --- >> AGENT++ >> Maximilian-Kolbe-Str. 10 >> 73257 Koengen, Germanyhttps://agentpp.com >> Phone: +49 7024 8688230 >> Fax: +49 7024 8688231 >> >> > > -- > --- > AGENT++ > Maximilian-Kolbe-Str. 10 > 73257 Koengen, Germanyhttps://agentpp.com > Phone: +49 7024 8688230 > Fax: +49 7024 8688231 > > _______________________________________________ SNMP4J mailing list [email protected] https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j
