Comments on: Restricting the number of JMS / MQ connections made by the OSB http://blog.xebia.com/2009/12/02/restricting-the-number-of-jms-mq-connections-made-by-the-osb/ Software development done right! Wed, 08 Feb 2012 14:41:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nikhil http://blog.xebia.com/2009/12/02/restricting-the-number-of-jms-mq-connections-made-by-the-osb/#comment-113764 Nikhil Thu, 24 Nov 2011 04:13:39 +0000 http://blog.xebia.com/?p=3781#comment-113764 Hi, We have 2 clustered weblogic servers (3 managed servers in each cluster and 1 jms server per managed server). The PS on 1st cluster is reading from a JMS queue on 2nd cluster. I noticed that the number of threads i.e consumers seen on the JMS queue was 32 on each JMS server in the 2nd cluster (this should be usually 16). When i create a workmanager in 1st cluster and give thread count as 2, the expected result is that each jms server should show 2 as consumer count i.e 6 threads for 3 managed servers but instead i see 4 as consumer count on each server i.e 12 threads for 3 managed servers. Is this a known issue? Regards, Nikhil Hi,

We have 2 clustered weblogic servers (3 managed servers in each cluster and 1 jms server per managed server). The PS on 1st cluster is reading from a JMS queue on 2nd cluster. I noticed that the number of threads i.e consumers seen on the JMS queue was 32 on each JMS server in the 2nd cluster (this should be usually 16). When i create a workmanager in 1st cluster and give thread count as 2, the expected result is that each jms server should show 2 as consumer count i.e 6 threads for 3 managed servers but instead i see 4 as consumer count on each server i.e 12 threads for 3 managed servers. Is this a known issue?

Regards,
Nikhil

]]> By: Tjeerd Kaastra http://blog.xebia.com/2009/12/02/restricting-the-number-of-jms-mq-connections-made-by-the-osb/#comment-100127 Tjeerd Kaastra Thu, 03 Feb 2011 09:27:31 +0000 http://blog.xebia.com/?p=3781#comment-100127 Hi Ernie, Well, actually the service bus by default uses simultaneous processing. These workmanagers work per node so if your cluster uses two nodes, both of them actually use at least one thread to read the queue. And hence there is a fair chance that you will have two messages processed simultaneous. I guess I do not have an out-of-the-box solution to this. WebLogic JMS has the unit-of-work settings to achieve this but I am not sure if you can use the same solution with MQ (over JMS). Best regards, Tjeerd Hi Ernie,

Well, actually the service bus by default uses simultaneous processing. These workmanagers work per node so if your cluster uses two nodes, both of them actually use at least one thread to read the queue. And hence there is a fair chance that you will have two messages processed simultaneous.
I guess I do not have an out-of-the-box solution to this. WebLogic JMS has the unit-of-work settings to achieve this but I am not sure if you can use the same solution with MQ (over JMS).

Best regards,

Tjeerd

]]> By: Ernie Mcginty http://blog.xebia.com/2009/12/02/restricting-the-number-of-jms-mq-connections-made-by-the-osb/#comment-100027 Ernie Mcginty Mon, 31 Jan 2011 18:48:25 +0000 http://blog.xebia.com/?p=3781#comment-100027 Hi, I have a requirement to use an OSB MQ proxy service to pick messages off of a queue one at a time sequentially. How do these settings work in a clustered environment, there is nothing that indicates an active passive configuration like the MQ JCA adapter has with it's singleton property. How do I know that for 2 OSB servers each isn't taking request off of the queue concurrently? Hi, I have a requirement to use an OSB MQ proxy service to pick messages off of a queue one at a time sequentially. How do these settings work in a clustered environment, there is nothing that indicates an active passive configuration like the MQ JCA adapter has with it’s singleton property. How do I know that for 2 OSB servers each isn’t taking request off of the queue concurrently?

]]> By: Tjeerd Kaastra http://blog.xebia.com/2009/12/02/restricting-the-number-of-jms-mq-connections-made-by-the-osb/#comment-96633 Tjeerd Kaastra Mon, 27 Sep 2010 08:58:40 +0000 http://blog.xebia.com/?p=3781#comment-96633 Hi Krishna, If I understand this correctly, you are trying to use the MaxThreadsConstraint to restrict the number of messages that may be handled simultaneous. But to achieve this, you should use Throttling. The MaxThreadsConstraint only limits the number of threads which can be used for example to limit the number of listening threads on a queue. You can check the number of open connections from your OSB server to your JMS server to see that this setting works (e.g. by using netstat or lsof on unix to see the established tcp connections). Throttling on the other hand limits the number of messages that can be processed by the business service. So if your business service cannot cope with too many concurrent messages, you can edit your business service and go to the Operational Settings tab. There you can set the Throttling State to enabled and enter the number of simultaneous messages in the field Maximum Concurrency. You could also set the max no. of messages to be held back in the Throttling Queue setting or the max wait time in Message Expiration but beware that these settings might remove messages if the load gets high! I hope that this explains things better. Regards, Tjeerd Hi Krishna,

If I understand this correctly, you are trying to use the MaxThreadsConstraint to restrict the number of messages that may be handled simultaneous. But to achieve this, you should use Throttling. The MaxThreadsConstraint only limits the number of threads which can be used for example to limit the number of listening threads on a queue. You can check the number of open connections from your OSB server to your JMS server to see that this setting works (e.g. by using netstat or lsof on unix to see the established tcp connections).

Throttling on the other hand limits the number of messages that can be processed by the business service. So if your business service cannot cope with too many concurrent messages, you can edit your business service and go to the Operational Settings tab. There you can set the Throttling State to enabled and enter the number of simultaneous messages in the field Maximum Concurrency.
You could also set the max no. of messages to be held back in the Throttling Queue setting or the max wait time in Message Expiration but beware that these settings might remove messages if the load gets high!

I hope that this explains things better. Regards, Tjeerd

]]> By: krishna http://blog.xebia.com/2009/12/02/restricting-the-number-of-jms-mq-connections-made-by-the-osb/#comment-96601 krishna Fri, 24 Sep 2010 19:24:59 +0000 http://blog.xebia.com/?p=3781#comment-96601 Hi, I tried using this approach for setting MaxThreadsConstraint for a proxy service in OSB 11g. But i dont think its actually working. When i give concurrent requests at a time. It simply pass overs everything with out any delay. I am not able to confirm that the DIspatch policy Max Trheads constraint is working. Could you please help. Thanks Hi,

I tried using this approach for setting MaxThreadsConstraint for a proxy service in OSB 11g. But i dont think its actually working. When i give concurrent requests at a time. It simply pass overs everything with out any delay. I am not able to confirm that the DIspatch policy Max Trheads constraint is working. Could you please help. Thanks

]]>