https://issues.apache.org/bugzilla/show_bug.cgi?id=52044
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |[email protected] | |om --- Comment #3 from Philippe Mouawad <[email protected]> 2011-10-18 06:43:37 UTC --- (In reply to comment #0) > Created attachment 27800 [details] > screenshot with strange error > > r1183374 > > See attached TP. > > Run AMQ web admin monitor and open Queues tab - the queue displays "0" (zero) > Number of consumers. > > Run the TP and stop it in few seconds: > > 1) Jmeter is not stopping - "Shutting does all test treads. Please be patient" > message is staying forever; JMeter cannot "shutdown" unless it receives a message because you set timeout to 0 (means no timeout) so JMeter is waiting on receive until it receives a message(I don't see any solution to this unless interrupt is fixed in AMQ so stop will work) My test with Stop works. > 2) Check AMQ web-console - there are all initiated threads have not been > closed > its connections; Yes duplicate of bug 51997 > 3) stramge error for "JMS Subscriber - 001" - Response message: > javax.naming.NamingException: Something already bound at Elite_To_MorphoTrak; > This issue is mentionned by many AMQ client and not reproductible with OpenJMS. It is related to ReadOnlyContext and LazyCreateContext in AMQ, maybe you should check AMQ issues. I think it's a concurrency issue in AMQ JNDI layer. Maybe you should submit an issue to AMQ. Test with OpenJMS is OK. > ER: > 1) Jmeter stops successfully; > 2) AMQ displays "0" consumers against the queue; > 3) error for "JMS Subscriber - 001" has to be "0 message(s) received > successfully"; -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
