as3-stomp - Project Hosting on Google Code

Older Oct 11, 2009 issue 12 (Patch to expose securityexception events + connection error ...) commented on by mark81 - Thanks! Thanks! Oct 11, 2009 issue 12 (Patch to expose securityexception events + connection error ...) commented on by dwischusen - patch approved and committed. thank you. patch approved and committed. thank you. Oct 11, 2009 issue 12 (Patch to expose securityexception events + connection error ...) changed by dwischusen - This issue was closed by revision r17. Status: Fixed This issue was closed by revision r17. Status: Fixed Oct 11, 2009 r17 (Added patch from mark81 to "...expose securityexception even...) committed by dwischusen - Added patch from mark81 to "...expose securityexception events + connection error reporting + different reconnect strategy" fixes issue 12 Added patch from mark81 to "...expose securityexception events + connection error reporting + different reconnect strategy" fixes issue 12 Oct 11, 2009 r16 ([No log message]) committed by dwischusen - [No log message] [No log message] Oct 09, 2009 issue 12 (Patch to expose securityexception events + connection error ...) Status changed by dwischusen - Thank you Mark. I haven't had a chance to take a look in detail yet, but from your description this sounds like I change I have been meaning to make. So you've saved me some work. I'll check it out this weekend, run it through some tests, and then most likely go ahead and integrate it. Thanks again, Derek Status: Accepted Thank you Mark. I haven't had a chance to take a look in detail yet, but from your description this sounds like I change I have been meaning to make. So you've saved me some work. I'll check it out this weekend, run it through some tests, and then most likely go ahead and integrate it. Thanks again, Derek Status: Accepted Oct 09, 2009 issue 12 (Patch to expose securityexception events + connection error ...) commented on by mark81 - Oh btw, this also fixes some instances of those invalid socket operation errors that can possibly occur during reconnection (see issue 2 ). Normally those should only happen if one if Stomp.transmit is called when the socket is not connected. Oh btw, this also fixes some instances of those invalid socket operation errors that can possibly occur during reconnection (see issue 2 ). Normally those should only happen if one if Stomp.transmit is called when the socket is not connected. Oct 09, 2009 issue 12 (Patch to expose securityexception events + connection error ...) reported by mark81 - What steps will reproduce the problem? 1. Setup ActiveMQ. 2. Serve appropriate cross-domain file 3. Stop ActiveMQ, but leave server up with cross-domain file. 4. Attempt to connect. You'll get a SecurityException about 20 seconds after you get an IOErrorEvent (and screws up the reconnecting). What is the expected output? What do you see instead? No SecurityException should be reported later, only the initial IO exception. What version of the product are you using? On what operating system? Please provide any additional information below. Attached is a patch file that fixes this issue, and exposes securityexception events from Stomp.as. Also added: - ReconnectFailedEvent - thrown when a reconnection attempt has failed (rather than throw an exception in the event thread where it cannot be caught). - Changed the reconnect strategy to try once every minute, indefinitely. (ReconnectFailedEvents are thrown on reconnect failures, allowing the app to track progress if it wants to). - Close socket events now work with Flex 4. I can't seem to email you through Google Code (or rather, I should say, I can't figure out how to do that). If you have questions for me, I'd love to work towards getting this patch integrated, and I'll check the comments here for responses. Thanks much for a great library! What steps will reproduce the problem? 1. Setup ActiveMQ. 2. Serve appropriate cross-domain file 3. Stop ActiveMQ, but leave server up with cross-domain file. 4. Attempt to connect. You'll get a SecurityException about 20 seconds after you get an IOErrorEvent (and screws up the reconnecting). What is the expected output? What do you see instead? No SecurityException should be reported later, only the initial IO exception. What version of the product are you using? On what operating system? Please provide any additional information below. Attached is a patch file that fixes this issue, and exposes securityexception events from Stomp.as. Also added: - ReconnectFailedEvent - thrown when a reconnection attempt has failed (rather than throw an exception in the event thread where it cannot be caught). - Changed the reconnect strategy to try once every minute, indefinitely. (ReconnectFailedEvents are thrown on reconnect failures, allowing the app to track progress if it wants to). - Close socket events now work with Flex 4. I can't seem to email you through Google Code (or rather, I should say, I can't figure out how to do that). If you have questions for me, I'd love to work towards getting this patch integrated, and I'll check the comments here for responses. Thanks much for a great library! Jun 05, 2009 issue 11 (re-connect doesn't not work if server still think as3-stomp ...) changed by dwischusen - Status: Accepted Owner: dwischusen Status: Accepted Owner: dwischusen May 27, 2009 issue 11 (re-connect doesn't not work if server still think as3-stomp ...) reported by kuokon - What steps will reproduce the problem? 1. make the reconnect time larger (from default 5 to 30 times) 2. connect stomp 3. un-plug cable, wait for 3 to 4 seconds, reconnect What is the expected output? What do you see instead? expect: reconnect successfully. actual: stomp recieved 'xxx-client-xxxxx already connected from /XXXX What version of the product are you using? On what operating system? - v0.41 Please provide any additional information below. What steps will reproduce the problem? 1. make the reconnect time larger (from default 5 to 30 times) 2. connect stomp 3. un-plug cable, wait for 3 to 4 seconds, reconnect What is the expected output? What do you see instead? expect: reconnect successfully. actual: stomp recieved 'xxx-client-xxxxx already connected from /XXXX What version of the product are you using? On what operating system? - v0.41 Please provide any additional information below. Apr 11, 2009 r15 (fixed minor error introduced in last patch.) committed by dwischusen - fixed minor error introduced in last patch. fixed minor error introduced in last patch. Apr 11, 2009 r14 (fixes performance issues that occur when receiving messages ...) committed by dwischusen - fixes performance issues that occur when receiving messages that do not contain a content-length header. Contributed by Peter Mulreid. fixes performance issues that occur when receiving messages that do not contain a content-length header. Contributed by Peter Mulreid. Oct 26, 2008 issue 7 (add ssl/tsl support with As3Crypto com.hurlant.crypto.tls.TL...) Status changed by dwischusen - Status: Fixed Status: Fixed Oct 26, 2008 issue 7 (add ssl/tsl support with As3Crypto com.hurlant.crypto.tls.TL...) commented on by dwischusen - My solution for this was to add parameter to the connect method so that you can pass in any type of Socket that you want. For example, var socket: Socket = new TLSSocket(); stomp.connect("localhost",61613, ch, socket); Please note that this only works with the latest version of as3crypto source since earlier versions of TLSSocket did not inherit from Socket. My solution for this was to add parameter to the connect method so that you can pass in any type of Socket that you want. For example, var socket: Socket = new TLSSocket(); stomp.connect("localhost",61613, ch, socket); Please note that this only works with the latest version of as3crypto source since earlier versions of TLSSocket did not inherit from Socket. Oct 26, 2008 issue 8 (Inactive Consumer of AS3 Stomp Client) Status changed by dwischusen - I can't reproduce this issue. In the latest version of the Stomp client you can now listen for the socket close and socket error events. So if the auto reconnect fails then you can reconnect it externally. Status: WontFix I can't reproduce this issue. In the latest version of the Stomp client you can now listen for the socket close and socket error events. So if the auto reconnect fails then you can reconnect it externally. Status: WontFix Oct 26, 2008 issue 9 (Compiling from Flash CS3) Status changed by dwischusen - removed. Status: Fixed removed. Status: Fixed Oct 26, 2008 issue 10 (incomplete broadcast support for topic and fanout exchanges ...) Status changed by dwischusen - Thank you for the code. I've rolled it into the latest release. Status: Fixed Thank you for the code. I've rolled it into the latest release. Status: Fixed Oct 26, 2008 r13 (Added exchange and routing_key headers to SubscribeHeaders t...) committed by dwischusen - Added exchange and routing_key headers to SubscribeHeaders to better support AMQP brokers (such as RabbitMQ). Fixes issue# 10 Added an optional parameter to the connect method in Stomp class for passing in a Socket. This makes it possible to pass in custom socket implementations, such as the TLSSocket form as3crypo (see http://code.google.com/p/as3crypto). Fixes issue#7 Previously removed all references to any classes in the Flex framework. This makes it possible to use the Stomp lib with Flash projects Fixes #9 Added exchange and routing_key headers to SubscribeHeaders to better support AMQP brokers (such as RabbitMQ). Fixes issue# 10 Added an optional parameter to the connect method in Stomp class for passing in a Socket. This makes it possible to pass in custom socket implementations, such as the TLSSocket form as3crypo (see http://code.google.com/p/as3crypto). Fixes issue#7 Previously removed all references to any classes in the Flex framework. This makes it possible to use the Stomp lib with Flash projects Fixes #9 Sep 22, 2008 issue 10 (incomplete broadcast support for topic and fanout exchanges ...) reported by joes.mailing.lists - I'm using the latest svn revision of the as3 stomp code. The SubscribeHeaders object does not contain an 'exchange' header, or a 'routing_key' header, both of which are required in order to subscribe to fanout or topic exchanges in rabbitmq. Without the ability to specify these headers, it is not possible to broadcast messages. I was able to fix this functionality very quickly, by adding the required headers to the SubscribeHeaders.as file, and recompiling the code. After making the necessary adjustments to the Sender and Receiver clients I was able to then successfully send messages via the default amq.topic exchange in rabbitmq. Although there is a bit of AMQP bleeding through here, this is a very trivial addition, and would provide some nice added functionality to future version of this client library. I have attached my modified versions of SubscribeHeaders.as where I have added the additional headers. I'm using the latest svn revision of the as3 stomp code. The SubscribeHeaders object does not contain an 'exchange' header, or a 'routing_key' header, both of which are required in order to subscribe to fanout or topic exchanges in rabbitmq. Without the ability to specify these headers, it is not possible to broadcast messages. I was able to fix this functionality very quickly, by adding the required headers to the SubscribeHeaders.as file, and recompiling the code. After making the necessary adjustments to the Sender and Receiver clients I was able to then successfully send messages via the default amq.topic exchange in rabbitmq. Although there is a bit of AMQP bleeding through here, this is a very trivial addition, and would provide some nice added functionality to future version of this client library. I have attached my modified versions of SubscribeHeaders.as where I have added the additional headers. Aug 23, 2008 r12 (removed reference to mx.utils.ObjectUtils, which reduced the...) committed by dwischusen - removed reference to mx.utils.ObjectUtils, which reduced the size of the lib by about 20k. Fixes #9 removed reference to mx.utils.ObjectUtils, which reduced the size of the lib by about 20k. Fixes #9 Aug 23, 2008 issue 9 (Compiling from Flash CS3) Status changed by dwischusen - I'll remove the reference to mx.utils.ObjectUtils. It's really not needed anyway and it's adding a lot of size to this lib. Status: Accepted I'll remove the reference to mx.utils.ObjectUtils. It's really not needed anyway and it's adding a lot of size to this lib. Status: Accepted Aug 22, 2008 issue 9 (Compiling from Flash CS3) reported by f.siafarikas - What steps will reproduce the problem? 1. Use of the Flash CS3 IDE instead of Flex Probable Solution: Not using the mx.utils.ObjectUtil class, since it isn't available in flash. What steps will reproduce the problem? 1. Use of the Flash CS3 IDE instead of Flex Probable Solution: Not using the mx.utils.ObjectUtil class, since it isn't available in flash. Aug 19, 2008 issue 8 (Inactive Consumer of AS3 Stomp Client) reported by powerteam001 - What steps will reproduce the problem? 1. Create Topic consumer by AS3 Stomp Client. 2. ActiveMQ doesn't send any message in at least 10 minutes. 3. AS3 Stomp Client can not receive any message any more. 4. Check ActiveMQ console and found the number of Topic's consumer decreased 1 What is the expected output? What do you see instead? AS3 Stomp client should keep alive if don't call its close or other similar close function. What version of the product are you using? On what operating system? V0.6 and Windows XP SP2 What steps will reproduce the problem? 1. Create Topic consumer by AS3 Stomp Client. 2. ActiveMQ doesn't send any message in at least 10 minutes. 3. AS3 Stomp Client can not receive any message any more. 4. Check ActiveMQ console and found the number of Topic's consumer decreased 1 What is the expected output? What do you see instead? AS3 Stomp client should keep alive if don't call its close or other similar close function. What version of the product are you using? On what operating system? V0.6 and Windows XP SP2 Jul 25, 2008 issue 7 (add ssl/tsl support with As3Crypto com.hurlant.crypto.tls.TL...) Status changed by dwischusen - Good idea. Status: Accepted Good idea. Status: Accepted Jul 24, 2008 issue 7 (add ssl/tsl support with As3Crypto com.hurlant.crypto.tls.TL...) reported by t.mcgee.lazyeye - It looks like as3Cryto is used in as3amqp for ssl/tsl support. Could it be used in this project too? I would like to use as3-stomp to talk to ActiveMQ in a project but at some point I know I'll need to start using ssl. It looks like as3Cryto is used in as3amqp for ssl/tsl support. Could it be used in this project too? I would like to use as3-stomp to talk to ActiveMQ in a project but at some point I know I'll need to start using ssl.

issue 12 (Patch to expose securityexception events + connection error ...) reported by mark81 - What steps will reproduce the problem? 1. Setup ActiveMQ. 2. Serve appropriate cross-domain file 3. Stop ActiveMQ, but leave server up with cross-domain file. 4. Attempt to connect. You'll get a SecurityException about 20 seconds after you get an IOErrorEvent (and screws up the reconnecting). What is the expected output? What do you see instead? No SecurityException should be reported later, only the initial IO exception. What version of the product are you using? On what operating system? Please provide any additional information below. Attached is a patch file that fixes this issue, and exposes securityexception events from Stomp.as. Also added: - ReconnectFailedEvent - thrown when a reconnection attempt has failed (rather than throw an exception in the event thread where it cannot be caught). - Changed the reconnect strategy to try once every minute, indefinitely. (ReconnectFailedEvents are thrown on reconnect failures, allowing the app to track progress if it wants to). - Close socket events now work with Flex 4. I can't seem to email you through Google Code (or rather, I should say, I can't figure out how to do that). If you have questions for me, I'd love to work towards getting this patch integrated, and I'll check the comments here for responses. Thanks much for a great library!

What steps will reproduce the problem? 1. Setup ActiveMQ. 2. Serve appropriate cross-domain file 3. Stop ActiveMQ, but leave server up with cross-domain file. 4. Attempt to connect. You'll get a SecurityException about 20 seconds after you get an IOErrorEvent (and screws up the reconnecting). What is the expected output? What do you see instead? No SecurityException should be reported later, only the initial IO exception. What version of the product are you using? On what operating system? Please provide any additional information below. Attached is a patch file that fixes this issue, and exposes securityexception events from Stomp.as. Also added: - ReconnectFailedEvent - thrown when a reconnection attempt has failed (rather than throw an exception in the event thread where it cannot be caught). - Changed the reconnect strategy to try once every minute, indefinitely. (ReconnectFailedEvents are thrown on reconnect failures, allowing the app to track progress if it wants to). - Close socket events now work with Flex 4. I can't seem to email you through Google Code (or rather, I should say, I can't figure out how to do that). If you have questions for me, I'd love to work towards getting this patch integrated, and I'll check the comments here for responses. Thanks much for a great library!

Older