I might be due to the fact the services running in IIS that a use non-http transport protocols will need to activated "woken up" when a message arrives for them.
You could implement an Activator and integrated it into WAS. Or implement a windows service that peeks the queue and then wakes the appropriate service in IIS by doing a HTTP request for its WSLD. Or you could install Windows Server AppFabric and enable Autostart which will make sure your service is always awake, although i have only used this for WCF services but i presume it should do the same for ASP services. I would try option three, and if that doesn't work try the secound option and final if that doesn't work try the last option, example of how to do it is included with the WCF-WF exacmples. Also Appfabric has some neat features. -- View this message in context: http://activemq.2283324.n4.nabble.com/how-to-achieve-OnMessage-event-in-asp-net-app-to-automatically-fetch-receives-tp4671879p4671958.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
