AW: [JBoss-user] Benchmarking Messaging in JBoss
Hi Peter, we posted the results yesterday (see posting by [EMAIL PROTECTED], Subject : Benchmark results for MDBs). What benchmark are you referring to (progress ?), and where can I find infos about it ? Best regards, Jubin Zawar -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von [EMAIL PROTECTED] Gesendet: Dienstag, 15. Mai 2001 22:02 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-user] Benchmarking Messaging in JBoss On 15 Maj, [EMAIL PROTECTED] wrote: hi list ! we are going to benchmark jboss for messaging. Great, and you will post the results I guess! Have you looked into the little benchmarking application done by progress (soniqmq, maybe you could use something from there)? //Peter scenario is the following : PostingClient thread posts messages to Topic 1, with a key as identifier and some junk data variable in size (Testing Parameter 1). Messagedriven Bean 1 listens on topic 1, writes the current time to lastTimeReceivedMDB1 in the message, increases the howManyTimesSent counter and posts it to topic 2. Messagedriven Bean 2 listens on topic 2, writes the current time to lastTimeReceivedMDB2 in the message and posts it to topic 1. MonitoringClient thread listens on topic 1. MDB1, also listening on topic 1, will recapture the message and then increase counter, write time, and post it to topic 2, etc. etc. PostingClient will continuously bring new messages to the system. MonitoringClient has facilities for identifying the messages in topic 1 and will care about : - time difference between MDB1 and MDB2 and other parameters. We are probably going to benchmark weblogic's newest app server version as well. Best regards, jubin ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user -- Peter Antman Technology in Media, Box 34105 100 26 Stockholm Systems ArchitectWWW: http://www.tim.se Email: [EMAIL PROTECTED]WWW: http://www.backsource.org Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Benchmarking Messaging in JBoss
hi list ! we are going to benchmark jboss for messaging. scenario is the following : PostingClient thread posts messages to Topic 1, with a key as identifier and some junk data variable in size (Testing Parameter 1). Messagedriven Bean 1 listens on topic 1, writes the current time to lastTimeReceivedMDB1 in the message, increases the howManyTimesSent counter and posts it to topic 2. Messagedriven Bean 2 listens on topic 2, writes the current time to lastTimeReceivedMDB2 in the message and posts it to topic 1. MonitoringClient thread listens on topic 1. MDB1, also listening on topic 1, will recapture the message and then increase counter, write time, and post it to topic 2, etc. etc. PostingClient will continuously bring new messages to the system. MonitoringClient has facilities for identifying the messages in topic 1 and will care about : - time difference between MDB1 and MDB2 and other parameters. We are probably going to benchmark weblogic's newest app server version as well. Best regards, jubin ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Benchmarking Messaging in JBoss
On 15 Maj, [EMAIL PROTECTED] wrote: hi list ! we are going to benchmark jboss for messaging. Great, and you will post the results I guess! Have you looked into the little benchmarking application done by progress (soniqmq, maybe you could use something from there)? //Peter scenario is the following : PostingClient thread posts messages to Topic 1, with a key as identifier and some junk data variable in size (Testing Parameter 1). Messagedriven Bean 1 listens on topic 1, writes the current time to lastTimeReceivedMDB1 in the message, increases the howManyTimesSent counter and posts it to topic 2. Messagedriven Bean 2 listens on topic 2, writes the current time to lastTimeReceivedMDB2 in the message and posts it to topic 1. MonitoringClient thread listens on topic 1. MDB1, also listening on topic 1, will recapture the message and then increase counter, write time, and post it to topic 2, etc. etc. PostingClient will continuously bring new messages to the system. MonitoringClient has facilities for identifying the messages in topic 1 and will care about : - time difference between MDB1 and MDB2 and other parameters. We are probably going to benchmark weblogic's newest app server version as well. Best regards, jubin ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user -- Peter Antman Technology in Media, Box 34105 100 26 Stockholm Systems ArchitectWWW: http://www.tim.se Email: [EMAIL PROTECTED]WWW: http://www.backsource.org Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
