[jira] Updated: (DAYTRADER-21) Indicate that MDB primitives are not intended for performance testing
[ http://issues.apache.org/jira/browse/DAYTRADER-21?page=all ] Christopher James Blythe updated DAYTRADER-21: -- Priority: Minor (was: Major) > Indicate that MDB primitives are not intended for performance testing > - > > Key: DAYTRADER-21 > URL: http://issues.apache.org/jira/browse/DAYTRADER-21 > Project: DayTrader > Issue Type: Improvement > Components: Web Tier >Affects Versions: 1.2 >Reporter: Christopher James Blythe >Priority: Minor > Attachments: daytrader-21.patch > > > The MDB primitives, PingServlet2MDBQueue and PingServlet2MDBTopic, are not > suited for testing MDB performance. The problem stems from a difference in > how fast messages can be placed on the queue/topic by the JMS client versus > how fast the MDBs can process them. Generally, the messages can be created > much faster than they can be consumed. This in turn leads to problems when > the maximum queue/topic sizes are reached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DAYTRADER-21) Indicate that MDB primitives are not intended for performance testing
[ http://issues.apache.org/jira/browse/DAYTRADER-21?page=all ] Christopher James Blythe updated DAYTRADER-21: -- Attachment: daytrader-21.patch This patch adds statements to the primitive list and individual primitives to indicate that they are not intended for performance testing > Indicate that MDB primitives are not intended for performance testing > - > > Key: DAYTRADER-21 > URL: http://issues.apache.org/jira/browse/DAYTRADER-21 > Project: DayTrader > Issue Type: Improvement > Components: Web Tier >Affects Versions: 1.2 >Reporter: Christopher James Blythe > Attachments: daytrader-21.patch > > > The MDB primitives, PingServlet2MDBQueue and PingServlet2MDBTopic, are not > suited for testing MDB performance. The problem stems from a difference in > how fast messages can be placed on the queue/topic by the JMS client versus > how fast the MDBs can process them. Generally, the messages can be created > much faster than they can be consumed. This in turn leads to problems when > the maximum queue/topic sizes are reached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
