The Oracle Advanced Queue
TomatoMeter: **********
Sounds cool right? Advaaaaaaannced Queue. Alright, let's cut to the chase. Being used to the open source tools, one can develop a high-level of tolerance on poorly documented systems, that's forgiveable because all those involved in the project might be paid little or none at all. But what if some very exorbitantly priced software does not seem to work according to specifications and examples the way they suppose to be? To people who has been programming with JMS the drill is the same no matter what vendor is providing the MQ. It usually goes this way:
- Obtain ConnectionFactory usually from JNDI
- Obtain Connection from ConnectionFactory
- Obtain Topic or Queue from JNDI
- Obtain Session from Connection
- Create consumer/listener or producer objects from Session.
- Send or receive/listen a message.
But Oracle Advaaaaaaanced Queue has broken all that. I think it's advanced but not necessarily asynchronous hahaha. If a MessageListener has been registered to a Receiver or Session object, the only time it can receive message is when the JMS client is run the first time then it will go to Deaf Mode so new messages are mysteriously ignored. So what do Oracle zealots will tell me? Read the Fucking Manual? Fuck them! I don't think we bought this crap to do that or to register at Oracle Technoshit Network and mingle with the DBAs. So what's a workaround? One, do a recursive receive() calls, pretend that you are in a listening mode, near real time. But of course it's quite stupid.
Sounds cool right? Advaaaaaaannced Queue. Alright, let's cut to the chase. Being used to the open source tools, one can develop a high-level of tolerance on poorly documented systems, that's forgiveable because all those involved in the project might be paid little or none at all. But what if some very exorbitantly priced software does not seem to work according to specifications and examples the way they suppose to be? To people who has been programming with JMS the drill is the same no matter what vendor is providing the MQ. It usually goes this way:
- Obtain ConnectionFactory usually from JNDI
- Obtain Connection from ConnectionFactory
- Obtain Topic or Queue from JNDI
- Obtain Session from Connection
- Create consumer/listener or producer objects from Session.
- Send or receive/listen a message.
But Oracle Advaaaaaaanced Queue has broken all that. I think it's advanced but not necessarily asynchronous hahaha. If a MessageListener has been registered to a Receiver or Session object, the only time it can receive message is when the JMS client is run the first time then it will go to Deaf Mode so new messages are mysteriously ignored. So what do Oracle zealots will tell me? Read the Fucking Manual? Fuck them! I don't think we bought this crap to do that or to register at Oracle Technoshit Network and mingle with the DBAs. So what's a workaround? One, do a recursive receive() calls, pretend that you are in a listening mode, near real time. But of course it's quite stupid.
Comments
not so true. please open your mind. We just have a different mind setting than you guys.
I'm just searching the net for infos and found this blog(lala) just because you mention some of the jms servers that am working on. Are you really a developer? =P
You're searching in the net for stuffs and things and stumbled because you are in total deep shit and in a tight ass deadline because you are going to read this anyway :P
I am not a developer, I am a superstar, I am an American Idol. Dig that!
And another stupid thing from you, I didn't mention some jms servers, only Oracle AQ.