ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Additional instances for JavaCompute Node

Post new topic  Reply to topic
 Additional instances for JavaCompute Node « View previous topic :: View next topic » 
Author Message
upcominggeek
PostPosted: Mon Apr 25, 2011 7:57 pm    Post subject: Additional instances for JavaCompute Node Reply with quote

Apprentice

Joined: 21 Aug 2006
Posts: 35
Location: Boston, US

Well,
First of all, I apologize for starting a new thread on an old post. But since the broker version has changed from the time of the original post, thought it made more sense to start a new thread.
My question is pretty much the same as that is discussed in this thread. Is Java Compute Node going to work on a single thread in one execution group as mentioned in infocenter (http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ac20805_.htm?resultof=%22%6a%61%76%61%22%20%22%63%6f%6d%70%75%74%65%22%20%22%63%6f%6d%70%75%74%22%20%22%6e%6f%64%65%22%20)?
The below thread says it is not. I am a bit confused as to which one is correct.
http://www.mqseries.net/phpBB/viewtopic.php?p=219326&sid=c1a6423d9fc51e207b4bdcd85d9bc05b
My project expects very high throughput and I need to integrate with 2 EJBs from MB. If infocenter is true, then I am wondering if we should move towards an MDB based integration to support parallel processing?
Or will making java calls as external functions help?
Any help is appreciated.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Apr 26, 2011 1:12 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Okay, so you need to be clear on a couple of things.

One, the class that you create for a JavaCompute node is just that - a class. What the mqseries.net thread you point to mentions that at no point will broker ever instantiate more than one instance of that class - that is, it will create no more than one Java object of that class type.

This has nothing to do with how many threads running in the jvm can call methods on that class, and whether there is any coordination on the calling of those methods from those threads by the JVM.

So when you deploy a flow that has a JavaCompute node and assign multiple instances, then Broker will create one Java object, and each instance of the message flow will call the evaluate() method on that object at the appropriate time.

The infocenter link you provide has a pointer to "threading considerations for user-defined extensions". If you have concerns over whether or not your evaluate method can step on it's own toes if two threads call it at once, you should review that link.
Back to top
View user's profile Send private message
upcominggeek
PostPosted: Tue Apr 26, 2011 10:49 am    Post subject: Reply with quote

Apprentice

Joined: 21 Aug 2006
Posts: 35
Location: Boston, US

Some of my java basics were brought into question as part of this confusion. But I think I am clear now.
Thanks, Jeff for the clarification. It definitely helped to put my understanding in the right perspective.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Additional instances for JavaCompute Node
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.