Re: [javagroups-users] [ERROR] NAKACK.handleXmitReq()
Brought to you by:
belaban
From: Bela B. <be...@ya...> - 2006-09-15 06:06:19
|
Sorry, I get exactly the *same* results: forgot to enable bundling. Without bundling, I get ca 19000 msgs/sec, with bundling I get 90000 msgs/sec. I attached the config I used Gianluca Puggelli wrote: > Hi all, > > I tried to run the perf_test in three 2-way Solaris 10/x86 machines > but I got a lot of error messages > like the following: > > 806928 [ERROR] NAKACK.handleXmitReq(): - (requester=10.50.4.37:7800, > local_addr=10.50.4.38:7800) > message 10.50.4.38:7800::2702582 not found in sent msgs. > Sent messages: [2706596 - 2742395] (35800) > > Can someone explain to me how to avoid them. > > Here there are the HW and configuration details: > > JVM: > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) > Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode) > > JGroups version: 2.4CR2 > > Hw: Three 2-way x86 with Solaris 10 > - vezer 10.50.3.37 > - SunOS vezer 5.10 Generic i86pc i386 i86pc > - Status of virtual processor 0 as of: 09/14/2006 > 09:53:05 on-line since 08/21/2006 22:24:20. > The i386 processor operates at 2389 MHz, and has an > i387 compatible floating point processor. > -Status of virtual processor 1 as of: 09/14/2006 > 09:53:05 on-line since 08/21/2006 22:24:23. > The i386 processor operates at 2389 MHz, and has an > i387 compatible floating point processor. > > oks 10.50.3.38: > - SunOS oks 5.10 Generic i86pc i386 i86pc > - Status of virtual processor 0 as of: 09/14/2006 > 09:51:38 on-line since 08/21/2006 22:27:00. > The i386 processor operates at 1600 MHz, and has an > i387 compatible floating point processor. > - Status of virtual processor 1 as of: 09/14/2006 > 09:51:38 on-line since 08/21/2006 22:27:03. > The i386 processor operates at 1600 MHz, and has an > i387 compatible floating point processor. > > oster 10.50.3.40: > - SunOS oster 5.10 Generic i86pc i386 i86pc > - Status of virtual processor 0 as of: 09/14/2006 > 09:55:14 on-line since 08/21/2006 22:27:18. > The i386 processor operates at 2391 MHz, and has an > i387 compatible floating point processor. > - Status of virtual processor 1 as of: 09/14/2006 > 09:55:14 on-line since 08/21/2006 22:27:21. > The i386 processor operates at 2391 MHz, and has an > i387 compatible floating point processor. > > Stack used: tcp_nio > > JVM parameters: > -Xms512M > -Xmx512M > -XX:+PrintClassHistogram > -XX:MaxPermSize=364M > -XX:PermSize=364M > -XX:MaxNewSize=348m > -XX:NewSize=348m > -XX:SurvivorRatio=128 > -XX:+UseParNewGC > -XX:+UseConcMarkSweepGC > -XX:MaxTenuringThreshold=0 > -XX:CMSInitiatingOccupancyFraction=60 > -XX:+DisableExplicitGC > -verbose:gc > -Xloggc:./gc.log > -XX:+PrintGCTimeStamps > -XX:+PrintGCDetails > -XX:+PrintTenuringDistribution > -XX:+PrintGCApplicationConcurrentTime > -XX:+PrintGCApplicationStoppedTime > -server > -Dlog4j.configuration=config/log4j.properties > -Dresolve.dns=false > -Dbind.address=<bind_addr> > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.port=11138 > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > > perf_test config file: > transport=org.jgroups.tests.perf.transports.JGroupsTransport > num_msgs=2000000000 > msg_size=256 > num_members=3 > num_senders=3 > log_interval=1000000 > processing_delay=0 > dump_transport_stats=false > jmx=false > start_port=7800 > > thanks and regards > gianluca > > -- Bela Ban Lead JGroups / Manager JBoss Clustering Group JBoss - a division of Red Hat |